Bug 1130287
| Summary: | Guided rule editor, can the modify actions be greyed out if the variable doesn't exist | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BRMS Platform 6 | Reporter: | Jim Tyrrell <jtyrrell> | ||||||
| Component: | Business Central | Assignee: | manstis | ||||||
| Status: | CLOSED EOL | QA Contact: | Jiri Locker <jlocker> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 6.0.2 | CC: | kverlaen | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| 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:39:09 UTC | Type: | Enhancement | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 926886 [details]
Smaller list that happens w/o a variable inserted.
This requires a re-design of the screen. The "Update" and "Modify" actions do not prompt the User for a bound LHS fact to update/modify until after the action type has been chosen. The proposed changed requested by Jim requires selection of a bound LHS fact first and then selection of the potential actions that can be applied. TBH, and IMO, this is possibly more counter-intuitive than the current approach. Joe, could you please give a view on how to improve the popup? Thanks. How about replacing the THEN dialog with a two step wizard that offers you a type of action in the first step (insert, logically insert, modfiy, change, call method, etc.) and then, in the second step, lets you choose an argument for the selected action, e.g. a fact type or a variable. I agree that the list of all possible actions becomes too long when there are many fact types or bound variables. |
Created attachment 926885 [details] Showing all the choices that are available Description of problem: It is really hard to remember all the options in the then clause pop up. I really struggled with a few errors, before I got to the correct state. I would really like the modify/change options to be greyed out if the variable was not created. Or should the variable always be inserted when generating the when statement? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: