Let’s look at how you configure a rule for responsive pages in the Transaction Design Studio (TDS).
Parameters that determine when and for whom the rule is applied
Parameters vary according to the selected action. You can set all, some, or none of the parameters. When evaluating the rule at runtime, the application ignores the criteria for parameters that you haven't set. You can select multiple values for some parameters. Here is a list of parameters that you can use to configure a rule.
- Role: User security roles assigned for performing the action or viewing the page. This LOV shows all delivered and custom security roles.
- Legal Employer: Legal employers being acted on.
- Country: Used when the legal employer doesn’t fully support the requirement to create rules by country.
- Legislative Data Group: Used when the legal employer doesn’t fully support the requirement to create rules by country.
- Business Unit: Used when the legal employer doesn’t fully support the requirement to create rules by country.
- Worker Type: Worker types being acted on such as contingent worker, employee, nonworker, offer, and pending worker.
- When is the rule applied? View other’s info or Viewing own info is used when the page you're configuring is available to both workers and other users, such as HR specialist.
- Action (HCM): Available for transactions that use actions such as Create and Edit Job Offers.
- Recruiting Type: Recruiting types of the job requisition or the job requisition related to the object being acted on.
- Site Name: Name of the external candidate experience site that external candidates use to search and apply jobs.
- Application Flow Name: Name of an application flow that is used for external candidate's job application, requesting additional information or talent community sign-up.
- Performance Document: Name of the performance document as defined in the performance template.
Show or Hide Regions
This section applies to actions that include different sections. For example, Promote, Transfer, and Hire an Employee actions use the guided process design, which includes various sections of specific information. The Show questionnaire page field is set to Yes for actions that use the guided process. This allows users to mandate and show or hide the regions that they want to manage during the transaction.
TDS configuration rules take precedence over any other setting. If you enable the profile option Questionnaire Displayed in Guided Processes (HCM_TASK_CONFIGURATOR_RESPONSIVE_ENABLED) to show the questionnaire, it will display in the transaction page. Later, if you create a rule to hide the questionnaire it will be hidden even if the profile option is enabled. If you hide the questionnaire page, you navigate directly into the transaction details page to complete the transaction.
This section is shown even for actions that don’t use the guided process design but have different sections of information. You can rename a section, hide sections that aren’t delivered as required, and make optional sections required.
You can improve the quality of your data by ensuring that your users complete the required fields before submitting the transaction. For example, the Payroll Details and Salary sections are required in the Hire an Employee flow. When you initiate the process, Payroll Details and Salary aren’t displayed as options on the questionnaire because they are already part of the guided process. You need to complete these required sections before submitting the transaction. You can change the severity of the message from a warning to an error for some actions, to ensure that the required information is provided.
You set up required sections from the Reference Info Regions in the Page Attributes section in the TDS. Click the Show error message for mandatory sections that haven’t been viewed option to show an error message when the required sections aren’t visited. You can see a warning message if you configure sections as required in the TDS but don’t visit the mandatory sections in employment flows.
When an action or page includes regions, you select the region to see a list of available attributes on the Page by Region. When attributes are read-only, there’s no option to change the required setting. You can’t add new attributes to a page, but you can hide fields not delivered as required, make delivered optional fields as required, and enable descriptive flexfields segments.
A flexfield attribute is identified by a pencil icon. A point to note is that when a flexfield is defined as a check box, making the attribute mandatory will not force the user to select the check box. There’s always a value stored for each state of the attribute, whether selected or not. To enable a flexfield that’s already been compiled, click the pencil icon. For Employment or Contract pages, you can also decide which segments under a specific context are hidden or displayed. This doesn’t apply for Person pages.