Need JVM restart to see exposed properties on clipboard
When a new deployment adds additional property rules and those properties are exposed in the database by running DDL directly to create the columns, the properties do not appear on the clipboard until all of the JVMs are restarted in Pega 7.1.2.
Steps to Reproduce
- Run DDL on the database to create the columns for the new properties.
- Import the jar file containing the new properties.
This is expected system behavior.
The Pega engine reads database metadata that is - the structure of all objects for example table, procedures, views, and so on, which is again visible in the Pega schemas, on engine initialization only. Pega engine caches this information and references it for the duration of the engine uptime.
It does not re-read database object metadata for performance reasons. Thus, if the database structure has changed during runtime by an import or direct DDL, an engine restart is necessary.
Restart your JVM to force the Pega engine to read new metadata from the database, including all table and view changes.