- Move global config files to globals iso global folder, as the name global conflicts with python language

- Creation of Traicie Vancancy Definition specialist
- Allow to invoke non-interaction specialists from withing Evie's mgmt interface (eveai_app)
- Improvements to crewai specialized classes
- Introduction to json editor for showing specialists arguments and results in a better way
- Introduction of more complex pagination (adding extra arguments) by adding a global 'get_pagination_html'
- Allow follow-up of ChatSession / Specialist execution
- Improvement in logging of Specialists (but needs to be finished)

config/tasks/globals/EMAIL_LEAD_DRAFTING_TASK/1.0.0.yaml

@@ -0,0 +1,35 @@
+version: "1.0.0"
+name: "Email Lead Draft Creation"
+task_description: >
+  Craft a highly personalized email using the lead's name, job title, company information, and any relevant personal or 
+  company achievements when available. The email should speak directly to the lead's interests and the needs
+  of their company.
+  This mail is the consequence of a first conversation. You have information available from that conversation in the 
+    - SPIN-context (in between triple %)
+    - personal and company information (in between triple $)
+  Information might be missing however, as it might not be gathered in that first conversation.
+  Don't use any salutations or closing remarks, nor too complex sentences.
+
+  Our Company and Product:
+  - Company Name: {company}
+  - Products: {products}
+  - Product information: {product_information}
+
+  {customer_role}'s Identification:
+  $$${Identification}$$$
+  
+  SPIN context:
+  %%%{SPIN}%%%
+  
+  {custom_description}
+expected_output: >
+  A personalized email draft that:
+    - Addresses the lead by name
+    - Acknowledges their role and company
+    - Highlights how {company} can meet their specific needs or interests
+  {customer_expected_output}
+metadata:
+  author: "Josako"
+  date_added: "2025-01-08"
+  description: "Email Drafting Task towards a Lead"
+  changes: "Initial version"

config/tasks/globals/EMAIL_LEAD_ENGAGEMENT_TASK/1.0.0.yaml

@@ -0,0 +1,28 @@
+version: "1.0.0"
+name: "Email Lead Engagement Creation"
+task_description: >
+  Review a personalized email and optimize it with strong CTAs and engagement hooks. Keep in mind that this email is
+  the consequence of a first conversation. 
+  Don't use any salutations or closing remarks, nor too complex sentences. Keep it short and to the point.
+  Don't use any salutations or closing remarks, nor too complex sentences.
+  Ensure the email encourages the lead to schedule a meeting or take
+  another desired action immediately.
+
+  Our Company and Product:
+    - Company Name: {company}
+    - Products: {products}
+    - Product information: {product_information}
+
+  Engagement options:
+  {engagement_options}
+  
+  {custom_description}
+expected_output: >
+  An optimized email ready for sending, complete with:
+    - Strong CTAs
+    - Strategically placed engagement hooks that encourage immediate action
+metadata:
+  author: "Josako"
+  date_added: "2025-01-08"
+  description: "Make an Email draft more engaging"
+  changes: "Initial version"

config/tasks/globals/IDENTIFICATION_DETECTION_TASK/1.0.0.yaml

@@ -0,0 +1,24 @@
+version: "1.0.0"
+name: "Identification Gathering"
+task_description: >
+  You are asked to gather lead information in a conversation with a new prospect. This is information about the person
+  participating in the conversation, and information on the company he or she is working for. Try to be as precise as
+  possible.
+  Take into account information already gathered in the historic lead info (between triple backquotes) and add 
+  information found in the latest reply. Also, some identification information may be given by the end user.
+  
+  historic lead info:
+    ```{historic_lead_info}```
+  latest reply:
+    {query}
+  identification:
+    {identification}
+  
+  {custom_description}
+expected_output: >
+
+metadata:
+  author: "Josako"
+  date_added: "2025-01-08"
+  description: "A Task that gathers identification information from a conversation"
+  changes: "Initial version"

config/tasks/globals/IDENTIFICATION_QUESTIONS_TASK/1.0.0.yaml

@@ -0,0 +1,19 @@
+version: "1.0.0"
+name: "Define Identification Questions"
+task_description: >
+  Gather the identification information gathered by your team mates. Ensure no information in the historic lead 
+  information (in between triple backquotes) and the latest reply of the user is lost. 
+  Define questions to be asked to complete the personal and company information for the end user in the conversation.
+  historic lead info:
+    ```{historic_lead_info}```
+  latest reply:
+    {query}
+  
+  {custom_description}
+expected_output: >
+
+metadata:
+  author: "Josako"
+  date_added: "2025-01-08"
+  description: "A Task to define identification (person & company) questions"
+  changes: "Initial version"

config/tasks/globals/RAG_CONSOLIDATION_TASK/1.0.0.yaml

@@ -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"

config/tasks/globals/RAG_TASK/1.0.0.yaml

@@ -0,0 +1,22 @@
+version: "1.0.0"
+name: "RAG Task"
+task_description: >
+  Answer the query based on the following context, delimited between triple backquotes, and taking into account
+  the history of the discussion, in between triple %. Try not to repeat answers already given in the recent history, 
+  unless confirmation is required or repetition is essential to give a coherent answer.
+  {custom_description}
+  Use the following {language} in your communication, and cite the sources used at the end of the full conversation.
+  If the question cannot be answered using the given context, answer "I have insufficient information to answer this question."
+  Context:
+    ```{context}```
+  History:
+    %%%{history}%%%
+  Query:
+    {query}
+expected_output: >
+
+metadata:
+  author: "Josako"
+  date_added: "2025-01-08"
+  description: "A Task that gives RAG-based answers"
+  changes: "Initial version"

config/tasks/globals/SPIN_DETECT_TASK/1.0.0.yaml

@@ -0,0 +1,18 @@
+version: "1.0.0"
+name: "SPIN Information Detection"
+task_description: >
+  Complement the historic SPIN context (in between triple backquotes) with information found in the latest reply of the
+  end user. 
+  {custom_description}
+  Use the following {tenant_language} to define the SPIN-elements. 
+  Historic SPIN:
+    ```{historic_spin}```
+  Latest reply:
+    {query}
+expected_output: >
+
+metadata:
+  author: "Josako"
+  date_added: "2025-01-08"
+  description: "A Task that performs SPIN Information Detection"
+  changes: "Initial version"

config/tasks/globals/SPIN_QUESTIONS_TASK/1.0.0.yaml

@@ -0,0 +1,20 @@
+version: "1.0.0"
+name: "SPIN Question Identification"
+task_description: >
+  Revise the final SPIN provided by your colleague, and ensure no information is lost from the histoic SPIN and the 
+  latest reply from the user. Define the top questions that need to be asked to understand the full SPIN context
+  of the customer. If you think this user could be a potential customer, please indicate so.
+  {custom_description}
+  Use the following {tenant_language} to define the SPIN-elements. If you have a satisfying SPIN context, just skip and 
+  don't ask for more information or confirmation.
+  Historic SPIN:
+      ```{historic_spin}```
+  Latest reply:
+    {query}
+expected_output: >
+
+metadata:
+  author: "Josako"
+  date_added: "2025-01-08"
+  description: "A Task that identifies questions to complete the SPIN context in a conversation"
+  changes: "Initial version"