Problem
The constant creation tool does not support the Process Model type. Supported types are: TEXT, NUMBER, INTEGER, BOOLEAN, DATE, DATETIME, TIME, USER, GROUP, FOLDER, DOCUMENT, PROCESS_MODEL.
Process Model is listed in the tool schema as a valid type but creation fails when attempted.
Evidence
When building an application that uses a!startProcessLink, the standard Appian pattern is to reference a Process Model constant:
a!startProcessLink(processModel: cons!MY_PROCESS_MODEL)
Since Process Model constants cannot be created via the API, this pattern cannot be fully automated. The agent must either:
- Pass a raw UUID string as a workaround (non-standard, fragile)
- Flag it as a manual step for the developer
Expected Behavior
createConstant with type: "PROCESS_MODEL" and value: "<process-model-uuid>" should create the constant successfully, consistent with how FOLDER and DOCUMENT constants work.
Impact
Process model references in link expressions and start process calls cannot be fully automated. This is a common pattern in applications with navigation between record views and action forms.
Problem
The constant creation tool does not support the Process Model type. Supported types are: TEXT, NUMBER, INTEGER, BOOLEAN, DATE, DATETIME, TIME, USER, GROUP, FOLDER, DOCUMENT, PROCESS_MODEL.
Process Model is listed in the tool schema as a valid type but creation fails when attempted.
Evidence
When building an application that uses
a!startProcessLink, the standard Appian pattern is to reference a Process Model constant:Since Process Model constants cannot be created via the API, this pattern cannot be fully automated. The agent must either:
Expected Behavior
createConstantwithtype: "PROCESS_MODEL"andvalue: "<process-model-uuid>"should create the constant successfully, consistent with how FOLDER and DOCUMENT constants work.Impact
Process model references in link expressions and start process calls cannot be fully automated. This is a common pattern in applications with navigation between record views and action forms.