Oracle Field Service Implementation Professional flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Resource type vs user type

Resource type controls field-work capability and assignable activity types; user type controls application UI access and permissions. Both are assigned to a person and serve different purposes.

Custom property scoping

Properties are defined per entity - resource, activity, work order, inventory, service request - and are not shared across entities. A same-named property on two entities is two independent definitions.

Enumeration property list

A property whose allowed values come from a centrally maintained named list. Adding a value to the list makes it selectable wherever that list is referenced, without editing each property.

Screen configuration effect

Determines which properties and fields appear in the resource's UI. A populated property not placed on a screen is invisible to the field resource, so screen design gates data visibility.

Business rule trigger timing

Rules fire on defined events such as activity create, move, or complete. Conditions are evaluated at that moment only, so rule order and event choice determine the outcome.

Configuration promotion

Moving validated type, property, and rule changes from a test instance to production. Configuration is not automatically versioned, so changes must be exported or documented before promotion.

Quota vs filter

Filters exclude candidate resources from receiving an activity. Quotas cap how much work a resource can take by type or property value. Filters remove candidates; quotas limit load.

Integration user permissions

API calls authenticate as a configured user, so that user's type and permissions bound what the integration can read or write. There is no separate unrestricted integration account.

Routing eligibility triad

A resource is a routing candidate only if its work zone covers the activity location, its skills meet the required skills, and it has available work time that day.

Work zone hierarchy

Zones nest: a parent zone includes all child zones. Assigning a resource to a parent makes it eligible for activities anywhere beneath it, so zone design directly widens or narrows coverage.

Work skill rating and ratio

Skills carry a rating, often 1 to 10, and a ratio. Routing can require a minimum rating, and the ratio affects how much of the resource's capacity the skill consumes.

Routing plan vs dispatch

A routing plan run assigns bucket activities to resources on a schedule. Dispatching then sends the assigned work to the resource. Assignment and dispatch are separate steps.

Bucket vs scheduled activity

Bucket activities are unassigned work awaiting routing. Scheduled activities have a resource and time slot. A routing run moves work from bucket to scheduled.

Capacity planning inputs

Available work time per resource per day, minus time off and non-working days, compared against total required activity minutes including travel and overtime modeled explicitly.

Crew assignment constraint

Multi-resource activities require every crew member to be available for the full duration. If any member is only partially available, the crew cannot take the assignment.

Routing reassignment limits

Routing options decide whether already-assigned activities can be moved. Activities already in progress are normally excluded from reassignment regardless of plan settings.

Work order vs activity

The work order is the customer-facing container; the activity is the schedulable unit assigned to a resource. One work order can hold several activities, and activity status drives work order status.

Activity status model

Statuses progress from pending through started or en route to completed, with not-done and cancelled branches. Transitions follow the activity type's model and cannot be skipped arbitrarily.

Activity type duration change

Editing an activity type's duration affects activities created after the change. Activities already scheduled keep their existing duration unless individually updated.

Service request conversion

A service request captures intake data via its request type. Converting it creates a work order and activities, with property mapping between request and work order configured in advance.

Required inventory effect

Inventory required by an activity type is reserved or consumed when the activity is scheduled or completed. Insufficient stock can block completion depending on configuration.

Activity link constraints

Predecessor and successor links prevent a successor from being scheduled before its predecessor completes. Same-time links force simultaneous assignment of linked activities.

Time window enforcement

Routing must place an activity inside its time window. A missed window yields a late activity that routing may flag but does not always correct on the next run.

Mass update rule bypass

Bulk status or property changes can skip business rules that fire on individual edits. Validate rule-dependent fields after a mass update completes.

Outbound message retry

Outbound messages are delivered to a configured endpoint and retried on failure. Endpoints must therefore be idempotent so repeated delivery does not create duplicate records.

API client authentication

Integrations authenticate as a configured user through an API client. Tokens are issued per client, and the user's permissions limit accessible objects and operations.

Property type validation

Inbound records must supply property values matching each property's declared type, such as integer, date, or enum. A mismatch causes the record to be rejected.

Message scenario payload template

Outbound payloads are templates with explicitly selected fields. Adding a property to an object does not add it to existing messages, so templates need updating.

External ID idempotency

Supplying a stable external identifier on create lets retries update the existing record instead of duplicating it. Essential for reliable at-least-once integration delivery.

Time zone conversion boundary

Store times in the instance time zone and convert at the integration boundary. Activity time zone derives from resource or location, and mismatches cause off-by-hours scheduling errors.

Message queue backlog

A growing queue backlog signals a slow or failing consumer rather than a producer problem. Monitor backlog depth and failed retries as the primary integration health signal.

Bulk import validation

CSV or bulk loads are validated for required fields and referential integrity. Failed rows are reported individually rather than silently discarded, so the report must be reviewed.