This documentation supports the 22.1 version of BMC Helix ITSM.To view an earlier version, select the version from the Product version menu.

Completing steps

Dataload jobs are run according to the defined set of steps that are composed to run in a sequence. You can choose to use the steps that are provided out-of-the-box or create custom steps. 

The following table describes the steps available for a standard out-of-the-box-job:

Related topics

Creating-and-managing-data-load-jobs

Data-Management


Step

Behavior of the steps

Load step

The Load step imports your data from the source files to the data load staging forms.
This step leverages Atrium Integrator jobs, which integrate source and target data stores with data transformation based on specific rules.

The DMT User or DMT Admin provides the source location and connection information that the Atrium Integrator adapter uses for the transformation process.

Data can be imported to one or more staging forms in one Load step. For example, a Load step can import company and company alias data from a Company.xlsx spreadsheet to two different staging forms.

Load step imports your data from your source files to the staging forms by performing the following tasks:

Validate step

When you decide to run a dataload job, the data load is automatically validated. The validation of data occurs before the data is promoted. Each Validate step represents the validation of data for one staging form.

Validate step validates staging form data y performing the following tasks:

Promote step

The Promote step either automatically or manually pushes all staging form records that are valid to their respective target forms within the BMC Helix ITSM applications, based on the option selected for each Promote step within the job.

Each Promote step represents a data promotion for one staging form. You can also choose automatic or manual promotion when you configure your application preferences for all jobs. For more information, see Configuring-Data-Management-application-preferences.

Data must be validated without error before it can be promoted. All errors are captured in the Error Management console. For more information about using the Error Management console, see Managing-data-errors-from-data-load-jobs. If you selected the Create Only mode for the Validate step, the related Promote step only creates new records in the target forms. If you did not select the Create Only mode, the new records are created in the target forms and the existing records are updated according to the following points.

Knowledge Managementfollows these rules when articles with multiple versions are promoted:

  • If an article has multiple versions, and the newest version is in a Draft state.
  • The article with a version that precedes the newest version is promoted with a Published state.
    All the articles with a version less than that is promoted with a Closed state.
  • If the newest version of an article is in the Published state, all the articles with a version less than the newest version will be promoted with a Closed state

For more information about the steps, see the following video (4:25):

icon-play.pnghttps://youtu.be/Qc1FZSzeUyk

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*