I had a scenario where the customer wanted the helpdesk user to fill in some call analysis fields when a case was resolved.
Initially I made a new status called Completed, I created some new fields for the users to fill in regarding customer satisfaction, if they resolved the case within the time period and some other fields.
When the user changed the status to completed, some JavaScript made those fields required so the user had to fill them.
This worked fine unless the user press the Resolve Case button and this just closed the case without them having to fill in call analysis fields.
I initially looked into changing the case resolution form. The case resolution form pops up when you press the case resolved button and you have to fill in a few fields, the perfect place for some call analysis. Perfect except you can’t modify it, Microsoft don’t let you modify this Activity. I have no idea why but there you go.
I briefly thought about adding some rules to enable the case resolution button only when you clicked on the status completed.
I then saw some Javascript which did the job. It’s quite clever and I learnt some thing new in CRM.
The solution to my problem was some javascript which is triggered on the OnSave event on the Case form, it checks what type of save has happened and if it was triggered from pressing the Case Resolution it validated the form.
The answer although was shown on many forums originated from the blog post below. The blog post has a link to the javascript file you can download so I would definitely go there to get it. Also this is a great site for CRM developers with lots of other great blog posts like how to trigger a workflow using javascript
The original Javascript and example is taken from this blog post but has now been created as a wiki page blog post below, you need to look at the original article because it explains the whole solution ands walks you through it which I am not going to do.
// Use the following function on Form Save Event,
// CRM will pass the execution context in function parameter prmContext
function FrmOnSave(prmContext) {
// Local variable to store value indicating how the save event was initiated by the user.
var wod_SaveMode, wod_SaveEventVal;
// Change the Save Event Value as per required Save Event
wod_SaveEventVal = <Value>;
if (prmContext != null && prmContext.getEventArgs() != null) {
wod_SaveMode = prmContext.getEventArgs().getSaveMode();
// 1 will pass on Recalculate button click
if (wod_SaveMode == wod_SaveEventVal) {
// Write your validation code here
alert("Write your validation code here");
// Use the code line below only if validation is failed then abort function save event
prmContext.getEventArgs().preventDefault();
}
}
}
You can download the code from the blog link to a skydrive, click here for that
The code above is a neat solution to the problem. In the OnSave event it gets the code to pass variables, this then passes the context. Using the context you can then get the save mode prmContext.getEventArgs().getSaveMode() this gives you a number. If the number is 5 then you know the save has been triggered by pressing the resolve case button.
This was interesting because I didn’t know that save events had different numbers depending on where they were triggered. The blog post has a list of all the save events
Although I was capturing the save event, when I changed some fields to be required it didn’t seem to stop the page from saving, so I had to add some Javascript which stopped the Case form from saving and popped up a javascript message warning the user to fill in some Call analysis fields. I added some validation which checks to see if certain fields are null, if they are then I stopped the form from saving.
prmContext.getEventArgs().preventDefault();
alert(“You must enter Call Analysis information”);
There are probably other ways to do this but it shows you the power of CRM 2011 that you have quite a few options
Hosk's Dynamic Blog 