Asynchronous Separation of Duties Simulations
advancedControlsRolesProvisioning Based on 26C
Look up Asynchronous Separation of Duties Simulations. Actions include approve provisioning request and get request status. Changes only through its actions.
The record key advancedControlsRolesProvisioningUniqID 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)3 actions
- Record key
advancedControlsRolesProvisioningUniqID- Required on create
- no create on this resource
- At a glance
- 7 fields1 finders0 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /fscmRestApi/resources/11.13.18.05/advancedControlsRolesProvisioning?fields=conflictingRole,controlId,controlName,incidentPath,incidentPathCode&limit=25&onlyData=true
{
"items": [
{
"conflictingRole": "<string, max 256>",
"controlId": 0,
"controlName": "<string, max 256>",
"incidentPath": "<string, max 256>",
"incidentPathCode": "<string, max 256>"
}
],
"count": 25,
"hasMore": true,
"limit": 25,
"offset": 0
}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 26C REST specification.
Fields 7
| Attribute | Type | Use |
|---|---|---|
conflictingRole | text · max 256 | Read-onlySearchable |
controlId | number | Read-onlySearchable |
controlName | text · max 256 | Read-onlySearchable |
incidentPath | text · max 256 | Read-onlySearchable |
incidentPathCode | text · max 256 | Read-onlySearchable |
inputRoleCode | text · max 256 | Read-onlySearchable |
inputRoleName | text · max 256 | Read-onlySearchable |
Names, types, labels and flags from Oracle's REST specification (26C). 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.
getUserProvisioningAnalysisIncidents·requestId
Check a payload
Checked in your browser only; nothing you paste is sent anywhere. Checks names and flags, not values.
Actions 3
POST …/action/approveProvisioningRequest·requestIdapprovedRolesPOST …/action/getRequestStatus·requestIdPOST …/action/runUserProvisioningAnalysis·provisioningInfouserName
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
/fscmRestApi/resources/11.13.18.05/advancedControlsRolesProvisioningand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
getUserProvisioningAnalysisIncidentsfor 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:conflictingRole, notconflictingrole. 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.