AKJ

I brought this up a few months ago but didn't get a reply. It's interesting refreshing the page fixes it for you – myself and a few other members in our organisation have this persist permanently across different browsers and sessions, meaning it's tied to our accounts in some way as opposed to the mailbox itself.

Looks like it's working for me now, thanks again!

Thank you both for your speedy responses and for looking straight into it!

I'm working on a time-sensitive Workflow but am unable to do anything realistically as myself and others are getting the following errors across all Workflows: "Failed to load bpm flowcode script. Please contact support." "Failed to load bpm answers flowcode script. Please contact support." This seems to only happen for Hornbill Automations as soon as I click into the node. For example, this is all I see for a node updating custom fields: There is nothing below this so the entire list of custom fields is not present. The same can be observed for any other Hornbill Automation. Please can this be looked into as it's preventing any work on Workflows being undertaken. It was fine at around 15:30 (GMT) yesterday and only started this morning.

Ignore most of this post, I didn't realise semi-colon was the button to trigger email separation. Would still appreciate the ability to send previous replies in an email chain through the reply function instead of in just forwarding though.

Now that the new email function has been deployed to the new UI, it is no longer possible to reply or reply all to an email and quote the previous email chain. To do this, I have to click forward instead and then 'See forwarded content', then re-type the email addresses I want to reply to. However, it looks as though we can no longer use either reply or forward to send emails to recipients outside of the domain connected to Hornbill, thereby making this email system highly unusable in many calls. Could we have the ability to email external email addresses in the email function, and quote previous correspondence when replying to emails?

Yep @Berto2002, had a few instances yesterday where the customer failed to change

Hi, this is still an issue unfortunately and is continuing to cause us headaches now and again by actioning calls for the wrong people. It doesn't look like a fix has been released via the announcements section either; is there any timescale as to when this might be resolved?

Ah cool, glad it's on your radar! Many thanks for letting me know.

We've seen an issue that is cropping up now and again that started a few weeks ago and affects a few workflows. If the customer is raising their call on behalf of someone else, the expected behaviour is that the customer changes to the person they're raising the call for via an update customer node in the business processes, and the person who raised it is added as a connection through a Raised on behalf connection node. For reasons we cannot figure out, the Raised on behalf connection works as normal but the customer remains as the person who raised the call. This is leading to a lot of confusion when it does happen and the customer must be changed manually. As far as we can tell, only service requests have been affected and does not occur often but seemingly randomly. Workflows affected have not been modified in this regard for several months, so we're at a bit of a loss as to what is causing this. Is there anything we could check to see what might be causing this?