HI All,
I am trying to schedule the start node of the process model using Timer in Appian. PFB the configuration:
I am trying to schedule it at an interval of some hour. I want this hours to be configurable so used constant rather than hardcoding it.
Now the problem I am facing is whenever I change the value it only picks the old value.
Let say the current value is 15 and if I change it to 20, it will still run after interval of 15 hour. and later if I change it to 22, it will run after 20 hours.
So I am not sure why this weird behaviour.
anyone have notices this and anyone knows the solution to this ?
Is there a way to refresh the values before using it . or something like that ?
Thanks
Discussion posts and replies are publicly visible
No. Timers are static and will refresh once the model is deployed.
The usual way of creating configurable scheduled processes is, to run the process at a fixed interval and add a XOR to evaluate the business rule.
But then how it's picking the second last value ?
and as I want to make the schedular configurable so that if the requirement changes we should be able to change the timer interval from the constant without making changes in the process model itself. how will I be able to achieve this..
Hello sourabh2512
what do you mean by this?
Are you changing the constant value?
What do you mean?
You configure the scheduler to run every hour, 24/7, and then add a XOR directly after the start node in which you evaluate your conditions. This will pick up the latest values of your constants.
oh so is that right way to do it ? got you.
so what i have understand from you is it does not matter whether we are changing the constant value or not, it will pick the value with which it's deployed initially ryt ?
if yes then my query is if I update the constant, it will pick the second last updated value. Like initially the constant value was 3, i.e. 3 hour of interval, then I changed the constant to 24 and it was still using 3 hour, but the moment I changed the constant value to 15 it start picking the value 24 and now process is running after interval of 24 hour so I am still confused with this behaviour.
Eh ... what ????
A timer configured in the start node will use the value from a constant. But only the value it had at the time of deployment. It will not pick up any later changes without another deployment.
Any expression evaluated in a XOR will always take the latest value of the constant without the need for another deployment of the model.
okay Stefan I understood what you are saying.. so in development you mean after changing the constant value I have to republish the process in order to pick the latest value ryt ?
And also does that also applies to other settings of Node like delete after property ? it will not pick the value if we are giving it from constant ? and what are other fields that won't reflect if we are using the constant and changing it ?
Thanks for your guidance and help really appreciate.
I said that a timer in the start node does not automatically pick up the value of a changed constant. Anything else will do that.