Configuring Workflow in CRM4
And I am back.Having gotten back in the saddle with MSCRM it is time to start logging my thoughts. Now with CRM4 (on my office system which was upgraded while I was on another project so I did not have anything to do with it).
So what have I been trying to do? Get workflows working.
I still have a bit of work to do with inbound email routing but the outbound seems to be working now. Which is nice.
For a while I could not get the workflows working. Each workflow kicked off and sat in a waiting state. Ever since the upgrade workflows had not worked but this had not been noticed. On investigation I found 150,000 outstanding workflow jobs so deleted them to ensure that when this did actually kicked of I did not crash the system as it plowed through them.
I deleted all old workflows and all workflows upgraded from CRM3 as there were only 5 of them and almost all were being retired anyway.
And as I said, the workflow did not work. After a quick search I found this forum post that suggested I had a problem with the host headers. Our server has three and this could have caused an issue to remove them so in investigating further I discovered this site and thought the update SQL was quite revealing.
I found that in fact the AsyncSdkRootDomain did not contain my server name. It was blank. I updated it with our server:port and the workflows started working. Tasks are created and things are moving. Just at the moment no emails are being sent.
I can send an email as an activity from a service case but cannot automatically route it out from a workflow.
So it is back to Exchange...
Callouts not being fired
Over in Ronald's blog he has a good trouble shooting list for when your callout does not work.
He has missed one thing out though that still affects one of my sites.
In it the callout did not fire because the entity was updated by a workflow. Someone changed a bit value to indicate they had checked the record, the record had a status on a dropdown updated and that update should have then triggered a web service call to inform a third party of its existence and passage through a QA procedure.
After some experiments we discovered that if you changed the status of the dropdown by hand and saved it the callout was fired but if we allowed the workflow to change it then it did not. On googling MSDN this turned out to be a known issue pre rollup 1 but my client was only a week from go-live when we (I) discovered this. They have still not got around to applying the roll up as far as I am aware and the workflow was altered to create a task against an admin person to change the status by hand.
Not pretty but worth knowing.