Description of problem: When a new screen plugin is created and screen component is added to a column of perspective plugin, newly created screen plugin name is not listed in select element of Place Name parameter. Version-Release number of selected component (if applicable): BRMS 6.2.0.ER2 How reproducible: - Steps to Reproduce: 1. Create a new screen plugin. (Extensions -> Plugin Management -> New... -> New Screen) 2. Create a new perspective plugin. (Extensions -> Plugin Management -> New... -> New Perspective) 3. Add screen component to a column in the created Perspective plugin. 4. Try to select name of the newly created Screen plugin in Place name select element. Actual results: Name of the Screen plugin is not listed in Place name select element. Expected results: Screen plugin name is selected. Additional info: -
Right now, this only works if the user reloads the application. There is a UF feature related with that: https://issues.jboss.org/browse/UF-234
After a reload, this commit allows a screen to be displayed in Edit Screen drop-down. https://github.com/uberfire/uberfire-extensions/commit/e4655234b740d0496a4205c728c1fd3751b5bc36. The "live reload" feature will be implemented in the future. (https://issues.jboss.org/browse/UF-234)
I still cannot select newly created screen component in 'Place Name' dropdown menu because the screen component is not listed. I tried to refresh the browser (ctrl + F5) and I also tried to restart eap server after 1. step but it does not help. Tested on BRMS 6.2.0.ER5.
Fixed: https://github.com/uberfire/uberfire/commit/6a7c8561fbcbae31f43c7ba708c6c0d57dab52db https://github.com/uberfire/uberfire-extensions/commit/50414a2c6fc90f7610d3411b51840abe37ef0056
Thanks Eder. Verified on BRMS 6.2.0.CR2.
Tests on BPMS 6.2.2.CR1 revealed that even though fixed for BRMS, this issue is still present in BPMS (both 6.2.2 and 6.2.0 - so this isn't a regression).
This seems outdated, I was able to select my screen component in the perspective after a refresh in BPM Suite as well.
Verified with BPMS and BRMS 6.3.0.ER2. I also tried the steps on the latest BPMS 6.2.2 build and I did't see the issue.