search results

Hi, right now app, process and workflow's associated form type user privileges can only be set for users and/or groups. It would be great if global business rules could be used too. A filter could be set that only global business rules with return type „user list“ can be used. This way e.g. a business admin could manage users in a dictionary and dynamic privileges would be possible with a b

(...) Hi, unfortunatelly global "objects" (business rules, form rules , constants, automations) have no app binding functionality as data sources have. Some global constants, business or form rules and automations may contain critical data (e.g. api tokens) that should not be useable by all devs with studio access. An option to set an object as protected and enabling an app binding to allow the usage would s (...)

(...) Hi, right now configurations are process specific and contain amongst others business rules, form rules , constants, automations. If multiple processes of the same app or even other apps need one of those there is the possibility to create a global equivalent in system settings. Unfortunatelly global objects have no app binding functionality as data sources have. Some global constants, business or form (...)

Hi, I'm experiencing an issue with selection attributes. If a user types a value but doesn’t explicitly confirm the selection, the value still appears in the field after saving the form or moving along the workflow path. However, the problem is that the value change rules are not triggered in this case, which often results in the form not being populated correctly. Has anyone encountered

(...) It would be very useful if the Attachments panel could be controlled by form rules in the same way as regular form fields. For example, functions such as: * `ENABLE[Attachments]` * `DISABLE[Attachments]` * `MARK REQUIRED[Attachments]` * `MARK NOT REQUIRED[Attachments]` * `HIDE[Attachments]` * `SHOW[Attachments]` Use case A workflow instance is assigned to a user as a task. Therefore, the (...)

I would like to raise a performance concern related to forms containing large Item Lists. My analysis shows that server side callbacks and business rule requests include the current state of the entire form, including Item List rows and columns, even when the executed rule does not reference the Item List. In my tests, a form with approximately 40 Item List rows generated requests of around

(...) ill: b#Outlook (Mail) So it seems that the stored label (Outlook (Mail)) is ignored when rendering the field and the current meaning of ID b is used instead. This also affects business rules/form rules . For example, we had a rule which made an additional text field required when: h = Other After inserting or moving an answer above it, h refers to a different answer, while the business rule (...)