Skip to main content

How could a notification be configured to be scheduled at a point in the future?

 

We have a requirement to send certain notifications after an ‘age’ threshold has been surpassed.

 

This frequently requires a non-standard table or view (one not included in the baseline notification function) and would need to run after a date comparison determines that an item has exceeded an age based on a date stored in the table, and the current server time? - This seems to present a challenge as no server fields have changed

 

Has anyone successfully used non-standard tables for notification triggers?

 

How have you been able to handle the notifications which need to be sent in the future? 

Good Afternoon,

 

We have several scenarios in place that operate like that. 

One example is RMA Aging - on 14/30/60 days notify request contacts that there are still pending returns.

 

We accomplished this with Scheduled Processes

  • scheduled process executes on set interval
    • hierarchy select to find aging records (could be supported by a custom view)
    • insert event or update record.
  • Business Rule to process notification. 
    • on inserted event // updated record: trigger notification. 

 

hope this helps.

-Rudy

 

 

Building upon the previous answers, you can possibly utilize the Service Monitor Engine (SME) to trigger some action after some time has passed (Eg: After 10mins/hours).

 

You can go through the answers of the following post

 

https://community.ifs.com/service-touch-apps-mwo-mro-43/escalations-base-previous-escalation-status-3730

Reply


Terms & ConditionsCookie settings