P
peter.oxheden@exicom.se
Guest
Hello! First, thank you kindly for helping me with this, it's much appreciated! This worked very well in getting the workstepname to the CopWorkstepName dataslot. I wonder why it didn't work to use the Set Dataslot logic to set CopWorkstepName to the System Dataslot WorkstepName, but since this did work, that doesn't really matter. 
However, while this works (again, thank you!), it's not optimal, as it requires a separate dataslot and then for each subprocess that we want to send the logging information to it would require adding this extra script. And since in some of our "main processes" we have up to 20 accesses to various subprocesses (in the more extreme cases) that feels like a lot of extra work and bound to be forgotten. Is there no way to do this as I am already able to do with ProcessInstanceId? With ProcessInstanceId I can just add that to the list of dataslots to send directly to ProcessB. In the Dataslot Property form of the activity that "is" ProcessB in ProcessA I have added ProcessInstanceId. Then I have changed the "Input to Sub-Process" value to "CopProcessInstanceId", so that ProcessB "receives" ProcessInstanceId "as" "CopProcessInstanceId". This works just fine. I don't have a separate dataslot for it in ProcessA or anything. If I could do the same with WorkstepName that would really simplify the processbuilding. And since WorkstepName is a system dataslot just like ProcessInstanceId it feels like it "should" work in the same way. We're currently on 11.5 by the way, if that makes any difference? Again, thank you for your help! - Peter
Continue reading...
However, while this works (again, thank you!), it's not optimal, as it requires a separate dataslot and then for each subprocess that we want to send the logging information to it would require adding this extra script. And since in some of our "main processes" we have up to 20 accesses to various subprocesses (in the more extreme cases) that feels like a lot of extra work and bound to be forgotten. Is there no way to do this as I am already able to do with ProcessInstanceId? With ProcessInstanceId I can just add that to the list of dataslots to send directly to ProcessB. In the Dataslot Property form of the activity that "is" ProcessB in ProcessA I have added ProcessInstanceId. Then I have changed the "Input to Sub-Process" value to "CopProcessInstanceId", so that ProcessB "receives" ProcessInstanceId "as" "CopProcessInstanceId". This works just fine. I don't have a separate dataslot for it in ProcessA or anything. If I could do the same with WorkstepName that would really simplify the processbuilding. And since WorkstepName is a system dataslot just like ProcessInstanceId it feels like it "should" work in the same way. We're currently on 11.5 by the way, if that makes any difference? Again, thank you for your help! - PeterContinue reading...