Build Factory Process Node

A Build Factory node is a Production process node that runs a factory configuration file or measures scripts, which creates cPlans and cBases per data set, as described in the script.

Production Build Factory node

The Build Factory node has Closedfour panes where you set attributes.

Production Build Factory node panes

You set attributes for the Build Factory node in the Closedattributes pane.

Production Build Factory node attributes

Attribute Description
Name Supply a descriptive name for the node (lower case recommended to maximize space).
Failure type Specify how to handle a Build Factory node failure:
  • Set to Any by default (recommended) causes the node to fail if any of the listed scripts fail.
  • If set to Any with a Failure node set (see below) and one of the scripts fails, the task flow goes to the Failure node.
  • If set to All, the task flow stops only if all the scripts fail; otherwise it continues onto the next node.
File with list of scripts
(Required if no Factory Config Files attribute is set)

Specify a text file that contains the names of the script or scripts (on separate lines) to be run. Use the browse button (...) that appears when you click in the empty field.

Use this attribute or the Factory Config Files (see below) attribute as they are mutually exclusive.
Simultaneous Define the maximum number of script files to process at the same time: 
  • 0 or Blank—When set to 0 or blank, the number of simultaneously run files depends on the number of available processors.

  • 1 (Default)—When set to 1, all files run sequentially, one at a time.

  • 2, 3, 4, or More—If more files than processors are specified, the files run in the order that they are listed.

Skip Test Dive

If set to False, a test dive generates after a build completes.

If set to True, no test dive is created.
Custom Success State Rules Opens the Edit Custom Output Filters dialog box where you can define a custom warning state (Failed/Succeeded/Warning) based on text found in the node's output. See Custom Output Filters
Email Object for failure Set to have an email sent to a predefined mailing list if the node fails. The drop-down list is populated with items from the Email Template section of the Mailing Lists tab of the Project Settings tab (see Mailing Lists Tab).
NOTE: These Email Objects are referred to as Email Templates in Project Settings > Mailing Lists.
Email Object for success Set to have an email sent to a predefined mailing list if the node succeeds. The drop-down list is populated with items from the Email Template section of the Mailing Lists tab of the Project Settings tab (see Mailing Lists Tab).
NOTE: These Email Objects are referred to as Email Templates in Project SettingsMailing Lists > Mailing Lists.
Email Object for warning Set to have an email sent to a predefined mailing list if the node generates a warning. The drop-down list is populated with items from the Email Template section of the Mailing Lists tab of the Project Settings tab (see Mailing Lists Tab).
NOTE: These Email Objects are referred to as Email Templates in Project Settings > Mailing Lists.
Failure node Set next node upon failure. The drop-down list contains all nodes placed on the Task Flow.
Success node Set next node upon successful completion (automatically fills if a connecting line is set on the Task Flow). The drop-down list contains all nodes placed on the Task Flow.
Working Directory Set the directory this node executes in. Sets the Working Directory for this node only—leave blank for the default. This overrides the setting in the Start node for a Default Working Directory (see Start Control Node).
Default Working Directory Display-only field showing the Default Working Directory set in the Start node (see Start Control Node). Appears blank if not set.
External File Encoding

Set file encoding for input files coming into the node. If left blank, Workbench attempts to auto-detect the encoding.

Also used when saving logs and may need to be adjusted when using data with high bit Latin-1 characters or Unicode characters.

Each node has an area where you can enter comments.

It is a DI best practice to enter a note for every node in a Production script. These notes can help you or a coworker understand the intent of the node and troubleshoot issues in the future.

Specify one factory configuration file (factory) or one or more measures script files (measure) in the ClosedFactory Config Files panel (bottom left).

Factory Config Files pane

When specifying a single factory configuration file (factory), a special Measure Factory license is required.
Additional control attributes allow more detailed control of settings per file than if using the File with list of Factory Config Files attribute. These attributes include:

  • Disabled—Allows you to disable specific Measures scripts, which may be useful for debugging (defaults to no). Not applicable to factory configuration file.
  • Failure Type—Allows you to set how to handle an individual Measures script file failure: Fail, Never, or Warning (defaults to Fail). Not applicable to factory configuration file.

Use this attribute or the File with list of Factory Config Files attribute (see above) as they are mutually exclusive.

Define parameters in the ClosedParameters panel (bottom right) for this node.

Production Build cBase Parameters

NOTE: Node-level parameters are available only for the current node.
See Parameters in Production for more information.