Recreate automated AX processes in Robots

Important

Only proceed with recreating automated processes in Robots if you have completed all previous stages of the migration. For more information, see Performing the migration: our recommended approach.

Once you have migrated or recreated your organization's scripts and any data, you are ready to recreate automated AX processes in Robots. For each automated process you create a task inside a robot. You use the task to select which scripts should run, specify any input parameters for the scripts, and create a schedule.

Create a robot task for each automated process

For each automated process, create a task in development mode first so that you can test the process to ensure it is working correctly.

For detailed information, see Creating a robot task to run a script.

From the Launchpad home page (www.highbond.com), under Audit & Analytics, select the Robots app.
You need to sign in to Diligent One if you are not already signed in.
From the dashboard in Robots, select ACL Robots.
Navigate to the robot that you want to contain the task, and select the robot to open it.
In the upper-right corner of the robot, click Development to switch to development mode.
The production mode header has a light background and the development mode header has a dark background.
On the Tasks tab, click Create task.
The Task Designer opens.
Type a name for the task that identifies the automated process, and click Save.
Progress through the Task Designer to configure the task settings:
1. Select the scripts to run and enter any required parameter values.
  Replicate the parameter values from the AX process unless for some reason you are changing the values.
2. Optional. Schedule the task.
  You are going to run the task ad hoc, so you can skip creating a schedule. Or you can create a schedule if you also want to test the scheduling capability.
3. Optional. Select one or more recipients to receive an email notification if the task does not run for any reason.
Review the task configuration settings, and click Confirm and create task.
Result The task is created using the settings that you specified.

Test a task by running it ad hoc

Test each task in development mode and troubleshoot any problems that occur.

On the Tasks tab, select the task that you just created and click > Run now.
The task starts and you can monitor its progress and view results in either the Tasks tab or the Task runs tab.
In the Task runs tab, once the task completes, click the entry for the task.
The Task run details side panel opens and displays detailed information about the task run, including a list of any output tables and files generated by the //RESULT analytic tag.
Review any output results to confirm that the correct tables, logs, or files were generated.
For information about viewing the content of the output results, see Viewing the tables, files, and logs in an ACL robot.
In the Input/Output tab, review any output data tables to confirm that the correct tables were generated.
Tables generated by the //DATA analytic tag are listed in the Other tables section. For information about viewing the content of the data tables, see Viewing the tables, files, and logs in an ACL robot.
If a task fails, or if output tables or files are missing, the Basic troubleshooting steps might identify the problem.
If a task continues to fail after you attempt troubleshooting, contact Diligent Support for assistance.

Basic troubleshooting steps

Type of problem	Possible cause, or action to take
General	Check the Result status in the Task run details side panel. In some cases, a message appears explaining the reason for the task failure.
General	If a log file was output, click View to inspect the log. The log should include an entry, marked with a red X , that indicates why the analytic script failed.
Task input	If the task uses a linked table as input, confirm that the table is present in the Linked tables section in the Input/Output tab. For more information, see Sharing and linking data tables in ACL robots.
Task input	If the task uses a non-Analytics related file such as Excel as input, confirm that the file is present in the Files section in the Input/Output tab. For more information, see Managing working data stored in a robot.
Analytic header	In Analytics, check the analytic headers on all analytic scripts run by the task. Confirm that all required analytic tags, such as //RESULT , //DATA , and //FILE , are present and correctly formatted. For detailed information, see Analytic headers and tags.
Robots Agent service	On the Windows server where the Robots Agent is installed, check that the Robots Agent service is running. Start the service if it is stopped and re-run the task.

Activate a script version to production mode

Once a task is running correctly, activate the script version used by the task to production mode.

For detailed information, see Development mode and production mode in Robots.

In the Script versions tab, select the script version used by the task that you just tested.
In the Version details panel, click Activate.
Optional. Enter a comment in the version history to explain what you are activating.
Tip
Entering an informative comment when you activate a script version is a best practice that can be very helpful when reviewing automated analysis at a later date.
Click Activate versionNumber.
Result The script version is activated and becomes available in production mode. The Scripts tab in production mode lists the individual analytic scripts, and any auxiliary scripts, in the script version.

Create and schedule a robot task in production mode

The final step is to create and schedule a robot task in production mode.