Steps can have substeps, however substeps are not required.

Steps have defined criteria to control the region of data, opening of steps, review criteria, and reopening of steps if required.

If a step has no substeps, you must associate at least one action with the step. If a step has one or more substeps, you associate actions with the substeps, not with the step itself.

All steps and substeps can have more than one action associated; the primary action is the launch action, the additional actions appear in the action pane when the primary action is launched.

Steps may require approval by a reviewer before the system considers the BPF step complete. Substeps are not subject to approval criteria.

You must perform steps in sequential order, but you do not need to perform substeps in sequential order. You do not need to complete all substeps to complete a step.

Each step is assigned a driver dimension, which determines the generation (iteration) of the step by region of data. The driver dimension assigned to the step also defines the owner and reviewer property for each step region. The owners and reviewers can be modified when you create a BPF instance.

The BPF instance owner can finalize the BPF only when all steps are completed.

Up to one thousand steps per BPF template/instance can be defined.

Up to one million step regions per BPF instances can be defined. The step regions can be calculated as a product of the number of steps and number of regions.