Hi Dojo,
we tried to create a generic automation script that does a specific task to use it in different other automation scripts. Unfortunately we discovered that the handover parameters show a different behavior when used in condition compared when we just add it as separate action.
When using this as separate Action we can access the initial automation script parameter as variables to handover to the second automation script. This is not possible when the second automation script is inside a condition. 
Is this intended behavior? Is there another way to access the parameter from the main automation script.
Any help on this would be appreciated!
Best regards
Manuel
Hi Manuel,
I believe this is a bug in the software and a task should be created to handle this. Maybe as a workaround you can run the generic script from within the main script.
SubScriptOptions sesVideoScript = engine.PrepareSubScript("SES Video (Automation) Insight");
sesVideoScript.Synchronous = true;
sesVideoScript.SelectScriptParam("ServiceKey", serviceKey);
sesVideoScript.SelectScriptParam("AttributeId", attributeId);
sesVideoScript.SelectScriptParam("AttributeValue", attributeValue);
sesVideoScript.StartScript();
Some more information on this can be found here PrepareSubScript
Hi Wannes,
Many thanks for the workaround!!
I’ll open a task to get that checked out.