Workflow Extension for Microsoft Dynamics CRM

Workflow Extension for Microsoft Dynamics CRM

In the course of time every customer will realize the power of a workflow tool using which the specific application logic of the CRM solution is set up. Flexible workflow is an outstanding competitive advantage. The workflow designer itself is highly intuitive and user-friendly, which makes it the best fit even for less skilled users, and contributes to the success of its implementation.

Image Image

As the time proceeds, customers’ demands on the workflow continue to grow and at the end reach a point where some of the working procedures can no longer be realized due to the limited functionality of the workflow designer.

This is the experience that a great number of users have. They may scheme out a simple workflow, and then during its implementation face a problem of not having:

  • A function necessary for condition testing.
  • Capability to carry out a necessary action because the system does not support it.

The problems mentioned above can easily be solved with plug-in modules that will extend the workflow designer. Although the creation of these plug-ins is easy, it requires programming in Visual Studio, and therefore the ease of the initial workflow implementation is consequently lost.

Our company specializes in the creation of workflow plug-ins based on specific customer needs and demands.

For our prospect customers we have prepared a range (which will further grow) of free plug-ins.

By filling in an inquiry form a customer shortly describes his needs (or directly describes a required action and input/output parameters) and we suggest an applicable plug-in. The customer then adds the thus created plug-in to his Dynamics CRM installation.

The example below explains the procedure of workflow designer extending with a simple plug-in.

A customer needs to automate some routine activities related with a receipt of an e-mail message in the CRM. The customer however lacks a possibility of checking whether the received e-mail message has been recognized – tracked in the CRM; i.e. whether its sender has been recognized and assigned to an appropriate record in the CRM (marked blue) or whether it is a new (unknown) sender (red).

  1. A customer describes his needs in an inquiry form and sends it to the addon@dynamica_cz.
  2. Our specialists suggest a plug-in and set a price for it. It is a plug-in with one input parameter (mail identifier), and an output - a return value (-1 = error, 0=unrecognized, account=account recognized, contact=contact recognized, lead=lead recognized, systemuser=CRM user recognized, queue=CRM queue recognized).
  3. The customer accepts and approves the suggested plug-in and price.
  4. We supply the customer with three files – the plug-in itself (.dll file), a required configuration (.xml file) and installation instructions.
  5. Using a registration tool the customer simply registers the new plug-in on his CRM server. Image
  6. In the same utility the customer configures this plug-in for which the customer uses the supplied configuration file.
  7. Image Image Image
  8. The customer restarts the Microsoft CRM Async service.
  9. The customer now prepares his workflow procedures with the new functionality. Image Image Image Image Image Image Image

This procedure is very simple, and for our prospect customers we have prepared a range (which will further grow) of free plug-ins.

So don’t hesitate and test some of our free available plug-ins. It is easy, and you will certainly strike upon a lot of other ideas how to extend the workflow in your company with other ways and means.