Adding a requirement to the activity
Prerequisites
- Access to the Process (PM063) menu.
- Previously created and modeled process.
- User activity, system activity, or decision added to the process flowchart.
Introduction
Requirements are used to define attachments and documents that must be mandatorily presented or filled out during the execution of an activity in the process.
By configuring requirements, it is possible to increase the control, compliance, and traceability of the activities, ensuring that essential documents are properly associated with the process.
See how to add requirements to process activities:
Adding a requirement
1. On the activity/decision data screen, click on Configurations > Requirement.
2. The requirement addition screen will be displayed.
3. Click on the
button.

4. On the screen that will be opened, enter a name for the requirement.
5. In the Type field, select the requirement classification:
- Attachment: select this option so that the requirement to be filled out is an attachment of the activity.
- Document: select this option so that the requirement to be filled out is a document associated with the activity. This option will only be available if SoftExpert Document is part of the solutions acquired by your organization.
6. If the selected requirement type is Document, fill out the Category field by clicking on the
button to define the category in which this document will be created. If desired, check the following option:
- Require digital signature when executing: makes digital signature mandatory for the selected document when a defined activity of the process with a specific action is executed. Keep the option unchecked if it is not mandatory to digitally sign the document.
8. Once done, click on Save and exit.
Remember that, to enforce the completion of the requirements, it is necessary that the Requirement option be selected on the data screen of the action that will execute the activity/decision, in Rules > Mandatory to fill out action items. See how to check this option in the Configuring an action in the activity article.
Conclusion
Thus, the activity/decision requirements have been successfully configured!