Custom forms: supported examples
The custom form feature can be used to customize standard, delivered forms and custom forms. This topic describes capabilities through examples where the feature can be used to maximize the utility of your organizations forms.
Making a system-delivered field required
You can make a system-delivered field required by using conditions that you define. To require a field, you must modify the entrance rules for the UpdateTransitionTaskData action within ResourceTransitionTask. Add logic to make the field required on conditions. You can add any one of three types of conditions:
- a condition for the form or field
- a constraint that field has been completed
- a message that is shown when the field is not completed
Making a user field required
You can make a field required by creating a condition that contains one or more rules. When you create the user field in ResourceTransitionTask, use the Conditionally Required option. Select a condition for the form on which the field is required. To make the field required using on multiple factors, build a condition that includes all of the required rules.
Configurinng ResourceTransitionTask business class only
Examples where data are not required to be stored on a candidate record or resource record after task completion:
| Example | Field | Form |
|---|---|---|
| Collect allergy information on the Personal Information form | User/System ResourceTranstionTask | System |
| Collect allergy information on a custom form | User ResourceTransitionTask | User |
| Collect EEO information on the Personal Information form | System ResourceTransitionTask | System |
System-delivered business class with relationship to ResourceTransitionTask
Examples where the data must be stored on a candidate or resource after task completion. A relationship must already exist between the destination business class and ResourceTransitionTask.
| Example | Field | Form |
|---|---|---|
| Collect employee data that exists in the system on the Personal Information form | System Emp/User ResourceTransitionTask | System |
| Collect employee data that exists in the system on a custom data form | System Emp/User ResourceTransitionTask | User |
| Collect new employee data on thePersonal Information form | User Emp ResourceTransitionTask | System |
| Collect new employee data on a custom form | User Emp ResourceTransitionTask | User |
System-delivered business class without relationship to ResourceTransitionTask
Examples where the data resides in a business class that does not have a relationship with ResourceTransitionTask:
| Example | Field | Form |
|---|---|---|
| Collect EmployeeBenefit data that exists in the system on the Personal Information form | System EmpBenefit/User ResourceTransitionTask | System |
| Collect EmployeeBenefit data that exists in the system on a custom form | System EmpBenefit/User ResourceTransitionTask | User |
| Collect new EmployeeBenefit data on thePersonal Information form | User EmpBenefit/User ResourceTransitionTask | System |
| Collect new EmployeeBenefit data on a custom form | User EmpBenefit/User ResourceTransitionTask | User |
User-defined business class without relationship to ResourceTransitionTask
These are examples of situations where the data that is collected on system-delivered or custom transition forms is not contained in the system:
| Example | Field | Form |
|---|---|---|
| Collect allergy data on the Personal Information form | User Allergy/ResourceTransitionTask | System |
| Collect allergy data on a custom form | User Allergy/ResourceTransitionTask | User |