Hi,
We created a case type in our implementation application, inheriting OOTB case type. The OOTB case type has the coach enabled. We are seeing the GenAI coach widget in our case type as well.
However, we don’t see any settings to control GenAI coach in the app studio as we don’t have Gen AI enabled for us.
Is there an option to disable the coach without customizing pyDetails view in dev studio?
GenAI coach.docx (196 KB)
@Sreedhar Ganduri @agars Could you please check?
@LakshayD17563872
This is a GenAI-powered tool. All generated answers require validation against the provided references
Assessment & Recommendation
Try disabling the GenAI Coach by adjusting the configuration settings in Dev Studio, as detailed below.
Analysis
GenAI Coach settings are managed through configuration toggles in Dev Studio, not App Studio.
Proposed Solution
To disable the GenAI Coach without customizing the pyDetails view, follow these steps:
- Navigate to Dev Studio.
- Go to Configure > System > Release > Toggles.
- Locate the EnableGenerativeAI toggle and set it to OFF.
- Ensure that this setting is applied to the appropriate user roles or operators.
Options to Disable GenAI Coach Without Customizing pyDetails:
-
Remove the Coach from the Full Page View Tabs:
- Go to App Studio > Case Types > [Your Case Type] > UX tab.
- Check if the GenAI Coach widget is added as a tab or section.
- If present, remove the tab or widget from the Full Page View.
-
Use Visibility Conditions:
- If the widget is conditionally rendered, you might be able to set a visibility condition (e.g., based on a flag or user role) to hide it.
- This can sometimes be done in App Studio without needing to go into Dev Studio.
-
Check for DSS or Feature Toggles:
- Some GenAI features are controlled via Dynamic System Settings (DSS) like
AutopilotServiceBaseURL.
- If such DSS is present, you might be able to disable or remove it to prevent the Coach from initializing.
-
Switch to a Custom View:
- If the OOTB case type uses a specific view that includes the Coach, consider switching to a custom view that excludes it, rather than modifying
pyDetails.