Universal Containers (UC) is using standard Service AI Grounding. UC created a custom rich text field to be used with Service AI Grounding. What should UC consider when using standard Service AI Groun

The correct answer is B. Service AI Grounding only supports String and Text Area type fields.. Standard Service AI Grounding in Salesforce only supports String and Text Area (plain text) field types. Rich text fields - which store HTML-formatted content - are not supported by Service AI Grounding. This means UC's custom rich text field will not be usable as a grounding sou

AI Features for Service (e.g., Einstein Bots, Next Best Action)

Question

Universal Containers (UC) is using standard Service AI Grounding. UC created a custom rich text field to be used with Service AI Grounding. What should UC consider when using standard Service AI Grounding?

Options

AService AI Grounding only works with Case and Knowledge objects.
BService AI Grounding only supports String and Text Area type fields.
CService AI Grounding visibility works m system mode.

How the community answered

(44 responses)

A
2% (1)
B
95% (42)
C
2% (1)

Explanation

Standard Service AI Grounding in Salesforce only supports String and Text Area (plain text) field types. Rich text fields - which store HTML-formatted content - are not supported by Service AI Grounding. This means UC's custom rich text field will not be usable as a grounding source without converting it to a plain text field type. Option A is incorrect because Service AI Grounding works with more than just Case and Knowledge objects. Option C is incorrect because Service AI Grounding does not operate in system mode; it respects the running user's visibility settings.

Topics

#Service AI Grounding#Field Types#Custom Fields#AI Feature Limitations

Community Discussion

No community discussion yet for this question.

Full AI-201 Practice