The Orchestrator Policies settings specify history settings for processes that run on the Orchestrator touchpoint. They also specify the default schedule and the default process in the library. You can configure separate policies for separate Orchestrators. The Delete Archive Instances button appears only on the Orchestrator host.
Specifies the policy for retaining old versions when you check in an edited automation object, where options include:
Defines the complete path to the default process for the selected Orchestrator. Default process handlers can provide default lane change rules and exception handling. This ability takes affect when these rules are not specified in the process itself. Click the button at the end of the field to open the Object Browser, select a process from the CA Process Automation library, and click OK. The Open button opens the default process.
Defines the number of days to save process instances that ran on a touchpoint or remote host. Keeping this value small avoids excessive growth of the library and consequent increase to the system response time.
If you configure one day, the process remains in the library for a minimum of 24 hours. After this time elapses, the process instances are archived.
Defines the minimum number of Failed instances of each object for every object type ( process, schedule, and SRF ) that are retained. To view the retained instances of an object, select the Current filter of the respective object from the Operations dashboard. The remaining objects are archived and to view the archived objects, select the Archived filter of the respective object from the Operations dashboard.
When the Failed instances exceed the specified value, the application archives the instances of each object for every object type, with the oldest timestamp of completion. However, the instances are archived only after they are retained for a minimum number of days as specified in the Minimum Days of Process History field.
For example:
If there are 3 objects (Process,Schedule, SRF) and assume each object has 3 object instances, then there are 9 object instances for the 3 objects. If you specify 1, then 1 object instance for each object type is retained and the remaining is archived.
Default value: 0. You can specify a positive integer value.
When 0 is specified, instances are archived but are not retained.
Defines the minimum number of Finished (completed and aborted) instances of each object for every object type ( process, schedule, and SRF ) that are retained. To view the retained instances of an object, select the Current filter of the respective object from the Operations dashboard.
The remaining objects are archived and to view the archived objects, select the Archived filter of the respective object from the Operations dashboard.
When the Finished (completed and aborted) instances exceed the specified value, the application archives the instances of each object for every object type, with the oldest timestamp of completion.
However, the instances are archived only after they are retained for a minimum number of days as specified in the Minimum Days of Process History field.
For example:
If there are 3 objects (Process,Schedule, SRF) and assume each object has 3 object instances, then there are 9 object instances for the 3 objects. If you specify 1, then 1 object instance for each object type is retained and the remaining is archived.
Default value: 0. You can specify a positive integer value.
When 0 is specified, instances are archived but are not retained.
Defines the maximum number of log messages that can be retained and displayed when the process instance is opened from a process watch.
Defines the minimum number of days to store an attachment in the CA Process Automation database before deleting it.
Users can use web services to trigger processes. A user can directly start a process or schedule a Start Request Form. Users can send files as attachments in the web services calls. When a web service call triggers a process, users can access the files in that process. A user can use the SOAP operator to forward an attachment to the outgoing web services call.
Defines the policy for purging archived data. Options include:
Values: The drop-down list includes the following values:
Defines the time of day at which to purge the archived instances that have been retained for the configured number of days. The time is specified in hh:mm format, where the range is 00.00 (12:00 AM) to 23.59 (11:59 PM).
Default: 00:01 (1 minute after midnight)
Defines the number of days to retain archived process instances. After an archived instance is kept for the configured number of days, it is purged at the specified time.
Default: 10
Specifies whether to authenticate users who attempt to access attachments outside of CA Process Automation.
Values:
Specifies whether to permit processes to use runtime security.
Values:
Note: If you select the Enable Runtime Security option here, you can select Run as Owner as the Runtime Security option for a process. In this case, use Set Owner to establish your ownership of each affected process object. For more information, see the online help or the Content Designer Guide.
The button lets you purge currently archived instances on demand. (This button appears on a selected Orchestrator host, not on a selected Orchestrator touchpoint.)
|
Copyright © 2014 CA.
All rights reserved.
|
|