Global preference changed after update to 11.3

lock
push_pin
done
Answered
3

Hi,

After my demo tenant was updated from 11.2->11.3 I've noticed that the global preference "Enable editing of messages" is set to No.

Is this a bug or an intentional change?

2 Sep 2025 | 11:05 AM

All Replies (3)

Btw, I've tested this in 3 different tenants, all on 11.3. The preference is always set to No.

2 Sep 2025 | 11:06 AM
Hi Thomas,

We are investigating and testing this now. I will get back to you during the day.
3 Sep 2025 | 08:12 AM
We have now tried with multiple tenants, 10+, to reproduce this behaviour but in all our tests where the preference was set to "Yes" in 11.2 and then upgraded to 11.3, the preference was still set to "Yes".

By default this value is always No.
3 Sep 2025 | 02:49 PM

Additionally these triggers have also been removed:

2 Sep 2025 | 11:08 AM

Hi Thomas,

Looking into the observed preference change... nothing to respond yet.

Looking at the release notes, I see that there are two "new" triggers... perhaps these are what you are looking for? 

2 Sep 2025 | 06:09 PM
Looking at a couple of smaller tenants who where upgraded to 11.3 they all have the preference set to "No".

The triggers I'm referring to are "Before/After saving ticket message" which have disappeared in 11.3
3 Sep 2025 | 07:10 AM
Hi Thomas,

The triggers for "Before/After saving ticket message" have never been implemented and have unintentionally been visual in the GUI to prepare for the new trigger in 11.3 called Load Message and Load Request. This means that it doesn't break any scripts or processes at customer sites when we remove the icons for the non-functional triggers.
3 Sep 2025 | 08:11 AM

Add reply