Show TOC

Process documentationWorkflow for Approving Digital Assets Locate this document in the navigation structure

 

The approval workflow ensures that new digital assets are checked by an employee. This workflow prevents the user from uploading digital assets that have not been released to the system, where they are directly available to the end user for selection.

The workflow is activated when the status of a digital asset is set to For Approval and the version of the digital asset is saved.

For more information, see also Digital Asset Management and SAP Business Workflow.

Prerequisites

  • You have activated the event linkage (SAP==>CRM==>CRM-MKT==>CRM-MKT-DAM) for the workflow

  • The system default is that all users get one approval work item If only specific users should get the approval work item, set this in the processor assignment.

  • The approval workflow is based on CRM_DAM_STATUS in the Business Configuration Set, which must be activated.

    If you want to use another status, modify it for the approval workflow.

For more information, see also the Implementation Guide at   Customer Relationship Management   Basic Functions   SAP Business Workflow  

Process

Technical Implementation

Workflow Template

The current procedure is implemented in workflow template WS15100039 (CRM_DAM).

Here you have the following options:

  • Set the version to Active.

  • The version gets Active document status. An existing active version is set to the status that is defined in Customizing as an after-effective status.

  • Set the version to In Process.

  • The version is set to In Process document status and you must perform further qualifications.

  • Set the version to Rejected.

  • The version is set to Rejected document status.

  • You can cancel processing. The workflow entry stays in your inbox.

    All options are performed synchronously.

Triggering Events for the Workflow Template

Triggering event for the workflow is the event VERSION_CHANGED. The event belongs to object BUS2000261, which is triggered when the version of a digital asset is set to For Approval status and the version of the digital asset is saved.

Object Types

BUS2000261 – Asset version