Asset Group Rules
assetGroupRules Based on 26C
Create, change, delete and look up Asset Group Rules, with grouping attributes and usages.
- Operations
- GET (list)GET (one)POST (create)PATCH (update)DELETE
- Record key
RuleId- Required on create
RuleCodeRuleName- At a glance
- 7 fields0 finders2 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /fscmRestApi/resources/11.13.18.05/assetGroupRules?fields=EnforceUniqueAssignmentFlag,InactiveOn,RuleCode,RuleDescription,RuleId&limit=25&onlyData=true
{
"items": [
{
"EnforceUniqueAssignmentFlag": false,
"InactiveOn": "2026-01-31",
"RuleCode": "<string, max 30>",
"RuleDescription": "<string, max 240>",
"RuleId": 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 7
| Attribute | Type | Use |
|---|---|---|
EnforceUniqueAssignmentFlag | yes/no · max 1 · default false | Optional on createUpdatableSearchable |
InactiveOn | date | Optional on createUpdatableSearchable |
RuleCode | text · max 30 | Required on createUpdatableSearchable |
RuleDescription | text · max 240 | Optional on createUpdatableSearchable |
RuleId | number | Optional on createUpdatableSearchable |
RuleName | text · max 120 | Required on createUpdatableSearchable |
RuleReferencedFlag | yes/no · max 255 | Read-only |
Names, types, labels and flags from Oracle's REST specification (26C). Flexfield and custom attributes vary by pod: check /describe for yours.
Check a payload
Checked in your browser only; nothing you paste is sent anywhere. Checks names and flags, not values.
Children 2
Child resources sit under one record: /fscmRestApi/resources/11.13.18.05/assetGroupRules/{RuleId}/child/<name>. Add them to a GET with expand.
groupingAttributesGET · POST · DELETE Grouping Attributes · 3 fieldsAttributeCodeAttributeNameRuleGroupingAttributeIdusagesGET · POST · DELETE Usages · 3 fieldsRuleUsageIdUsageCodeUsageName
Use in AI Agent Studio
- Point a Business Object or REST tool at
/fscmRestApi/resources/11.13.18.05/assetGroupRulesand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - 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:EnforceUniqueAssignmentFlag, notenforceuniqueassignmentflag. - 1 fields are read-only: sending them in POST or PATCH fails or is ignored. The builder leaves them out.
- Send dates as
YYYY-MM-DD; date-time fields take ISO 8601 with a time zone. - A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through. - Text fields have maximum lengths (shown in the field table). Longer values are rejected.