User Voice

I'm giving this post a +1. This feature is highly requested by our clients. The lack of "per-ticket" permission management (other than manually adding permissions to thousands of tickets) or preserving the existing permissions from the original ticket is holding our clients back from implementing an archiving mechanism.

Hi,

I suggest to add a custom CSS box in the configuration of a report view.

One use case is to override the default CSS of tiles. The advanced JSON works like a charm to customize each column. But it’s clearly not possible to customize the outer tile.

A simple needed custom CSS would be to create a 4 column design by just setting a tile’s width to 24% instead of default 100% and to hide all column title labels.

A supplement would be to add the GUID of the report as attribute in the DOM. This way the custom CSS could be set in System settings or Theme settings. But a CSS box as suggested would be way more convenient.

Kind regards
Sébastien

Hi,

when using global constants in the global email template the reference is done with the IDs instead of the GUID. By this it‘s not possible to just copy & paste the HTML code to other environments without having to replace all occurrences of those references.
Therefore I suggest to use GUIDs instead of IDs.

Having global business rules for the email template would be great too.

Kind regards
Sébastien

It would be nice to have such feature alike "Audiences", e.g. web parts in SharePoint

Currently, when an email is sent to users with different profile languages, WEBCON splits it and sends separate emails per language group. This works fine, but inside the email template there is no variable that tells what language is used for that specific group of recipients.

Why it would be useful:
Allows dynamic content in emails based on recipient language
Makes it easier to build multilingual templates (no need for hardcoding or workarounds)

Expected behavior:
Add a context variable (e.g. RecipientsLanguage) available in email templates/action, returning the language used for that specific email batch.

Hi,

in the field matrix it’s sufficient to set a form field group as readonly to set also all of its child fields as readonly - respective disabled.
Unfortunately the disable/enable function in the form field editor doesn’t accept form field groups.
It would be much more convenient if a whole group could also be disabled (readonly) and enabled instead of having to handle all child form fields.

Kind regards
Sébastien

Hi,

in a path configuration there is no editor for the name of a task. But in the Create Task action the name field supports an editor.
Therefore I suggest to add the same editor functionality for the path configuration.

Kind regards
Sébastien