Unable to use the current value of constant in Start Node Appian Timer

RE: Unable to use the current value of constant in Start Node Appian Timer

Stefan Helzle — Tue, 04 Jul 2023 05:41:09 GMT

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.

RE: Unable to use the current value of constant in Start Node Appian Timer

sourabh2512 — Tue, 04 Jul 2023 05:06:44 GMT

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.

RE: Unable to use the current value of constant in Start Node Appian Timer

Stefan Helzle — Mon, 03 Jul 2023 12:33:20 GMT

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.

RE: Unable to use the current value of constant in Start Node Appian Timer

Konduru Chaitanya — Mon, 03 Jul 2023 11:55:37 GMT

It is the correct way. But it should be taking the latest value of the constant. but As far as I know the instances which have already began before you changed the constant value will use the previous value.

RE: Unable to use the current value of constant in Start Node Appian Timer

sourabh2512 — Mon, 03 Jul 2023 11:53:15 GMT

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.

RE: Unable to use the current value of constant in Start Node Appian Timer

sourabh2512 — Mon, 03 Jul 2023 11:48:46 GMT

yes!!! I am changing the constant value ryt. isn't it correct way to do ?

RE: Unable to use the current value of constant in Start Node Appian Timer

Stefan Helzle — Mon, 03 Jul 2023 11:46:51 GMT

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.

RE: Unable to use the current value of constant in Start Node Appian Timer

Konduru Chaitanya — Mon, 03 Jul 2023 11:46:29 GMT

Hello sourabh2512

what do you mean by this?

Are you changing the constant value?

RE: Unable to use the current value of constant in Start Node Appian Timer

sourabh2512 — Mon, 03 Jul 2023 11:42:37 GMT

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..

RE: Unable to use the current value of constant in Start Node Appian Timer

Stefan Helzle — Sun, 02 Jul 2023 11:38:52 GMT

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.