Bug 724331 (BRMS-276)
| Summary: | declarative model doesn't allow to use a fact as a field type when that fact was created later | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Jaroslaw Kijanowski <kijanowski> |
| Component: | BRM (Guvnor) | Assignee: | manstis |
| Status: | CLOSED UPSTREAM | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.0.1, 5.0.2, 5.1.0.ER1, 5.1.0.ER2 | ||
| Target Milestone: | --- | ||
| Target Release: | BRMS 5.3.0.GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/BRMS-276 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
When a new declarative model was created there were limitations on which facts could be added as fields to other facts. The limitation was based on the order of creation of the facts. Upgrading the components from BRMS 5.2 resolved the issue.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-02-10 03:13:46 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: | |||
|
Description
Jaroslaw Kijanowski
2010-03-23 16:19:06 UTC
Triaged by BRMS PM team for 5.2.
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:
When a new declarative model has been created there are limitations on which facts can be added as fields to other facts. The limitation is based on the order of creation for the facts. This will be resolved in a future release.
Oops. This bug was missing the jboss-brms-5.2.0 flag, so it was missed completely. Proposing for 5.3.0.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-When a new declarative model has been created there are limitations on which facts can be added as fields to other facts. The limitation is based on the order of creation for the facts. This will be resolved in a future release.+When a new declarative model has been created there are limitations on which facts can be added as fields to other facts. The limitation is based on the order of creation for the facts.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-When a new declarative model has been created there are limitations on which facts can be added as fields to other facts. The limitation is based on the order of creation for the facts.+When a new declarative model has been created there are limitations on which facts can be added as fields to other facts. The limitation is based on the order of creation of the facts.
The attached JIRA says this should be fixed already. Fixed. And that allowed me to find bug 755129.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-When a new declarative model has been created there are limitations on which facts can be added as fields to other facts. The limitation is based on the order of creation of the facts.+When a new declarative model was created there were limitations on which facts could be added as fields to other facts. The limitation was based on the order of creation of the facts. Upgrading the components from BRMS 5.2 resolved the issue.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |