The Deployment Status of a Business Task reflects where the underlying Transports are in the workflow process. Each control point within a path can be configured with a Business Task Deployment status. Whenever a Business Task, or any of the Transports attached to it are changed or move along a transport path, the Business Task Deployment status is updated. The Deployment Status assigned to each control point in a transport path is configured as the target is associated to a Path during path configuration.
A Deployment Status can be configured for each control point enabled (Inbox, Test Queue and Outbox). A sequence number allocated to each Deployment Status helps indicate the statuses nearer the start of the workflow (lower numbers) and the statuses relating to control points near the end of the workflow (higher numbers). The numbers themselves do not specifically matter (ie ActiveControl will not handle 1,2,3,4,5 any differently to 10,20,30,40,50).
When ActiveControl calculates the Deployment status of a Task, it takes into account all of the Transport Forms assigned to the Task plus the Deployment Status Calculation configuration. If transports are in several control points, ActiveControl will use the status with either the lowest or highest sequence number depending on this configuration option. If all transports assigned to the Business Task are finished in all paths, ActiveControl will set the system Deployment Status as ‘Deployment Complete’.
Configuration
Deployment Status’ are created and maintained via the Statuses app tile on the Administration screen.
Figure: Deployment Status configuration screen.
Post your comment on this topic.