I am facing a critical issue in Appian Process . We had deployed the application

RE: I am facing a critical issue in Appian Process . We had deployed the application

cedric02 — Tue, 11 Mar 2025 17:05:01 GMT

Hi Jyoti,

Could you tell some details or a little example, about this "key-value pair mapping" best practice please ?

or maybe do you have the Appian documentation URL which explain this?
(I would like to make some tests with process examples)

RE: I am facing a critical issue in Appian Process . We had deployed the application

marky — Wed, 27 Jan 2016 22:25:21 GMT

If you call the SAIL form in the user input task by Keyword, then you can build the logic for both old and new process instances into your first SAIL form using an if statement. If you call the SAIL form in the user input task by Parameter, then the only choice is to build new SAIL rules.

RE: I am facing a critical issue in Appian Process . We had deployed the application

Mike Schmitt — Mon, 09 Nov 2015 18:19:07 GMT

I'd like to tack on to @jyotim's comment and point out that if your SAIL form updates are too incremental to consider making differently-named versions, you should be able to create "safe" upgrades if you call the SAIL interfaces using dictionary syntax, always pass PVs and ACs in as Rule Inputs, and always upgrade your SAIL forms in such a way as they will still work if "old" data were being passed in as well as "new" data.

For large updates, of course, Eduardo's method is probably safer in general, though I still strongly recommend not directly referring to PVs inside the interface, or calling interfaces without using dictionary (i.e. key-value) syntax.

RE: I am facing a critical issue in Appian Process . We had deployed the application

satheeshm — Mon, 09 Nov 2015 14:09:00 GMT

Hi Nilesh,

you are upgrade the process. once create SAIL run every time.

RE: I am facing a critical issue in Appian Process . We had deployed the application

Jyoti Mishra — Mon, 09 Nov 2015 08:27:45 GMT

Hi Nilesh,
Have you followed the key-value pair mapping which is an appian best practice for the process models?
I had faced this issue but eversince I have implemented this for all the process models, it no longer persists.

RE: I am facing a critical issue in Appian Process . We had deployed the application

Eduardo Fuentes — Mon, 09 Nov 2015 06:04:10 GMT

The way this works solves the problem where people would need to run process upgrade to migrate instances to a newer version of the models. The advantage of the interfaces is that no matter what version the process is on, it can still use the latest version of the interface which gives you an advantage to even correct bugs in the interface that will get propagated to running instances even if they were launched after the update.

You don't have to create a new SAIL form every time. What we are saying is that you have to do this only if the new one is not compatible with the previous version of the model.

RE: I am facing a critical issue in Appian Process . We had deployed the application

nileshkumarg — Mon, 09 Nov 2015 06:01:24 GMT

I feel Appian should come up with the better solution . Coz this is basic need for the new deployment. Consider the scenario wherein we have lot of SAIL form that changes with every requirement, If we follow the process that you mentioned, it will be a cumbersome task

RE: I am facing a critical issue in Appian Process . We had deployed the application

nileshkumarg — Mon, 09 Nov 2015 05:58:13 GMT

that means for every new deployment , i have to create the new SAIL form and update the model. Dont you think that it will create alot of work? And if let say my all the SAIL forms are changing it will create lot of effort to modify them

RE: I am facing a critical issue in Appian Process . We had deployed the application

Eduardo Fuentes — Mon, 09 Nov 2015 05:51:21 GMT

For backwards compatibility, if the signature of the new SAIL Interface is changing I think it's better to create a new one with a new name (e.g. append the version as a suffix) and update the model to use the new version. This way only new instances will start using it.

RE: I am facing a critical issue in Appian Process . We had deployed the application

abhi.jana — Mon, 09 Nov 2015 05:37:10 GMT

The only option i think would be to revert to using the old forms to fix your older instances, and then work on creating a different named form (rather than a different version of an existing form) and save and publish the model with this new form. That way the old instances won't be affected since they use an older PM version that has the old form.