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...
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.
When managing form with multiple instances it is necessary to be able to filter out some of the statuses and work on the rest. i.e. in attached to filter out the backlog, not suitable and rejected and just leave the live instances. Either by allow...
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
