Victor

@Fizza Before any further discussion, we need to have a more clear understanding of the terms "Customer" and "Logon ID". When referring to the customer, it is important to specify whether this pertains to the customer of the request at hand. Furthermore, we need to determine if this customer is an external user, such as a contact, or an internal user, such as a basic or full user. This distinction is essential in order to accurately assess the situation and provide appropriate solutions.

When you get the first "broken template" displayed, F5 to refresh the page. This will then display the "whole template". And also, you can then edit any other template, without encountering this issue. This is being looked at by development.

@Val C what exactly are you looking to get from this report?

@JamesGreen ok... as mentioned above the tool does not have anything "built-in" to route connections through proxies it simply uses the connection as provided by the environment where it runs... so I would say something in your environment has the connection routed through the proxy... maybe the machine itself needs to be restarted after the changes, not sure... but not my area of expertise I'm afraid..

Just FYI while in the pipeline, no one will be able to see it apart from the user designing the service, and only for the purpose of designing the service further until is ready to be included in the catalogue.

@Lee C you would do this in "Profiles" in the admin tool. This option is located in the "Data" section. https://docs.hornbill.com/esp-config/data/profiles

@Lee C https://docs.hornbill.com/servicemanager-config/customize/workflows/service-manager-workflows#email-notifications

The tool does not have anything inherently built to use connections via proxy it simply uses the connection set in the environment... in cmd prompt window if you type in netsh winhttp show proxy what do you get? If the environment has no proxies configured it should show something like this: If the tool still tries to connect via proxies it is the connection in your environment still set to use proxies. Maybe the machine needs a restart once the proxy config is reset (removed). However, I am no expert in this area.

@Andrei Spiridon would recommend using the option on your Premier Success plan and raise a support request. If this is a defect you will also be provided with a defect reference you can then track with our support team.

As far as we know, it shouldn't. The issue should only be when editing workflow nodes. If you experience an issue with raising requests, I would advise raising it with support. The issue might be related to the one on workflow but might very well be something different that would need to be investigated separately.

A fix is being rolled out. ETA for fix deployment is currently 10 min.

@Jacopo Carraro we have moved this thread to the appropriate section but just an FYI reminder:

@Liam Jackson we have moved this thread to the appropriate section but just an FYI reminder:

@MacLean Ferguson we have moved this thread to the appropriate section but just an FYI reminder:

@JamesGreen we have moved this thread to the appropriate section but just an FYI reminder: