Technical Blog Post
Abstract
BiLog: Best Practices…Reuse ROS for Application Export Data Analysis
Body
Reduce. Reuse. Recycle. Not only are these three words critical to insuring a sustainable environment, but they can also be critical to how we approach reporting.
Today, I’m going to focus on reusing functionality - - specifically with Report Object Structures (ROS). A few months back, some of the BiLog entries talked about the importance of ROS as they are the building blocks of Version 7’s ad hoc reporting tool, QBR (Query Based Reporting). These entries included how maxrelationships and cardinality are used within a ROS,
Because ROS are extremely powerful, you may spend time carefully creating the parent-child hierarchical relationships, and defining which fields should and should not display to users. In Version 7.5, you can quickly apply the power of the ROS you create - in a different manner - with the Application Export functionality.
Application Exporting can be enabled from within the various Version 7 applications. It is similar to QBE, or data download, in that it exports the results of a user's query. This enables your users to further analyze or act upon the exported data set. However, QBE is limited to the list tab fields only -- whereas Application Exporting can export multiple database objects and attributes. This occurs as Application Exporting is also based on Object Structures with their multiple object capability.
How can you use your ROS with the new 7.5 Application Exporting? Start by following the simple steps outlined on this wiki page or detailed in the Version 7.5 QBR Reporting document available here
The steps include duplicating your ROS as an integration object structure for exporting, and then setting the 'Add/Modify Application Export Support' action. You can then define how many rows of data your users can export, and you can also define who has security access for this functionality.
Using application exporting is another way for your users to analyze data - and another way for you to reuse the powerful ROS you create.
- Reduce the number of custom reports you design, develop, test, administer and maintain.
- Reuse functionality to meet varying user business needs.
- Recycle what you have learned, and apply to existing and future releases
Today, I’m going to focus on reusing functionality - - specifically with Report Object Structures (ROS). A few months back, some of the BiLog entries talked about the importance of ROS as they are the building blocks of Version 7’s ad hoc reporting tool, QBR (Query Based Reporting). These entries included how maxrelationships and cardinality are used within a ROS,
Because ROS are extremely powerful, you may spend time carefully creating the parent-child hierarchical relationships, and defining which fields should and should not display to users. In Version 7.5, you can quickly apply the power of the ROS you create - in a different manner - with the Application Export functionality.
Application Exporting can be enabled from within the various Version 7 applications. It is similar to QBE, or data download, in that it exports the results of a user's query. This enables your users to further analyze or act upon the exported data set. However, QBE is limited to the list tab fields only -- whereas Application Exporting can export multiple database objects and attributes. This occurs as Application Exporting is also based on Object Structures with their multiple object capability.
How can you use your ROS with the new 7.5 Application Exporting? Start by following the simple steps outlined on this wiki page or detailed in the Version 7.5 QBR Reporting document available here
The steps include duplicating your ROS as an integration object structure for exporting, and then setting the 'Add/Modify Application Export Support' action. You can then define how many rows of data your users can export, and you can also define who has security access for this functionality.
Using application exporting is another way for your users to analyze data - and another way for you to reuse the powerful ROS you create.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
UID
ibm11133301