Hi everyone
I'm running into an issue with completing a workflow assignment using the OSLC API in Maximo. I'll share my findings and details below - maybe someone has faced this before or knows the fix.
Case 1 – Works Fine (Task Node with 1–2 Choices)
For normal task nodes (where the workflow assignment has only one or two possible actions), I can complete the assignment successfully.
Get assignments
GET /oslc/os/mxapiwfassignment?lean=1&oslc.select=*&oslc.pageSize=100&_lid=...&_lpwd=...
Example response snippet:
{
"wfassignmentid": 33843,
"description": "SR needs review.",
"assignstatus": "ACTIVE",
"wfaction": [
{
"instruction": "Submit SR.",
"actionid": 8
},
{
"instruction": "Cancel SR.",
"actionid": 7
}
]
}
Complete the assignment
POST /oslc/os/mxapiwfassignment/33843?action=wsmethod:completeAssignment&_lid=...&_lpwd=...
Header: x-method-override: PATCH
Body:
{
"memo": "Assignment completed",
"accepted": true
}
Result: Works perfectly - workflow moves forward.
Case 2 – Fails (Input Node with 3+ Choices)
The issue appears when the workflow input node has more than two options.
Get assignments
GET /oslc/os/mxapiwfassignment?lean=1&oslc.select=*&oslc.pageSize=100&_lid=...&_lpwd=...
Response snippet:
{
"wfassignmentid": 33927,
"description": "PM WO needs review.",
"assignstatus": "ACTIVE",
"wfaction": [
{
"instruction": "Select suitable action:",
"actionid": 35
}
]
}
Try to complete the assignment
POST /oslc/os/mxapiwfassignment/33927?action=wsmethod:completeAssignment&_lid=...&_lpwd=...
Header: x-method-override: PATCH
Body:
{
"memo": "Assignment completed",
"accepted": true
}
Response:
{
"nodetype": "INPUT",
"internalnodetype": "WFINPUT",
"member": [
{
"actionid": 38,
"instruction": "Initiate WO.",
"href": "null/0-97"
},
{
"actionid": 36,
"instruction": "Hold WO for site availability.",
"href": "null/1-95"
},
{
"actionid": 37,
"instruction": "Cancel WO.",
"href": "null/2-96"
}
]
}
At this point, it correctly returns the available options - but all the href values are "null/...", and the base URLs point to another old server, which already looks suspicious.
Try to choose one option manually
POST /oslc/os/mxapiwfassignment/33927?action=wsmethod:completeAssignment&_lid=...&_lpwd=...
Header: x-method-override: PATCH
Body:
{
"actionid": "37",
"memo": "Assignment completed"
}
Response:
{
"oslc:Error": {
"spi:reasonCode": "BMXAA5426E",
"oslc:message": "BMXAA5426E - Primitive type parameter cannot have null value."
}
}
Summary
✅ Works fine for task nodes with 1–2 choices
❌ Fails for input nodes with 3+ options
❌ Returns "href": "null/…" and old base URLs
❌ Throws BMXAA5426E - Primitive type parameter cannot have null value when I try to select one action manually
What I Think
This looks like an OSLC configuration problem rather than an API syntax issue.
The "null" hrefs and old hostnames suggest the OSLC Base URL or related system properties (mxe.oslc.webappurl, etc.) might be misconfigured.
Question
Has anyone else faced this issue with workflow input nodes having multiple options?
Is there a known fix or configuration step needed to make OSLC routing work correctly for these cases?
Any pointers would be really appreciated
#Administration#Integrations#MaximoUserGroups------------------------------
m gh
futech
------------------------------