OCI Digital Assistant Professional flashcards

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

Digital assistant vs. skill

A digital assistant routes utterances across one or more skills and owns global interruptions; a skill contains its own dialog flow, intents, entities, and backend integrations.

Skill routing precedence

The digital assistant checks its own intents first, then routes to skills by confidence; explicitly naming a skill in the utterance overrides automatic confidence-based routing.

Immutable versions

A published digital assistant or skill version is a fixed snapshot; to change production behavior, clone the version, edit the clone, and republish.

Draft versus published

The draft is the editable working copy used by the skill tester; published versions are what channels and downstream assistants actually consume at runtime.

Global interruptions

Interruptions configured at the digital assistant level, such as cancel or start over, apply across skills; skill-scoped interruptions stay inside one skill's flow.

Variable scoping

Digital assistant variables are shared across skills; skill variables are local to that skill unless explicitly mapped into a shared variable.

Composite bag entity

A composite bag groups several related entities into one resolution unit, reducing flow state count and centralizing prompts and error handling.

Default transition requirement

Every dialog flow state needs a reachable default transition or error handler; otherwise the runtime raises a routing error when no condition matches.

Intent utterance count

Aim for roughly 10-20 varied training utterances per intent; overlapping utterances across intents lower confidence and should be merged or disambiguated.

Confidence threshold

Utterances scoring below the skill's confidence threshold route to unresolvedIntent; raising the threshold reduces false positives but increases fallbacks.

Entity type categories

Value-list entities enumerate allowed values, regex entities match patterns, and derived entities compute values from other entities during resolution.

Resolution order in bags

Composite bag entities resolve their members in a configurable order; placing the most discriminating entity first lets partial matches fail fast.

Flow state anatomy

A dialog flow state has an optional entry action, prompt, post-action, and transitions; a state with no matching transition errors at runtime.

FreeMarker expressions

Dialog flow text and conditions use Apache FreeMarker syntax such as ${variable}; the flow variable is always available, and error is populated in error handlers.

Built-in system entities

System entities such as system.date, system.time, system.number, system.currency, and system.person resolve common values without custom training, though locale settings may be needed.

maxPrompts and maxAttempts

These bound retries during entity resolution and prompting; exceeding the limit transitions to the configured next state or an error handler.

REST service definition

A REST service holds the base URL, authentication, and timeouts; custom components reference it and map dialog variables to request and response fields.

Custom component schema

Each custom component declares a name, version, and property schema; the dialog flow must satisfy that schema or validation fails at design time.

REST authentication options

Supported REST service authentication includes basic auth, OAuth 2.0 client credentials or authorization code, and API keys in headers or query parameters.

Backend error mapping

Map HTTP 4xx and 5xx responses to explicit transition states via the component's error action instead of letting the flow crash.

Service timeout tuning

REST services expose connection and read timeouts; default read timeouts are short, so long-running backends need explicit increases to avoid spurious failures.

Component package export

Custom component packages export as a zip containing the component definition and service metadata; target-environment credentials are not included and must be re-entered.

Entity event handlers

Event handlers on entities can call custom components to validate or transform a resolved value, such as looking up an account ID, before the flow proceeds.

Bag versus chained components

For multi-turn collection of related fields, a composite bag entity keeps state count and error handling simpler than a chain of separate custom components.

Channel attachment

Channels such as web, Slack, Teams, and Twilio SMS attach to a published digital assistant version; changing channel configuration requires republishing.

Channel secrets rotation

Signing keys, bot tokens, and webhook URLs are stored per channel; rotate them in the channel configuration rather than embedding them in dialog flows.

Web channel authentication

The web channel authenticates with a JWT or OAuth token from the identity provider; configure explicit allowed origins for CORS instead of a wildcard.

Role-based access

The digital assistant administrator role manages channels and publishing; the developer role edits skills but cannot promote them to production.

Deployment path

Develop in draft, test with the skill tester, publish a version, attach channels, then promote environments by exporting and importing the assistant package.

Credential handling on import

Secrets and connection credentials reside in the identity domain or a vault, not in exported packages; re-enter them after importing into a new environment.

Conversation transcript retention

Enable channel logging and transcripts for audit, but apply retention limits consistent with privacy policy because transcripts contain raw user utterances.

Separate health monitoring

Monitor channel webhook endpoints and backend REST services independently; a failing backend appears as repeated error-handler transitions in the flow.