Electronic Signature Preferences
electronicSignaturePreferences Based on 26C
Create, change, delete and look up Electronic Signature Preferences, with electronic signature transaction types. Actions include validate pending work order approvals.
- Operations
- GET (list)GET (one)POST (create)PATCH (update)DELETE1 action
- Record key
SignatureOrganizationId- Required on create
OrganizationId- At a glance
- 4 fields1 finders1 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /fscmRestApi/resources/11.13.18.05/electronicSignaturePreferences?fields=OrganizationCode,OrganizationId,OrganizationName,SignatureOrganizationId&limit=25&onlyData=true
{
"items": [
{
"OrganizationCode": "<string, max 18>",
"OrganizationId": 0,
"OrganizationName": "<string, max 240>",
"SignatureOrganizationId": 0
}
],
"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 4
| Attribute | Type | Use |
|---|---|---|
OrganizationCode | text · max 18 | Read-onlySearchable |
OrganizationId | number | Required on createUpdatableSearchable |
OrganizationName | text · max 240 | Read-onlySearchable |
SignatureOrganizationId | number | Optional on createUpdatableSearchable |
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.
findByTransaction·OrganizationIdTransactionTypeCode
Check a payload
Checked in your browser only; nothing you paste is sent anywhere. Checks names and flags, not values.
Children 1
Child resources sit under one record: /fscmRestApi/resources/11.13.18.05/electronicSignaturePreferences/{SignatureOrganizationId}/child/<name>. Add them to a GET with expand.
electronicSignatureTransactionTypesGET · POST · PATCH · DELETE Electronic Signature Transaction Types · 10 fieldsAdhocSignerScopeSignatureDefinitionIdSignatureEnabledFlagSignatureModeEditableFlagSignatureOrganizationIdSignatureTypeSignatureTypeCodeTransactionTransactionTypeCodeTransactionTypeId
Actions 1
POST …/action/validatePendingWorkOrderApprovals·organizationIdsignatureEnabledFlag
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/electronicSignaturePreferencesand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
findByTransactionfor 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:OrganizationId, notorganizationid. - 2 fields are read-only: sending them in POST or PATCH fails or is ignored. The builder leaves them out.
- A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through.