Workflow and ServiceDesk Community

 View Only

Wait For All Workflow Components (Merge) 

Jun 13, 2012 10:29 AM

Wait For All Workflow Components (Merge)

Component definition

This component waits for all workflow components (found in Workflow Components component toolbox path) to complete in any model in this workflow. You should never use more than one of these in a single Project.

Component Toolbox Path: Workflow Components > Merge

This component is only available in a Workflow project.

Component icon

[Insert component icon image file here.]

Description of component output paths

The component output paths are described in the following table:

Property

Description

done

When all workflow component, in any model in this workflow, have completed, the workflow follows this output path.

Description of component tabs and their properties

The properties on the Passive Merging tab in the Wait For All Workflow Components (Merge) component are listed and described in the following table:

Property

Description

Check Passive Completion

Lets you check for the termination of workflow components in any model in this workflow.

Do not uncheck this option unless you have all paths terminating into this component.

Check Time Span

Lets you set the time to wait between system checks.

The system checks repeatedly to see if all workflow components have completed execution.

The system checks repeatedly to see if all workflow components have completed execution. The system waits a certain amount of time (Check Time Span) between checks

The properties on the Settings tab in the Wait For All Workflow Components (Merge) component are listed and described in the following table:

Property

Description

Component Class Name

The class name of this component. This property is not editable, but useful if you call Symantec support.

Description

The description of this component. This property lets you describe how the component is used. You can use it to provide any wanted documentation for this component.

This description is included in the model reports that are created when you click Plugins > Generate Business Model.

Location

The physical location of the top left point of this component on the workflow model.

Name

The name of this component. You can change the name.

If you changed the component name when you double-clicked it on the workflow model, the changed name appears here.

Override Background Color

This property lets you change the background color of this component.

To Do

This property lets you record what you still need to do with the component. Use this property to help you remember the configuration that you want to apply to this component.

The text that you enter for this property appears at the bottom of the component editor. If you enter text for this property, a checklist symbol appears on the component in the workflow model.

Web Service Name

The name of the Web service. You can change the Web service name.

Is Enabled

This property lets you enable or disable the component. By default, components are enabled. When a component is disabled, it has no effect on the Project. Uncheck Is Enabled to disable the component.

  • Execution Outcome

    If a component with more than one outcome path is disabled, you must select which outcome path you want the component to take. Click the Execution Outcome drop-down list and select the outcome path for the workflow to follow.

  • Disabled Mapping

    If the component has output parameters, you must configure all output parameters with fixed data to pass on. This configuration can be performed in the Disabled Mapping option.

The properties on the Merge Data tab in the Wait For All Workflow Components (Merge) component are listed and described in the following table:

Property

Description

Merge Type

Lets you handle process data. If you handle global data under the Merge Data tab, you must map the data changes back into the global variables.

Merge Type options:

  • NoMerge

    No data is merged. The data from the last thread is used, and all other data is lost.

  • SimpleMerge

    All incoming branch data is exposed.

    Variables with the same name overwrite each other, but the distinct variables from the branches are retained.

  • ModelMerge

    Lets you create a data merge model.

Data Merge Model

Lets you create a data merge model.

While in this model, a variable called _Previous_Run_Data_ is available. The _Previous_Run_Data_ variable contains the previous run data on all available variables in the Project. It does not contain the current data from all available variables in the Project.

The properties on the Merge Global Data tab in the Wait For All Workflow Components (Merge) component are listed and described in the following table:

Property

Description

Global Data Merge Type

Lets you handle global data. These settings read and write directly to the Project global data.

Global Data Merge Type options:

  • NoMerge

    No data is merged. The data from the last thread is used, and all other data is lost.

  • SimpleMerge

    All incoming branch data is exposed.

    Variables with the same name overwrite each other, but the distinct variables from the branches are retained.

  • ModelMerge

    Lets you create a global data merge model.

Global Data Merge Model

Lets you create a global data merge model.

While in this model, a variable called _Previous_Run_Data_ is available. The _Previous_Run_Data_ variable contains the previous run data on all available variables in the Project. It does not contain the current data from all available variables in the Project.

Connection information

[If this component connects to a process or product outside Workflow, insert the definition of the connection string and/or authentication requirements to make that connection.]

Component settings

[Describe any setting options that change the way this component behaves.]

Use cases

[Name each use case that you include below.]

Example use case 1

[Describe the use case. Insert screen shots or package files. Insert a description of how the settings are configured. Insert additional information about the use case.]

Example use case 2

[Describe the use case. Insert screen shots or package files. Insert a description of how the settings are configured. Insert additional information about the use case.]

Statistics
0 Favorited
1 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Related Entries and Links

No Related Resource entered.