Report builder attributes

In report builder, the behavior of all objects is described and controlled by its attributes. Therefore, to skillfully use the objects in report builder to make complex and perfect reports, you must be familiar with the attributes of each object and understand its usage. Setting the attributes of an object is completed in the attribute palette. Report builder classifies the attributes of an object into the attribute segments of the attribute palette based on their functions. For example, the attributes of a text object are classified into five attribute segments: general information, fixed background object, web link, general layout, and advanced layout. The "general information" attribute section contains some general information about the object, and the "fixed background object" attribute section contains attributes such as "type" (such as straight lines and rectangles) of the object, the "web link" attribute section contains the HTML/pdf behavior attributes of the object, and the "regular layout" attribute section contains attributes applied to all layout objects, the "Advanced layout" attribute section contains attributes that control the object formatting method. In report builder, some attributes are common attributes of report objects. For example, fields, frameworks, repeat frameworks, and charts (charts embedded in reports) all have web links, regular layout, and advanced layout attributes, you can set these attributes to define the HTML or PDF behavior and object layout of the report output to the Web browser. However, each object in a report has its own unique attributes. For example, the database column object only has two attribute segments: General information attribute and column attribute. The column attribute segment contains multiple column attributes, such as "column type" and "column separation order. In addition to common information and column attributes, the formula column object also has the "PL/SQL formula" attribute, which is used to specify the calculation formula in the report operation. Another example is positioning an object. This object only has two attribute segments: General information attributes and positioning attributes, the positioning attribute section contains "child object name", "parent Object Name", and "Horizontal hiding" and other attributes that determine the positioning information of child objects and parent objects. P.s: 1) Some attributes can be activated only when one or more other attributes have been set. For example Program Command Line attribute, which can be activated only after you set the "pdf operation" attribute of the object to "start the application. 2) some attributes are read-only in the attribute option board and cannot be modified by users. These attributes are mainly used for users to view object information. For example, the vertical repeating frame, horizontal repeating frame, and horizontal product group attributes of a matrix object are read-only. Because the "matrix" object is created during the matrix layout of the report, its "vertical repeat frame", "Horizontal repeat frame", and "horizontal product group" attributes cannot be modified by users. 3) Some attributes must be set in the attribute palette, while others are optional. For example, the "Remarks" attribute of the Framework object is an optional attribute. That is to say, it is irrelevant for the user to specify the remark information for the Framework object, which can be determined based on the user's actual needs. The "Vertical Scaling value" and "horizontal scaling value" attributes of the Framework object must be set because they determine, the vertical and horizontal changes of Frame Objects. Attributes that must be set usually have default attribute values. 4) Some attributes are only applicable to special platforms or reserved for compatibility with previous versions. Therefore, setting these attributes may be invalid. For example, to set the "direction" attribute of a report, this attribute takes effect only on Bi-direal Al platform. This attribute is invalid for common platforms (with only one writing direction, such as the Chinese operating system. 5) when setting an attribute, the attribute displayed in the attribute palette is sometimes changed due to the setting of an attribute. For example, when setting the tag attribute of a button object, according to the selected button tag type ("text" or "icon "), the corresponding "text" or "icon name" attribute is displayed in the property palette. When setting the behavior attribute of a button, different attributes such as "multimedia file" and "PL/SQL trigger" are displayed because the selected button behavior is different.