Forums - Thread Details
  • State Not Answered
  • +1 person also asked this people also asked this
  • Replies 3 replies
  • Subscribers 322 subscribers
  • Views 854 views
  • Users 0 members are here
Forum Actions
Related

Best practice for trigger a process definition after a long period of time.

Marciano Ballestero

Hello, I hope you are all well. I have a request from my business to update a field on the contact record after 120 days, simple enough, so I thought. My first thought was to create a Process Definition to look for the event and wait 120 days. But I had some thoughts that I wanted to get feedback on. 

  • Does having several process in a waiting status cause issues? 
  • How long can I reliable keep a process in queue? 
  • What is the best practice for queuing PD's after a long period of time? 

I did some searching around but couldn't seem to answer these. Words from your bright minds will be greatly appreciated. 

Parents
  • 0

    Hi ,  We now have many process definitions with wait events.  Some for just hours, some for days.  We don't have anything over months though.   While it seems to be happy with these sitting in the cron table (I guess that is where they live) and they function well  - I do like your question and would be interested to hear an expert opinion too ;-)

    Our original integrators also created a way to expire warranties in our system which runs custom code ('Job') from the Scheduler (runs daily).   In my mind this seems preferable to filling up the cron table with pending rows of 'stuff' waiting.   I think?...    And that may be a more in depth code implementation than an simple admin function like BPM would be.   It maybe depends on how many records you are talking about to know if you could expect performance issues?   I suspect 120 days is perfectly OK for process Definitions if the amount of records is reasonable.

    Sorry this is not an 'answer', I am just interested also in the same question ;-)

    Luke.

      

Reply
  • 0

    Hi ,  We now have many process definitions with wait events.  Some for just hours, some for days.  We don't have anything over months though.   While it seems to be happy with these sitting in the cron table (I guess that is where they live) and they function well  - I do like your question and would be interested to hear an expert opinion too ;-)

    Our original integrators also created a way to expire warranties in our system which runs custom code ('Job') from the Scheduler (runs daily).   In my mind this seems preferable to filling up the cron table with pending rows of 'stuff' waiting.   I think?...    And that may be a more in depth code implementation than an simple admin function like BPM would be.   It maybe depends on how many records you are talking about to know if you could expect performance issues?   I suspect 120 days is perfectly OK for process Definitions if the amount of records is reasonable.

    Sorry this is not an 'answer', I am just interested also in the same question ;-)

    Luke.

      

Children
No Data