optum / kie-examples Goto Github PK

In this case, we made a rule flow expression that was set to "drools" but had a FEEL expression in it. This caused a build error, but didn't say which Rule Flow it was in which makes it really hard to debug.

In a long FEEL expression, the text gets cut off if the window isn't wide enough

It is really common for rule authors to copy and paste cells when creating test scenarios. We need to evaluate and make sure this works with all cell types. It looked like it was not working when the cell type was a list, but it could be in other scenarios as well.

I haven't tried this in the newest versions so it is possible something has changed, but I remember having trouble to input objects that had a lot of nested data as input to a DMN. It could only be 1 or 2 levels deep. Let's explore what is possible here to see if that is something that can be added.

When calling a DMN from Java code, we can pass in a Date or DateTime object and it will convert to a DMN Date type to be used in the decision making.

It would be really nice if properly formatted Strings would also be supported to convert to a Date type. With the current implementation, we haven't figured out how to call a DMN deployed to KIE Server with a Date type as input. If you pass a string, it errors, and we can't send the Date type of object in the JSON body in the request.

We will need to explore this behavior more, and create a well documented example of the current behavior and what we can't do with it in regards to dates.

In a context, when creating a decision table, it should automatically populate input and output clauses. This behavior is different from how it works when the decision table is standalone.

This field could be auto-populated, saving a lot of headache for rule authors. Let's document this issue with KIE Group and work on a fix

Let's open an issue and add this feature to Business Central.

When copying a DMN, the file name changes, but often the model name stays the same. Ideally, the model name should update as well or the project will fail to compile because of duplicate model names existing in the project.

In a BPMN, when adding a Business Rule Task for a DMN, it would be really great if there was an auto-populated drop down to select a DMN Model name and Decision name from DMNs in the project. It then would automatically fill out the namespace field. This makes it easy because currently we have to copy these values from a DMN.

We need to document and describe this feature request, and hopefully contribute a fix for it to https://github.com/kiegroup/drools-wb

Creating this issue to track progress on Example 1

In a context, when using a structure in the data output object, the columns behave differently than when not in a context. The columns aren't grouped under the structure, and they don't auto-populate the field names.

When we edit placeholder text, such as "annotation-1" in a DMN, the cursor starts at the end and there are extra keystrokes to remove the placeholder text.

Currently it only supports entering the FEEL expressions directly