Requirement Status

The requirement statuses are configurable, except 99. A requirement can have one of four statuses. An explanation of few statuses are provided below.

• New: In the template when a requirement is first added, it is configured to be in "new" status .
• Outstanding: When the requirement is first created, it will have a RequiremenStatusCode value of 01, indicating it is outstanding. This status indicates that the requirement conditions have not been met.
• Canceled: If the requirement is canceled manually by the user by selecting the Cancel option from the drop-down on the Requirement screen, then the status will change to 05, indicating it is canceled. The requirement will no longer be considered by the DeliveryRequirements rule. At the same time, the RequirementCloseDate will be populated with the system date. Security controls are needed to cancel the requirement. The activity cannot be processed if the requirement is canceled. If the activity is reprocessed, then the same requirement will be created again, until the Requirement is satisfied.
• Completed: If a requirement is satisfied by manually entering the RequirementCloseDate on the Requirement screen, then the status will change to 03, indicating it is completed. The status change for each requirement will happen as data is entered but will not be committed until the user clicks Save or OK at the bottom of the screen. Clicking Cancel or Close will discard any changes. The RequirementCloseDate is not null.
• Expired: When a user right-clicks on a requirement listed on the Requirement screen, a window will appear with the options for Delete and Requirement Details. Select Delete to remove the record from the Requirement screen. The status will change to 99, indicating it is expired. The activity cannot be processed. If the activity is reprocessed, the same requirement will be created again, until the requirement is satisfied.