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

User Voice

MVP

Hi,

it when the "Incorrect rule configuration" name is thrown, it would really help, if the name object would include the parent object.

I currently get this error:
Incorrect rule configuration for object "Site".

This got me really confused because there wasn't any rule on the field. In the end I found another "Site" which is a column in an item list.
Incorrect rule configuration for object "Target sites: Site".

Best regards,
Daniel

We love the inbuilt analytics features. The give us the opportunity to take a quick look whats going on. Especially for smaller Applications the Advanced Analytics Framework is very useful.

Currently a user needs at least the role "Business Administrator". But we do not want to give this high-level access rights (change / delete workflows) to our analysts (department manager, process manager, ....)

So a dedicated Role "Analytics" (in combination with read all instances) would be very helpful.

Currently, the only way to provide data to our process managers is by sending them screenshots, since I cannot and am not allowed to give a process manager the role of "Business Administrator" under any circumstances.

MVP

Hi,

it would be great if an option is added to exclude processes from the analytics overview.
I tried to "remove" those by entering a date far in the future for this flag:
Limit the scope of analytics data – parameter is used to limit the scope of processed data available in the Analytics reports. If this option is activated, all measures of analytical reports will not be calculated for workflow instances created before the given date.

It didn't have any effect.

This new flag would have a default value based on the type of process:
- Dictionary: Exclude from analytics
- Document template: Exclude from analytics
- Standard: Include in analytics.

While this is the default value, it should still be possible to modify it. For example, if the dictionary process is not sufficient for storing master data and we need to use a standard process.

Best regards,
Daniel

Hi,

it would be great if one could
use nested application groups instead of a flat list. This way one could create e.g. a group for HR division and 2 child groups for apps for internal (only HR employees) or external (all employees) usage.
A hierarchy with three levels should be sufficient.

This concept could also be applied for all other objects where groups exist as global form/business rules, data sources, connections, …

Kind Regards,
Sébastien

Hi,

we use the app vsb.actions from vsb/smoodi and would like to give the name another name for internal use because we don't like to use names of vendors for products/services. We now could change the app name in the Designer Studio and with each update of vsb.actions that we import in Studio we would have to rename the app name.

It would be nice if there could be an option to set a configurable display name for apps that get displayed in the portal. This way one could use the app vsb.config to set a customised name that can be set as variable in the needed new "alternative display name" option that I suggest here. This field could be added in the general tab of the app und the name field with the option of a String or usage of a form rule or field to get the value dynamically.

Kind Regards
Sébastien

MVP

It would be nice to have :)
On the contrary, argument that "The lack of this functionality forces users to manually retrieve data using SQL queries, which contradicts the Low-Code platform's principles." doesn't really convices me.
Platform is Low-Code, not No-Code. SQL is necessary to use it's full potential, and such simple query will be done once.

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.