Page Comparison

...

...

If you have an existing starter-kit project with no specific customizations on the existing upload feature, you will only have to respect the Prerequisites. It means you will have to create all the new structures, to restore all changes on the existing structures and update/create all the created/updated instances present in the narNAR.

Then if you want to fully benefit from the creative workflow, follow Common steps .

1.2/ Existing with customizations

If your project has a customized workflow for the upload feature, the install installation of the creative workflow will be more complicated. The new feature needs the update made on the workflow of massimportitems objects. This means, that on the project side, a choice has to be made : Using the creative workflow, OR using the upload.

...

• disable this plugin : PACKAGED_CreativeWorkflow

• disable the “spaces” feature on portal’s features config

• enable the uplaod upload feature on the portal’s features config

1.4/ Creative workflow with security from security.xml

Here you will find current permissions by role (provided with a starter-kit) transcribed into readable text. This way, we hope you can setup set up appropriate security rules for the creative worklow workflow while using a security from security.xml.

...

In this case, you will only have to respect the Prerequisites. And they are all comming coming by default with the 2024.1.

Just be sure to call the update (admin) endpoint given by PACKAGED_Security.

For You will need to create all your new library structures you will need to create them by copying the current asset structure, because you will need to have the space spaces prop and the tags from the asset on your library structures.

...

The existing wkfmassimportitem and it’s its actions have been updated for the creative workflow. Also, this workflow is still usable for the upload feature, only some status/action labels will be different.

These are the main updates on the workflow :

• Position reordering

• Colors The colors have been changed

...

• New statuses

  • id 3 : check => default status for imported items

  • id 4 : validate

• “Index” status (id 8 ) has been renamed to review

• Wkfmassimportitemactions have been reorganized. Actions have been added from and towards each one of these statuses : rejected, check, review, validate, approved

• Also for the existing statuses, when it was possible, existing actions have been updated to avoid adding actions and having other actions becoming become useless. Depending on the modified instance, the update was on the target status , or on the action name.

• Statuses names, ids IDs, and action names are used on the portal’s configuration for dam-import and for spaces domain.

4/ Configuration possibilities

Change the status of assets created by the Creative workflow

By default, the status of a media asset exiting the creative workflow is “published”.

This status can be changed if necessary, following these recommendations :

The current behavior is configured by a damutils configuration, which enables the transition of all assets created through the creative workflow to the published status (ID 6).

The actual configuration :

...

an asset published from the creative workflow has the status Published.

At first, the asset has the default status set on the asset’s structure (Draft state the object asset provided by the NAR). Then, the following asynchronous transformation, configured on the parameter dam_denormalization_config of the plugin PACKAGED_DAM_Utils, will be applied on top of it to execute a workflow trigger that takes the asset to the Published state :

{
            "objectSelector": "#damobject",
  
         "preventGuard": {
                "classAlias": "negate",
                "input": {
 
                  "preset": "canPublishisSpaceAsset"
                }
            },
            "workflowTrigger": [
                "publish"
   
        ]
        }

This configuration works for the assets created from the creative workflow, only because :

• We are filling tmpsource with “massimport” on the item (before asset creation), and then the created asset has a tmpsource value which removed just after the status change

• User has the enough rights to change the status of the asset.

So if you want to change the status of asset created with the creative worfklow, you will have to change the action called in worfklowTriggertransformation does the following, on inserted (or updated if it is enabled) instances :

• It is applied on object instances that have the tag #damobject on their structure

• If the instance has been published from a space inside the creative workflow (the preset isSpaceAsset checks if there is at least one instance inside the property spaces), the action “publish“ is processed on the instance.

In conclusion, to personalize the status of the assets created from creative workflow, you can :

• Use your desired default status defined on your asset’s structure and remove/disable provided transformations that apply workflow triggers.

• Create transformations inside the parameter dam_denormalization_config of the plugin PACKAGED_DAM_Utils that follow your desired logic. The following page deals with how to create a transformation that suits your needs: https://crossmedia.atlassian.net/wiki/spaces/WD/pages/377585665/Metadata+and+AI+extraction+with+DAM+Utils#Setting-up-the-transformations.
  

Examples of transformations for damobject instances that utilize workflow triggers

    {
        "objectSelector": "#damobject",
        "preventGuard": {
            "classAlias": "negate",
            "input": {
                "preset": "canPublish"
            }
        },
        "workflowTrigger": [
            "publish"
        ]
    },
    {
        "objectSelector": "#damobject",
        "preventGuard": {
            "classAlias": "negate",
            "input": {
                "preset": "canSubmit"
            }
        },
        "workflowTrigger": [
            "submit"
        ]
    }

The above examples of asynchronous transformations, which are set up on the parameter dam_denormalization_config, and are thus applied on damobject instances not having the spaces property filled, do the following in that order:

• If the damobject instance has been created by a user who has the rights to publish the asset, the workflow action publish will be executed for the asset

• If the damobject instance has been created by a user who has the rights to submit the asset, the workflow action submit will be executed for the asset.
  To sum up, with those 2 transformations, the new asset will have the Published status if the user who created the asset has rights to publish it. Else, if the surfer has the rights to submit it, the workflow action submit will be executed on the asset.

Portal configuration

...