When it's not DueDate anymore

Today we will focus on 2 "Click" products and more specifically, on one interaction point between them: ClickSchedule and ClickAnalyze.

I recently seen more and more projects that are using other Task properties than DueDate for fetching unscheduled tasks. Lets assume we have new user defined property (UDP), which represents the date that an unscheduled task should be scheduled (many times it is called OptimizeOnDate). I would like ClickAnalyze to use this new UDP instead of the DueDate in default conditions.

First, I change the setting of the Service Optimization Administration snap-in. I want to be able to edit the XML in the Body property of a specific setting object.

You can see I added the standard XML editing to Setting object with Category="Reports" and SubCategory="Components".


Now I can open the Components setting using standard XML editing, and manipulate the Body property directly.






I expand the components until I found the "Time Resolution" dimension.

You can see that it includes additional node after the "Type Specific Information" comment.





I expand the third OQL condition for the tasks collection.

Just to remind you, OQL stands for Object Query Language. This is the XML that is used in the group objects of the "Click" products.

I can spot that DueDate property is used twice (see red arrows).

In my customization, the ID of the OptimizeOnDate property is 105. So I changed both places and keep those changes.

Now I'm creating new report for ClickAnalyze Reporting.

I added "Count Objects" measure and named it Tasks.



You can see that the default condition for tasks is no longer on the DueDate property, but on the new OptimizeOnDate property.


You can use the same technique to have new OQL conditions for new collections that include date properties.