[jboss-jira] [JBoss JIRA] Commented: (JBRULES-671) Rule modeller costmetic improments

[Michael Neale (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBRULES-671?page=comments#action_12352913 ] 
            
Michael Neale commented on JBRULES-671:
---------------------------------------

(Comments from Burr Sutter, some may no longer be relevant as this was from an old mockup).

1)       My Fact list could get really long therefore the drop-down list to choose a fact in the add condition pop-up dialog might be cumbersome.

2)       It is not clear how I add facts to the overall system.  Facts might also have security aspects as well.

3)       I'm not sure if "package" makes sense to an average end-user.  I would have thought the screen above was under "rules".  

4)       I'm not sure how to save my edits

5)       It would be nice to see the generated .drl and have free-form editing. While I realize this is an end-user tool it seems to me that the person wielding this tool will still need to be very rules savvy to deal with "facts", "constraints", "condition type", "condition templates", etc.  There is a lot of jargon being used here, some of which I don't know.  Like what is a template condition/action?

6)       In the pop-up dialogs (from the green plus sign), the close button should be more clearly labeled and the red X should be in the top right corner. I would offer the user both ways to escape the modal dialog box.

7)       It is unclear to me how you pull a series of If-Then "packages" into a single .drl for deployment.  

8)       Will there be a screen that shows me the "version" associated with a deployed/deployable unit?

9)       How do I know which version is deployed into production?

10)   If you click around the menu too many times it stops working altogether (in FireFox 1.0.7 on Windows). The work around is to restart Firefox.

11)   What will the security model be like? Rule reviewers, rule editors, rule packagers (the deployable unit), rule publishers (pushing the unit to production)?

12)   Will we have the concept of development, qa, staging and then production to allow for testing?  There really needs to be a solution to basic rule editing and running basic tests. Perhaps have some test facts loaded into the repository.

13)   If testing is allowed how does someone run the automated tests?

> Rule modeller costmetic improments
> ----------------------------------
>
>                 Key: JBRULES-671
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-671
>             Project: JBoss Rules
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira