Configure the advanced properties of an activity
- Select the activity.
- On the Properties bar, click Settings .
- On the Extended Properties page, click the Advanced tab.
Activation Probability for an activity; the average probability of an
execution path leading to a node becoming active.
To override the reset limit for automatic activity set in the system settings, click
Override Server Reset Limit and set the limit for resetting the automatic
If the reset attempts for the activity exceed the specified limit, the job suspends and an error message is added as a job note. By default, the Override Server Reset Limit is set to No and the limit set on the server is used. See "Auto Activity Reset Limit" under General System Settings.
To specify if the activity should be suspended when the timeout interval exceeds the expected duration, click
TimeOut Action (default: Retry. This means the activity is reset if the
timeout interval exceeds the expected duration).
If the target duration of an activity is set, this will be used as the timeout interval for an activity; otherwise, the value specified for the CoreWorkerActivityTimeoutIntervalInMinutes setting is used as the timeout interval for automatic activities. For capture activities, this value is set in the Transformation Server configuration file.The Timeout Action property is only available for automatic activities.
Optionally, to assign a suspend reason to an activity, consume the required variable or provide an inline value
(maximum 50 characters) in the
Suspend Reason box.
At runtime, when the job created on the automatic activity is suspended, the suspend reason associated with the activity is recorded against the job. If the suspend reason is not provided at the design time, the suspend reason defaults to the activity name.The Suspend Reason property is only available for automatic activities.
- Click Yes for Track Changes to allow the variable history of an activity to be recorded. You can see the variable value before and after the activity is executed.
Allocate to allow resources to be allocated manually. (Default: No)
Mobile Friendly. (Default: No)
A number of activities cannot progress through a phone device because they require significant quantities of data. Therefore it is imperative to indicate if an activity can be performed from a phone device to prevent the work queue from getting cluttered.The Mobile Friendly property is only available for ordinary activities.
To enable the activity to be
MFP Ready, select one of the following:
The MFP Ready property is only available for manual activities.
No: The activity cannot be completed on a Lexmark Multi-Functional Peripheral (MFP) device. (Default: No)
MFP Friendly: Enables the activity to be completed on a Lexmark MFP device and desktop.
MFP Only: Enables the activity to be completed only on a Lexmark MFP device.
MFP Only- No Password Required: Enables the MFP operators to take the activity on the MFP without specifying the password. This setting is available for HP, MFP Emulator, and Lexmark eSF devices.
After Scan Event box,
consume an event
that is raised after images are completely uploaded to the server so that the activity is completed and progressed to the next
The After Scan Event property is only available for scan activities.
- Use Help Text to add information about an activity as plain text or a URL to a web page.
Thread Pool to associate with the activity.
The Thread Pool list contains thread pools created in TotalAgility System Settings. For more information about creating thread pools, see Add a thread pool.
The thread pools are only available for capture and non-capture automatic activities.
By default, the Default thread pool is selected for the activity.
- To evaluate the predictive model score when the activity becomes available or is completed, click Yes for Available Evaluate Score and/or Completed Evaluate Score. For more information about predictive models, see Predictive model.
- To select the Fire Events to start when an activity becomes available or completed, consume the business event in the Available Fire Event and Completed Fire Event boxes.
To record achieved
Milestones when an activity becomes pending or completed, consume milestones
Milestone Available and
Milestone Completed boxes.
Calculate or record an achieved milestone date either upon one activity being completed or another activity starting. For example, in a software project, a set of activities must be completed or become pending before you can achieve the Code Complete milestone. Recording milestones depends on the configuration of process activities at design time.All nodes can have completed milestones except the decision and end nodes, which can only have pending milestones.
- For other advanced properties of an activity, see the following topics: