1. How do I use AI Agent Studio?
  2. Configure an AI Guidance Node in a Workflow

Configure an AI Guidance Node in a Workflow

Use the AI Guidance node to write new guidance or read previously created guidance. Guidance can include summaries, recommendations, alerts, insights, and actions that can be shared and used consistently across agentic experiences.

You can associate guidance with a business object and a specific business record, an agentic application, or an Ask Oracle plugin. For business object references, the node uses the business object’s record resolution and security model.

  1. Go to AI Agent Studio.
  2. From the Workflows tab, edit a workflow and add an AI Guidance node to it.
  3. Enter a name and description for the node. The code is automatically populated based on the name.
  4. Select an error handler node to define failure handling.
  5. From Operation, select either of these options:
    • Read: Retrieves existing guidance for the configured context. For business object references, the node validates the current user’s access to the business object before retrieving guidance. This operation is selected by default.
    • Write: Stores guidance generated by the workflow and makes it available to other users. You can specify the guidance to store and the applicable attributes for the guidance.
  6. Select the Reference Type to associate the guidance with. Based on the selected operation and reference type, specify the details for the guidance node. You can also use expressions to specify values for supported fields, wherever applicable. For more information, see Expressions.
    1. Read operation for a business object reference type:
      1. From the Family list, select the applicable product family.
      2. From the Product list, select the applicable product.
      3. From the Business Object list, associate the guidance with a specific business object and business record.
      4. In the Record Key field, enter the value that identifies the business record or use an expression to specify the value.
      5. In the Filter field, enter the criteria to filter the applicable guidance or use an expression to specify the filter criteria.
      6. In the Returned Reference Filter field, enter the criteria to filter the references returned by the node or use an expression to specify the filter criteria.
      7. In the Target Persona field, enter the persona for which the guidance applies or use an expression to specify the value. Use ALL when the guidance applies to all supported personas.
    2. Write operation for a business object reference type:
      1. From the Family list, select the applicable product family.
      2. From the Product list, select the applicable product.
      3. From the Business Object list, associate the guidance with a specific business object and business record.
      4. In the Record Key field, enter the value that identifies the business record or use an expression to specify the value.
      5. In the Target Persona field, enter the persona for which the guidance applies or use an expression to specify the value. Use ALL when the guidance applies to all supported personas.
      6. From the Guidance Type field, specify the type of guidance to store. Select Insights, Summary, Recommendation, or Alert. Alternatively, use an expression to specify the value.
      7. Select a corresponding Guidance Subtype or use an expression to specify the value.
      8. From the Category field, specify the category of guidance to store. Select Commercial, Usage, Service, Engagement, Process, or Financial. Alternatively, use an expression to specify the value.
      9. In the Status field, specify the status of the guidance to store. Select Active or use an expression to specify the value.
      10. In the Urgency field, specify the urgency of the guidance to store. Select Low, Medium, High, or Critical. Alternatively, use an expression to specify the value.
      11. In the Generated By field, specify an expression that identifies the source that generated the guidance. The default value is {{'agent:' + $context.$workflow.$code}}.
      12. In the Agent Job Key field, specify an expression that identifies the agent job that produced the guidance. The default value is {{$context.$workflow.$traceId}.
      13. In the Effective End Date field, specify the date and time when the guidance expires. If you leave the field blank or specify a date more than 30 days after the guidance is created, the guidance expires 30 days after creation.
      14. In the Payload field, specify the guidance payload to store. Enter inline JSON or use a workflow expression that resolves to the payload.
      15. In Additional References, add related records to the guidance. For each reference, select the AI Guidance-enabled Reference Business Object, specify the Reference Key, and select Yes or No for Primary Reference. The parent record is added automatically.
    3. Read operation for an agentic application reference type:
      1. From the Application Code list, select the agentic application to associate with the guidance.
      2. In the Filter field, enter the criteria to filter the applicable guidance or use an expression to specify the filter criteria.
      3. In the Returned Reference Filter field, enter the criteria to filter the references returned by the node or use an expression to specify the filter criteria.
      4. In the Target Persona field, enter the persona for which the guidance applies or use an expression to specify the value. Use ALL when the guidance applies to all supported personas.
    4. Write operation for an agentic application reference type:
      1. From the Application Code list, select the agentic application to associate with the guidance.
      2. In the Target Persona field, enter the persona for which the guidance applies or use an expression to specify the value. Use ALL when the guidance applies to all supported personas.
      3. From the Guidance Type field, specify the type of guidance to store. Select Insights, Summary, Recommendation, or Alert. Alternatively, use an expression to specify the value.
      4. Select a corresponding Guidance Subtype or use an expression to specify the value.
      5. From the Category field, specify the category of guidance to store. Select Commercial, Usage, Service, Engagement, Process, or Financial. Alternatively, use an expression to specify the value.
      6. In the Status field, specify the status of the guidance to store. Select Active or use an expression to specify the value.
      7. In the Urgency field, specify the urgency of the guidance to store. Select Low, Medium, High, or Critical. Alternatively, use an expression to specify the value.
      8. In the Generated By field, specify an expression that identifies the source that generated the guidance. The default value is {{'agent:' + $context.$workflow.$code}}.
      9. In the Agent Job Key field, specify an expression that identifies the agent job that produced the guidance. The default value is {{$context.$workflow.$traceId}.
      10. In the Effective End Date field, specify the date and time when the guidance expires. If you leave the field blank or specify a date more than 30 days after the guidance is created, the guidance expires 30 days after creation.
      11. In the Payload field, specify the guidance payload to store. Enter inline JSON or use a workflow expression that resolves to the payload.
      12. In Additional References, add related records to the guidance. For each reference, select the AI Guidance-enabled Reference Business Object, specify the Reference Key, and select Yes or No for Primary Reference. The parent record is added automatically.
    5. Read operation for an Ask Oracle plugin reference type:
      1. From the Plugin Code list, select the Ask Oracle plugin to associate with the guidance.
      2. In the Filter field, enter the criteria to filter the applicable guidance or use an expression to specify the filter criteria.
      3. In the Returned Reference Filter field, enter the criteria to filter the references returned by the node or use an expression to specify the filter criteria.
      4. In the Target Persona field, enter the persona for which the guidance applies or use an expression to specify the value. Use ALL when the guidance applies to all supported personas.
    6. Write operation for an Ask Oracle plugin reference type:
      1. From the Plugin Code list, select the Ask Oracle plugin to associate with the guidance.
      2. In the Target Persona field, enter the persona for which the guidance applies or use an expression to specify the value. Use ALL when the guidance applies to all supported personas.
      3. From the Guidance Type field, specify the type of guidance to store. Select Insights, Summary, Recommendation, or Alert. Alternatively, use an expression to specify the value.
      4. Select a corresponding Guidance Subtype or use an expression to specify the value.
      5. From the Category field, specify the category of guidance to store. Select Commercial, Usage, Service, Engagement, Process, or Financial. Alternatively, use an expression to specify the value.
      6. In the Status field, specify the status of the guidance to store. Select Active or use an expression to specify the value.
      7. In the Urgency field, specify the urgency of the guidance to store. Select Low, Medium, High, or Critical. Alternatively, use an expression to specify the value.
      8. In the Generated By field, specify an expression that identifies the source that generated the guidance. The default value is {{'agent:' + $context.$workflow.$code}}.
      9. In the Agent Job Key field, specify an expression that identifies the agent job that produced the guidance. The default value is {{$context.$workflow.$traceId}.
      10. In the Effective End Date field, specify the date and time when the guidance expires. If you leave the field blank or specify a date more than 30 days after the guidance is created, the guidance expires 30 days after creation.
      11. In the Payload field, specify the guidance payload to store. Enter inline JSON or use a workflow expression that resolves to the payload.
      12. In Additional References, add related records to the guidance. For each reference, select the AI Guidance-enabled Reference Business Object, specify the Reference Key, and select Yes or No for Primary Reference. The parent record is added automatically.
  7. Review Output Specification. The output schema is predefined for the selected artifact and is read-only.
  8. Publish the workflow.
When the workflow runs, the node performs one of the following operations:
  • A Write operation stores the generated guidance in the AI Guidance Store and associates it with the configured reference. For a business object reference, the business object serves as the primary reference for the stored guidance, making it available to subsequent consumers.
  • A Read operation retrieves existing guidance for the configured context. For a business object reference, the node resolves the applicable business record and validates the current user’s access to the business object before retrieving guidance. The configured filters and target persona determine which guidance is returned.