Index page
Back

Contents

VEM Components and Security Role

What are the different parts of VEM?

VEM consists of a number of components that are seamlessly integrated into MS Dynamics CRM to enhance eMarketing capabilities. The 'VEM User' security role assists in separating users you wish have access to VEM features and those you do not.

User Interface

The VEM user interface consists of integrations into both the CRM sitemap and ISV configuration. Principal VEM custom entities are accessible via the VEM section on the CRM 'wunderbar', which is made visible only to users who have privileges endowed with the VEM User role. Integrations on standard entities are made visible/active only after testing for this role.

VEM Reports

VEM offers basic drillldown analysis reports for quick and normal email activities. These may be accessed currently via the Workplace Reports and are available to all users. This visibility may be customised by changing the top level reports from organization-wide to personal and then sharing the report with individuals or teams as appropriate.

Sitemap - VEM Section

This section appears after the Marketing section and shows a 'dashboard' report together with access to setting up Scheduled Email Sendings and Email Links, You can also see a deep view of Email Clicks and List Subscriptions generated by recipients. Likewise associated views appear for these latter entities under related entities like recipients (accounts, contacts and leads), marketing lists and email links.

ISV Configuration

Up

The VEM User role includes ISV Config viewing, but as this privilege may be assigned anyway all actions on VEM introduced buttons and menu items are first specifically verified against this role.

VEM Template Editor - this button is placed on the templates grid toolbar. For VEM Users it opens the VEM enhanced template editor, for others it opens the standard template editor.

Start VEM Processing Workflow - this menu item may be found on the grid toolbar of quick and normal campaigns and also campaign activities. For VEM Users it creates a new instance of the VEM Processor Workflow that retrieves and sends the oldest batch of draft emails awaiting the VEM delay-send scheduler - it expedites this process. The parameters of this batch are determined in the workflow activity. For others it simply refreshes the grid.

System Entity Form Customizations

The primary entity used by VEM is email and the VEM onload handler, after checking whether a VEM User switches the visibility of VEM custom attribute fields depending on context. These fields are generally visible in the forms shown in the email quick campaign and the distribute email campaign activity.

Certain email views may be further user-customized to utilise VEM custom attributes such as Last Read, Read Count, Response Type (undefined, delivery status notification, out-of-office, response).

The VEM Dynamic List feature allows periodic synchronisation of the list to a predetermined view constructed in Advanced Find, which is gated by specific negative list subscriptions created by recipients themselves. This feature utilises a VEM custom workflow and adds Dynamic View and Last Sync'd fields to the marketing list form for VEM Users.

VEM User Role

Apart from System Adminstrators, access to VEM's features and facilities can mostly be controlled by assigning this role to users. It is intended to provide the minimum set of privileges to allow use of VEM.


Top | Back
Copyright 2000-2012. Vizola Technology. All rights reserved. All trademarks acknowledged. Privacy statement