Service Desk Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

SD5 View with To Dealine is slow

Highlighted
SDSKonline
Regular Collector

SD5 View with To Dealine is slow

Hi,

I'm using SD5 with SP1 and I found out that using SC views with the attribute "to Deadline" makes loading of this view a lot slower.

When I say 'a lot' I mean it takes about 10 times the tie it dows without the attribute.
9 REPLIES
SDSKonline
Regular Collector

Re: SD5 View with To Dealine is slow

Does anyone experience the same? Is this normal? Anyway I can dispay it without the delay?

Thanks in advance!
Ruth Porter
Honored Contributor

Re: SD5 View with To Dealine is slow

Hi there,

this is my experience as well and so i have stopped using it.

Instead I am using scheduled DB rules which set a custom field when a SC is an hour from deadline and I show that on the view.

I would suggets you log it with HP.

Regards

Ruth
http://www.teamultra.net
SDSKonline
Regular Collector

Re: SD5 View with To Dealine is slow

Hi,

Ok, i understood your partial solution.

I think that i'm going to do it in a similar way, probably using a clode with various alerts with increasing urgency as the SC nears the deadline.

Thanks.
SDSKonline
Regular Collector

Re: SD5 View with To Dealine is slow

Can you explain in greater detail what your rule looks like?

I'm using the fields Actual Start and Actual Finish to duration control. My problem is: against what am I going to schedule the update?

Actual Finish is filled when the SC is closed (obvious). I have "Deadline" and "to Deadline", but i don't seem to be able to use them in rules...
Ruth Porter
Honored Contributor

Re: SD5 View with To Dealine is slow

Hi there,

My rule uses a custom code field called "Escalation level" and it has 2 values "1" and "2".

The rules are:

When SC modified or created
Conditions:
Deadline* is Not empty
Status not equal to Resolved, Closed scheduled 1 hour before Deadline
Action: update data set Escalation Level to 1

The second rule is:
When SC modified or created
Conditions:
Escalation Level* equals 1
Status not equal to Resolved, Closed scheduled 1 hour before Deadline
Action: update data set Escalation Level to 2

Then I format the rule on Escalation level

Hope this helps

Ruth
http://www.teamultra.net
Ruth Porter
Honored Contributor

Re: SD5 View with To Dealine is slow

Hi there,

My rule uses a custom code field called "Escalation level" and it has 2 values "1" and "2".

The rules are:

When SC modified or created
Conditions:
Deadline* is Not empty
Status not equal to Resolved, Closed scheduled 1 hour before Deadline
Action: update data set Escalation Level to 1

The second rule is:
When SC modified or created
Conditions:
Escalation Level* equals 1
Status not equal to Resolved, Closed scheduled 1 minute before Deadline
Action: update data set Escalation Level to 2

Then I format the rule on Escalation level

Hope this helps

Ruth
http://www.teamultra.net
SDSKonline
Regular Collector

Re: SD5 View with To Dealine is slow

I understood your rule.

I'm using a very similar DB rule (difference is that i'm using more than 2 escalation levels...)

Is it working flawlessly? The schedules?
SDSKonline
Regular Collector

Re: SD5 View with To Dealine is slow

I'm willing to log this to HP. How can I do it?
Ken Briscoe
Honored Contributor

Re: SD5 View with To Dealine is slow

You can only do it (I think) if you have a support agreement or a system handle and an HP Passport - then you can use http://support.openview.hp.com/casemanager/index.do
Otherwise maybe through your HP rep I guess.
My email is kenilian@bigpond.com.au
//Add this to "OnDomLoad" event