Menu
Provide information and rules for Axon Ivy variables configurations. Use when working with Axon Ivy variable.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Rules and best practices for Axon Ivy HTML Dialog implementations including PrimeFaces, PrimeFlex, CSS, JS, and Ivy components.
Rules and patterns for the `com.axonivy.utils.persistence` library — the Axon Ivy community helper around JPA. Covers `AuditableIdEntity`, `AuditableIdDAO`, `CriteriaQueryContext`, and `UpdateQueryContext`. Use whenever Java code in `src/` reads or writes data through a DAO that extends `AuditableIdDAO` or an entity that extends `AuditableIdEntity`.
Rules and patterns for creating, editing, reviewing, and fixing Axon Ivy workflow processes (.p.json files). Use this when working with any .p.json file — including checking existing processes for errors, reviewing script code, or fixing IvyScript issues.
Verification checklist for Axon Ivy process files (.p.json). Use this whenever a .p.json file is created, modified, or reviewed — either after axon-ivy-process skill, or when a user asks to check, verify, or fix a process file for errors.
Master router skill for all requirement clarification, create story, development, review, and testing tasks. Detects user intent and orchestrates the correct path using specialized skills and parallel subagents.
Rules and patterns for sending email from an Axon Ivy project. Covers sender / recipient resolution, subject and body templating, attachments, and the recommended builder pattern for one mail type per class. Use whenever Java code or a process step composes or sends an email.
| name | axon-ivy-variable-config |
| description | Provide information and rules for Axon Ivy variables configurations. Use when working with Axon Ivy variable. |
config/variables.yaml.json filesconfig/variables.yaml : Environment variables
Variables default to String. To use a different type, add a YAML comment annotation:
| Annotation | Type | Example Value |
|---|---|---|
| (none) | String (default) | "My Application" |
# [type: Integer] | Integer | 3 |
# [type: Password] | Password (encrypted, hidden in UI) | "secret-value" |
# [file: json] | JSON file reference | "" (value in separate .json file) |
The annotation comment must appear on the line directly above the value: entry.
Variables:
# String (default type)
AppName: "My Application"
# Integer
MaxRetries:
# [type: Integer]
value: 3
# Password (encrypted, hidden in UI)
Api:
Secret:
# [type: Password]
value: "secret-value"
# JSON file reference
Portal:
# [file: json]
Dashboard: ""
# Nested JSON in subfolder
Processes:
# [file: json]
ExternalLinks: ""
For JSON-type variables, create a variables folder under config/:
config/
├── variables.yaml
└── variables/
└── Portal/ # Matches "Portal:" section
├── Dashboard.json # Portal.Dashboard
└── Processes/ # Nested namespace
└── ExternalLinks.json # Portal.Processes.ExternalLinks
Empty array (Portal/Processes/ExternalLinks.json):
[]
Complex configuration (Portal/Dashboard.json):
[
{
"id": "default-dashboard",
"version": "13.0.0",
"titles": [
{ "locale": "en", "value": "Dashboard" }
],
"widgets": []
}
]
// Access variables in Java/IvyScript
String appName = Ivy.var().get("AppName");
String apiUrl = Ivy.var().get("Api.BaseUrl");
// In EL expressions
#{ivy.var.AppName}
#{ivy.var.Api.BaseUrl}