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

[Michael Anstis (JIRA)]

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

Michael Anstis commented on DROOLS-1825:
----------------------------------------

Personally moving it to "Overview" should be avoided.. mainly because the "Overview" widget is used by ALL editors and customising it for GDT would be a PITA. It's also arguable that "Hit Policy" is something really specific and not part of the general "Overview" content. I think having the "Hit Policy" selector at the same place as the "Parent rule" selector (I'll attach a screen shot in the next comment.. just need to find it!). In the future there are other configurations specific to decision tables that would probably need including in the same place: Extended Entry/Limited Entry and orientation (rule as row/rule as column). 

IIRC there is a JIRA somewhere to change the way columns are managed (moving the "Add" and "Edit" buttons to a new tab for "Columns"). It's possible this new tab could be re-purposed as "Configuration" that lists columns, hit policy, parent rule etc and provides the means to manipulate 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
>   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)