Hide Forgot
Created attachment 577052 [details] error shown in the server log Description of problem: Processes created in the Global Area don't have their name, id and package set. When they are imported into a package, the package is set, the name and id are left blank. The missing process name and id are obviously a problem. This, however, can be fixed - you simply fill in the fields. Worse is, if you import the process into more than one package, the process has only the one package set, obviously, and building the packages throws an error: org.drools.RuntimeDroolsException: invalid package name. Version-Release number of selected component (if applicable): BRMS 5.3.0. ER5 Steps to Reproduce: 1. Create a process in the Global Area. Save it. 2. Import it into package A. 3. Import it into package B. 4. Rebuild all binaries. Actual results: After step 1, the process does not have it's name, id and package set. After step 2 the package is set to A (which is okay at the moment). After step 3, the package is set to B - that is a problem, because the process is both in the package B and in the package A. Step 4 rebuilds all the packages, an error is logged into the server log - see attachement. Additional info: The process imported from the Global Area into packages is one and the same in all the packages - it is not copied into the packages, it is linked. This means that all the changes done to the process in package A are visible from package B and Global Area too. While the Asset package stays at globalArea, the process package, the one the Designer shows and is part of the process source code, changes.
RuleFlow assets physically contain the Package Name. Therefore when copying such an Asset from the Global Shared Area to other packages it is the same physical asset (think of symlinks). Hence the Package Name problem.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Business processes created in the Global Area do not have their name, ID, or package set. When processes created in the Global Area are imported into a package the package is set, however the name and ID are not. The workaround is to set the name and ID value manually.