In many occasions we use date for something that is yet to happen. Yet the user can input a date in the past. Having the ability to restrict the date for future events as related to the date of input of information would avoid this kind of errors.
Expand on visibility assignments for roles and users
Quite often (almost every multi contractor form) requires visibility to be restricted to Client and anyone in the Creator's organisation. We currently manage this by asking the user to assign a role set up for their company to the AssignedUsers pr...
See source of model and Ability to remove model from iModel viewer
Using the iModel viewer in the browser gives a list of different models. It doesn't show however where these models come from. It would be useful to see that (when hovering or in the properties ...) At the same time it would be useful to have the ...
Get overview of "local" connectors from within the cloud environment
I sometimes use the iTwin Synchroniser from my desktop to directly synchronize models from a local source to the iModel. This means I don't have to first upload them, makes it also easier to deal with versioning. Unfortunately outside of the local...
I often have models or drawings that are not created in the same (/correct) local coordinate system. In Microstation application it is possible to assign GCS to those different files and then reference them with "GCS reprojection". Meaning that th...
When designing visibility in complex relation projects we need to add company specific role to AssignedUsers list to assure everyon from that company can see their forms. We can currently exclude the roles from a user list control but it will be m...
We find it increasingly necessary to have to be abl eto define a default value for various controls: Textbox, Numberbox, DropDown, UserList. The alternative atm is to have a script to populate that default value plus for some controls we need a pa...