Thursday, June 11, 2009
The WQW wizard is a specialized query builder that we integrated into dynamics workflow engine. The wizard facilitates the creation of aggregate queries without the need to write custom code for each requirement that we have. This helps us create various complex workflow rules that are not available by the out of box workflow designer. A good usage example is when you need to create Monitoring / Alerting workflows or need to take some action depending on existing or non-existing amount of records that answer a specific set of conditions.
The WQW also facilitates the creation of specific business counters on the parent entity. This is done by updating the parent entity with the WQW result using the workflow built in functionality (update record step). One of the biggest advantages of using the WQW and the business counters is that it can help you create not-in queries.
Consider, for example, a scenario where you need to find accounts without contacts or open incidents.
by creating a WQW workflow step and a new account attribute (counter attribute) called number of accounts / number of open incidents you can write the WQW result to each attribute counter. This enables the user to retrieve all accounts that have 0 contacts / or 0 open incidents in each respective account counter.
The video demonstration illustrates 2 simple scenarios that make the WQW such a wonderful workflow addition.
The first scenario monitors the amount of long duration outgoing calls that are made by a user. The second scenario alerts a manager when too many on-hold cases are open for a specific user. These are just examples. There is no limit on the type of Alerts or Actions that you can take using the wizard. As long as you are able to build a query around your requirement the wizard will facilitate the actions and enable you to easily create workflow rules depending on the their results.
Another feature that the WQW has to offer is the dynamic binding of values in the current workflow context. If you take a look at the second scenario you’ll notice that the WQW uses the owner attribute dynamically. Since the owner is not known at design time the values are taken from the context at runtime and integrated into the query.
I’m sure this addition will save you hours of tedious development effort. If you have question regarding the wizard fill free to post them here.
The wizard will be available on our website next week. Enjoy…
In order to rewind right click on the flash movie and select play
Posted by Adi Katz at 12:14 PM