The Workflow module is a collection of components that augment the NetXposure Digital Asset Management (DAM) application into an asset workflow system. The module has four main components:
- Review and Approval
- Status Attribute and Icons
- CS Workflow app
- Auto Task
These components are integrated and work in conjunction with each other; however, each can be used by itself as well.
See Video Web Demo of Workflow Module
Workflow Module Topology
The high-level view of these components starts with the Review and Approval functions. These allow users within the DAM to collaborate on work-in-progress asset files. The Review tool allows users to enter notes on their opinions and to set various status levels (eg “Approved”, “Rejected”, etc) on assets under review.
The workflow module allows for a custom attribute mapping for those status levels. So when a user changes the status of an asset in a review (or otherwise) that asset can be presented with visual icons that designate that status. And because the status is mapped to an attribute, assets in lists can be sorted on their status. Additionally, saved searches can be set up around categories and status to provide project “smart folders” for creatives.
The CS Workflow app turbo-charges your creatives in their interaction with the DAM. Instead of: logging into the Web UI, searching there, downloading files to their Desktop, opening those files in Adobe Creative Suite applications, editing those files, and finally uploading them back into the DAM — the CS Workflow streamlines this entire process with an app that can broker the communication between the DAM and Creative Suites. The CS Workflow app provides a targeted User Interface for the creative user and allow them to work more directly in their preferred applications: Photoshop, Illustrator and InDesign. The CS Workflow app provides for check-in/out functions as well as status updates.
Finally, the Auto Task function provides for automating tasks that can further leverage the status of an asset, or otherwise. Criteria can be defined — such as a category move or attribute value change — and a wide range of actions can be executed including repurposing, attribute changes, moving, exporting, cloning, and notifications. For example, approved assets might be moved to a different category, repurposed into JPEG format for a web site, and then a notification is sent to a remote web service to retrieve the new data.
