Intended use of the new 'load request' and 'load request message' CRMScript triggers

Hi,

We have been hitting some issues/road blocks with migrating customers to the new service solution, where the customization possibilties are much more restricted.

One of the issues we have been hitting a lot is being unable to automatically fill in fields (either custom or default), in the 'old service' we could do this with url variables. In New Service this has not been possible (so protocol does not work).

Now with these new triggers we where hoping we could solve these challenges (and migrate more of our customers to new service), but sadly with the first 2 scenario's we tried it, immediately hit an issue:

#1 Setting a custom field value based on soprotocol, immediately hit a bug that getNavigateTo () does not work in triggers, preventing us from getting the SOProtocol being navigated to (if it works like that)

#2 Just tried to set the ticket priority based on the linked person contact ticket priority, but setting 'TicketEntity.Priority.TicketPriorityId' with setOutputValue doesn't do anything.

What is the intended use cases of this triggers here, should setting values with setOutputValue work?

The documentation of these triggers is not made yet (#2185), so we are not sure if we are looking at bugs here or if this is not the intended use case.