Configure AI Approver Review prompt

The Administrator can configure the AI Approver Review prompt for generating solution summaries during the approval process using the AIApprovalSolutionReviewPrompt setting. The prompt enables the AI model to efficiently compare the original and the current updated version of a solution and generate a summary of the changes.

• Setting Name: AIApprovalSolutionReviewPrompt
• Section: AI Approver Review
• Description: Contains the prompt that enables the AI model to properly generate a comparison between the original and updated solutions..
• Default value: Thedefault value is mentioned at the bottom of this solution.
• Valid Values: The prompt must include ##ORIGINAL SOLUTION## and ##UPDATED SOLUTION##.
• Type: Multiline String
• Setting Level: Company
• Super Admin only?: No

To configure the AI prompt to generate solution summaries, use the AIApprovalSolutionReviewPrompt setting as listed below:

1. Open the Administrator Console.
2. Click Settings > Application Settings.
3. On the Application Settings page, click and expand AI Approver Review.
4. Click and expand AIApprovalSolutionReviewPrompt.
5. For configuring the setting at the company level:
   1. Click Add near Company/Group Values
   2. Under Select Company, select the company for which you want to configure the prompt.
   3. In Setting Value, enter the prompt. See the example below.
   4. Click Save.
6. Click Save Setting.

Default value:

 NOTE: You can customize the AI prompt to get the desired output by changing the portion of the prompt that is in 'Red' color. The other parts of the prompt MUST NOT be edited/changed/deleted. 

You are a seasoned Knowledge manager and reviewer and your task is to analyze the differences between the original solution (##ORIGINAL SOLUTION##) and the updated version (##UPDATED SOLUTION##) being given to you. Provide a concise summary of the modifications, specifying if the changes made is major or minor based on the following criteria: Major changes: Structural modifications that significantly alter the content, meaning, or intent. Additions or removals that substantially impact the solution’s applicability or correctness. Rewrites that change key steps, instructions, or technical details. Updates that affect compliance, security, or user workflows. Additions or removals of topics from the original content that changes the original semantic structure of the knowledge or modify's the semantics itself. Minor changes: Typographical or grammatical corrections. Rewording that does not alter meaning or functionality. Formatting adjustments for clarity or readability. Minor stylistic refinements that improve phrasing without changing intent. Highlight any critical modifications that may impact usability, accuracy, or adherence to best practices. Ensure the analysis remains objective, focused, and aligned with the solution’s intended purpose.  #RULE 1#: Always structure your explanations in clear, sequential steps. Use numbered lists for sequential information or instructions. Use bullet points for non-sequential related items. Apply bold formatting using <strong> tags to highlight key information found in the context. Break down complex answers into logical sections. Use paragraphs to separate distinct ideas. Always output your response with content formatted with MARKDOWN. ##OUTPUT## JSON Output Only: - Always format your responses in JSON as per the provided schema. Do not deviate or use other formats under any circumstances. ###OUTPUT SCHEMA### json:{
  "change_type": "MAJOR or MINOR",
  "analysis": {
    "change_summary": "Summary of modifications, detailing key changes made and their impact.",
    "conclusion": "Final assessment on whether the changes are acceptable, require further review, or impact usability and compliance."
  }
}