This is a data model viewer tool that I use to view the contents of Oracle Policy Modeling projects without having to use Oracle Policy Modeling. Sometimes I just don’t have the right version, or I just don’t have the right laptop. All I want to do is view the project. It can also be very useful if I am working on designing data mapping with another application.
When I’m in the early phase of assessment, I don’t need to actually do the mapping, I just want to see what the project contains. And that includes attributes, value lists, upload groups and a lot more.
The tool itself looks at a variety of files:
- The projectDataModel.xml file
This file contains the entities and most important attributes – those that have a public name, those that are involved in mappings and the like. It gives a good overall picture. But
- The XGEN files
it does not contain all the attributes however. Many of them will be in the specific XGEN files generated for each Word or Excel file.
- The Enumerations file.
This file contains the value lists created for the Project, and their values.
- Decision Service Reference Files
If your Oracle Policy Modeling project calls any Decision Services, they are listed.
What can you do with the data model viewer?
- Download to SVG
My favorite and excellent for converting, adding to a presentation or just viewing in a browser.
- Download to PDF
Much slower, but still useful
- Print to a printer
- Find attributes without a defined type (they have an “(Auto)” type)
- Find attributes that don’t have a public name
- Find temporal attributes
What the Data Model Viewer does not read:
- hubModel.xml – This file contains all the mapping information and the Value Lists downloaded from a connected application. Given that there may be many hundreds of Value Lists and values, as wll as a lot of mapping data, this tool does not load this information at the moment. This may change in the future.
- Flow Schemes and Flow definitions. This will change in the future.
Things to note:
- The OIA Data Model Viewer will not match two attributes with differing white space. So if there is an attribute called “the cat is fat” in the projectDataModel file, and “the cat is fat” (two spaces) in one of the XGEN files, this will be recorded as two attributes, not one. It is useful to catch these and correct if needed. Thus the attribute count (from the View menu) may be slightly greater than that reported by Oracle Policy Modeling
What it does not do:
The OIA Data Model Viewer does not change any file. All files are opened for reading only. Here is a video about the origin of the Data Model Viewer.