Wednesday, November 19, 2008

Installing The Event Management Accelerator in a Hosted CRM environment

Hi Guys

I have been having a play around with the newly released accelerator on our hosted CRM platform, and I have to say so far so good.

I thought I would just drop down a few thoughts about the install process (which is very easy) and a few shots of what it should look like.

The very first thing that I found was that after the download had extracted itself, when I went to upload the customisations, CRM returned the error that the file path was too long, so my first tip is to extract the files to your own folder path rather than the default path and thus saving you a few minutes!

Once all customisations had been uploaded, it was then turn to publish the workflows, which as the instructions state cannot be published until you edit the three workflows that send emails, so you have to go in and change the sender from "Microsoft Web User" to a user within your organisation.

Once these are all published you should see within your Campaigns the added links on the left hand navigation.









The final part of the install is to add the eventmanagement plugin, by running the msa_eventmanagement.install.exe on your CRM server. You must remeber to state which organisation you are adding the plugin to (must be the same as the org you uploaded the customisations to)



Once this has successfully run, you will need to go into customisations and you will see the entity event management configuration, edit this entity and set it to show up in the settings area of CRM.



Finally go the settings area and you will see that the entity now appears as an admin area. Go into this area and you will need to set the first configuration settings


The settings should be as follows:


The Event status code values need to be read from the Status Code attribute of the campaign entity. We enter these manually just in case the import was not able to use the default values for Status Code. The following status codes should be used:
Event is Open for registration = 2 (Launched)
Event is Sold Out = 200001 (Sold Out)
Event is Waitlisting registrations = 200000 (Waitlisting)
These codes are used so that the portal can adjust the display of specific events and in the case of sold out events ensure that the web customer can’t register for the event.

The following Campaign Response Response Codes are used:
Registered = 200000 (Registered)
Registration Canceled = 200001 (Registration Canceled)
Waitlist = 200002 (Place this customer on the waitlist)

Additionally, we need to store the reference number for the Campaign Response Channel type which by default is set to 200000 for the web channel.


Once that is saved you are ready to start using Event Management!

No comments:

Post a Comment