DMN CUSTOM - AUTOCOMPLETE how can we additionally add autocomplete dropdown to input fields or can we add some values in your autocomplete feature in LITERAL EXPRESSION FIELD.

[Jainbhavik332]

hello , how can we support some additional autocomplete dropdown values for LITERAL EXPRESSION and for input fields is there any possible way @yesamer @tiagobento @ederign it will be very helpfull and dynamic .

[yesamer]

Hi @Jainbhavik332, thank you for your suggestion.

We already have a ticket to track that feature, do you mind if I close this by asking you to follow https://github.com/kiegroup/kie-issues/issues/206 ?

Thank you,

Yeser

[Jainbhavik332]

Hello , @yesamer can we customize this thing on our own is there any way ,

And one more thing for dmn input data can we have our own autocomplete feature for passing only few variables which are required . @tiagobento @ederign

Thankyou , Bhavik jain

[tiagobento]

@Jainbhavik332 You mean providing an arbitrary list of "values" that will appear on the autocomplete suggestions? I'm interested in hearing what's your use-case. Please share more details so we can understand what you're trying to achieve.

[Jainbhavik332]

The usecase is we want to provide custom list of parameters from external source for autocomplete dropdown ,Where user can decide its parameter with that data Which has limited set. @tiagobento @yesamer @ederign When I was refering the code I came to file FeelConfig.ts which as limited set of fields and same is only happening in literal expression only . I tried adding custom values of my own in the same file for the use only in kie standalone editor but it is refering the ts file from github. I was wondering how the same will be reflect in my project for input field,decision components. I will like to contribute the same functionality in the project with guidance from community . please refer the screenshot for details .

[firoozej]

@tiagobento Another use case for this is to suggest a list of Sub Data Types on a literal expression with a Custom Data Type. The literal expression can subsequently be used in a decision table header but not as a whole but by its values For example Literal_Expression_1 has a data type which contains {code: string, name: string} On the decision table header we have two columns for Literal_Expression_1.code and Literal_Expression_1.name It would have been good if there was a mechanism to have that suggestion or a way to customize the suggestion list and add those on the consuming side.

[tiagobento]

Ok, I think I got it. It looks like what you want is to have a string Data Type with an Enum constraint. You can already limit what goes where, but right now the Editor doesn't limit the inputs based on the Data Type constraints. That's a missing feature we have, and we hope to address it as part of the new DMN Editor. See https://github.com/apache/incubator-kie-issues/issues/625

[tiagobento]

@Jainbhavik332 If you're using KIE Sandbox, you can see that this already happens for the DMN Runner form and table.

If I understood it correctly, instead of directly providing a way for adding "autocomplete values", maybe we should add an easy way for creating Data Types programmatically?