We have successfully defined some mandatory metadata fields using Create, add, and manage metadata schemas. Everything is working as expected for saving assets -- not allowed if the required metadata isn't filled in. The red notification messages are showing appropriately on the assets with missing mandatory metadata also, however, this missing metadata isn't preventing the assets from being published.
How can I prevent publication with missing mandatory metafields? Do I need to create a custom workflow which somehow handles that?
Would I need to activate the time-based scheduler for Missing Metadata Notification in order to create the jcr:content node to have something to check before publishing? This could be too taxing on our server as the number of assets have grows.
Is it possible to hide/disable the Publish button for assets with missing metadata? That could be difficult when people want to publish large groups of assets at one time. I don't want to require assets to be published one at a time by disabling the Publish on the card view pages.
Version: 6.3.3.2
Any help would be appreciated.
Solved! Go to Solution.
"Do I need to create a custom workflow which somehow handles that" - the answer is yes. That would be the only way for this requirement.
Views
Replies
Total Likes
"Do I need to create a custom workflow which somehow handles that" - the answer is yes. That would be the only way for this requirement.
Views
Replies
Total Likes
Scott,
I don't have a lot of experience with custom workflows. Do you have any recommendations or tutorials that might help lead me in the right direction for something like this?
Thanks!
Views
Replies
Total Likes
Yes - we have many AEM HELPX articles on how to create a custom workflow step. Start with this one on how to create a custom workflow step and work with Assets via the AssetManager API:
Modifying Digital Assets using Adobe Experience Manager Workflows
This will teach you how to work with the various AEM APIs from within a custom workflow step.
Views
Likes
Replies