Use special syntax in various tasks contained in the ForEach subprocess to create easy-to-maintain workflows. In the ForEach subprocess, you can use the syntax to create dynamic and flexible bursting workflow processes.

Use these syntax to create dynamic and flexible bursting workflow processes.

SyntaxDescriptionExample
{{Subprocess}.Name}Resolves to the member name.E120
{{Subprocess}.Caption}Resolves to the member caption.Houston
{{Subprocess}.Key}

Resolves to the member key.

To be used in specific cases where the key is required.

12345
{{Subprocess}.PropertyName}Resolves to the member property value for the specified PropertyName.{{Subprocess}.Region} resolves to South.
{{{Subprocess}.Parent}.Name}Resolves to the member name of the parent process.

{{{Subprocess}.Parent}.Name}

Resolves to E120 when called from within a Run Workflow task within a For Each task.

For example, use this syntax when assigning Owners, Supervisors, and Contributors to workflow tasks within a For Each subprocess.

You may also use this syntax when specifying:

  • The Data Import Definition in a File Import or Data Transfer task.
  • A Model View to export in a Model Export task.
  • The Override Filename in a Generate Anaplan XL task.

Use Workflow Subprocess syntax when assigning tasks

To assign tasks in a ForEach subprocess:

ProcessActions
Identify the entities and roles
  1. Determine the entities you want to burst through in your ForEach subprocess.
  2. Create roles with a naming convention that includes the entity name. For example, Controller_120_WF, Controller_210_WF, etc.
Set up roles

Create roles in your system with names that follow the naming convention. For example:

  • Controller_120_WF
  • Controller_210_WF
  • Controller_220_WF
  • Controller_250_WF
Configure the ForEach Subprocess

Use the {Subprocess.Name} syntax in the Owner, Supervisors, and Contributors fields to dynamically assign tasks based on the entity name in the ForEach subprocess.

For example, configuration:

  • Owner: {Subprocess.Name}
  • Supervisors: {Subprocess.Name}
  • Contributors: {Subprocess.Name}
Execute the ForEach process

When the ForEach process executes, the tasks will be assigned to the appropriate roles based on the entity name.

For example:

  • Controller_120_WF for entity 120.
  • Controller_210_WF for entity 210.
  • Controller_220_WF for entity 220.
  • Controller_250_WF for entity 250.

Handle multiple entities per role

To handle multiple entities per role:

ProcessActions
Identify the entities and roles

Determine the entities that'll be assigned to a single role. 

For example:

  • Controller_North for entity 220 (New York).
  • Controller_South for entities 120 (Houston), 210 (Los Angeles), and 250 (San Francisco).
Create a property for each entity

Create a property for each entity that'll be used to assign tasks. 

For example, create a property called WFContributor for each entity under USA.

Set up the property rules

Assign the appropriate role to the WFContributor property for each entity. For example:

  • Entity 220 (New York): Controller_North.
  • Entity 120 (Houston): Controller_South.
  • Entity 210 (Los Angeles): Controller_South.
  • Entity 250 (San Francisco): Controller_South.
Configure the ForEach subprocess

In the ForEach subprocess, use the {Subprocess.PropertyName} syntax to dynamically assign tasks based on the property value.

For example:

  • Owner: {Subprocess.WFContributor}.
  • Supervisors: {Subprocess.WFContributor}.
  • Contributors: {Subprocess.WFContributor}.
Execute the ForEach process

When the ForEach process executes, the tasks will be assigned to the appropriate roles based on the WFContributor property value.

For example:

  • Controller_North for entity 220 (New York).
  • Controller_South for entities 120 (Houston), 210 (Los Angeles), and 250 (San Francisco).

Use Workflow Subprocess syntax when calling Data imports and exporting Model Views

Use the above techniques when specifying Data Import Definitions in File Import tasks and when specifying Model Views in Model Export tasks in ForEach subprocess.

  • Single Role per Entity:
    • Use the {Subprocess.Name} syntax to assign tasks to roles named after the entities.
    • Use the {Subprocess.Name} syntax to specify Data Import Definitions in File Import tasks.
    • Use the {Subprocess.MemberCaption} syntax to specify Model Views in Model Export tasks.
  • Multiple Entities per Role:
    • Create a property, for example, WFContributor) for each entity.
    • Assign role to the property for each entity.
    • Use the {Subprocess.PropertyName} syntax to assign tasks based on the property value.
    • Use the {Subprocess.PropertyName} syntax to specify Data Import Definitions in File Import tasks.
    • Use the {Subprocess.PropertyName} syntax to specify Model Views in Model Export tasks.

This approach ensures that tasks, Data Import Definitions, and Model Views are assigned correctly and efficiently, even when multiple entities are involved.