Fixing the two octet-stream Workflow endpoints

[jdcmsd]

Parent Issue

#28600

Task

Five endpoints remained unfinished in the Workflow API doc due to technical hurdles. Two of those five were return octet-stream data, and both would throw 406 errors when called from the API Playground, even with a data payload shown to work in curl.

This task is to attach a PR that fixes those two.

Proposed Objective

Documentation

Proposed Priority

Priority 3 - Average

Acceptance Criteria

POST /api/v1/workflow/actions/default/fire/{systemAction} and PATCH /api/v1/workflow/actions/default/fire/{systemAction} should both be able to return a 200 response if given a useful payload in the API Playground.

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[valentinogiardino]

IQA PASSED

• Tested on latest trunk trunk_324de85 - Chrome, Firefox, Edge
• In the API Playground, both endpoints return a 200 response if given a useful payload.

Screenshots

POST /api/v1/workflow/actions/default/fire/{systemAction}

PATCH /api/v1/workflow/actions/default/fire/{systemAction}

[bryanboza]

Fixed, tested on the latest trunk // Docker // FF