Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1146919

Summary: Designer ruleflow-group list does not show all options
Product: [Retired] JBoss BPMS Platform 6 Reporter: Sona Mala <smala>
Component: jBPM DesignerAssignee: manstis
Status: CLOSED EOL QA Contact: Sona Mala <smala>
Severity: high Docs Contact:
Priority: urgent    
Version: 6.1.0CC: kverlaen, manstis
Target Milestone: ER4Keywords: TestBlocker
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:43:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ruleflowgroup - Content of repository
none
ruleflowgroup - All options
none
ruleflowgroup - actual result 1
none
ruleflowgroup - actual result 2
none
ruleflowgroup - actual result 3
none
import - actual result
none
import - options after operation Save none

Description Sona Mala 2014-09-26 11:08:31 UTC
Created attachment 941521 [details]
ruleflowgroup - Content of repository

Description of problem:
When I run a fresh instance of BPMS, the show lists of RuleFlow Groups and Data Objects does not contains all options.


Version-Release number of selected component (if applicable):
6.1.0 DR3 BPMS

How reproducible:
the first time

Steps to Reproduce:
1. Prepare BxMS which has not been started (unzip BxMS on EAP)
2. Run server
3. Clone own repository where are rules with ruleflow-group and some data objects (Facts)
4. Open designer with business task (or create it)
5. Show list of options for:
   a) ruleflow-group - property of business task
   b) data object - 'import' property of process

Actual results:
See attached screenshots. When I open the show list the first time, there is only few options.

a) see screenshot "ruleflowgroup - ..."
Available rules are shown at "ruleflowgroup - Content of repository"

b) see screenshot "import - ..."


Expected results:
I am not sure if this is a problem of jBPM Designer or file system (indexing, etc.).
However, if I display the show list I will expect the current state of repository. I do not want to perform another action like building of project, openning rule editors, etc. for updating of list.
If jBPM Designer cannot guarantee that show list is actual then the editor should contain a button "Refresh" which will perform particular actions.


Additional info:
TestBlocker ... I am not able to run successfully this test on the fresh instance of BxMS. I have to run some test before, this has a negative effect on the test development and debugging of problems.

Comment 1 Sona Mala 2014-09-26 11:19:27 UTC
Created attachment 941522 [details]
ruleflowgroup - All options

Comment 2 Sona Mala 2014-09-26 11:20:43 UTC
Created attachment 941523 [details]
ruleflowgroup - actual result 1

Comment 3 Sona Mala 2014-09-26 11:21:07 UTC
Created attachment 941524 [details]
ruleflowgroup - actual result 2

Comment 4 Sona Mala 2014-09-26 11:21:50 UTC
Created attachment 941525 [details]
ruleflowgroup - actual result 3

Comment 5 Sona Mala 2014-09-26 11:23:00 UTC
Created attachment 941526 [details]
import - actual result

Comment 6 Sona Mala 2014-09-26 11:23:39 UTC
Created attachment 941527 [details]
import - options after operation Save

Comment 8 Kris Verlaenen 2014-10-31 00:06:27 UTC
Michael, should building of the asset oracle already be automatically performed after importing a new repo?

Comment 9 manstis 2014-11-03 09:55:15 UTC
(In reply to Kris Verlaenen from comment #8)
> Michael, should building of the asset oracle already be automatically
> performed after importing a new repo?

A new repository (cloned, or new) is indexed fully when created.

Comment 10 Jeremy Lindop 2014-11-20 14:35:07 UTC
Michael, this looks like a side-effect of the fact that indexing the repository takes some time. Can you suggest any way of dealing with this, or provide a fix?

If you import Sona's repository (the URL is in Comment 7) and edit the BP (also referenced in Comment 7), when you go to the "Ruleflow Group" property of 'businessTask', the first time it shows maybe 2 groups, then if you leave it a minute, it shows maybe 3, then after a few minutes, it shows all 6. I assume the same thing happens for data objects (as in the BZ description).

I reproduced this by making the http POST requests for the ruleflowgroups directly with the Chrome 'postman' extension:

1. Create fresh bpms installation
2. Login to the web console in Chrome
3. Import Sona's repository
4. In another tab in Chrome, use the 'postman' extension, run http POST request
URL:
http://localhost:8080/kie-eap-distributions-bpms-webapp-6.3.0-SNAPSHOT-kie-wb/calledelement

Parameters:
profile:jbpm
ppackage:org.jbpm
pid:designer.ruleFlowGroup
action:showruleflowgroups


The first response I got was empty. After 30 secs or so I got json containing 2 ruleflowgroups, then 3, etc. It took a few minutes to get the complete list of 6 ruleflowgroups

Comment 11 manstis 2014-11-21 14:57:20 UTC
Jeremy's analysis is correct.

I have made a few changes; that helps the user understand:-

1) When cloning a Repository, the "success" popup now states "xx"
2) Messages are written to the Message Console (in the Authoring Perspective) stating that indexing has started and when it has completed.

We could take this a stage further by restricting authoring in a Repository that is being indexed but that may be too restrictive. Please feed-back.

Comment 12 manstis 2014-11-21 14:58:52 UTC
Sorry I forgot to paste the message into "xx" above. The clone successful popup now includes "The Repository will be indexed. Some workbench features may be unavailable until indexing has completed."

Comment 18 Sona Mala 2015-01-23 12:22:00 UTC
I confirm that ER4 contains INFO message in server.log.

I will retest it later

Comment 19 Sona Mala 2015-02-02 12:00:39 UTC
My problems disappeared when I am waiting for the end of indexing in server.log.

This issue was verified on 6.1.0 ER4.