Sometimes we apply more than one drawing annotation to the same model. It would be good to have a model manager view with all the applied annotations group so that we can disable, remove or add. That way we could select what we want to remove inst...
Enhancing Named Boundaries: Updating Named Boundaries and Applying Geometry Rules
To enhance productivity and efficiency in live projects, we need dynamic Named Boundaries linked to Geometry. This includes the ability to update the shape or location of a named boundary after creating a sheet model, with the changes reflected in...
Configuration variable to control default path for .tiw files
When working in a fieldbook in survey, we want to set the default file path to a specific location for .tiw files. As it stands, ORD remembers the last location from which a .tiw was imported, but we want to set a file path for all users.
It would really be helpful for users with OBD to not have to open OBD prior to opening OBM. That is a big pain point that I get a lot of complaints about. Also it is very confusing for users at first, they don't understand why they can't just clic...
Add The Ability to use a Fence and Regular MicroStation Shapes as a Boundary When Using The "Analyze Volume" Tool
Currently, the "Analyze Volume" tool "Only" allows you to use an ORD Geometry Shape for a boundary. It would be much more useful and intuitive if we could also use a fence and/or a regular MicroStation shape for a boundary as well like you could w...
Include 32-bit or 64-bit data or product version in the SGN File Properties
We've created application entries in our ProjectWise environment for the 32-bit and 64-bit releases of SignCAD to control which application opens any .SGN files in our environment. We're looking for an automated solution to set the application ent...
The elevations of the event point can only be seen when one generated a Horizontal Alignment Event Point List Report. It would be better also if the elevations can be seen earlier in the Event Points List Table
Updating XS annotation group w/o resetting annotation placement
The XS annotation group will place annotations in text conflicting locations. Once the user resolves the text conflicts there is a chance that the annotations may have to be revised when the model is updated. Therefore, it would be helpful if ther...
When remapping feature definitions to an upgraded workspace the old workspace's feature definitions that are no long used remain in the DGN standards and available for use. This is a problem as the users made select them not know that the feat def...