[JBoss JIRA] (DROOLS-5089) enumeration reference iso value list
by Toni Rikkola (Jira)
[ https://issues.redhat.com/browse/DROOLS-5089?page=com.atlassian.jira.plug... ]
Toni Rikkola updated DROOLS-5089:
---------------------------------
Component/s: Enumerations Editor
> enumeration reference iso value list
> ------------------------------------
>
> Key: DROOLS-5089
> URL: https://issues.redhat.com/browse/DROOLS-5089
> Project: Drools
> Issue Type: Feature Request
> Components: Enumerations Editor
> Reporter: Werner Van Herrewegen
> Assignee: Toni Rikkola
> Priority: Minor
>
> In business central,
> when creating an enumeration to use in my rules,
> I find myself a lot copying the allowed value list to multiple fact-field-combinations
> Can I refer for the value list for a fact-field-combination-enumeration to another existing fact-field-combination-enumeration.
> That way I only need to maintain 1 value list
> not an option:
> use an enum from the java code
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (DROOLS-5089) enumeration reference iso value list
by Toni Rikkola (Jira)
[ https://issues.redhat.com/browse/DROOLS-5089?page=com.atlassian.jira.plug... ]
Toni Rikkola updated DROOLS-5089:
---------------------------------
Labels: drools-tools (was: )
> enumeration reference iso value list
> ------------------------------------
>
> Key: DROOLS-5089
> URL: https://issues.redhat.com/browse/DROOLS-5089
> Project: Drools
> Issue Type: Feature Request
> Components: Enumerations Editor
> Reporter: Werner Van Herrewegen
> Assignee: Toni Rikkola
> Priority: Minor
> Labels: drools-tools
>
> In business central,
> when creating an enumeration to use in my rules,
> I find myself a lot copying the allowed value list to multiple fact-field-combinations
> Can I refer for the value list for a fact-field-combination-enumeration to another existing fact-field-combination-enumeration.
> That way I only need to maintain 1 value list
> not an option:
> use an enum from the java code
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (DROOLS-5093) mass initial fill of guided decision table
by Toni Rikkola (Jira)
[ https://issues.redhat.com/browse/DROOLS-5093?page=com.atlassian.jira.plug... ]
Toni Rikkola updated DROOLS-5093:
---------------------------------
Component/s: Guided Decision Table Editor
> mass initial fill of guided decision table
> ------------------------------------------
>
> Key: DROOLS-5093
> URL: https://issues.redhat.com/browse/DROOLS-5093
> Project: Drools
> Issue Type: Feature Request
> Components: Guided Decision Table Editor
> Reporter: Werner Van Herrewegen
> Assignee: Toni Rikkola
> Priority: Major
>
> as a rule creator I want to have an option to download an excel grid based on the columns in a guided decision table and have the business fill this using excel and afterwards upload the filled excel as rows in the guided decision table.
> reasoning:
> for large mapping tables it would be nice to create the structure of the decision table in business central
> then get this structure into excel tables
> then give the business the excel
> after the business has filled in the values
> and after validation of the values by IT :-)
> we import these values as rows in the table.
> this is common practice for the initial upload of data in a new system.
> all changes afterwards will happen via business central webapp
> I know this bypasses data entry validation and should be used with care,
> though if implemented decently, mass upload data validation can be still be enforced during import.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (DROOLS-5093) mass initial fill of guided decision table
by Toni Rikkola (Jira)
[ https://issues.redhat.com/browse/DROOLS-5093?page=com.atlassian.jira.plug... ]
Toni Rikkola updated DROOLS-5093:
---------------------------------
Labels: drools-tools (was: )
> mass initial fill of guided decision table
> ------------------------------------------
>
> Key: DROOLS-5093
> URL: https://issues.redhat.com/browse/DROOLS-5093
> Project: Drools
> Issue Type: Feature Request
> Components: Guided Decision Table Editor
> Reporter: Werner Van Herrewegen
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> as a rule creator I want to have an option to download an excel grid based on the columns in a guided decision table and have the business fill this using excel and afterwards upload the filled excel as rows in the guided decision table.
> reasoning:
> for large mapping tables it would be nice to create the structure of the decision table in business central
> then get this structure into excel tables
> then give the business the excel
> after the business has filled in the values
> and after validation of the values by IT :-)
> we import these values as rows in the table.
> this is common practice for the initial upload of data in a new system.
> all changes afterwards will happen via business central webapp
> I know this bypasses data entry validation and should be used with care,
> though if implemented decently, mass upload data validation can be still be enforced during import.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (WFCORE-944) truststore path is ignored if provider is not JKS
by Ricardo Martin Camarero (Jira)
[ https://issues.redhat.com/browse/WFCORE-944?page=com.atlassian.jira.plugi... ]
Ricardo Martin Camarero updated WFCORE-944:
-------------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4242
> truststore path is ignored if provider is not JKS
> -------------------------------------------------
>
> Key: WFCORE-944
> URL: https://issues.redhat.com/browse/WFCORE-944
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Arto Huusko
> Assignee: Ricardo Martin Camarero
> Priority: Major
>
> truststore configuration ignores the path and relative-to parameters if the truststore provider is anything else than JKS.
> This works as documented, but it is not correct. There can be and are truststore implementations that need to load parameters or whatever data from a file, and the current implementation prevents these truststore providers from working.
> We have a custom truststore that is loaded from database, and database access parameters are read from a properties file. When trying to use this with Wildfly 9, the keystore engineLoad parameter is passed in as null, even though path and relative-to are configured.
> Even standard java supports PKCS12 truststores, where the same problem would occur.
> So I would suggest that
> - if provider is JKS, path is mandatory
> - if provider is not JKS, but path is specified, it is passed to the provider
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months