Microsoft Dynamics CRM 2011 overview. Thoughts about performance and development practices. Synchronous/Asynchronous processes. Process automation.

1. MS Dynamics CRM 2011
What is it all about?
CRM – customers relationship management

2. How it looks like?

3. How it looks in Outlook?

4. How it works?

5. Workflow vs Dialog
Workflows Dialogs
Triggers are supported for Triggers are not supported for
workflows. dialogs.

6. Workflow vs Dialog
Workflows Dialogs
Are synchronous processes, and require user
Are asynchronous processes, and do not input to run to completion. When you run these
require user input to run to completion. These processes, a wizard-like interface is presented
processes run in the background. to you so you can make appropriate selections
to run the processes.

7. Development tip
To add some button on ribbon you will need
to customize XML & Javascript

8. Workflow vs Dialog
Workflows Dialogs
Can be either started by a user or can be
Must be started by a user.
automated.

9. Workflow vs Dialog
Workflows Dialogs
The entity that stores the details about a The entity that stores information generated
running workflow is AsyncOperation. by a running dialog is the ProcessSession
(dialog session) entity.

10. Workflow vs Dialog
Workflows Dialogs
Both Windows Workflow Foundation 4 and Only Windows Workflow Foundation 4 custom
Windows Workflow Foundation 3.5 custom activities are supported.
activities are supported.

11. Workflow vs Dialog
Workflows Dialogs
Workflows that are created or updated outside Dialogs that are created or updated outside of
of Microsoft Dynamics CRM by creating or Microsoft Dynamics CRM by creating or
updating the underlying XAML file are updating the underlying XAML file are not
supported in Microsoft Dynamics CRM supported in Microsoft Dynamics CRM.

12. Workflow Architecture

13. Workflow states
• Ready
• Suspended
• Locked
• Completed

14. What to use workflow or Plugin?
 Changes in the business logic must be performed by people who are not
developers, or the changes should not be dependent on the availability of
a developer to do the work. When custom workflow activities are defined
as Workflow .NET assemblies, a person who is not a developer can use
Microsoft Dynamics CRM to define the conditions when the custom
actions are performed and the parameters that will be passed to the
assembly.

15. What to use workflow or Plugin?
 It is acceptable to have a delay between when the event occurs and when
the workflow rule runs. Unless applied manually, workflow rules run
asynchronously and run after the event occurs. If you need synchronous
processing, use plug-ins

16. What to use workflow or Plugin?
 You need the ability to let users apply your workflow logic manually. With
workflow processes, users can trigger the processing of workflow rules by
clicking Run Workflow on the form or from a grid.

17. Creating simple workflow?
• A few mouse clicks!
• Understanding of CRM entities
• A bit logical brain processes
• Stupid users? You will be confused.

18. Simple workflow created
Oh my god! What is this?
Disgusting SQL queries causes performance
loose!

19. Simple workflow created 2
• Complex issues should be done with hands
• Thoughts about plugins should be present

20. Performance tip
Long processes should be done with
workflow!

21. Why not to use only workflows?
Flexibility
You do what you want as you want
Special needs(e.g. integration with another
service)

22. THE END