Publishing Process Models

Hi PrakharGarg, As far as I know there is no smart service that will publish the process model on runtime. Lets see other practitioners ideas.
Just curious to know can you describe your requirement here.?

As per our requirement we want to give flexibility to support team to change the scheduling any time, currently our process runs every 3 hours and user want that whenever they want scheduling can be changed by support team

To handle this we have used a constant which describes the interval and giving flexibility through UI to update the value but as per my understanding if you are updating constant value used in scheduling process model should be published.

Publishing a process model in production is considered as code change and will require a complete release which we want to avoid and thought of giving configuration kind of functionality to support.

My requirement is that whenever support member updates the scheduling interval constant value should be updated and process model should get published automatically.

Hi ,

If you have directly used a constant in your Process Model Scheduling then you do not need to Publish the Process model every time after updating the constant. If process already started and after that you are changing the constant value, in this case it will hold old value and Schedule will work on old Constant value only.
We do not have any smart service to publish the process model.

Yes process is already running in production and now I want to give flexibility to update the constant value using UI and publish the pm

Hi Prashar,

you can try the plug-in : community.appian.com/.../republish-model-as-different-user

may be above plug-in solve your problem

I saw this plugin but after seeing the compatible version and last updated, I dropped the idea and didn't gave it a try.

I believe that if you are using a constant in the timer recurrence (in a process model) and the constant value is changed (to a different time) then the process model needs to be re-published to get the new time.

I think you'll need to re-design this entirely. One option would be to derive the next "Run At" (DateTime) value as a pv! using the value of a cons! e.g. fn!now()+cons!<futureDeltaValue>. But it depends on whether you're Ok with having the model run at the last derived value or if you need the last derived value to also be changed.

Hi  I believe in these cases, you can rely on db. Where you can expose an action for Support Team Group to update the row in db, and query this data while performing scheduling logic.

I believe this approach will be quite easy and reliable for your scenario.

Hence I would recommend to go for DB approach compared to constant approach.

Hope this will help you.

Hi Alok,

Thanks for the suggestion, Can you please elaborate a bit on the same and I have below queries:

How we will use the Query rule to fetch the Scheduling data (We have 6 timers on start event currently and constant has been used for the same)

1. AFAIK when we have timer on start event and publish the process model a snapshot of the scheduling is created and then process triggered ignoring the latest value of the constant, but in this case how it will work?
2. Suppose I have passed query rule in the scheduling then will it continuously query the DB to check the value of the timers?

I am bit confused how it will work?