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.

Unable to save fv!processInfo.pv.<process variable> back into interface using a!startProcess v25.4

Hi everyone,

I encountered an issue regarding saving process variable using a!startProcess -> onSuccess on version 25.4, the fv!processInfo.pv.subCategory was not saved back into local variable ri!checkStatusofChangingCategory. Here is the code:

a!startProcess(
processModel: cons!NFL_CONS_PROCESS_CHANGE_CASE_TYPE_CATEGORY,
processParameters: {
subCategory: ri!subCategory,
newCategoryId: local!selectedNewCategory
},
onSuccess: {
ri!saveInto,
a!save(
ri!checkStatusofChangingCategory,
append(
ri!checkStatusofChangingCategory,
fv!processInfo.pv.subCategory
)
),
a!save(
local!currentCategory,
local!selectedNewCategory
),
a!save(ri!subCategory, null),
a!save(local!selectedNewCategory, null),

}
)

The initial value of ri!checkStatusofChangingCategory was null after onSucess, it became [null].
This code worked with version a!startProcess_24r3 ( it successfully saved pv.subCategory into ri!checkStatusofChangingCategory), i want to know the reason why, what am i missing? I'm looking for an explanation for this issue as i already known a workaround.
What i have tried: 
  • Activity channing
  • using isSynchronous combine with onIncomplete
  • saving another variable

  Discussion posts and replies are publicly visible