Asset Workflow State - Githubissues

fashxp commented 2 months ago

markus-moser commented 2 weeks ago

@studio-backend-team

In addition to the already provided workflow actions in the API we will need some more details:

In the workflow places config we have a attribute visibleInHeader. We will need this to identify which places should be shown next to the transitions button: I think it is fine when we just add this to the existing /studio/api/workflows/details endpoint. visibleInHeader is not the best name anymore because it is not shown in the header anymore. But let's keep it at least for the moment. We can think about changing it in the workflow engine in the next major version(s) of pimcore/pimcore.
In the asset detail API we should add a boolean indicator if a workflow is available. This would avoid calling the workflow detail API all the time for entities without any workflow.
For the notes within a transition or global action you implemnted already commentEnabled and commentRequired attributes. We will need also the additionalFields (with the sub attributes name, fieldType, title, required and fieldTypeSettings) there.
Don't know if this is already respected but for the /studio/api/workflows/action endpoint we will also need to respect the various options like comment and additional fields.

lukmzig commented 1 day ago

@markus-moser

for the first point we added visibleInDetail parameter which reflects the visibleInHeader value
boolean indicator if a workflow is available - would it be possible to add this parameter into the GDI? That would be somehow the fastest solution for now since our detail API now delivers only data from the GDI.

pimcore / studio-ui-bundle