Ability to manually save changes in Forms Designer
When designing large Forms, the performance heavily degrades on any action like selection, editing, etc, due to auto-save continuously running in the background. This could be a toggle to enable/disable as required.
Currently, we need to pre-create multiple Sections for each anticipated entry. This leads to the following issues - Anticipating no. of entries in advance Large no. of bindings manually created Large no. of scripts required to display/hide each Se...
hi can we add dynamic expression into Form's action/scripts? please refer to the attachment that the Project Name is added to the action/scripts as a dynamic expression. whenever the Project Name changes, the value of that Control updates automati...
Bentley includes a "Limit to fields on the form" function in the Actions-Scripts function at the Design Form stage (whoever added this is a genius!). Please include the same "Limit to fields/bindings on the form" function on the Field Options part...
This is useful for cases where we want to make a field hidden by default, but it becomes visible and required based upon other related input. We can make fields required through workflow, but that is not available through initialization settings.
Roles without Create but with Edit permission should not see the Form in Create dropdown
Roles with Edit permission can begin a Form from the Create dropdown menu and complete all fields but cannot Save it. This can be misleading and result in wasted time and frustration, especially when filling out lengthy Forms only to discover at t...
Requesting that the notifications from IRS contain more information (e.g. Project name, Facility name, form type from IRS, etc.)
The only information coming through is the person who assigned the issue, and a number (example: TQ-SPS-xxxxx) that may not jump out at the user Related to idea SDP4-I-15 This is in Shell's AHA workspace that is separate from Bentley.
0
Likely to implement
0
Planned
