BPM 10g: Changes Made to WORKSPACE.PROPERTIES File Not Preserved (Doc ID 1506845.1)

Last updated on OCTOBER 01, 2021

Applies to:

Goal

CHANGES MADE TO WORKSPACE.PROPERTIES FILE NOT PRESEREVED.

 Steps to reproduce:
****************
 1. Set the fuego.workspace.executionDialog.maximize=true in
 workspace.properties file then regenerate and deploy the workspace ear
 
 2. For your user, delete the preferences in the FUEGO_STRPROPS FDI table:
 delete from <OBPM_DIR_SCHEMA_USER>.fuego_strprops where fuego_key ='OPTIONS' and fuego_modifier =''

 3. Login to the workspace.
 Create some instances and make them arrive to your interactive, so you few instances to play with.
 
.
 4. Run the SELECT * FROM <OBPM_DIR_SCHEMA_USER>.fuego_strprops where fuego_key ='OPTIONS' and fuego_modifier ='' You will see that at that point there is no preferences
 You may run any interactive, log out, log in, the query above will not return anything. Until you...

 5. Click on the "Collapse" (Little arrow on the top left side of the Inbox panel, near the "Work Items" text)
 As soon as you collapse, the preferences entry is generated in the FUEGO_STRPROPS table and the query above will return it.
 But if you analyze the properties, there is no fuego.workspace.executionDialog.maximize. You may even run an instance, and it will be still executed in maximized window.

 6. Now logout and login.
 The login will reload the preferences from the database, but even the fuego.workspace.executionDialog.maximize is not set, it will be treated as false.
 So, if run an instance, it will show up in non-maximized window.
 The database still doesn't show the fuego.workspace.executionDialog.maximize=false, but as soon as you make an operation that triggers the options to be stored (for example a logout or a collapse/expand), you will see the change in the database as well.
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.