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

I am facing a critical issue in Appian Process . We had deployed the application 4 months back with all thr SAIL forms and process model. Now after the new requirements and changes we made in the SAIL forms and process model we redeployed the application with the newer changes.
Now the issue is the old process which were already started are using the new SAIL forms which have the new Activity Parameter and Process Variable which are there is new Updated Process Model. Hence all the old instance are having issue,

Could you please let me know what needs to be done when we redeploy the applicatin with new funcationality ? Basically i want all the old process model to use the old version of the SAIL forms .

OriginalPostID-177591

OriginalPostID-177591

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer
    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.
Reply
  • 0
    Certified Lead Developer
    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.
Children
No Data