Optimize for Reporting option not available
Hi all,
I am trying to create a report with my newly created properties and I need to expose these properties to use them. However, I noticed that the option to optimize a property is not available. I also checked other properties from the same class and it seems that they do not have this option too.
Any ideas why I can't see the option to expose the property for reporting purposes? Am I missing something?
Pega Version: 6.3v
Thanks in advance!
Accepted Solution
Pegasystems Inc.
IN
Hi,
The prerequisites are:
1. The prconfig.xml setting 'database/AutoDBSchemaChanges' must not be set to FALSE.
By default, this property is not set in the prconfig.xml file. If your site wants to limit this type of operation, database/AutoDBSchemaChanges may have been added and set to FALSE in prconfig.xml.
2.The production level of your system is 1 or 2.
3.
The database user used to access the PegaRULES database must have ALTER TABLE and CREATE TABLE permissions.
This user's username and password are specified in the data source definition defined in your application server for the jdbc/AdminPegaRULES JNDI location, if defined, or else the base user specified in the data source associated with jdbc/PegaRULES.
If the Admin user is defined, PRPC attempts to use it for this operation.
If the Admin user is not defined, PRPC attempts to use the base user.
For more information, see the section Create JDBC Resources in your Installation Guide
Pegasystems Inc.
IN
See the prerequisites for using property optimization here:
https://community.pega.com/how-expose-property-database-column-property-optimization-tool
Accepted Solution
Pegasystems Inc.
IN
Hi,
The prerequisites are:
1. The prconfig.xml setting 'database/AutoDBSchemaChanges' must not be set to FALSE.
By default, this property is not set in the prconfig.xml file. If your site wants to limit this type of operation, database/AutoDBSchemaChanges may have been added and set to FALSE in prconfig.xml.
2.The production level of your system is 1 or 2.
3.
The database user used to access the PegaRULES database must have ALTER TABLE and CREATE TABLE permissions.
This user's username and password are specified in the data source definition defined in your application server for the jdbc/AdminPegaRULES JNDI location, if defined, or else the base user specified in the data source associated with jdbc/PegaRULES.
If the Admin user is defined, PRPC attempts to use it for this operation.
If the Admin user is not defined, PRPC attempts to use the base user.
For more information, see the section Create JDBC Resources in your Installation Guide