- Partner model additions
- menu changes to allow for partners - partner views and forms now in partner_forms.py and partner_views.py - Introduction of services layer - Allow all configuration to handle partner configurations, and adaptation of caching to allow for this
This commit is contained in:
27
config/tasks/global/RAG_CONSOLIDATION_TASK/1.0.0.yaml
Normal file
27
config/tasks/global/RAG_CONSOLIDATION_TASK/1.0.0.yaml
Normal file
@@ -0,0 +1,27 @@
|
||||
version: "1.0.0"
|
||||
name: "Rag Consolidation"
|
||||
task_description: >
|
||||
Your teams have collected answers to a user's query (in between triple backquotes), and collected additional follow-up
|
||||
questions (in between triple %) to reach their goals. Ensure the answers are provided, and select a maximum of
|
||||
{nr_of_questions} out of the additional questions to be asked in order not to overwhelm the user. The questions are
|
||||
in no specific order, so don't just pick the first ones. Make a good mixture of different types of questions,
|
||||
different topics or subjects!
|
||||
Questions are to be asked when your team proposes questions. You ensure both answers and additional questions are
|
||||
bundled into 1 clear communication back to the user. Use {language} for your consolidated communication.
|
||||
Be sure to format your answer in markdown when appropriate. Ensure enumerations or bulleted lists are formatted as
|
||||
lists in markdown.
|
||||
{custom_description}
|
||||
|
||||
Anwers:
|
||||
```{prepared_answers}```
|
||||
|
||||
Additional Questions:
|
||||
%%%{additional_questions}%%%
|
||||
|
||||
expected_output: >
|
||||
{custom_expected_output}
|
||||
metadata:
|
||||
author: "Josako"
|
||||
date_added: "2025-01-08"
|
||||
description: "A Task to consolidate questions and answers"
|
||||
changes: "Initial version"
|
||||
Reference in New Issue
Block a user