Currently, it's limited to a few standard columns but would want to see additional fields common to all the Form definitions, like Created Date, Project info, etc. This would be similar to the Dashboard's configure grid behavior. This is esp. impo...

Having a connection to ProjectWise is good, but consulting organizations use multiple document systems. To simplify workflows for consulting organizations with multiple documents sources working with owner/operators, contractors, other consultants...

If a Form was sent back upon a Review, the Creator should be able to resign or update the timestamp, for both the Signature and Timestamp controls.

Because the names of some types of forms are longer, there should be an option to adjust the size of this panel.

When editing a workflow, it is imperative that users select the "Publish Workflow" button to ensure changes are saved. The button will turn green to indicate that publishing is required. However, to further support users and reduce missed updates,...

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.

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.

We need a project-wide binding that can be assigned values at a project level, and be used across multiple Forms definition/Inspections. This will enable users to re-use repetitive information like Project Details.