App prompt
Add and manage prompts on the app edit screen
You can write prompts in real time on the app edit screen and apply them to the app immediately. Prompts are divided into the following two scopes.
App prompt: A prompt that is tied to and used only by a specific app. This is explained in detail in the guide.
Project prompt: A prompt that can be shared across multiple apps within a single project. For more details, Project prompt please refer to the guide.
1. Adding an app prompt from the app edit screen

Select the prompt scope. Choose App prompt.
Select the LLM model that will execute the prompt.
To use an existing prompt, select the prompt you want from the 'Prompt' dropdown.

To create a new prompt, click the + Add button.

Add and write the prompt 5-1. Enter the prompt name. 5-2. Enter the prompt description (a description to help distinguish the purpose of the prompt; it does not affect actual execution). 5-3. Enter the system prompt. The system prompt is used to configure the LLM's behavior. For example, you can assign a specific persona to the model or define behavioral guidelines the model should follow throughout the conversation.
⚠ When using dynamic inputs in prompts, use curly braces
{}without fail.5-4. Enter the user prompt In the user prompt, write the request or question the LLM should respond to. Writing queries and questions is recommended. It is optional.
⚠ When using dynamic inputs in prompts, use curly braces
{}without fail.5-5. Add dynamic inputs You can assign variables whose values change dynamically within the prompt.
Add dynamic input

Enter the name of the dynamic input item to use within the prompt.
Specify the variable value to be assigned to that item. There are two types of variable values that can be assigned to dynamic inputs: system and app.
a. System variable An input that is integrated with the Alli system and automatically receives values.
EMAIL,LANGUAGEare variables automatically provided by the system.
b. App variable
An option that allows you to specify variables directly within the app and enter their values.
Input values can be freely assigned according to the situation and needs, and values may change depending on the app's conversation flow.
Add an app variable

Enter the variable name.
Select the variable type.
Conversation: The value is stored and applied only within the conversation.
User: The user's value is stored and applied even after the conversation ends.
Select the variable kind. (Total 11 types)
For more details, Variable value guide can be found.
Click the Save button.
If necessary, choose the token trimming ON/OFF option. It is recommended to set to ON for variables with long tokens.
2. Managing app prompts
Go to Dashboard > Settings > Prompt Management > App page.
At this time, the permissions of members who can access the app page Follow app market or app management access permissionsfollow.

All public apps for which the member has viewer or editor permissions and all interactive apps currently being authored will be displayed in the list.

3. App prompt management actions by permission
The app prompt management features behave differently depending on whether the user has viewer or editor permissions for the app.

Members without permissions for the app will not see that app on the prompt management screen.


Conversely, members who have view or edit permissions for the app will see the app listed on the prompt management screen.
When clicking the shortcut button
Clicking the shortcut button allows you to see on the app edit screen which prompts are actually used in which nodes of that app.

If you do not have edit permission for the app, you can only view it.

If you have edit permission for the app, you can switch the app to 'Draft' status and edit it immediately.
When clicking an app's detailed prompt
If you click an app to enter the app prompt screen, a list of prompts created for that app will be shown.

If you do not have edit permission for the app (only view permission), you cannot directly delete or modify prompts, but you can copy them to another app or copy them so they can be shared in the project.

If you have edit permission for the app, you can create new prompts, delete, or modify them. However, prompts that are actually in use within the app cannot be changed directly. In that case, you must copy the prompt and then modify it.
Copy to project prompt
Let's copy a prompt that was used in an app to a project prompt that can be shared across all apps in the project and then modify it.

Click the Copy to Project Prompt button.

You can further edit the copied prompt as needed. You may leave it unchanged; when finished, click the Save button.

You can confirm that the prompt that was dependent on the app has been copied into the project as a single project prompt. A prompt copied this way can be used commonly by multiple apps rather than a single app, and it can be selected from the prompt dropdown list in the LLM execution node.
Copy to app prompt
To share a prompt that was used in one app with another app, let's use the app prompt copy feature to copy it to a different app.

Click the Copy to App Prompt button.

Select the target app to which you want to copy the prompt. For example,
TestApp2inTest1prompttoNEWApp

Click the Copy button.

You can see that the selected
tohasTest1the prompt copied into it

At this time, copying is only possible if you have edit permission for the selected app; if you do not have edit permission, a message will be displayed informing you that copying is not possible.
Last updated