Search the Community
Showing results for tags 'log request'.
Can we raise an enhancement request to have a setting to control the rendering of HTML Href within emails when emails are used to log or applied to Service Manager Requests. The setting is to determine what element of the Href is rendered into the text used as part of the timeline updated, i.e. the 'link text' or the 'url' value. At the moment the email rendering to textual timeline inserts the whole 'url' and not the human intended 'link text'. With the introduction of new security features in Office 365 in the form of Safe Links in Microsoft Defender for Office 365, embedded 'url' for Href in emails are encoded in a very long url which redirect all links to via the Microsoft's Safe Links dynamic checking facility rather then the original source url. https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/atp-safe-links?view=o365-worldwide#:~:text=Safe Links scanning is enabled,Block the following URLs" list. As these links are very long and also do not represent the original embedded link in a human readable form, we would like the setting to be added so the Href 'link text' is inserted into the textual timeline and not the 'url'' content. Without these setting the timeline entry become blotted and unreadable very quickly. Cheers Martyn
Linked to my earlier post below, when raising a new Known Error via the BPM Request - Log Request node can it be extended to allow for the specification of Root Cause and Workaround text, given that you should know these values when raising them from a problem request. Cheers Martyn
Hi, Can we have some fields added to the 'Log Request > Known Error' node? I am trying to get our Problem request to log a new Known Error if a workaround has been found. However I cant get it to log the request with all the required information. RCA and workaround are missing from the node. Being able to set this via a human task to capture these before the log request node makes sense to me, rather than having the BPM log the request and then having to go into the KE and add more info. Screenshot added for a little more clarity
Can the Requests - Log Request node be extended to include the options to copy over the following additional characteristics Connections Attachments Service Level Catalog Cheers Martyn