Description
Creates a task in the database for a specific process based on the ProcessorID and TaskTypeID.
Properties
Analyst
- Description: Optional text for documentation purposes.
Common
-
Continue On Error: Continues the execution of the workflow even if an error occurs during the execution of the activity.
-
Delay Before: Delay time in milliseconds before the activity is executed. The default value is 250 milliseconds.
-
Delay After: Delay time in milliseconds after executing of the activity. The default value is 250 milliseconds.
-
Disable Log: Disables the logging functionality for this activity.
-
Disable Protocol: Disables the protocol functionality for this activity.
-
Exclude from Global Delay: Excludes this activity from the Global Delay functionality.
-
Timeout: Duration in milliseconds in which the activity tries to execute.
Input
- TaskType: The TaskTypeIDs are necessary to map the specific workflow in your AMPRO-File to your TaskType created in the RPA Manager (for example, often you'll have a MainScriptRunner_PRO and a MainScriptRunner_DCO in one project). TaskTypes are also consecutively numbered. ProcessorID and TaskTypeID can always be looked up in the System Tables of RPA Manager assuming they have already been created.
- ProcessorID: Connects the specific AMPRO-File you want to create a task for with the Processor you set up in the RPA Manager.
- InputData: Insert a DataTable with all the relevant data that you want to pass to the created task (see the example below to gain a better understanding)..
- Source:You can specify the source of the created task. That might be interesting if in your process, tasks can be created in multiple ways (for example, via a daily or hourly running DCO as well as event-based).
- Diversity: The diversity functions as the unique identifier for a task. Depending on the structure of your DCO, (a combination of) different variables can be used to make assert that each task is unique (for example, the MailID, an order number or an order number plus the current date).
- Hash Diversity: If this check box is checked, the diversity will be encrypted.
Input [Expert]
-
Execution Date: You can set
a future execution date if the task should not directly be executed by the next
available client. Please Note: Currently, the execution date will only be considered if the Task Status ID is set to Delayed.
- InputDataString: Use this property if you want to pass input data as a string.
Options
- Task Status ID: Set the Task Status for the newly created task (default: Pending).
- Redoable: Choose if the task is redoable.
- Check Diversity: If checked, a task will only be created if no task with this specific diversity is already present in the Database (except for Tasks with status Canceled).
Output
- Task Created: Boolean that Indicates whether task was created or not.
Example
Typically, you will create tasks in a loop as shown in the screenshot below. Input data is passed to the task by using a DataTable as an input parameter. Therefore, in a loop, you will first use the Add Table Row Activity to add one data row to your DataTable (for example, an order date, order number, and some additional information). After using the DataTable in the Create Task Activity, it is cleared using the Clear Table Activity. This is necessary so that the next task is generated with the correct data.
Tips and Tricks
- Make sure that you provide the correct ProcessorID and Task type ID of the process for which you want to create the tasks.
- Check if you have added a database connection to your project information. See the section on project information within the Hyland RPA Designer documentation for more information.
- You would like to know your created task ID? The diversity of the task you create should be unique. You can use ExecuteQuery Activity to search for a task with this diversity and get the ID of this task. Select TOP 1 TaskId from dbo.Task where Diversity = "YourUniqueDiversity"
Troubleshooting
- Exception: The argument 'nameOrConnectionString' cannot be null, empty or contain only white space.The database connection is missing and you have to add a connection to your project or supply the corresponding connection string to the database.
- Exception: An unexpected error occurred getting the priority for the task! You might want to check your TaskType Prio Column: Check if your connection string is correct. This error appears if the connection to the database could not be established.