Guidelines for Loading Checklist Templates

You use a checklist template to define a sequence of related tasks with multiple performers, such as those for onboarding a new worker.

For example, you can create a checklist template for new hires, with tasks for providing system access, issuing badges, allocating parking space, and so on. This topic describes how to create and maintain Checklist Template objects using HCM Data Loader.

Checklist Categories

The checklist category must exist in the CHECKLIST_CATEGORY lookup for the target environment. In the Setup and Maintenance work area, use the following to manage checklist categories:

• Functional Area: Workforce Information

• Task: Manage Checklist Lookups

The combination of checklist name and checklist category must be unique. Enterprise Onboarding Step checklists must either already exist in the target environment or be in the same .dat file as Enterprise Onboarding checklists that reference them.

Checklist Tasks

These rules apply to checklist tasks:

• Checklist task names must be unique for the checklist.

• If the current task has a preceding task, then the preceding task must be loaded before the current task can be created.

• When you create tasks of the type Configurable Form, the descriptive flexfield context must have been configured in the target environment.

Checklist Actions, Areas of Responsibility, and Eligibility Profiles

If you plan to use actions in the checklist template, then those actions must exist in the target environment.

If you plan to use areas of responsibility to identify task performers, then responsibility types must exist in the PER_RESPONSIBILITY_TYPES lookup in the target environment. Alternatively, you can use one of the values shown in this table.

Value	Meaning
ORA_LN_MGR	Line manager
ORA_WORKER	Worker
ORA_INITIATOR	Initiator

The default performer is the line manager.

If you plan to use eligibility profiles in the checklist tasks, then those eligibility profiles must exist in the target environment.