Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Hello everyone, is it possible to have dynamic timer of one process model based on user set of schedules/timer?
Discussion posts and replies are publicly visible
rlalbario said:user set of schedules/timer?
What does that mean? And what is the use case of having a dynamic timer for a process model?
example is I have 2 user, one have setup that will run every 30 minutes and other is 60 minutes is it possible using only one process model?
No, that is not possible. Can you describe your use case in more detail?
What do you do when you have 1000 users? Does each user have his own process being started? That will not scale.
Example1. I have users that can set interval on the UI ex. run every 30 minutes, 60 minutes etc. (specific per user).
2. Those intervals will pass to the process model that has a timer.
3. The process model will run based on the users setup interval.
So its really not possible right?
the thing is: Appian process instances are based on process model which is providing the "template". So if you want to have a certain behavior which is independent from a process value like how often a process runs, then you need a own process model for it. and then the effect is system wide and not exclusively for one user.
no its not as the timer (interval) is more like a process property not a process variable which is flexible. like already said, a process model behaves independent from a user who starts it.here you try kind of mix starting by a timer and starting by user interaction.There is nothing like an individual process model. Process models acting system wide for all users the same way. (please ignore the corner cases ;) )
so its not possible to do that right? to the whole users, unless they have individual process model based on their setup timer?
you have to make a difference in process models. Set ups like who can start the process model, who receives the alert but as well the setting like run schedule are more or less process property settings.they are unique per process model but not per instance.The act differently than elements which can be influenced by a process variable like a gateway, task assignment etc.they can be unique per instance