https://store-images.s-microsoft.com/image/apps.968.2922c488-5847-4921-beb5-1490a08de08f.3e9f6360-6011-43d2-8dff-1a77d6a28573.385f1b24-6d4e-423a-ac8d-432e8db7dacd

Dynamic routing rules 4 week implementation

MAQ Software

During our 4-week implementation, we will develop a custom routing solution that enables you to easily configure complex routing scenarios in your Dynamics 365 environment

Routing rules ensure that records are automatically routed to the right people at the right time. A routing rule consists of a set of conditions and a destination user/team. If the rule condition is met, then the record is automatically routed to specified user/team. However, out of the box (OOB) routing rules are limited and do not support businesses with complex routing needs.

###Limitations of OOB routing rules

  1. Only works for case entity
  2. Limited comparison operators
  3. Multi-select fields are not supported
  4. Bulk rule updates are time-consuming

Advantages of custom routing rules

  1. Overcome the above stated limitations of OOB routing rules
  2. Ability to define attribute weights so that top ranking rule can be picked in case of multiple matches
  3. Updating rules does not require deployment, resulting in faster time to market and reduced downtime

As part of this offering, we will evaluate your existing routing scenarios, develop a custom routing solution, and integrate it with your existing Dynamics 365 environment.

Agenda

  • Week 1: Evaluate business needs and existing routing scenarios
  • Week 1: Propose an implementation plan
  • Week 2 & 3: Develop custom routing solution* Week 4: Integrate and configure solution in existing system

Deliverables

  • Document outlining existing routing scenarios and our custom solution
  • Custom routing rules solution integrated with existing Dynamics 365 environment. The main components of the routing solution are listed below:   * Workflow for handling ranking logic   * Plug-in to parse custom filters   * Entity to define routing rules

Note: The scope of this offering is defining routing rules for single entity with depth of 1 (i.e., a rule can be based on entities directly related to the main entity). If solution requires routing rules that must be defined for depth > 1 and with dependency on multiple entities, then we will evaluate and share implementation plan for the same.

De un vistazo

https://store-images.s-microsoft.com/image/apps.43663.2922c488-5847-4921-beb5-1490a08de08f.3e9f6360-6011-43d2-8dff-1a77d6a28573.fd5b0b36-8248-45af-b53a-e43dd0c858c4
https://store-images.s-microsoft.com/image/apps.56216.2922c488-5847-4921-beb5-1490a08de08f.3e9f6360-6011-43d2-8dff-1a77d6a28573.6e5d317c-ed37-4fd2-8c15-cd638bb4ebb8
https://store-images.s-microsoft.com/image/apps.22566.2922c488-5847-4921-beb5-1490a08de08f.3e9f6360-6011-43d2-8dff-1a77d6a28573.1f391bdd-c3f7-4830-86db-0f76dd8da21c
https://store-images.s-microsoft.com/image/apps.1348.2922c488-5847-4921-beb5-1490a08de08f.3e9f6360-6011-43d2-8dff-1a77d6a28573.f9ad7a3c-5b73-47d7-9a1d-730194e585c3