Newly created conditions for expiration levels will not fire, even when set up like the 30/60/90 days conditions?

[paw2]

Helsinki patch 8.

Created new conditions, configured similar to the "within 30 days" conditions, and they will not fire.   Contrary to SN docs, the 30, 60, 90 day conditions fire right away when the contract end date is adjusted accordingly and will show in the list view under expiration level   (sets this field) - the docs say it will do so off a nightly event: contract.expiration off the contract table (ast_contract).

==============================================================================================================

per SN docs:

Verify contract administrator assignment for notification

An event runs automatically each night to send reminders to contract administrators about contract expiration dates so they can renew or renegotiate the contract. You can verify that the right contract administrator is assigned to the contract.

Before you begin

Role required: contract_manager or admin

About this task

When the contract.expiration event runs on the Contract [ast.contract] table each night, an email message is sent to the person identified as the contract administrator. This occurs at the following times.

• 90 days ahead of the contract expiration date
• 60 days ahead of the contract expiration date
• 30 days ahead of the contract expiration date
• On the contract expiration date

A user with the admin role can edit the contract.expiration condition check that processes contract notifications. Follow the procedure below to verify that the right contract administrator is assigned to the contract.

=====================================================================================================================

I checked the event, and associated script include, etc., but don't see anywhere else that I would need to adjust.   Below is the new condition:

Does anyone know what is malfunctioning or did I miss something and something else needs to be updated?

Thanks, Pat

[Rose L]

It is already 2024 but the fix still works!

Much appreciate the explanation although it took me a while to figure out the empty condition to be numeric value of the last condition. 

In case anyone also encounter this issue, OOTB there are 5 conditions set in the system:

You will need to make the "(empty)" record's days value (circled in the screenshot) equals to the greatest days number you have. For example, if I create another condition which the contract will be expire within 180 days, then after creating this new condition, I should also go to the "(empty)" record to update the days to be 180 (by default it is 90).

[paw2]

Hi Bryan,

Actually, it was always numeric in the empty, but it stopped at the 90 day mark.   I had to change it to the 364 to allow for the additional time, in my case.

If for instance, you needed to review 120 days before expiration, then you would enter in 120.   Out of box, it was 90, because 30, 60, 90 are standard review times.

[Bryan Tay3]

hi Patricia,

yes you are right for the OOB default to 90 days.

If you need alerts earlier than that, u can add more condition such as 120, 160 days after "90 days" condition.

As for the first "Empty" condition, it doesnt matter because if will only be triggered when "Ends" is after X days from Now (expired contract).

so the OOB conditions will flow from

1. "Empty" -> Check if Ends is after X days from now.

2. "Expired" -> Check if Ends i after today.

3. "30 days" -> Check if now is between (Ends - 30 days) and Now.

4. "60 days" -> Check if now is between (Ends - 60 days) and Now.

5. "90 days" -> Check if now is between (Ends - 90 days) and Now.

Once match, it will mark the "Expiration Level" field with the appropriate level so that next day (E.g. within 90 days) will not trigger the same alert.

Ultimately it will only trigger 1 alert for 90 days, 60 days, 30 days and Expired.

Note: Empty condition will not fire any event, hence, no notification.

Hope this clarify.

cheers...:)

[gml35]

You my friend are a life saver!!!

[Kim Sullivan]

Can someone post the script for the Contract Compliance Checks job?  I don't seem to have that in my instance and didn't see it in OOB either?