Hello Experts,
figured out the contract expiration notification "workflow" (for lack of a better term) not changing anything OOTB, but, adding a new threshold to send an alert on.. I have seen many posts about adding thresholds above the max 90 day OOTB alert, but have not seen any adding one "in between" I have a task to add a 45 day check to the clm_condition_checker table as seen below, used insert and stay since the conditions when creating new do not exist in the form when using the "new" option (on or before values)
aafter creating this, I created a test contracts that expire in 43, 45, and 46 days to have a good source to pull from. The issue I have is when running the daily checks (there are two scheduled jobs, that call two different script includes for some reason) - The jobs are scrapping the "Expiration Level" field, (value = expiration) the 45 day contracts are not filling in this field on the ast_contract form
2 questions
what populates this field (expiration level)
and
do these send notifications every day? if there is a contract expiring in 90 days, will the admin/owner get a notification daily until it hits the 45 day mark, then the 60 day mark, then the 30 day mark, then expired? or is there a ref qualifier or something that says "hey this is already sent" no need to send again.
Hi Vince,
Going to answer your question slightly backwards to the way you laid your query out but hopefully it'll help clarify.
The expiration conditions on clm_condition_checker are relative so will only trigger once, well atleast the OOB ones will. They trigger the contract.expiration event which allows for a notification to be generated.
Because the job runs daily, what the following condition says is "find me every contract where the end date is between right now and 45 days from now" and triggers a notification. The notification only triggers once as the script include (private) only sends a notification if the expiration value on the record is being changed.
What you've done should be fine, especially if you copied an existing expiration entry (such as the 60 day one). I've tested this in my environment and it's correctly run.
