Reporting

<<Back

Property Optimization or exposing a property

·         Rule base table saves all the data into a single column called ‘pzPVStream’ in BLOB (Binary Large Object ) format

·         The properties of class will be available as columns compressed into pzPVStream column

·         The columns which are available in pzPVStream will lead to poor performance while reporting

·         To use the properties in reporting, we must have to optimize them.

·         When we optimize a property, PRPC creates a physical column in the table. This physical column is the copy of BLOB column.

·         *Only optimized columns (properties) can be used in the where condition of Report Definition and activity (Obj-Browse) rules

FN          LN         AGE C-123                A            B           1 C-123                B            A           1 C-123                B            B           1

UI List P (1) P (2) P (3)

C-123

 UIList

           

·         Like normal page properties, we can’t optimize page list properties

·         When we optimize the page list properties, it will create a separate table with multiple rows of data where each row corresponds to one indexed page in the page list

·         This table is called index table and will be mapped to an index class

Declare Index

·         Indexing improves the performance of the application when running the reports

·         If we want to use any properties in report rules, we need to optimize those properties

·         Unlike normal properties, when we optimize page list properties, PRPC will create below rules

1)      Index class which gets derived from the OOTB class ‘Index-‘. This index class is been mapped to an index table

2)      Declare index rule which maintains the mapping between Work table and index table

·         Declare Index will be created under Work class, SysAdmin category