(Note: This is one of the objects related to Application Requirements and Checklist. For a use case and example, see here.)
Introduced in v3.11, a Requirement represents the required actions that users need to perform for a process.
For example, an applicant is required to upload his academic transcript during the Program Application process.
Multiple Requirements can be grouped under a Requirement Set.
These will be created on the target object when a criteria field returns an expected value, to trigger the cloning from templates.
See use case here.
|The name of this record.
|The parent Requirement Set that this Requirement belongs under.
|Copied over from the code in the Requirement Template (a unique code for each individual).
The due date that this Requirement needs to be completed.
Unlike the Due Days in the Requirement Template, which starts after a Requirement is submitted, the Due Date in the Requirement can be set to a specific date.
As of v3.12, this is now calculated by the REQ_SetDates_TDTM.
|Rich text field for the description or notes (if any).
|Checkbox denoting if this Requirement has been submitted (user has performed the required action).
|The date this Requirement is submitted (user has performed the required action).
Status of admin or faculty's review for this Requirement:
|The date this Requirement has been reviewed (finalized).
|The Requirement Template this Requirement is copied from.