1z0-1071-22 Oracle Cloud Platform Digital Assistant 2022 Professional Questions and Answers

They define a business domain object as a collection of related system entities and custom entities.

When you add entities to the composite bag, you can control how they get extracted in related to other entities and when they are prompted for.

The composite bag will always enforce that every entity has a valid value before allowing the conversation to move on to the next state in the dialog flow.

You need to create a separate composite bag to handle nonentity types such as strings. Locations, andattachments.

The composite bag can resolve all entity values using only a single state in the dialog flow.

Theskilldisplaysthemessage"Pleasewait,we'rereviewingyourorder",thendisplays "Almostdone...",thendisplays "Thankyouforyourorder.",andthencompletestheconversation.

The skilldisplaysthemessage"Pleasewait,we're reviewing yourorder"and thenwaitsforuser input.

Theskilldisplays themessage"Pleasewait,we're reviewingyourorder",thendisplays"Almostdone...",and thenwaitsforuser input.

The skilldisplaysthemessage"Pleasewait,we'rereviewingyourorder",thendisplays"Almostdone...",then displays"Thankyouforyourorder.",and thenwaitsforuser input.

System.entityToResolve can reference the resolve value of all entity values defined within the skill.

The system.entityToResolve variable tracks an entity value, that is, as you resolve entities in the composite bag, it references the current entity resolved.

${system.entityToResolve.value.userinput} returns the text entered by the user.

${system.entityToResolve.value.resolvingField) returns the text entered by the user.

The system.entityToResolve variable can be referenced from within the system. ResolveEntities and system. commonResponse components to display, for example, information about the entity that has been resolved.

It should not be used for String entity items.

When set to True, an entity item value can be updated when prompting for a different entity item value.

Only set to True, an entity item value can be updated when prompting for a different entity item value.

Only when set to true can entity values be specific in any order in the initial user input.

When set to True, an entity item cannot be resolve until a dependent entity item is first resolved.

Keep iterating on user testing and add more training utterances until you can achieve a confidence level of 100% on your user input.

For every verb in your training utterances, ensure you add a version of the utterance which also covers the past, present, and future tense of the verb.

It is not always possible to achieve 100%confidence and adding more utterances may not help the problem. Therefore, do not make further changes to the skill if it is performing to your expectations.

The highest possible confidence with 10 intents is 10% (100% divided by the number of intents).So, no further changes to the skill are required.

Add more utterances to the unresolvedlntent.

You can use the alternatePrompt property for user input components to display alternative prompts.

You can use the onlnvaliduserlnput property on the System.commonResponse component to conditionally show or hide UI controls.

You can use the system. invaliduserinput?booiean expression to detect a previously failed input validation and display alternative prompts or additional UI controls.

You can use the user input component's textReceived action transition to detect validation errors and to navigate to a state in the dialog flow.

You can use the user input component's cancel action transition to navigate to a different state in the dialog flow, display a help message to the user, and navigate back into the dialog flow state that previously failed input validation.

System.ResolveEntities

System.Text

System.MatchEntity

System.CommonResponse

System.List

Create a value list entity called ToFromEntlty with values of "to" and "from" and with appropriate synonyms for each value. Create a value list called DirectionStation and add ToFromEntity and StationEntity to this. Then, add DirectionStation to the Routelnfolntent.

Create two derived entities based on StationEntity. In one entity, set the preceding phrase to "to" (along with any required synonyms). In the other entity, do the same but with the preceding phrase "from". Add both entities to the Routelnfolntent intent.

Duplicate StationEntity. In one version, prefix all of the train station nameswith "to" and in the other prefix with "from". Then add both entities to the Routelnfolntent intent.

Add StationEntity to the Routelnfolntent intent and then update the training data with phrases beginning with "from".