Edit and divide the Creating Your First Agent guide#11209
Conversation
|
|
||
| 5. Remove the **Save** and **Cancel** buttons. Add a new button with the caption *Ask the agent* below the **User input** text field. | ||
|
|
||
| 6. Open the **Model response** input field and set the **Grow automatically** option to `Yes`. |
There was a problem hiding this comment.
The data view automatically filled with a Text box, and I needed to convert to Text area before there was a Grow automatically option. Is it fine to just remove this instruction?
There was a problem hiding this comment.
Wouldn't it make more sense then to write to first convert it to a text area and then set the option?
There was a problem hiding this comment.
Also fine—I'm just wondering if there's a reason for it to be a text area vs text box or if I can just simplify here by not specifying.
linaaaf
left a comment
linaaaf
left a comment
There was a problem hiding this comment.
1st iteration :) Missing: create-agent-programmatically because there are open questions
|
|
||
| The end result is an example agent in a Mendix app. In this use case, you can ask IT-related questions to the model, which assists in solving problems. The model has access to a knowledge base containing historical, resolved tickets that can help identify suitable solutions. Additionally, function microflows are available to enrich the context with relevant ticket information, such as the number of currently open tickets or the status of a specific ticket. | ||
|
|
||
| This agent is a single-turn agent, which means that: |
There was a problem hiding this comment.
We should actually already use the word 'task' instead of single-call
There was a problem hiding this comment.
Got it. Should I also remove any mentions of "single call/single turn" throughout the docs rather leaving it as a supporting description?
| * Case B: The user is trying to solve an IT-related issue. Use the `FindSimilarTickets` tool to base your response on relevant historical tickets. | ||
|
|
||
| If the retrieved results are not helpful to answer the request, inform the user in a user-friendly way. | ||
| ``` |
There was a problem hiding this comment.
Could it be that something is wrong with rendering here, does the txt part maybe need to end differently? It seems to me that everything from the beginning of the system prompt is now txt and the ``` are not taken into account
There was a problem hiding this comment.
It's just a bug in the way it renders in GitHub, but it looks fine in the local build.
|
|
||
| Create and configure the required Model and Agent documents in Studio Pro, including prompts and a context entity: | ||
|
|
||
| 1. In the **App Explorer**, right-click your module and select **Add other** > **Constant**. Set the **Type** to `string` and the **Default value** to your text generation [resource key](/appstore/modules/genai/mx-cloud-genai/Navigate-MxGenAI/#keys) from the Mendix Cloud GenAI Portal. |
There was a problem hiding this comment.
It is not a best practice to specify a constant's value inside of a module. Instead you specify the value for the constant belonging to a module as part of the App Settings. The reason for this is that the value of the constant is not shipped as part f the App Package, instead it is an Environment variable
Let me know if you have questions, in the current How to it says pragmatically
'For the Model key, create and select a string type constant that contains your text generation resource key from the Mendix Cloud GenAI Portal.' This might be a bit short, what do you think about:
'For the Model key, first create a string type constant inside of the module and then, inside of the App Settings, set its value to your text generation resource key from the Mendix Cloud GenAI Portal.'
There was a problem hiding this comment.
Same goes for the part about the knowledge base key
|
|
||
| ## Calling the Agent | ||
|
|
||
| The button does not perform any actions yet, so you need to create a microflow to call the agent. Your completed microflow will look like this: |
There was a problem hiding this comment.
Add in the beginning that this is the 'Ask the agent' button on the TicketHelper_Agent page. Also, if they import this page the button it will ask for 'ACT_TicketHelper_Agent_AgentCommons' which is another example microflow they can lookup in the showcase app if interested
|
|
||
| 5. Remove the **Save** and **Cancel** buttons. Add a new button with the caption *Ask the agent* below the **User input** text field. | ||
|
|
||
| 6. Open the **Model response** input field and set the **Grow automatically** option to `Yes`. |
There was a problem hiding this comment.
Wouldn't it make more sense then to write to first convert it to a text area and then set the option?
2 participants
No description provided.