Technical Blog Post
Abstract
BiLog: Brownies, Bronies and Adding LD to ROS
Body
One W separates brownies from bronies. Brownies are incredible, delectable chocolate goodness, while bronies are followers of a children's TV Show. Bronies and their collections of Little Ponies have become increasingly popular in the Software Development world thru their features in Wired Magazine. 1. First, access the Database Configuration application and verify that a relationship exists between the parent Work Order and the child Long Description. In this example a relationship does not exist, so one was added as shown here. 2. Next, go to the Object Structure application and add the new child object of Long Description to the Work Order ROS. Make sure to specify the cardinality and type of database join properly. 3. Select Exclude/Include Fields from the Select Action menu to exclude any attributes from the Long Description Object that you do want to display to your users. For example, you may want to exclude attributes like LONGDESCRIPTIONID. 4. The Long Description Object is now available within the Work Order ROS for your users as shown here. These 4 simple steps above illustrate how quickly you can customize your data collections by including long descriptions in your ad hoc reports. And as for bronies or brownies…I’m definitely going for the brownies…although they never last long enough to form collections!
To recap, Report Object Structures (ROS) are the building blocks of ad hoc reports. ROS define which database objects and attributes are available for the user to select to his ad hoc report. To enable your users to add the long description field to their ad hoc report, you must first add the Long Description object as a child to the ROS.
To illustrate this, the steps below detail an example of how you can configure the Work Order ROS to include the child Long Description object.
UID
ibm11134099