If you have a process creating using LiveCycle 7.x that has been migrated into LiveCycle ES, and it contains branches, you notice that data variables lose their values when moving from one branch to the next.
Consider this example:
The example shows two branches, each containing a User activity, which assigns a task to a user's queue with a form merged with data. Different data is set for each user in the first step in each branch. Therefore User1 opens a form in Workspace and expects to see <BRANCH 1 DATA>; User2 expects to see <BRANCH 2 DATA>.
Note the following variables for this process:
There are separate variables for each branch. However, when the process is run and the flow reaches the first User activity in branch1, it overwrites the data in branch2 (in the branch2_form), which means that both users see <BRANCH 1 DATA> in the form at run time.
A private patch is available for this issue for LuveCycle ES 8.2.1.2. Contact Adobe Support if you encounter this issue and require this patch.
Keywords:
cpsid_80767
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.
