[jboss-jira] [JBoss JIRA] (DROOLS-1825) [Guided Decision Table] Ability to change HIT policy in a decision table anytime

[Toni Rikkola (JIRA)]

    [ https://issues.jboss.org/browse/DROOLS-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487384#comment-13487384 ] 

Toni Rikkola commented on DROOLS-1825:
--------------------------------------

[~manstis] might be right that the Overview is not the best since it is the same for all assets. 

Still I don't really like the idea of this being placed in a location where you have the most common actions are done. Since changing the hit policy completely changes how the table is used. I imagine the most common changes will be from first order to resolved. Giving the user the freedom to change the rule order. So this is really rare.

Extended/limited change and parent rule would be in the same group with hit policy change. Used as often, something that has huge impact on the table visualization or table behavior.

Now even with all these ideas. I am not sure what the best fix is :) Could be some button/menu item that lists these table properties and gives the option to change them. 

> [Guided Decision Table] Ability to change HIT policy in a decision table anytime
> --------------------------------------------------------------------------------
>
>                 Key: DROOLS-1825
>                 URL: https://issues.jboss.org/browse/DROOLS-1825
>             Project: Drools
>          Issue Type: Enhancement
>          Components: Guided Decision Table Editor
>    Affects Versions: 7.1.0.Beta2
>            Reporter: Ivo Bek
>            Assignee: Toni Rikkola
>            Priority: Critical
>              Labels: UX
>         Attachments: DROOLS-1825 (Parent Rule).png
>
>   Original Estimate: 1 week
>  Remaining Estimate: 1 week
>
> Today, it's possible to set 1 of 5 HIT policies when we create a new guided decision table. However, the user might not know which HIT policy he/she should use at this early beginning. Therefore, it should be possible to set the policy to None when we create a new guided decision table and set the HIT policy later after we add columns and rows, fill in some data and see and decide based on the created table how the rules should behave using the HIT policy.
> Thus, it should be possible to change HIT policy in a decision table anytime.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)