Resurrect functionality Executing Commands Via API

[urbanekv (Václav Urbánek)]

I was trying to use existing functionality - calling work queue commands from API - described here - ORIGAM 2015 11 Release Notes - paragraph " Executing Commands Via API"

We make use of it, and it stopped working.

[jsusen (Jindřich Sušeň)]

The api will be on this path:
/workQueue/{QueueName}/{CommandName}?workQueueEntryId=xxx

It will be public. Access to the functionality will be controlled with role asignement. “*” means anyone can access it authorized or not.

pull request to 2022.4

[jsusen (Jindřich Sušeň)]

Executing WorkQueue Commands from API

You can call work queue commands by sending a POST http request to this end point: /workQueue/{QueueCode}/{CommandText}?workQueueEntryId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx Where QueueCode is content of the Code field on the screen Settings -> General -> Work Queues , The CommandName is content of the field Text on the same screen. The workQueueEntryId is id of the work queue entry to send to the command as a parameter. You can find the id on the screen Work Queue -> "the work queue". Here y…

[jsusen (Jindřich Sušeň)]

Work queue api

[jsusen (Jindřich Sušeň)]

Work queue api 2022 4

[zcapkova (Zuzana Čapková)]

Are the QueueName and CommandName parts of the path case sensitive?

[jsusen (Jindřich Sušeň)]

FIX: Authentication in work queue api made optional

[jsusen (Jindřich Sušeň)]

FIX: Authentication in work queue api made optional 2022.4

[jsusen (Jindřich Sušeň)]

FIX: Authentication in work queue api made optional 2023.1