Yes I've had something very similar. At the moment it looks as though WebDesk has slight differences in the way it handles filters and queries to the one true source - console. Other examples are that it doesn't seem possible to write a filter that behaves like the popular query on the incident window to list all notes in most recent order create first. You can try but ....Also if you have a filter which refers to an attribute on the window and change the contents of that atriibute the filter, WebDesk still uses the old value prior to you changing it. Console correctly uses the new value you have changed the attribute too.
As a thought, you could perhaps use two categories one for SR and one for Incident with different processes? Someone who knpws has told me is a requirement for ITIL3.
Thank you for the reply.
Yep, we use two different processes, however, both are built under the Incident module. We also use two sets of Categories/Impact/Urgencies.
The ones for Service Request are prefixed with an "SR". Hence the filter.
Support is labeling this as a bug in WebDesk and escalating it.......
Thought I'd list an update.
This has been reported as a bug to development/engineering. Filtering does not work on the Process/Lifecycle name.
A work around is to create a new boolean attribute, then create a template with the new attribute set.
The filter can then have a condition on this new attribute.....
has there been any updates on this issue?
I can still reproduce this error in v7.5 after it has been escalated to development 3 years ago...
Nope, no updates.
The only thing we use is the work around Karen P provided us.
There is an enhancement request for this, but I can't seem to find the link since they updated the web page this past weekend.....
It's a known problem in support. The filter will only work for the process who is set as the "standard" process...
Log it with support. Currently the prio is "low".
I think we might be referencing two different issues here:
Marcello is I think referring to problem 5321 - "Filtering does not work in Web Access before saving a record if not using the default window". This is available as a patch for 7.4 that can be requested and is planned to be addressed in SP1 for 7.5.
The specific problem at the top of this thread is to do with being unable to filter on the Lifecycle object and is problem 5226 - "WebAccess adds its own criteria when creating a filter on some relationships making them unusable". From our records, this has been experienced by two customers who both worked around the issue. This is a Medium priority issue currently so if anyone experiences this please do let your support provider know.
Sorry you are right. I understood we talking about problem 5321. But nice to know that it will be fixed in a 7.5 service pack ;-)
Hi Karen, hi Marcello,
Thanks for the patch information.
I am trying to create a filter on the Incident Response level Attribute. The filter works fine in Console. However in WebDesk it does not.
This is just happening with the response level field. Other fields work great.
1 of 1 people found this helpful
As I understand your filter criteria is something like: lifecylce is equal to X and/or Y
How to create a new field on the business object response level and use this new field to filter?
a drop down / ref list "customer"
if customer A
if customer B
or create a checkbox and use this to filter instead of the lifecycle
did you tried this already?
If you first of all save the window, then try expanding the filtered response level list again does it then filter the list correctly? This will help me work out whether this relates to problem 5321.
As an aside, have you considered instead using the SLA matrix to filter your Response Levels? I'm not sure if this would be applicable to your requirement.
Me again. If you are filtering on lifecycle, (the process that is being used), then the workaround we put in place in the past was to store the lifecycle name into an attribute on the window and then filter off this.
Even after selecting the response level again from the filter list the filter does not work.
However I worked with the SLA Matrix that you suggested and now I have the result I was looking for. So no need for a Filter there.
Thanks you two for your Help.