41-50

Who can configure the approval workflow for the offer? Note: There are 2 correct answers to this question. Operators with permission to launch the Offer Approval in the respective applicant status if the approval workflow is configured as editable. Users with permissions to configure the Offer Details template within Manage Recruiting templates. System admins with permission to "Manage Route maps" in the Admin Center. Users with permissions to Manage Offer Letter Templates in the Admin Center.

How do you define permissions for job requisition fields? Note: There are 3 correct answers to this question. Assign a permission to a field for each status (pre-approved approved and closed). Add the operators for each permission block. Permission the J role for each field. Set the permissions to write or read for each field. Define the permissions in the Role-Based Permissions section in the Admin Center.

The (S) Sourcer operator has a field permission taken away but the V operator gives permission to that field. The (S) Sourcer is an approver in the Route Map. What is the result?. The V permission overrides the taken away S permission. The V permission causes the S permission to only allow for reporting of the field in question. It depends on the order in which the permissions were configured. It depends on the order in which the permissions were configured. The V permission is irrelevant in this situation.

You need to set up a route map step where the Hiring Manager reviews a job requisition during the creation process. This hiring manager does NOT necessarily need to be the person who creates the form. What needs to be configured in the first step of the Route Map? Note: There are 2 correct answers to this question. The Originator role needs to be added to the modify step. The Hiring Manager (G) needs to be added to the modify step. The modify step needs to be configured as a single role type. The modify step should be configured as an iterative or collaborative step depending on the requirements of the customer.

Which of the following standard objects CANNOT be configured in the Job Requisition template?. Position. Location. Division. Offer. Type.

You have updated a standard field label in the Job Requisition template. However this change was NOT reflected when creating a new job requisition. What must be configured? Note: There are 2 correct answers to this question. The field label must be updated in the permission section of the Job Requisition template. The field label must be updated in Custom Token Settings in Provisioning. The new field label must be updated in Job Requisition System Field Labels in Provisioning or Admin Center. The field label must be updated in the Job Requisition template field definition.

Which fields have a pull-down or "find value" where the values are configured directly in the Job Requisition field definition?. Instruction. Enum. Derived. Bool.

How do you make custom fields reportable? Note: There are 2 correct answers to this question. Define the fields as reportable in the template. Add the fields in Provisioning and synchronize the data. Define the public="true" attribute in the template. Define the fields in the template.

In order to associate a Job Requisition to an approval workflow what must be done? Note: There are 2 correct answers to this question. The Job Requisition must be associated to the appropriate Route Map in Form Template Settings. A Route Map must be created and configured in Admin Center. A business rule to trigger the approval workflow must be created in Admin Center > Configure Business Rules. Multiple Route Maps can be associated to one Job Requisition template.

Which field types in the Requisition template designate the dropdown values that can be found in Admin Center? Note: There are 2 correct answers to this question. Picklist. Enum. Derived. Text.