Perform an HTTP request POST payload empty

[fulkron]

In an old workflow (several versions ago) I had to request and external web call using POST request method.

I the old workflow I provided a list of template entries in the payload, please see below:

{"document_uuid":"{{document.uuid}}", "document_type":"{{document.document_type.label}}","titolo":" {{ document.label }}","\":"{{ document.pk}}","workflow":"{{ workflow_instance.workflow }}","workflowID":"{{ workflow_instance.id}}"}

I discovered using the same payload in the new version (4,.8.2) all empty fields except those related to workflow_instance…

for example: {{document.uuid}} how is called now ? the same for {{ document.label }} end so on…

Where can I find the documentation in this knowledge base to transform my payload with new template entries ?

Thanks a lot

Dario

[roberto.rosario]

Locations

The best places to look for such changes are the release notes under the “Backward incompatible changes” section.

https://docs.mayan-edms.com/releases/4.5.html#backward-incompatible-changes

The other place is the Knowledge Base articles sharing work in progress for upcoming versions.

Version 4.8 work in progress

And the follow up articles after a version is release explaining changes and showcasing the new features.

Version 4.8 new features
Configuring File Metadata Drivers
Using Ollama Integration to Automatically Classify Driver Licenses by US State

Upgrade method

For multi version upgrades we recommend doing them in steps by the latest bug fix release of each minor version. Then read each release notes for the next version to know what to expected, do adjustments to the configuration and then proceed to the next minor version. This way disruptions are kept to a minimum.

Databases and for the most part settings are automatically migrated. Only user entered content is not migrate because of the difficulty parsing it. Attempting to automatically migrate user content might end up causing more problems.

Further changes

Besides making workflow document access work under the variable workflow_instance there are not other changes in that regard.

The only change related to workflows is the addition of a new variable to make things easier. This was an undocumented variable, later removed, now re-added as an official feature.

entry_log variable references here:

https://docs.mayan-edms.com/releases/4.8.html#workflows

and here:

HTTP workflow Actions not executed after upgrade to 4.7

Since version 4.5 the context of the workflow is being updated incrementally into namespaces to avoid context clutter. https://docs.mayan-edms.com/releases/4.5.html#id9 I can’t find the exact commit where entry_log was removed from the state action context. My guess is that this variable was regarded as internal/private to the workflow instance and not meant for user access. I’ll audit the commits of the workflow for the past releases to determine if this was the correct course of action to m…

[fulkron]

Fixed with {{workflow_instance.document.uuid}} and so on.
Thanks!
Dario