Configuring a validity
 |
 |
 |
Prerequisite
- Access to the Configuration > Validity menu.
Introduction
The validity configuration step is crucial as it is used to define the validity date of the objects and the users who will be notified of their expiration.
See below an example of this configuration:
Configuring a validity
1. Access the Configuration > Validity menu.
2. Click on the 
option on the toolbar.
3. Enter an ID # and name for the validity.
4. Then, fill out the Default time field to indicate the days, months, or years during which the object will be valid.
5. After doing that, click on the 
button.
6. On the Approval tab, it is possible to determine that the objects with the validity configuration associated will go through certain approvals.
In case of questions regarding approval configuration, access the How does approval work? article.
7. Once the configurations are performed, click on the 
button.
Complementary resources
See further details regarding each field available for the validity configuration
Default time
| Validity |
Enter the number of days, months, or years during which the objects will be valid. The default time is counted from the object validity date, thus, when this time expires, the "Object due date" task will be generated for the responsible parties, in order for its revalidation to be performed. |
|---|---|
| Fixed | Select this option so that, when revalidating the object, the Validity field is filled out by the system with the default time and cannot be edited. |
| Variable | Select this option so that, when revalidating the object, the Validity field is filled out by the system with the default time and it is possible to edit it. |
Enable revalidation date to be changed
| CHECKED | UNCHECKED |
|---|---|
| When revalidating the object, it will be possible to edit the Date field. | The Date field will be filled out by the system and may not be edited. |
Scheduling
| Scheduling options | Checked | Unchecked |
|---|---|---|
| Notify before due date |
The responsible party for revalidating the objects that had the validity configuration associated with their types will be notified through the "My Tasks" e-mail on the day before the previously defined default time expires. In that case, the following fields are available: |
The responsible party for revalidating the objects will not be notified on the day before the previously defined default time expires. |
| Notify on due date | The responsible party for revalidating the objects that had the validity configuration associated with their types will be notified through the "My Tasks" e-mail on the day the previously defined default time expires. | The responsible party for revalidating the objects will not be notified on the day the previously defined default time expires. |
| Notify after due date |
The responsible party for revalidating the objects that had the validity configuration associated with their types will be notified through the "My Tasks" e-mail after the previously defined default time has expired. In that case, the following fields are available: |
The party responsible for the revalidation will not be notified after the expiration of the objects. |
| Subordinates' tasks | Allows defining other users to be notified of the expiration of the objects. To do that, configure the fields below. | Other users will not be notified of the expiration of the objects through the "Subordinates' tasks" e-mail notification. |
| 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:
|
The leader of the user responsible for the task will not be notified of the expiration via e-mail. |
| Specific user |
The "Subordinates' tasks" 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 the field to add a new user to be notified, fill out the field with the data of the logged user, and clear it. |
The due date notification will not be sent to a specific user through the "Subordinates' tasks" e-mail. |
If the "Default time" is later changed in the validity configuration, this change will be applied to the next revision (provided it is Fixed) or revalidation of the objects already recorded and to the new objects that are included in the type that has the validity configuration associated.
Conclusion
After correctly configuring the validity, the next step is to associate it with a specific category or type. This ensures the validity is applied according to the characteristics of the object.