Timeline for Passing parameters to an External (Workflow) Activity
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 26, 2013 at 13:09 | vote | accept | Chris Summers | ||
| Oct 25, 2013 at 13:42 | comment | added | Nuno Linhares♦ | I smell an ER. File it here ideas.sdltridion.com or we will all forget about this. | |
| Oct 25, 2013 at 13:38 | comment | added | Chris Summers | OK, probably PI variables is not the way to go, but something officially supported like Eric's "Option #2" would be very convenient, and make creating workflow process definitions from pre-made modular classes very easy. That way a "Non-Developer" can make workflows and just plug in parameters using Visio. | |
| Oct 24, 2013 at 21:04 | comment | added | Syav4eg | Honestly, I don't agree.PI.Variables must be used for specific ActivityInstances(so, you have activity instance and want to share some info with another ActivityInstance). But activityinstance is some dynamic stuff...As I've understood you want to deal with ActivityDefinitions in static context (all ActivityInstances created for this ActivityDefinitions will used the same values...so they are static, not dynamic). Why in this case not to use ApplicationData for specific activityDefinition? Probably ApplicationData is approach, when you must add some additional information to Tridion objects. | |
| Oct 24, 2013 at 16:44 | comment | added | Chris Summers | I think there is a valid ER here, it would be great to be able to add PI.Variables in the Visio box for External Activities so you don't need to do it in the previous activity. Anyone else agree? | |
| Oct 24, 2013 at 16:42 | comment | added | Chris Summers | I tend to agree that #2 is a hack, but using the PI.Variables involves making a lot of extra activities, and complicating the WF development process in my opinion. Thanks @Eric for the great info. | |
| Oct 24, 2013 at 7:52 | comment | added | Syav4eg | 2) is really a hack (I didn't expect, that it is possible) + not documented. As I understand, during implementation of this approach assumed, that user will share his additional parameters through Process Instance variables (btw - it on of the reason, why it is available in ExternalActivity class). So idea was, that before finishing one activity you save some variable(to PI.Variables), and you can use it during execution another activity. | |
| Oct 24, 2013 at 2:48 | history | answered | Eric Huiza | CC BY-SA 3.0 |