05-21-2014 04:49 AM
when ess users access the ticket link attached to the notification mail, it does not direct them to the ticket itself, instead it just open the ess front page. Although the link provided included the ticket number as following:
and when I tried to access it the following error showed up:
I have no idea where such error comes from, as I am not using this field anywhere.
any idea what might be going wrong?
Thanks a lot,
05-21-2014 07:10 AM
I was doing some research on this error and found discurrion that might help
If you find that this post or any post resolves your issue, please make sure to mark it as an accepted solution."
05-25-2014 12:41 AM
thanks for your help,
actually I have checked the case you have provided me, but could not relate that to mine.
My case is that users are getting such error when they access the link attached to their tickets update notification, which by the way are sent on incident update, not interaction update.
I am guessing this could be the cause of the error, but is there any way by which I could solve this?
thanks a lot,
05-25-2014 03:42 PM - edited 05-25-2014 07:51 PM
Incidents cannot be accessed via ESS links and no one can update an incident via ESS.
An ESS user can only open and/or update interactions. While there is an option to view a related record, it is not possible for a user logged in via ESS to update related changes, incidents, or requests. Any user who needs to update those records is required to log in using the full client (and will consume a license to do so).
If the emails are being sent to technical teams, they should include the full client (index.do) URL. This allows the technical user to directly access and update the incident. Attempting to modify the ESS client controls so that a user could update incidents would violate the license agreement.
The linked topic above describes a similar case where the use of the ESS client would be prohibited by system controls and license restrictions. A user logged into the ESS client is authorized to only view/update interactions where they are the callback contact or service recipient (the error message you're seeing is caused by that filter), approve records from other modules, and can only view records related to the interactions to which they have access. Any access outside of those limits requires the use of the index.do client.
05-26-2014 01:32 AM
thanks for that, but the thing is that I dont want ESS users to update tickets, I just want them to view their tickets through accessing the link sent in the notification mail $L.ess.link.
However I am sending this notification mail on Incident update, not on interaction update, so that ess users can see the incident solution provided, and while they try to open the link they get such error and the link does not direct them to the ticket itself instead to the ESS SM front page. So they get lost.
any idea why this error shows up, considering that I am not using this field anywhere.
that was my question,
05-26-2014 01:46 AM - edited 05-26-2014 01:47 AM
Alternatively, you could update your incident notification format to include the closure information, removing the need for a link.
05-26-2014 01:53 AM
Actually the resolution is not being copied from incidents to interactions, so when I send notification mail on interaction closure including the resolution field, it goes blank in the mail because the resolution is only there in the incident reord.
something else, links are needed in here because of attachments, sometimes the second line send their solution to the ess users in terms of attachments to check.
05-26-2014 02:03 AM
--the out of box systems copy incident resolution to the interaction. If it is not happening, a tailoring change likely interfered with the functionality.
--the recommended method to provide an attachment for an ESS user would be to attach it to the customer-facing record(the interaction), but it is also possible to display the attachments from incidents related to the interaction in the Interaction form. (Search for existing topics which provide step-by-step instructions: they are for displaying the interaction attachments in the incidents, but you can use it as a model to do the opposite).
--the query restriction is applied by RAD to enforce ESS access restrictions. I know of no way to remove it.
05-26-2014 02:22 AM - edited 05-26-2014 02:24 AM