Working with coding agents in Creatio
The agent builds what you describe, so the result depends on how precise your prompt is. Copy the prompts below and adapt them to your app.
Write a precise prompt
Include the following in your prompt:
- the app, page, or form to create or update
- the field, section, detail, or stage where the behavior applies
- the exact rule
- when the behavior should run
- what the user should see
- whether invalid input must block saving
- how calculated or derived values should be shown
Use this pattern as a starting point:
Create or update the [app, page, or form].
Apply this behavior to [field, section, detail, or stage].
The rule is: [exact condition].
Run it [on change, on save, on stage change, or for display].
If the rule fails, [show message, clear field, block save, or block transition].
For calculated or display values, use: [formula, formatting, read-only behavior, icon, or label].
Additional tips:
- Describe the business result, not the implementation approach.
- Specify dependencies between fields.
- Include examples of expected output for calculated or formatted values.
Create a new app
Describe an app in business terms, and the agent creates its initial structure for you.
Create a vendor onboarding app with two sections: Vendors and Vendor Requests.
Create a vendor onboarding app. It should include Vendors and Vendor Requests. Vendor Requests must have request number, request date, status, owner, vendor, requested services, and approval comment. Generate a request page and a vendor page. Add lookups where needed and make the app ready for data entry.
Extend an existing app
Add sections or features to an existing app without rebuilding it from scratch.
Add a Warranty Claims section to the existing Case Management app.
Extend the existing Case Management app with a new Warranty Claims section. Reuse existing Account and Contact data where possible. Add a claim form page with claim number, product, claim reason, date opened, resolution date, and status.
Add new fields to the existing Customer Requests app using a change specification document.
Use the following Creatio environment:
URL: https://your-site.creatio.com
Username: <your-username>
Password: <your-password>
I have an existing Creatio application called Customer Requests that was built using Creatio AI app development toolkit. I am attaching a change specification document that describes a set of enhancements I want to apply to the existing app.
Please read the attached specification carefully, then implement all described changes:
- Extend the existing CustomerRequest object with the new fields listed
- Create the new Request Channel lookup entity with its values
Prevent invalid data from being saved
Add validation logic to keep your data clean. For example, you can ask the agent to:
- check the text format
- limit the text length
- apply rules to numbers
- compare several fields
- check totals in expanded lists
- reject empty or spaces-only text
- check that a value is unique
Validate text format and length on a customer form.
On the customer form, Full name must contain only Latin letters and spaces. Phone number must start with + and contain 10 to 15 digits. Registration code must contain 8 to 10 digits. If the value is invalid, show a clear message and prevent saving.
Enforce character limits on a job request form.
In the Job request form page, Job number field must contain no more than 10 characters. Description field must be limited to 500 characters, and the page must show that limit near the field.
Enforce numeric rules on a Loan Application app.
In the Loan Application app, Age must be 18 or higher. Requested amount cannot be below 0. Score can only be 0, 17, or any value from 100 to 1000.
Compare field values on a warehouse operation form.
In the Warehouse Operation form, Issued quantity cannot be greater than Available quantity. Internal amount and External amount together must equal Total amount.
Validate totals across expanded list rows in the Project Allocation app.
In the Project Allocation app, the total allocation across expanded list rows cannot exceed 100 percent. The sum of all expanded list rows must also match the planned allocation in the main record.
Require meaningful text input on a citizen request form.
In the Citizen Request form, Subject is considered filled out only if it contains meaningful text. Empty or spaces-only values are invalid.
Check email uniqueness across contacts.
In the Contact Management app, email must be unique across contacts. When the user changes the email, check whether it is already used by another contact. When editing an existing contact, its own current email must remain valid.
React immediately when the user changes a field
Add page logic that runs while the user works with the page, not only on save. For example, you can ask the agent to:
- clear dependent fields
- recalculate values right away
- block a stage change if conditions are not met
- explain why Creatio changed a field value
Clear a dependent field and block a stage transition based on field values.
In the Procurement Request page, when Standard destination changes, clear Loan category immediately and explain why. When the request is moved to Approved, block the change if Purchase type is Below threshold and Budget is greater than 50000.
Change page behavior when a field changes
Describe how the page must react to a field value, and the agent creates the business rules. For example, you can ask the agent to:
- show or hide fields
- make fields read-only or editable
- populate a field from a related record
- calculate a field value using a formula
The agent creates page business rules for the behavior of page elements and object business rules for the field values.
Add business rules to the form page of a Todo app. The page includes the Name, Description, Completed, Estimated minutes, Spent minutes, Overtime minutes, Contact, and Contact phone fields.
Create business rules for this Creatio Freedom UI form page:
<link to the form page>
When the Completed field is true:
- Make the Name and Description fields read-only.
- Set the Contact phone field from the selected Contact's Mobile phone value.
- Set Overtime minutes using the formula: Spent minutes - Estimated minutes.
As a result, the agent creates page business rules that make the Name and Description fields read-only. The agent also creates object business rules that populate the Contact phone field and calculate the Overtime minutes field.
Apply date-based logic
Add rules and page behavior based on dates. For example, you can ask the agent to make sure that:
- the end date is not earlier than the start date
- the planned date is not in the past
- the birth date matches a minimum age
Validate date fields and enforce a minimum age on the Event Management app.
In the Event Management app, End date cannot be earlier than Start date. Planned date cannot be in the past. Birth date must correspond to a person who is at least 18 years old. Prevent saving when the rule is violated and show a clear explanation.
Calculate and display derived values
Calculate values on the page and show them in a readable format. For example, you can ask the agent to:
- calculate fees, totals, or percentages
- show read-only calculated values
- format calculated values so they are easy to read
- combine calculations with validation rules
Create a loan application form that combines validation, conditional logic, and calculated read-only fields.
Create a Loan Application Management app.
On the application form, add a Loan details section with these rules:
- Name: only Latin letters are allowed, and the value must be displayed in uppercase on the page.
- Age: must be 18 or higher.
- Credit score: must be between 100 and 1000. For scores below 500, show a down arrow icon. For scores of 500 or higher, show an up arrow icon.
- Loan amount: must not exceed 5000 if the credit score is below 500.
- Loan start and end dates: the loan duration must be at least 1 month, the end date must be later than the start date, and the start date cannot be earlier than today.
Add a Loan calculations section with read-only fields calculated from the entered data:
- Fee: 3% of the loan amount, displayed as "3% from 100$ = 3$".
- Total loan amount: Loan amount plus Fee, displayed as "100$ + 3$ = 103$".
Each validation or restriction must be shown as an inline hint during form editing and must prevent saving the form if the rule is violated.
Improve how values are shown on the page
Show data on the page more clearly without changing it. For example, you can ask the agent to:
- combine several fields into one readable caption
- show readable labels instead of stored codes
- format progress, percentages, or status text
- show display-only values without changing stored data
Combine multiple fields into a single readable caption on a request page.
On the request page, show a display field that combines request number, status, and created date into one readable caption.
Display a stored code as a readable label on a customer page.
On the customer page, display customer type as a readable label instead of the stored code value.
Show fulfillment progress as a formatted percentage and status text on an order page.
On the order page, show fulfillment progress as a formatted percentage and a textual state such as Not started, In progress, or Complete.
Reuse the same logic across multiple pages
Make the same logic work the same way on different pages of the app.
Apply the same validation rule to two different pages.
Create a Customer page and a Partner page. On both pages, Registration code must contain exactly 8 digits. The behavior and message must be the same everywhere.
Build business processes
Describe the process in business terms, and the agent creates it, including branching, sub-processes, and script tasks. Business process generation is available for Creatio 8.3.4 and later. The agent can also help you test the process. The tests might not cover every case. Check the process before you use it.
The agent configures the following process elements:
- Events: Simple start, Signal start that runs when a record is added, modified, or deleted, and Terminate end.
- Gateways: exclusive (XOR) and parallel (AND) gateways, conditional and default flows.
- System actions: Read data, Add data, Modify data, Delete data, Change access rights, Formula, Script task, and Process file.
- User actions: Perform task, Send email with a custom body or an email template, Open edit page, Approval, and Pre-configured page.
- Sub-process.
The agent also adds process parameters of all types and maps them between elements. When you ask the agent to change an existing process, the agent keeps the elements it does not configure unchanged.
Some elements need a newer version of the CrtProcessBuilder package in the environment. If the package is outdated, the agent offers to install it.
Before you activate a generated process, check it:
- Generate the process in a development or test environment. A saved process runs right away: a process with a signal start reacts to record events as soon as you save it.
- If something is unclear, ask the agent to describe the process: what starts it, which records it reads or changes, who gets tasks or emails, and how it branches.
- Check the filters of the Delete data, Change access rights, and Modify data elements, and the recipients of the Send email element. A Change access rights element without a filter applies to every record of the object.
- If the process has script tasks, run it after the agent compiles it, check the output parameters, and make sure the run completed without errors.
- Approve the test run when the agent offers it. The agent runs the process with test data and can delete the test records afterward.
- To change an existing process, ask the agent to save the change as a new version without activating it. Test the version, then activate it. To roll back, activate the previous version.
Create a process with several script tasks that pass data to each other.
In the Vendor Requests app, create a business process that runs when a request is approved. Use two Script task elements: the first calculates the total cost of the requested services, and the second compares it with the budget limit. Pass the total cost from the first script task to the second as a process parameter. If the cost exceeds the limit, send a notification to the request owner.
Use a script task only when other process elements cannot do the job. A script task reads and writes process parameters using the Get<T>("Code") and Set<T>("Code", value) methods. The parameter code is case-sensitive, and the C# type must match the parameter type, for example, string for Text, decimal for Money, and Guid for Lookup. For example, the agent creates a script task like this one to calculate a discounted amount:
// Process parameters: AmountParameter (Money, In), DiscountRateParameter (Float, In),
// DiscountedAmountParameter (Money, Out)
decimal amount = Get<decimal>("AmountParameter");
decimal rate = Get<decimal>("DiscountRateParameter");
if (amount < 0 || rate < 0 || rate > 100) {
return false;
}
Set<decimal>("DiscountedAmountParameter", Math.Round(amount * (1 - rate / 100), 2));
return true;
Build dashboards, desktops, and home pages
Create or change pages with analytical widgets of all types: dashboards, home pages, desktops, and workplaces. If your request does not name the widgets, the agent suggests a set of widgets and asks you to confirm it. For the best result, name the widgets, filters, and roles that need access.
Create a dashboard for a user role. The agent proposes the widgets and asks which package to save the dashboard to.
Create a dashboard for support managers.
Create a desktop with specific widgets and grant access to it.
Create the "IT requests" desktop for the IT requests app. Add a column chart with new requests by month, donut charts with requests by priority and by satisfaction, and metrics with the percentage of overdue requests and the percentage of requests resolved on time. Grant access to the desktop only to the "IT admins" role.
Add a dashboard to a form page. The agent filters the widgets by the data of the open record.
On the account form page, add a dashboard with the opportunities and cases of the current account.
Create an app with a home page and add it to a workplace.
Create a To-do list app for managing everyday tasks: create, view, edit, and delete tasks, update their status, and assign them to users. Add a home page with task metrics. Everyone in the company must be able to open the app.
If the workplace does not exist, the agent creates it and names it after the app. To use a different workplace, name it in the request.
Create a home page in an existing workplace.
Create the "IT request overview" home page in the IT requests workplace. Add a chart with new requests by month, a chart with requests by priority, a funnel with requests by satisfaction, the number of open critical requests, and the number of closed requests with satisfaction 1.
Manage users and roles
Set up who can work in Creatio: create users, build the role structure, assign licenses, and control access. You can ask the agent to manage the following:
- Users: find, create, rename, activate, deactivate, and delete users, link them to contacts, unlock accounts, and set new passwords.
- Roles: create, rename, move, and delete organizational roles, divisions, teams, and functional roles, add manager groups, add users to roles and remove them, and link functional roles to organizational roles.
- Role membership: show the roles of a user, including inherited and delegated roles, and the users who have a role.
- Licenses: assign licenses to users and remove them, link license packages to roles, and redistribute licenses by role.
- Access: manage IP access rules, delegate rights from one user or role to another user, and grant or deny permissions for system operations.
The agent asks for confirmation before each change and reads the result back before it reports success. Some operations need the latest Creatio 10.1 updates and ClioGate. If ClioGate is outdated, the agent offers to update it.
Keep the following in mind:
- Do not add passwords to the prompt. Save the password to an environment variable named
CLIO_ADMIN_PASSWORD_<SUFFIX>and give the agent only the variable name. Remove the variable after use. - The agent creates users only for existing contacts.
- A new role has no access to records. Set up access rights to records separately.
Create a user for an existing contact and add the user to a role.
On dev-env, create a user j.smith for the existing contact "John Smith".
The temporary password is in CLIO_ADMIN_PASSWORD_JSMITH; require a change at first login.
Then add the user to the "Sales managers" role.
Create a functional role and link it to an organizational role.
Create a functional role "Claims reviewers" under All employees on dev-env and link it to the "Claims department" organizational role.
Show all roles of a user.
Which roles does j.smith have on dev-env, including inherited and delegated ones?
Assign a license to a user.
Assign a "Creatio Sales" license to j.smith on dev-env and confirm it is assigned.
Unlock a user account.
a.brown is locked out on dev-env. Unlock the account but keep it inactive.
Delegate rights to another user.
Delegate m.jones's rights to j.smith while m.jones is on vacation.
See also
Creatio AI app development toolkit
Set up Creatio AI app development toolkit
Start working with Creatio AI app development toolkit
Build an app with Creatio AI app development toolkit
Migrate a section from Classic UI to Freedom UI
Convert web pages to mobile pages