Business Process User Alert Configurations
businessProcessUserAlertConfigurations Based on latest (2026.09)
Run actions on Business Process User Alert Configurations. Actions include get error templates and is alert config feature enabled.
Oracle's specification marks GET (list), GET (one), POST (create), PATCH (update), DELETE as not supported on this resource.
The record key businessProcessUserAlertConfigurationsUniqID is a generated hash. Take it from the record's links (rel self) in a GET response; never build it yourself.
- Operations
- GET (list)GET (one)POST (create)PATCH (update)DELETE3 actions
- Record key
businessProcessUserAlertConfigurationsUniqID- Required on create
- none marked
- At a glance
- 3 fields1 finders0 children
Try it
No parameters listed.
POST /hcmRestApi/resources/11.13.18.05/businessProcessUserAlertConfigurations/action/getErrorTemplates Content-Type: application/vnd.oracle.adf.action+json
{}Shapes and placeholders, not real data. Replace https://<your-pod> and the login with your own: this site never sees them. Based on Oracle's latest (2026.09) REST specification.
Fields 3
| Attribute | Type | Use |
|---|---|---|
AlertTemplateGlobalUniqueId | text · max 255 | Read-onlySearchable |
PersonId | text · max 255 | Read-onlySearchable |
ProcessId | text · max 255 | Read-onlySearchable |
Names, types, labels and flags from Oracle's REST specification (latest (2026.09)). Flexfield and custom attributes vary by pod: check /describe for yours.
Finders 1
Predefined searches: ?finder=Name;variable=value,variable2=value2. Pick one in Try it to build the call.
getUserConfigurationForProcessId·pProcessId
Check a payload
Checked in your browser only; nothing you paste is sent anywhere. Checks names and flags, not values.
Actions 3
POST …/action/getErrorTemplatesPOST …/action/isAlertConfigFeatureEnabledPOST …/action/updateAlertConfiguration·processIdalertParamsuserConfigList
Actions use Content-Type: application/vnd.oracle.adf.action+json. A path with a {key} runs on one record.
Use in AI Agent Studio
- Point a Business Object or REST tool at
/hcmRestApi/resources/11.13.18.05/businessProcessUserAlertConfigurationsand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
getUserConfigurationForProcessIdfor the agent's main search: its variables become clean tool parameters. - Narrow with
q=on searchable fields and a smalllimit; for a count usetotalResults=true&limit=1. - Call once and pass the result on to later steps rather than calling the same endpoint again.
- This resource can change data. Put a human approval step before any create, update, delete or action call.
More in For Builders.
Pitfalls
- Attribute names are case-sensitive in
q,fieldsand bodies:AlertTemplateGlobalUniqueId, notalerttemplateglobaluniqueid. - 3 fields are read-only: sending them in POST or PATCH fails or is ignored. The builder leaves them out.
onlyData=trueremoveslinks, and this resource's key only comes fromlinks. Leave it off when you need the key.- A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through.