last - call - button in cc.incquick.g

[eisefr]

Hi..

did anyone noticed the problem in Version 5.1 with the 'last Call' - Button?

If you hit the last call-Button after you closed a call.. the system brings you back to the display screen cc.edit.incident instead of cc.first.

The problem about this IS.. the display options from cc.edit.incident and cc.first are totally different. SO nothing works like it is working in cc.first when you are in cc.edit.incident. (As you can see in the attached hardcopy)

I tryed to copy all display options from cc.first into cc.edit.incidents.. but it did'nt work correctly either after that.

I get a error message when I want to open a call from a duplicated call.

In my eyes thats a bug in the SC5.1-Version.

Maybe someone knows if there is a fix available already or someone has fixed that 'problem' already?

[tommy]

That works as designed. Remember this button is equivilent to doing a search and select of that particular incident.

[eisefr]

That wasn't designed like this in SC3 though.
I liked it more the way it was made in SC3.

In SC5.1 you cannot just go back to the last call, duplicate it and change the contact name.. close the call again or create a problem ticket from it.

I didn't find anything to complain about in SC5.1... so far!
but changing the functionality of this last call button was REALLY not a good idea! :evil: :evil: :evil:

[tommy]

Well its not the last button functionality that has changed. It is the general display of the incident that has changed.

But You can change it, start by having a look at the document engine object, states and processes for incident.

[eisefr]

Well its not the last button functionality that has changed. It is the general display of the incident that has changed.

But You can change it, start by having a look at the document engine object, states and processes for incident.

I'll look into that..

What I tryed for now.. is ..

after I duplicated the call I clicked on OPTIONS , LINKED , INCIDENTS, OPEN.. and I got an errormessage. Does that happen in your system too Tommy?

[tommy]

Yes I get that error too. sigh another oob error that need to be reported.

It should be easy to fix though. Because it is just because the call has not been saved yet. I'll check it out it should be enough to add a save process or change the "save first" to true on the correct process.

[eisefr]

Hi Tommy...

Would be cool if we could fix that....
Thats really a feature what we really need absolutly necessary in our system. If I bring a SC 5 - Installation without that feature online.. they are gonna hurt me. :lol: .

I'll look into that tomorrow too...

Thanks for your help

[tommy]

Yes I get that error too. sigh another oob error that need to be reported.

I reproduced the error and have reported it to Peregrine.

[tommy]

Hi Tommy...

Would be cool if we could fix that....
Thats really a feature what we really need absolutly necessary in our system. If I bring a SC 5 - Installation without that feature online.. they are gonna hurt me. :lol: .

I'll look into that tomorrow too...

Thanks for your help

See http://www.sc-resources.net/viewtopic.php?p=36400#36400 for a workaround.