Custom forms: considerations and requirements

Transition Management supports collecting data from external candidates during preboarding and resources post-hire.

Considerations for custom form data mapping

Custom forms can be used to collect data for candidates and resources. We recommend that custom forms be used to gather data for candidates or resources, not both, when possible.

We recommend that the hire process be updated to map custom data from the candidate-related business class to the resource-related business class under these conditions:
  • When a form is used to collect data during the preboarding of a candidate
  • and that data must be maintained for the resource long-term.

Custom user fields

User fields must be added to the ResourceTransitionTask business class. The existing business class that is related to the candidate or the resource is not required. The user business class that is related to the candidate or resource is not required.

All fields that are used in custom or system-delivered Transition Forms must be added to the ResourceTransitionTask business class. This applies even when the field is ultimately stored in a candidate-related or resource-related business class.

Custom user field names

Field names across business classes must be consistent. When building a custom form using fields outside of ResourceTransitionTask, always name fields consistently with the owning business class. This way, fields are correctly displayed and saved back to the business class. This applies when adding user fields to ResourceTransitionTask from business classes that already have a relationship to ResourceTransitionTask. It also applies to those that do not yet have a relationship.

When adding fields from another business class, you must configure an action in ResourceTransitionTask to ensure that data is saved.

See Configure Exit Rules for UpdateTransitionTaskData for details.

Guidelines for user forms

Transition Management uses the ResourceTransitionTask business class to collect data from candidates and resources.

All custom forms must be created as user forms in ResourceTransitionTask. Each user form can contain ResourceTransitionTask system-delivered fields and ResourceTransitionTask persistent user fields,

See Custom forms: supported examples.