In the past, we had the requirement to force the user to add exactly one document. Of course, this can be done with validation rules. However, it would be perfect, if after reaching the maximum amount of attachments, the buttons to add new documents would be disabled. Just how it is already implemented for a dictionary template element.
Could you please extend the BPS group with an optional email field? Reason: By having an email field for the BPS group, it would be possible to send the email to a group mail box, rather than to every user.
hi, It would be useful to know at what stage the comment was added. The name of the step could appear next to the user name and date in the comment header. Regards.
Hi, it would be great if the link of an entry in a report column could be set to a link to the instance of the displayed object in the form field value. This option only exists right now if the choice field is related to a BPS internal view but not for choice fields with a data source of type dictionary or user/group. The form field value link of a dictionary entry could lead to the dictionary's entry and a link to a user or group could lead to a profile page. The screenshot shows the g (...)
Hi, it would be great having an audit log or audit trail feature as e.g. Microsoft and Atlassian have it to get an easy overview of what a specific user has done. Security relevant features like last login/access timestamp to WEBCON portal, Designer Desk and Designer Studio should get saved seperately. Right now there seems to be no information available in the database when a user last used one of the modules. The audit log could also contain login events for failed logins for easier d (...)
[Benefits and business justification] - In many business processes, items are archived after a certain period to reduce the load on the production database. - However, access to historical data is often essential – e.g., in the context of audits, analysis, reporting, or trend comparisons. - Granting appropriate permissions enables precise management of archive access, aligned with real business needs. Optimization of analytical and reporting processes - Archived data is often analyzed (...)
New assignment filter: All active where I am delegated/substitute Currently, such a report is created in the SQL filter if you do not want to show the user's active tasks.
Hi everyone! What do you think about adding a customization option on the home page, e.g., to support, so that every user would immediately know where to report information related to a problem? Additionally, if it were possible to add “Useful links” on the left side of the navigation bar, I think it would be very helpful for system users.
The system looks inconsistent — we can easily change colors for group headers and tab panels, but not for the comments and attachments sections. These sections look similar to tab panels, so it would make sense to allow color changes there too.
Please verify the ability to filter by each column type in the item lists. Filtering on the header is similar to an Excel spreadsheet.
Would you be open to adding a way to archive items (like employee requests) while keeping some of the access permissions? Right now, archived items can only be accessed by people who see the whole archive. It’s possible to manually give someone read access, but that’s not very practical. Could you add an option to automatically give read access based on a field in the form during archiving or a bulk action to assign read permissions to archived items?
Would you be open to exploring the option of exporting packages with anonymized connections, so that credentials like client ID, secret, and account names are not included?
Please verify the addition of the option to add additional columns in the "Fixed values list" data source
Please verify the possibility of adding calculated columns to the dictionary data source. Regards,
Hi, as dictionaries always get created through applications it would be great if the overview table would also at least have a column with the application name to get more structure and filter options here. A flat list of hundreds of dictionaries is not easy to handle and a good naming convention is the only way to get dictionaries quiet a bit structured. Maybe it would be also an option to use group containers in the tree list that correspond to the application itself instead of the functio (...)
Hi, it would be great if in the section Data sources of the Designer Studio all entries (authentications, connections and all types of data sources) could also have group containers as they exist e.g. for form/business rules. Flat lists miss structure and having more and more entries lead a bit to confusion. The only way to get structure is having a really good naming convention right now - what is always a good idea to have. ;) Kind Regards
It would be great if all configuration options as they exist for floating-point number form fiels would also exist for calculated columns in reports or bps internal views with the type decimal number. Missing configuration options are: - show thousands separator - display format - Prefix - Suffix The only existing option is number of decimal places.
Hi! Add the ability to configure dashboards in applications that should be default for a specified user or the user would decide which one they want to have as default if there are many of them.
Hi, it would be nice to arrange more fields horizontally e.g.: choice fields or fields in tabs that are part of a group - here I can only arrange all in the group horizontally but not espacially only field in one of the tabs in this group Thanks in advice Monica
Hi, data table /rows display the values as they are returned from the data source. In case of the MSSQL data source this is fine for text fields and for choose fields, integers/decimals we can work around it. Either by using the available functions or using format functions and the current user language. In case of date time there's no work around. The issue is especially visible when users are located in different time zones because the date time is returned in the server time. Of cou (...)