[LifeCycle] - Integration of before expiration days logic within the task
[LifeCycle] - Integration of before expiration days logic within the task
The main concept is to allow the evaluation of a specific resource (from supannRessourceEtatData ) that is about to expire and to change the subState to "notification".
This will create an audit entry, allowing notification to catch it and therefore send the proper mail to recipients.
Technically : (overview).
- A new attribute will be defined to set the numbers of days before the expiration of resource. (Supann).
- The attribute allowing to set extra days after the ending of the resource (which was the original logic) must be grayed out.
- The task will run and verify the resource expiry days (like always) minus the number of set days before expiration.
- As the resource has been modified, an audit entry will be created.
- A task of notification must be set specifically to handle this change of supann resource. Allowing to verify the content of the change, if the value of the subState is of "notification" the proper mail template linked to the task "notification" will be sent.