Idea template Thank you for submitting an idea. Please provide the problem, user needs and high-level requirements, any screenshot or recording that may help our team understand this. Problem to solve: Integrate Audit Trail from Comment Tab into...

With the recent merge of Synchro Inspection configurarion, hierarchy configuration and inspection groups. Both available under Project and Build ( We are still waiting to have the full fonctional deploy features) It would be really handy to allow ...

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.

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.

Idea template Thank you for submitting an idea. Please provide the problem, user needs and high-level requirements, any screenshot or recording that may help our team understand this. Problem to solve: The ability to open the schedule view and n...

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

Want the ability to Delete a Binding(s) that are unused and unassigned on FORM Definitions

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