[ https://issues.jboss.org/browse/JBRULES-2866?page=com.atlassian.jira.plug... ] Tihomir Surdilovic reassigned JBRULES-2866: ------------------------------------------- Assignee: Tihomir Surdilovic (was: Mark Proctor) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-2866?page=com.atlassian.jira.plug... ] Jason Mihalick commented on JBRULES-2866: ----------------------------------------- I definitely want to be able to parameterize the metadata value per row in the spreadsheet. I am using metadata to assign an identifier of my choice to each rule and then outputting that at runtime when I generate messages. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-2866?page=com.atlassian.jira.plug... ] Jason Mihalick commented on JBRULES-2866: ----------------------------------------- Did this fix make it into 5.2? Thanks. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-2866?page=com.atlassian.jira.plug... ] Mark Proctor updated JBRULES-2866: ---------------------------------- Fix Version/s: 5.2.1.Final (was: FUTURE) Forum Reference: http://lists.jboss.org/pipermail/rules-users/2011-January/018013.html (was: http://lists.jboss.org/pipermail/rules-users/2011-January/018013.html) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-2866?page=com.atlassian.jira.plug... ] Mark Proctor resolved JBRULES-2866. ----------------------------------- Resolution: Done -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBRULES-2866?page=com.atlassian.jira.plug... ] Jason Mihalick edited comment on JBRULES-2866 at 4/17/12 12:25 PM: ------------------------------------------------------------------- Thanks, I have reviewed the documentation and I've been able to get the metadata to work in my decision table. But, it took a little trial and error for me to figure out how to use multiple @metadata_key( metadata_value ) pairs. I first tried comma separating, like this: {code} id( $1 ), type( $2 ) {code} but only the first metadata_key gets picked up and the resulting compiled rule has this: {code} @id( my_first_metadata_value ), type( my_second_metadata_value) {code} Notice the absence of the '@' on the second metadata_key. I then tried this: {code} id( $1 ), @type( $2 ) {code} and I got this output in the compiled decision table: {code} @id( my_first_metadata_value ), @type( my_second_metadata_value) {code} Close, but not quite there. I then eliminated the comma: {code} id( $1 ) @type( $2 ) {code} and I got the output below which successfully compiles: {code} @id( my_first_metadata_value ) @type( my_second_metadata_value) {code} I also see that you can have multiple *METADATA* columns, so you could also have one metadata_key in each column. was (Author: jrmihalick): Thanks, I have reviewed the documentation and I've been able to get the metadata to work in my decision table. But, it took a little trial and error for me to figure out how to use multiple @metadata_key( metadata_value ) pairs. I first tried comma separating, like this: {code} id( $1 ), type( $2 ) {code} but only the first metadata_key gets picked up and the resulting compiled rule has this: {code} @id( my_first_metadata_value ), type( my_second_metadata_value) {code} Notice the absence of the '@' on the second metadata_key. I then tried this: {code} id( $1 ), @type( $2 ) {code} and I got this output in the compiled decision table: {code} @id( my_first_metadata_value ), @type( my_second_metadata_value) {code} Close, but not quite there. I then eliminated the comma: {code} id( $1 ) @type( $2 ) {code} and I got the output below which successfully compiles: {code} @id( my_first_metadata_value ) @type( my_second_metadata_value) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira