| Summary: | Relog needed after promoting model to Global Area or importing it from G.A. | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Zuzana Krejčová <zkrejcov> |
| Component: | User Interface | Assignee: | Mark Proctor <mproctor> |
| Status: | VERIFIED --- | QA Contact: | Lukáš Petrovický <lpetrovi> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | BRMS 5.2.0-ER1 | CC: | atangrin, lpetrovi, rzhang |
| Target Milestone: | --- | ||
| Target Release: | BRMS 5.2.0.GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Zuzana Krejčová
2011-08-11 14:11:53 UTC
Similar issue with archiving-deleting a model. Unless you relog, you can still use it. Tried again and changed the step slightly. The problem disappears, when you do this: - have a rule in a package and model in global area 1. Import the model into the package 2. Open the rule and edit as you please - facts are visible. BUT the problem stays, when you do this: - have a rule in a package and model in global area 1. Browse the package Business Rules Assets and open the rule. (Seeing the desired fact from the model in G.A isn't present:) 2. Import the model into the package. 3. Switch back to the rule. Nothing changes. Even after closing the rule and opening it again, refreshing the tab with rules or closing and opening it again and then reopening the rule. Here, relog helps. Fixed on 5.2.x. You still need to close and reopen the asset though. There is a more complete fix on master (drools 5.3.0.beta1), which does not require closing and reopening the asset. However the fix can not be applied to the 5.2.x branch because the EventBus mechanism is not in place on 5.2.x. Assigning to the proper Quality Engineer |