// fusionrest agent · financials · list of values
Workflow Users List of Values
workflowUsers Based on 26C
Look up the list of values for Workflow Users.
/fscmRestApi/resources/11.13.18.05/workflowUsers
- Operations
- GET (list)GET (one)
- Record key
PersonId- Required on create
- no create on this resource
- At a glance
- 9 fields3 finders0 children
Try it
Response fields ·
Filters (q)
Only attributes Oracle marks as searchable are offered.
Finder
Paging and options
limit
GET /fscmRestApi/resources/11.13.18.05/workflowUsers?fields=EmailAddress,FirstName,LastName,LoggedInUser,ManagerName&limit=25&onlyData=true
Response shape (placeholders)
{
"items": [
{
"EmailAddress": "<string>",
"FirstName": "<string>",
"LastName": "<string>",
"LoggedInUser": "<string>",
"ManagerName": "<string>"
}
],
"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 9
| Attribute | Type | Use |
|---|---|---|
EmailAddress | text | Read-onlySearchable |
FirstName | text | Read-onlySearchable |
LastName | text | Read-onlySearchable |
LoggedInUser | text | Read-onlySearchable |
ManagerName | text | Read-onlySearchable |
PersonId | text | Read-onlySearchable |
TransactionIdentifier | text | Read-onlySearchable |
Username | text | Searchable |
WorkflowName | text | 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 3
Predefined searches: ?finder=Name;variable=value,variable2=value2. Pick one in Try it to build the call.
advancedSearch·emailfirstNamelastNameuserIDbasicSearch·searchStringfindUser·transactionIdentifieruserIDworkflowName
Check a payload
Checked in your browser only; nothing you paste is sent anywhere. Checks names and flags, not values.
Use in AI Agent Studio
- Point a Business Object or REST tool at
/fscmRestApi/resources/11.13.18.05/workflowUsersand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
advancedSearchfor 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.
More in For Builders.
Pitfalls
- Attribute names are case-sensitive in
q,fieldsand bodies:Username, notusername. - A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through.