What's the business logic behind Syncade DCA Change Requests (CR) not being auto-archived when they are promoted to Effective status?
That's a question that I recevied earlier today from our European office. When a CR is being routed for review and approval both the CR and the document(s) in the CR follow a similiar and connected status lifecycle until both reach the Effective status. As the CR moves through the lifecycle notifications are sent to the CR reviewers and CR approvers as they need to complete their assigned activity. In addition the CR Administrator is notified at each status change of the CR promotion lifecycle including when the CR (and documents) are promoted to the Effective status. Effective CRs are then autoarchived by the DCA - CCA Engine task. By setting the task timer to a shorter timer frequency the CRs will be autoarchived faster and no longer displayed in the Effective status for CR Admins.