WELCOME TO THE COMMUNITY
find what you are looking for or ask a new question
Home > User Voice > Latest posts

User Voice

I think this is a well-thought-out and useful change. It ensures flexibility in comment moderation while maintaining transparency in administrative actions. Offering both options (complete removal or replacement with default text) gives the administrator more control depending on the context. The most crucial part is the change history, which allows for an audit and prevents potential abuse.

Currently, the only option is to delete the comment by updating the **WFD_Description** column.

Description of change:

In the low-code system in the Comments field, the System Administrator should be able to delete a comment added by a user.
First option:
The deleted comment will not be visible to normal users. (as if it had never been added)
OR
Second option:
The deleted comment will be replaced by the default type text: {username} delete added comment (something like deleting a message in Messenger)
OR both :)
In the change history (in administrative mode), the comment will remain always available for viewing to maintain full transparency of administrative actions.
For the system administrator, a Delete option will appear next to each user comment.

Justification:

Increases control over content entered into the system.
Provides the ability to moderate comments where necessary.
A change history will allow an audit of administrative actions.

MVP

Hi,

it would be nice, if we could define, whether the description field is displayed is displayed when uploading a new attachment.
If we are using the old "add attachment" option we can select the category.
If we are using the new "add from camera" option, we can overwrite the filename and set the category.

If the user want's to provide a description, he has to:
- finish the upload
- Click on attributes
- Save the changes

If the description field would be available during the upload, it would:
- improve the user experience
- reduce the training effort
- reduce the number of questions

Best regards,
Daniel

Please consider adding an additional option in the Active Directory action configuration: "Synchronization Mode: Disabled/None."

In environments where full or incremental Active Directory synchronization is configured to run frequently, and where applications which generates a high volume of changes to AD user/group accounts, this situation leads to unnecessary service activity.

Hi,

having dev, test and prod systems it would be great if an admin could set the link to the Designer Desk of the dev system in prod and test systems in the administration of the portal. This way users can open Designer Desk on dev system from prod and test and projects get published in dev system directly. Exporting published projects on prod and importing to dev wouldn't be necessary anymore - if users would use Designer Desk on prod system instead of dev.

Kind Regards
Sébastien Anselment

Privacy overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognizing you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.


To see a full list of the cookies we use and learn more about their purposes, visit our Privacy Policy.