Not able to get the value of a expression rule using script task

RE: Not able to get the value of a expression rule using script task

Mike Schmitt — Thu, 08 Sep 2022 14:02:32 GMT

Without seeing the process instance value of your PV it's hard to tell exactly, but among other possibilities, your property names don't match, so the expression rule's value would NEVER save properly into a CDT where the map value properties are named "13thDay" and the CDT's corresponding property is named "ThirteenthDay" (etc). Appian would have absolutely no way of knowing that those property names are referring to the "same" thing, even though they evaluate to the same literal meaning in English.

RE: Not able to get the value of a expression rule using script task

saifalikhan13 — Thu, 08 Sep 2022 11:12:55 GMT

Thanks

RE: Not able to get the value of a expression rule using script task

Stefan Helzle — Thu, 08 Sep 2022 10:59:35 GMT

This depend a lot on your overall use case. One pattern is to just start a child process for each.

RE: Not able to get the value of a expression rule using script task

saifalikhan13 — Thu, 08 Sep 2022 10:58:34 GMT

One more thing Stefan,
I got the values in the cdt object and the same values are coming up in the single process variable which is of type multiple.
But, for every value going forward in the process variable, I need to take the decision.
What should i do in this case?

RE: Not able to get the value of a expression rule using script task

saifalikhan13 — Thu, 08 Sep 2022 10:51:09 GMT

Thanks for the directions Stefan
Let me try to remove the map and directly bind it to the CDT type object.

RE: Not able to get the value of a expression rule using script task

Stefan Helzle — Thu, 08 Sep 2022 10:48:28 GMT

The issue is, that your expression creates a list of lists where each sub-list contains one map.

Two questions.

1) Could it be that you use a foreach and wrapped the a!map() call into curly brackets? Remove them.

2) Why do you create a map instead of the CDT type?