How do I troubleshoot my Generate Win Story custom layout issues?

Generative AI can help create win stories from existing data about won and closed opportunities. The default layout for Generating Win Story saves the generated win story in the Comments field on the Opportunity. It's advisable to create a custom Long text field to save the win story. You'll need Visual Builder (VB) to make any change to your layout to reference the custom fields.

You can easily share the AI generated win stories with your sales organization to help other sales team members learn from existing won opportunities.

Here are some troubleshooting tips to help you successfully generate your win story and fix any issues you might experience:

Steps	Considerations
Field Mapping in Layout	Check if the Long Text field is correctly mapped. For example, in the Generate Summary layout (page layout or Application Composer), ensure that the new Long Text custom field is assigned as the target for the generated summary output (Win Story). Ensure that the field should is visible and is set as the output field for summary generation.
Setup in Application Composer	Navigate to Application Composer and select you Opportunity or Custom object. Open the Pages section and find the relevant layout. Make sure the summary generation action (such as Generate Win Story) is configured to use your custom Long Text field as the destination for the generated output.
Process or Automation Configuration	Check that any related processes are setup correctly. For example, if there's an Oracle Sales or Classic Sales setup such as an Action or Process that triggers summary generation, make sure that the process references the correct field. Sometimes the automation is hard coded to update the standard Comments field. you might need to update the process or logic (using Visual Builder or Groovy scripts) to use your custom field.
Permissions and Visibility	Check the field-level security. Ensure that your user role has Edit and View access to the custom Long Text field. Without appropriate permissions, the action might not complete as intended.
Save and Publish All Changes	After updating the layout and logic, save your changes and perform a full publish to ensure that your changes take effect.
Test with Minimal Layout	Try putting only the custom Long Text field on the layout and see if content gets generated. If not, revert the changes and test with the Comments field again to verify the process.
Oracle Support	If the above steps don't resolve the issue, it might be a product limitation or you might require support from Oracle. Sometimes, built-in summary generation is hard coded to the original Comments field or there's a missing fragment or template which allow the AI to generate the content.

Ensure the summary generation logic targets your custom Long Text field. This might require changes in automation or to your business processes. If you've verified that your configuration is correct and it's still not working, Oracle Support can confirm if there are any limits or restrictions.