Oberdan Luiz May
My feedback
8 results found
-
1 vote
Oberdan Luiz May shared this idea ·
-
28 votes
Hello everyone,
I’d like to share our plans to introduce support for XSL (Extensible Stylesheet Language) normalization rules. This new feature is designed for handling complex normalization tasks. It offers the flexibility of a full programming language, enabling advanced data manipulation. This will complement our existing normalization rules based on DROOLS, maintaining all of its current capabilities.
Would the addition of this new type of normalization rule meet the requirements outlined in this idea?
Oberdan Luiz May supported this idea ·
-
8 votes
Oberdan Luiz May shared this idea ·
-
56 votes
Oberdan Luiz May supported this idea ·
-
31 votes
An error occurred while saving the comment Oberdan Luiz May shared this idea ·
-
131 votes
An error occurred while saving the comment Oberdan Luiz May commented
Yeah, I miss this too... It should be possible to use receivers/receiver/preferred_language and then print the table headers accordingly, but there will be a series of very long ifs.
Oberdan Luiz May supported this idea ·
-
173 votes
Oberdan Luiz May supported this idea ·
-
54 votes
Hello everyone,
I’d like to share our plans to introduce support for XSL (Extensible Stylesheet Language) normalization rules. This new feature is designed for handling complex normalization tasks. It offers the flexibility of a full programming language, enabling advanced data manipulation. This will complement our existing normalization rules based on DROOLS, maintaining all of its current capabilities.
Would the addition of this new type of normalization rule meet the requirements outlined in this idea?
An error occurred while saving the comment Oberdan Luiz May commented
I agree that we should have a script language. Drools is way too limited...
Oberdan Luiz May supported this idea ·
Hello Moshe,
Yes, this is exacly what we need.
Regards,
Oberdan