Enhance reporting and configuration options
Consider additional configuration options where possible to aid in reporting.
Consider a re-do of the View Definition Wizard.
Examples of better configuration include:
- Choosing fields or attributes to view on reports or panels
- Defining and using calculated fields
- Allowing Option fields to be displayed on some views so that they can be used to create personalized reports
- Store and use more user-defined fields, like those in Asset Management
Consider these changes for specific views in Foundations as well (buildings, rooms, assets, employees).

-
spogoloff commented
I agree with all Dan Miller's ideas, but I'd like to add some simple additions: add choices to add the Field Selection Gear, and Hide Field. Allow the Data button to be permanently blocked so it won't reappear on Alter View. On Report Only VDW, remove requirement to assign to Application/Process since for My Favorites that is confusing and irrelevant. (It could be stored in a special application process, e.g., Favorites). Then add an ability to message a System Administrator to move a Favorite to a permanent menu.
-
With Archibus v25.3, which is the upcoming release, we have implemented some of the ideas in this topic.
For example:
- User Defined Fields for Buildings, Floors, Rooms and Employees.
- Promoting any existing field for Buildings, Floors, Rooms and Employees so that it can be used for data entry or reporting .
- Reporting on promoted fields and user defined fields by showing or hiding them in the grid reports available in the Define Rooms, Define Locations, Define Employees and Space Console. This includes moving columns in the desired location and exporting the report to XLS.
- Highlight by promoted fields in the Space Console and print the result to PDF.We also have on our roadmap to improve the Report Definition Wizard.
-
Tiffany Lam commented
Would be nice if there was an earlier dynamic preview in the View def wizard while the user is picking and choosing fields. Right now a user defines and picks all the fields and virtual fields...and if there an incompatibility with the dataset (ie because they were making a 2D chart or if there's no data in a field) then go next and they get nothing to display at the end. So it would be nice to have a very early preview to know what fields yield good data.
-
Dan Miller commented
I agree with Fred, a revamp of VDW is needed. The solution is currently too technical. A layer of abstraction needs to be applied so an everyday user can create a report without knowing all of the technical details of creating a report. The UI is also clunky and requires too many steps. How many users understand Applications and Processes that are necessary to save a report to the pnav or homepage?
In addition, the standard report UI needs to be updated to allow a user to add/remove fields to a report without using the VDW. Think about moving features in the VDW directly into each report so you can individually add/remove fields, set filters, set restrictions, and maybe one day group data. This would be a welcomed improvement, though may require a significant overhaul of the reporting engine.