Eagle Performance allows you to maintain a status along with performance data. You can assign performance data a status of Preliminary or Final, such that preliminary data can be recalculated, while final data is locked down and cannot be recalculated. In addition to using the default Preliminary and Final statuses, your organization can use the Commit Journal to track additional performance statuses that occur after Preliminary and before Final. For example, you can create a status named Reviewed that occurs after Preliminary and prior to Final.
You can create up to nine custom, or user-defined, performance statuses that Eagle Performance treats as it does preliminary statuses. That is, Eagle Performance can recalculate any performance records assigned a custom performance status.
When adding custom performance statuses, create a code value with a short description of the number 1 to 9 and a corresponding long description that describes the status. Add the codes with short descriptions that indicate the workflow order in which you process the statuses. For example, if you add statuses 1 (Under Review), 2 (Reviewed), and 3 (Waiting for Marketing Approval), Eagle Performance assumes you use a workflow order of:
...