Working With Lifecycle Status Reasons
An institution can modify (add or remove) the lifecycle status reason that applies to the default business process flow (BPF) that’s associated with the lifecycle entity.
Values of the lifecycle status reason are associated with BPF stages and with one of the values of the overall lifecycle status (Open, Won, or Lost). This association is critical to an applicant’s progress through lifecycle stages and determines the value that is set in the lifecycle status when it is closed. The following diagram illustrates how a lifecycle is closed based on its status:
Default Mappings of the Lifecycle Stages with Lifecycle Status Reasons
The following table lists the default mappings of the Lifecycle Stage with Lifecycle Status Reason values:
| BPF Stage | Lifecycle Status Reason |
|---|---|
| Prospect | Expressed Interest(Default) |
| Prospect | Not Eligible |
| Prospect | Not Interested |
| App in Progress | Incomplete Application |
| App in Progress | Cancelled |
| App Complete | Pending Review |
| App Complete | App Requirements Pending |
| App Complete | Ready for Decision |
| App Complete | Cancelled |
| Admit | Admitted with Conditions |
| Admit | Cancelled |
| Deposit | Deposit Pending |
| Deposit | Cancelled |
| Matriculate | Matriculate |
Default Mappings of the Lifecycle Status with Lifecycle Status Reasons
The following table lists the default mappings of the Lifecycle Status with values of the Lifecycle Status Reason:
| Lifecycle Overall Status | Lifecycle Status Reason |
|---|---|
| Lost | Not Eligible |
| Lost | Not Interested |
| Lost | Cancelled |
| Open | Incomplete Application |
| Open | Admitted with Conditions |
| Open | App Requirements Pending |
| Open | Deposit Pending |
| Open | Expressed Interest (Default) |
| Open | Pending Review |
| Open | Ready for Decision |
| Won | Matriculate |
Configuring a New Lifecycle Status Reason
The following steps summarize the mandatory tasks that an administrator must perform to implement a scenario where a new lifecycle status reason is added:
-
Edit the cmc_Lifecyclestatus field of the lifecycle entity and add the required value of the lifecycle status reason.
-
Map the value of the lifecycle status reason with the lifecycle status. To do so, double-click the statuscode field and associate its value (Open, Won, or Lost) with the new lifecycle status reason created in step 1. You will need to type the value in the Add List Value dialog.
-
Update the lifecycle workflow (Lifecycle – Close Lifecycle) with the new lifecycle status reason. Perform this step only if the new lifecycle status reason is mapped to the Won or Lost statuses.
-
In the Lifecycle BPF tab of the Default Configuration page, map the new lifecycle status reason with Lifecycle Stages. This mapping must align with your institution’s business process.
Best Practices
Ensure that you do not edit the default BPF that is shipped with Anthology Reach. You need to copy the default BPF and then make edits to the copied BPF.
Associating a Lifecycle Type With a New BPF
Anthology Reach includes capability to support the use of unique BPFs in different processes within an institution.
When a new BPF is created for the lifecycle entity, to enable its use, it must be mapped to a value of the Lifecycle Type field. This association happens in the Lifecycle BPF tab (the Lifecycle Types area) of the Default Configuration page.
At a user level, the Lifecycle Type field determines the BPF that will be used. If a user working with the default BPF sets a value in the Lifecycle Type field that is associated with a custom BPF, the default BPF will be replaced with the custom BPF. This will occur after the user saves the lifecycle record.
