Hello JBKM,
Thanks for sharing the bpmn and the task code. While you have changed the task code to create the new output, the bpmn does not know about it. So, naturally, you will not see the new output the way you see the others that the bpmn is aware of.
Your modification of an existing task in an already deployed Federated Area (FA) violates the IRM principle that once deployed an FA is immutable except for the landing area where data can be updated through Live ETL.
Please note that once you modify a task signature (in this case, creating a new output), you have essentially created a new task. The correct way of doing this change will be to have the new task in your Personal Federated Area (PFA), use the Scripting Client to create job-flow script, execute the job-flow script (say, in SAS Studio), inspect the created instance that everything looks correct and then have this new task and the created bpmn (generated when you execute the job-flow script) copied over into a new FA. Why a new FA? Because once deployed an FA is immutable as mentioned above.
If you do want to make this change in the existing FA, you will have to first make sure that you have deleted ALL instances of the job flow, replace the current bpmn with the new bpmn and then create an instance of the job flow.
Hope this helps!
... View more