Scope field in a branch step


can anyone give me more information on the purpose of “scope” field in a branch step. The definition which I found in the developer’s guide is “The name of a document (IData object) in the pipeline to which you want to restrict this step. If you want this step to have access to the entire pipeline, leave this property blank”.

I found the above definition a bit vague, if anyone can explain me the field in detail with an example it would be nice.


Say you have a document in the pipeline named ABC:


If you specify the scope to be ABC, only field1, field2 and field3 will be visible to the step. If used on a branch step, your branch could then use BRANCH on /field2 instead of BRANCH on /ABC/field2