...
Expand | ||
---|---|---|
| ||
View Action:
Insert Action:
Update Action:
Update Action:
Update Action:
Delete Action:
Delete Action:
Change Status Action:
Change Status Action:
|
Expand | ||
---|---|---|
| ||
Action : viewfor objects :
permissionsPermission:
for objects :
permissions Permission :
for objects :
permission :
|
...
Expand | ||
---|---|---|
| ||
View Action:
Insert Action:
Insert Action:
Update Action:
Update Action:
Delete Action:
Delete Action:
Change Status Action:
Change Status Action:
|
...
Info |
---|
|
Status of assets created with the creative workflow
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 :
Code Block |
---|
{
"objectSelector": "#damobject",
"preventGuard": {
"classAlias": "negate",
"input": {
"preset": "canPublish"
}
},
"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 worfklowTrigger
If new workflow status added, how will notifications behave
We are currently sending email notifications on each status change for each teammember or only for the owner according to PACKAGED_CreativeWorkflow.send_notification_to_team 's value.
Here you will find more detailed information about the notification system setup for the creative workflow.
As status change email notification are based on the delayed notification system, if you want to add a customized behaviour for a specific status (for example), you will have to create your own Groovy script (you can check existing ones for inspiration).
and update the configuration of PACKAGED_CreativeWorkflow.batch_topics_processors. You will have to follow the instructions described in the link provided above.