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.

Currently, we need to maintain a singular spreadsheet to add additional Form Definitions to the same project. This spreadsheet can become very large and hard to manage, and would be easier to have distinct spreadsheets for sets of similar Forms.

It seems the Region sometimes goes to a random location, within another Region if i try to move it around. This mostly happens if I drop it part outside the canvas. Also, doesn't look like i can move a Control below a region, but have to move the ...

Currently, the files are exported as per the image below. It should zip only if attachments are available, but just export the raw pdf otherwise.

This is esp. helpful when setting up a template projects and provisioning them to production. Bindings could be map to project metadata like Project Name, No. etc, and be autofilled in all Form definitions.

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 helpful in instances where the final approval will always be the one that's assigned a closed Form. A good place to disable it would be under Forms > Set workflow > Edit transition button > Advanced > Include comment on transit...

We should be able to maintain the mapping if the fillable fields are the same. This will save much time remapping when small updates (additions/formatting) to the PDF have to be reimported.