Persisting CDT data elements the are called in a task form

A Score Level 1

Dear all,

I have a CDT with a number of data elements that is being used in a Process Variable.  Some of the data elements (not all) are prepopulated before my process calls a user task.  When the user task is called, more data elements are populated by the user task.  However, I noticed that the entire CDT is overwritten with only the data elements that are populated in the user task.  Is there a way to configure the data tab of the user task so that both previous CDT elements and new CDT elements are preserved in the PV?

Thanks

Parents
  • I suspect this is a mapping issue in the way you've set up passing the pv! to the Task and thence into the Interface. When I teach this topic I use a diagram to try to explain how the data flows from a pv!variable to an ac!variable (and how the ac!variable is mapped to a ri!, making it very clear that a ri! is NOT a variable but a pointer to the ac!variable).

    I've attached this diagram in case that helps clarify the conceptual model and therefore hep you diagnose your issue.

Reply
  • I suspect this is a mapping issue in the way you've set up passing the pv! to the Task and thence into the Interface. When I teach this topic I use a diagram to try to explain how the data flows from a pv!variable to an ac!variable (and how the ac!variable is mapped to a ri!, making it very clear that a ri! is NOT a variable but a pointer to the ac!variable).

    I've attached this diagram in case that helps clarify the conceptual model and therefore hep you diagnose your issue.

Children
No Data

 Discussion posts and replies are publicly visible