Does script task has any limitations?
Thanks.
Discussion posts and replies are publicly visible
I should also mention that using a CDT would fulfil the same concept. If you can reference a pv! then it's just as easy to reference an element in a CDT that's in a pv!. The Map was supposed to get around having to define CDTs to make this pattern work as you can generate them at run-time. But you also need to be pretty darn sure you know what your Map contains so that you address its contents reliably.
Hi Mike,
If I understood you correctly, on saving different parts of the output to different PVs.
We can query the database in the input tab of Script task, and use that activity class param in the output tab.
So the query is executed only once and extract total count, data, and other fields to the different output PVs.
Chris said:Say you have 30 Data Outputs, trying to find which one is being saved into a certain variable requires up to 30 clicks.
I find the process documentation useful for such situations.