I need some help in mind storming the best method to achieve what I need. Your t

Adel Ammari over 8 years ago

I need some help in mind storming the best method to achieve what I need. Your thoughts and comments will be highly valuable.

I want to start a process, automatically once its date and time matches that of a predefined constant. Every year, this constant will be updated to prepare for the next year. And I want the process to auto start every year based on that constant.

Using a start even at the beginning of a process [followed by a controller rule] only works for 1 time after I publish the process. But when the constant is updated the process does not run again after 1 year, unless the original process was republished sometime after it auto ran the 1st time. Any thoughts?

I have this idea of using a message sending/receiving somehow, but have not wrapped my mind around it yet.

Thanks for your thoughts.

Discussion posts and replies are publicly visible

Parents

0 Chris over 8 years ago

My solution would be similar to sagarl511's above, if you are not going the DB route as phil suggests. I would do this with 2 processes, since date/time should be exact it is not feasible to have a process that starts regularly, terminating if not current time >= cons!runTime.

One process would be used to update the constant. This would send a kill message to any annual process waiting (to allow for date/time changes), update the constant, then call the annual process asynchronously. The annual process will start and wait until the date/time selected. Once completed, the annual instance terminates. The Update mechanism will then start a new instance of the annual process which waits until the next date/time to continue.

My example is attached.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Chris over 8 years ago

My solution would be similar to sagarl511's above, if you are not going the DB route as phil suggests. I would do this with 2 processes, since date/time should be exact it is not feasible to have a process that starts regularly, terminating if not current time >= cons!runTime.

One process would be used to update the constant. This would send a kill message to any annual process waiting (to allow for date/time changes), update the constant, then call the annual process asynchronously. The annual process will start and wait until the date/time selected. Once completed, the annual instance terminates. The Update mechanism will then start a new instance of the annual process which waits until the next date/time to continue.

My example is attached.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data