Configuring a validity
 |
 |
 |
 |
 |
Prerequisite
- Access to the Configuration > Validity menu.
Introduction
Validity configuration is an essential step, as it allows for setting an expiration date for objects and selecting the users who will be notified when this period is over.
See the example below to understand how to perform this configuration.
Configuring a validity record
1. Access the Configuration > Validity menu.
2. Click on the 
toolbar button.
3. Enter an ID # and a name for the validity.
4. In the Default time section, specify how the object will be considered valid:
| Validity |
Enter the number of days, months, or years during which the objects will be valid. The default time is counted from the expiration date of the object; thus, when this time is over, an object due date task will be generated for the responsible parties in order for them to revalidate it. |
|---|---|
| Fixed | Select this option so that, during the revalidation of the object, the Validity field is filled in by the system with the default time and cannot be edited. |
| Variable | Select this option so that, during the revalidation of the object, the Validity field is filled in by the system with the default time, but can be edited. |
If the default time is changed in the validity configuration later, this change will be applied to the next revision or revalidation of the objects already created with the validity, provided that it is Fixed.
5. Check the Enable revalidation date to be changed option so that it is possible to edit the Date field when revalidating the object.
6. In the Scheduling section, set the desired configurations:
| Notify before due date |
The party responsible for revalidating the objects that have the validity configuration associated with the type will be notified through the "My tasks" e-mail before the day on which the default time that has been set is over. In this case, the following fields are available: |
| Notify on due date | The party responsible for revalidating the objects that have the validity configuration associated with the type will be notified through the "My tasks" e-mail on the same day when the defined default time is over. |
| Notify after due date |
The party responsible for revalidating the objects that have the validity configuration associated with the type will be notified through the "My tasks" e-mail after the day on which the defined default time is over. In this case, the following fields are available: |
| Subordinates' tasks | It allows for defining other users to be notified of the expiration of the objects. To do so, configure the fields below. |
| Notify leader of responsible user | The "Subordinates' tasks" e-mail will be sent to the leader of the user responsible for the task. The following fields will also be enabled: Go up: enter the number of hierarchical levels, above the leader of the user responsible for the task, that will receive the e-mail. Frequency: enter the number of days that will make up the range in which the system will rise the hierarchy until reaching the previously configured level. |
| Specific user |
The "Subordinates' task" e-mail will be sent to a specific SoftExpert Suite user. In the Specific user field, select the name of the desired user. Use the other buttons next to this field to add a new user to be notified, to fill in the field with the data of the logged user, and to clear it. |
7. Click on the 
button to enable the Approval tab.
8. In the Approval tab, it is possible to determine that the revalidation of the objects with this validity will go through approval.
Click here and learn how to configure the approval step.
9. Once the configurations are performed, click on the 
button.
Conclusion
After correctly configuring a validity, the next step is to associate it with a specific category or type.