1z0-1003-22 Practice Exam Questions with Answers Oracle Field Service 2022 Implementation Professional Certification

Set the reoptimization goal to "Reduce Overdue". Then, using routing filters, set the cost of not assigning 'Meter Read activities in existing routes to 'High',and the cost of not assigning 'New Connect' activities in the routing bucket to 'Normal'.

Set the reoptimization goal to 'Assign high priority activities'. Then, using routing filters, set the cost of not assigning 'Meter Read activities in existing routes to 'High', and the cost of not assigning 'New Connect' activities in the routing bucket to 'Low'.

Set the reoptimization goal to 'Assign high priority activities'. Then, using routing filters, set the cost of not assigning 'Meter Read activities in existing routes to 'Low', and the cost of not assigning 'New Connect' activities in the routing bucket to 'High'.

Set the reoptimization goal to 'Assign high priority activities'. Then, using routing filters, set the cost of not assigning 'Meter Readactivities in existing routes to 'Highest', and the cost of not assigning 'New Connect' activities in the routing bucket to 'Normal'.

Create a 'start-after' link template between the preliminary work and the scheduled work.

Select the 'Prework' action from within the activity record in Oracle Field Service Cloud (OFSC).

Add a new 'Prework' custom property to the'Edit/View activity' context in Oracle Field Service Cloud (OFSC).

Create a 'start-before' link template between the preliminary work and the scheduled work.

Routing may assign activities to them, but contingent workers will not be included in quota calculations.

Contingentworkers cannot participate in Teamwork within OFSC.

Contingent workers' reported activity durations are not factored into company-wide statistics and estimations.

Contingent workers will be included in quota calculations, but routing will not assignactivities to them.

Contingent workers will be removed from the OFSC system if they have not activated a route m twelve continuous months.

OFSC will set the start date depending on the Customer contract rules set within OFSC.

OFSC will not create the activity, and an error will be returned in the API response.

OFSC always uses the Activity Creation Date as the SLA start date.

OFSC will use the Activity Creation Date as the SLA start.

OFSC will use available capacity to determine the most suitable start date.

'send_request'

'change_activity'

'create_request'

'create_activity'

Routing will notassign that activity to John Smith due to a soft skills mismatch.

Routing will not assign that activity to John Smith due to a work skills mismatch.

Routing will consider assigning that activity to John Smith because if a resource has no specific work skills designated on their record, they are assumed to have all skills at levels of 100.

Routing will only consider assigning that activity to John Smith if no other resources in the bucket have the 'Installation' work skill directly designated on their records either.

Delivery Windows are calculated for all Activity Types by default.

Delivery Windows are enabled per Resource Type calculations.

Delivery Windows are configurable by size and granularity by Activity Type.

Delivery Windows are configurable by size and granularity as a global setting in OFSC.

Delivery Windows are enabled and calculated per Activity Type configurations.

The activity turns red and a Resource Tree warning appears.

The activity turns red, a Resource Tree warning appears, and a message scenario is launched (if configured).

The activity turns red

A Resource Tree warning appears and a message scenario is launched (if configured).

Shifts can be used within a variety of work schedules.

Nonworking time is used to identify known absences such as vacations or holidays.

Nonworking reasons are set by default and cannot be modified.

Holidays for calendars are defined using the configuration option of Holidays.

Work Schedules can contain combinations of shifts and nonworking times.

Working time can contain multiple work schedules.

Ensure that the Senior Administrator's assigned User Type has access to the appropriate Configuration screen icons.

Create a subscription via the Core REST API to include all 'configurationUpdated' events.

Ensure that the Senior Administrator’s assigned User Type has access to the Configuration History report within Core Manage.

Create a subscription via the CoreREST API to include all 'configurationChangesMade' events.

broadcast messages to users based on their assigned Collaboration group(s)

broadcast messages to users based on their proximity to a location on the map

broadcast messages to users based on their compliance with Smart Location settings

broadcast messages to users based on their matches to an activity's work zone, work skill, and timing requirements

broadcast messages to users based on their assigned Help Desk(s)

broadcast messages to users based on their assigned User Type

Planned capacity can only be set if the capacity area is configured to manage booking based on time slot.

Planned capacity can be set at the day level only for a given capacity area and it's organization units.

Planned capacity can be automatically calculated by entering the preferred variance as compared to available capacity.

Planned capacity can be entered either by resources or capacity (days, hours, minutes) depending on what is configured in the 'Working time unit' parameter.

Planned capacity can be set at the day, capacity category and time slot levels for a given capacity area and it's organization units.

An SLA window indicates when an activity should be completed.

An SLA window indicates how long an activity should take to complete.

An SLA window indicates that there is enough time available within it to perform an activity.

An SLA window indicates when an activity should start.

An activity dragged and dropped into a Collaboration chat with a resource must be accepted by that resource in Oer for it to be assigned.

An activity broadcasted via Collaboration as part of an Immediate routing plan schedule gets assigned to the first technician to accept it.

An activity broadcasted via Collaboration as part of any type of routing plan schedule gets assigned to the first technician to accept it.

An activity dragged and dropped into a Collaboration chat with a resource can be automatically assigned without the resource having to accept It.