Hi,

Unfortunately it is not possible to associate a data-type with a @{key} field at present.

In order to do so we'd need to parse the DRL text to determine the Fact\Field to which the key relates (if indeed any). This is a significant enhancement.

Being able to set a default value for BRL Fragments that contain zero keys is more achievable short-term.

Could you please raise a JIRA at https://issues.jboss.org/browse/GUVNOR.

With kind regards,

Mike

On 16 August 2012 22:27, jasonxzhong <jason.zhong@ellucian.com> wrote:
You are right - use @{keyname} does work! Is there way to attach enumeration
values to the column when it is constructed this way? It seems the guided
decision table is not able to associate any defined enumerations to the
@{keyname}.

Regarding boolean checkbox for BRL Fragments, I understand the flexibility
it provides. I do wish that there is a place to enter a default value
(similar to an simple condition where a boolean value is expected) so I can
set the default to "true", hide the column and still be able to have the BRL
fragment being added to each rules generated from the table.

Thanks,

Jason





--
View this message in context: http://drools.46999.n3.nabble.com/Hiding-a-column-in-web-guided-decision-table-disables-a-condition-or-action-tp4019169p4019218.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users