- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-27-2017 02:16 PM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2017 10:05 AM
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2023 05:43 PM
Were you able to find the job?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2023 07:45 AM
I have 4 conditions (30, 60, 90, and 120) and I changed the 'empty' condition to reflect the 120, however, when the schedule item runs, it is wiping out the expiration field on the contract. This is not how we want it. How can we change this?