Bug 1047761
| Summary: | No way to rename a guided rule using the UI | ||
|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Toni Rikkola <trikkola> |
| Component: | Business Central | Assignee: | manstis |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | jvahala |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0.0 | CC: | abhumbe, ajuricic, etirelli, lpetrovi, mbaluch |
| Target Milestone: | ER1 | ||
| Target Release: | 6.0.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-08-06 19:56:59 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
Toni Rikkola
2014-01-02 07:48:05 UTC
I don't see this as a big issue. Most people probably never rename the .rdrl files. It can cause harm or trouble when: #1 User makes a typo in the rule name when making a guided rule. #2 User makes a rule "Test" renames it to "My first test" and then makes a rule "Test". Now there are two rules named "Test" and the project fails to compile. I have implemented a change that ensures the "rule name" reflects the file name for Guided Rules; for both "rename" and "copy" operations (as "copy" was also affected). I have also made a change to ensure the "base rule name" reflects the file name for Guided Rule Templates (for both "rename" and "copy"). Furthermore I've made a change to ensure "table name" reflects the file name for Guided Decision Tables (for both "rename" and "copy"). The user is not provided with an option to only update the file name, or both file name and rule name as both - for the average user - would be regarded as being the same logical identifier. *** Bug 1059766 has been marked as a duplicate of this bug. *** Verified on 6.0.1 ER1. |