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.

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 ...

Have PDF documents from the SYNCHRO Documents folder, such as "shop drawings or detail sheets" that can be accessed by clicking in the properties section of a 3D model that links directly to the PDF sheet it's referencing.

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.

Current Problem: In our document control project utilizing PW/SYNCHRO, we currently face a significant efficiency bottleneck when editing data. Despite having an Excel-like grid view with filtering capabilities, any modification to a specific form...

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.