Automatically identify the element linking the Forms to the iModel
To add value to the digital documentation management strategy using Forms (whether Issues or other types) add the element attribute; allowing to evaluate the elements of the model according to the number and type of associated forms.
Transition Buttons behavior that have Required Conditions
in forms, each transition button can have a conditions that has to be met to use it. If a user selects the option then they get an error message that may not be intuitive. Can only transition buttons show up where the condition is met, or a button...
In form workflow there are multiple valid options. Only 1 option is shown in full size then the others available are small when clicking the dropdown arrow. Users sometimes see these are not primary valid options due to the way they are presented....
In forms, the workflow transition buttons are listed by how they were created. is there a way a sort property can be added so they show up in a priortized order.
Limit users from sending documents for Review from outside PW
Currently, when a new Design Document Review form instance is created (or any form for that matter), the user can attach documents both from inside the CDE (Documents) or by uploading from their own computer. While in some cases this can be accept...
It would be good to be able to share my own Measurement/Dimensions with other Project Members. In old iTwin Design Review Platform there was a Share Button for each Dimension to publish it for all members. Would be good to get this back on current...
iModels are becoming a very convenient way to conduct design reviews in a federated environment. However, there are early stages of design before federation that require reviewing design files individually rather than in a federated environment. C...
0
Needs review