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

[Bryan Tay3]

hi Patricia,

Does the existing 90/60/30 days notification working? or only your newly added 180 and 360 days not working?

Could you also post screen for the "condition check definition" list (Contract -> Condition Check Definitions) as well?

thanks.

[paw2 · Accepted solution]

Both conditions and notifications were not working.   However, it turns out the 'empty' record was the culprit.

Here is the fix:

change the empty condition to be numeric value of the last condition you have ..... in this case 365.

This is the correct answer!    

[Bryan Tay3]

hi Patricia,

The "empty" is to set the "Expiration Level" field to empty after 365 days as you specified.

Am I right to say that when you mentioned numeric value should be entered, which means in the past it was not numeric value being placed at that "Empty" condition, which later trigger an exception and it will stop the processing of other subsequent condition?

Anyway, glad that you resolve ur own problem.

cheers...

[DaSmith9]

5 year old fix/thread, but much appreciated! Fix still works, and 'empty' still needs to be updated if you add expiration thresholds beyond the 90 days configured out of the box.