JMA

20260130.205

Jan 30, 2026

API version: 9.2.0

Jobs, WorkData and ProcessingSteps now have TagDetails which holds specifics to the internal representation of tags
- Migrate internal tag representation to full semantic model
- Migrate existing tags

Jan 15, 2026

API version: 9.1.0

Allow filtering ProcessingSteps by ProCon version property, by exact string match

Jan 13, 2026

API version: 9.0.0

Allow filtering and sorting by versions
Allow version ranges to be used (similar to npm)
Fix issue with admin query: public ProcessingSteps was not visible when admin was using normal query
More actions now require code contributor permission
Reworked registering of PS, now only an upload is used and version, function name are taken from manifest
ProcessingSteps now contain the ProCon version used when a deployment exists
ProcessingStep property edit is more limited now
Platform user and owner renamed

Dec 9, 2025

API version: 8.8.0

Fix copy PS to user and org did not return new PS ID
Add Action classes “Destructive” and “LongRunningBackground” for more information on the effect
Add fix OTL metric requested non existing PS Queues if the PS was deprecated
Do reverse mapping of grants and roles in info endpoint
Add remote endpoint in info HTO which is used to connect with remote workers Info->Remote
Now all JMA actions have modern Draft 2020-12 JsonSchemas
- more properties are now required in the schema to allow the caller to check early

Dec 2, 2025

API version: 8.8.0

Processing steps can now be deployed directly via JMA API.
Registering or deploying a ProcessingStep now requires CodeContributor permissions
A CodeHash must be assigned beforehand to any processing step that is to be deployed. Existing CodeHash cannot be changed but it can be removed by an admin and assigned again by a user with sufficient authority.
Afterwards, the processing step can be deployed by optionally configuring these parameters or using default values: ResourcePreset, EntryPoint and Scaling.
A deployed step can be re-deployed with a different configuration infinite number of times.
A deployed step may be suspended by the user, in which case the configuration is saved but the deployment itself is removed. A suspended deployment can be resumed later with the saved configuration.
A processing step that is not platform deployed can optionally be marked as “externally deployed” to provide information that it is externally deployed.
Deployments can be removed at any time by the user.

Nov 17, 2025

API version: 8.6.0

Use the new background worker feature for “restore all job read models” and “restore some job read models” operation.

Nov 4, 2025

API version: 8.6.0

Add API events, provides an SSE feed with information on changes
Add cache headers to EntryPoint, and Root nodes and parameter schemas so clients know they can be cached
Allow caching of CORS response
New RMQ queue layout, including the organization context
- no function naming collision between contexts
Present registry and SSE endpoint in Info
Fix action titles do now contain a title usable in UI

Oct 27, 2025

API version: 8.5.0

Processing steps can now be deprecated.
- Jobs can not start with deprecated function
- No RMQ queues maintained for deprecated functions

Sep 8, 2025

API version: 8.3.0

Aug 28, 2025

API version: 8.2.0

Add action to delete Processing step. It only succeeds if the step is not used by any job.