Hide Forgot
Description of problem: When first accessing jbpm-console, it starts listing processes from any package that has a binary available from Guvnor. After that point no new packages start to be tracked and their processes won't show up in the jbpm-console. Here's an example: I have defaultPackage with Evaluation process and another myPackage with no processes. I build both and go to jbpm-console to check the Process Overview. Evaluation process is there. Then I create two new processes, one in defaultPackage, the other in myPackage and build the packages again. All three processes are listed in Process Overview in jbpm-console. Ok up to now. Lastly, I create a new package newPackage, create MissingProcess in it and build the new package. MissingProcess will not show up in the Process Overview. Version-Release number of selected component (if applicable): BRMS 5.3.0 ER3 How reproducible: always Steps to Reproduce: see description Actual results: jbpm-console does not list processes from packages that were created after accessing the Process Overview for the first time Expected results: jbpm-console should list processes from all packages that have binaries at the time of the query. Additional info:
This happens due to knowledge agent is configured with change set that is populated with all known packages at the time of creation (first time process definitions are retrieved) and it capable of rebuilding knowledge base on changes applied to known resources. And as adding new package in Guvnor will not be known to knowledge agent so it will not be visible in jbpm-console. As far as I know there is no way to configure change set for the agent to consider not existing resources (packages). Alternatively we could try to periodicly check for changes in packages and add them to knowledge agent that is already configured, kidn of delta of new packages.
Refresh of Process Definitions in Console will check if there are new packages available in Guvnor and if so will add them to the agent configuration.
Update status to ON_QA. Please verify them against ER6.
Verified in ER6.