October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2071) Guided Score Card "Found duplicate declaration for type org.drools.pmml.pmml_4_1"

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2071?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2127 to DROOLS-2071: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2071 (was: GUVNOR-2127) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Score Card Editor (was: Guided Score Card) Affects Version/s: 6.1.0.Final (was: drools_6.1.0.Final) > Guided Score Card "Found duplicate declaration for type org.drools.pmml.pmml_4_1" > --------------------------------------------------------------------------------- > > Key: DROOLS-2071 > URL: https://issues.jboss.org/browse/DROOLS-2071 > Project: Drools > Issue Type: Bug > Components: Guided Score Card Editor > Affects Versions: 6.1.0.Final > Reporter: Kinga Borkowska > Attachments: gsc.txt > > > When trying to Build & Deploy project with Guided Score Card file I get following errors: > > Found duplicate declaration for type org.drools.pmml.pmml_4_1.PMML4AbstractField > Found duplicate declaration for type org.drools.pmml.pmml_4_1.ScoreCard > Found duplicate declaration for type org.drools.pmml.pmml_4_1.ScoreRank > Found duplicate declaration for type org.drools.pmml.pmml_4_1.ScoreCardData > Found duplicate declaration for type org.drools.pmml.pmml_4_1.Score > Found duplicate declaration for type org.drools.pmml.pmml_4_1.InitialScore > Found duplicate declaration for type org.drools.pmml.pmml_4_1.BaselineScore -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2070) 'Use Reason Codes' in Guided Scorecard cannot be set to 'true'

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2070?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2639 to DROOLS-2070: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2070 (was: GUVNOR-2639) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Guided Score Card Editor (was: Guided Score Card) Affects Version/s: 6.4.0.Final (was: drools_6.4.0.Final) > 'Use Reason Codes' in Guided Scorecard cannot be set to 'true' > -------------------------------------------------------------- > > Key: DROOLS-2070 > URL: https://issues.jboss.org/browse/DROOLS-2070 > Project: Drools > Issue Type: Bug > Components: Guided Score Card Editor > Affects Versions: 6.4.0.Final > Reporter: Tugba Kulahcioglu > Assignee: Guilherme Carreiro > Attachments: ReasonCode.png > > > Guided Scorecard interface do not allow the "use reason codes" field be set to true -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2064) File Uploader: Upload button should read "Upload and check in" and allow the user to write a checkin comment

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2064?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1652 to DROOLS-2064: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2064 (was: GUVNOR-1652) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: XLS Decision Table Editor (was: XLS Decision Tables) > File Uploader: Upload button should read "Upload and check in" and allow the user to write a checkin comment > ------------------------------------------------------------------------------------------------------------ > > Key: DROOLS-2064 > URL: https://issues.jboss.org/browse/DROOLS-2064 > Project: Drools > Issue Type: Enhancement > Components: XLS Decision Table Editor > Reporter: Toni Rikkola > Assignee: Michael Anstis > Priority: Minor > > Because that is what it does. There is just no way to comment the upload. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2065) XLS Decision table: Add support for a boolean column indicating that the row (rule) should be negated

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2065?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1237 to DROOLS-2065: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2065 (was: GUVNOR-1237) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: XLS Decision Table Editor (was: XLS Decision Tables) > XLS Decision table: Add support for a boolean column indicating that the row (rule) should be negated > ----------------------------------------------------------------------------------------------------- > > Key: DROOLS-2065 > URL: https://issues.jboss.org/browse/DROOLS-2065 > Project: Drools > Issue Type: Feature Request > Components: XLS Decision Table Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Minor > > Add a boolean column to the XLS decision table parser to allow rules to be negated:- > When "turned on" for a rule:- > when > not ( > pattern1.. > pattern2.. > ) > then > ... > end > When "turned off" for a rule:- > when > pattern1.. > pattern2.. > then > ... > end -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2066) Missing Revision inforrmations of uploaded Decision Tables

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2066?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1646 to DROOLS-2066: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2066 (was: GUVNOR-1646) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: XLS Decision Table Editor (was: XLS Decision Tables) Affects Version/s: 5.5.0.Final (was: drools-5.3.0.Beta1) > Missing Revision inforrmations of uploaded Decision Tables > ----------------------------------------------------------- > > Key: DROOLS-2066 > URL: https://issues.jboss.org/browse/DROOLS-2066 > Project: Drools > Issue Type: Feature Request > Components: XLS Decision Table Editor > Affects Versions: 5.5.0.Final > Environment: Mac OS X 5, JVM 6, JBoss BRMS 5.1 > Reporter: Serge Emmanuel Pagop > Assignee: Michael Anstis > Attachments: BRMS_Decission_Table_Feature_Request.odp > > > When you upload a decision table in the BRM you save it and write a description of the revision. But if you update the Decision table and upload it again and plan to save it you can not figure out on which version of DTs you're working. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2067) XLS Decision table: Add support for negating a Fact pattern i.e. "not Person(...)"

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2067?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1284 to DROOLS-2067: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2067 (was: GUVNOR-1284) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: XLS Decision Table Editor (was: XLS Decision Tables) Affects Version/s: 5.5.0.Final (was: drools-5.2.0.M1) > XLS Decision table: Add support for negating a Fact pattern i.e. "not Person(...)" > ---------------------------------------------------------------------------------- > > Key: DROOLS-2067 > URL: https://issues.jboss.org/browse/DROOLS-2067 > Project: Drools > Issue Type: Feature Request > Components: XLS Decision Table Editor > Affects Versions: 5.5.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Minor > > Add support in XLS Decision Tables for the negation of patterns (as currently available in Guvnor's guided Decision Table),i.e. not Person(...) in addition to existing Person(...) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2068) XLS Decision table: Add support for "otherwise" values in Condition Column cells

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2068?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-1278 to DROOLS-2068: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2068 (was: GUVNOR-1278) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: XLS Decision Table Editor (was: XLS Decision Tables) > XLS Decision table: Add support for "otherwise" values in Condition Column cells > -------------------------------------------------------------------------------- > > Key: DROOLS-2068 > URL: https://issues.jboss.org/browse/DROOLS-2068 > Project: Drools > Issue Type: Feature Request > Components: XLS Decision Table Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Minor > > Add support for "otherwise" cell values in Condition Columns. E.G. "not in (x, y, z, ...)" where x, y and z are explicit literal values in the column. "not in" supports the equality operator, ideally other operators should also be supported. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2069) Import: Extend import rule from spreadsheet to support Openoffice in addition to Excel

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2069?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-286 to DROOLS-2069: ----------------------------------------------- Project: Drools (was: Guvnor) Key: DROOLS-2069 (was: GUVNOR-286) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: XLS Decision Table Editor (was: XLS Decision Tables) Affects Version/s: 5.5.0.Final (was: drools-5.0.0.CR1) > Import: Extend import rule from spreadsheet to support Openoffice in addition to Excel > -------------------------------------------------------------------------------------- > > Key: DROOLS-2069 > URL: https://issues.jboss.org/browse/DROOLS-2069 > Project: Drools > Issue Type: Feature Request > Components: XLS Decision Table Editor > Affects Versions: 5.5.0.Final > Environment: CR1 build > Reporter: Len DiMaggio > > Importing from Excel is supported - not from Openoffice spreadsheet files: > 2009-05-01 22:01:28,615 INFO [STDOUT] ERROR 01-05 22:01:28,614 (ServiceImplementation.java:buildAsset:1541) org.drools.template.parser.DecisionTableParseException: An error occured opening the workbook. It is possible that the encoding of the document did not match the encoding of the reader. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2062) XLS dtables: JS alert only shown when re-uploading the same file

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2062?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2445 to DROOLS-2062: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2062 (was: GUVNOR-2445) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: XLS Decision Table Editor (was: XLS Decision Tables) Affects Version/s: 6.4.0.Beta2 (was: drools_6.4.0.Beta2) > XLS dtables: JS alert only shown when re-uploading the same file > ---------------------------------------------------------------- > > Key: DROOLS-2062 > URL: https://issues.jboss.org/browse/DROOLS-2062 > Project: Drools > Issue Type: Bug > Components: XLS Decision Table Editor > Affects Versions: 6.4.0.Beta2 > Reporter: Zuzka Krejčová > Labels: reported-by-qe > > When user uploads a new XLS dtable, an alert is presented with the text "Uploaded successfully". The same alert should be shown when uploading a new version via the XLS dtable editor. > If user uploads the same file, the alert is shown. > If user uploads a different file, it is not shown. > In both cases, user gets the "Item successfully created" fly-over notification. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2063) request to improve error message when failed to upload spreadsheet

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2063?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2474 to DROOLS-2063: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-2063 (was: GUVNOR-2474) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: XLS Decision Table Editor (was: XLS Decision Tables) Affects Version/s: 6.3.0.Final (was: drools_6.3.0.Final) > request to improve error message when failed to upload spreadsheet > ------------------------------------------------------------------ > > Key: DROOLS-2063 > URL: https://issues.jboss.org/browse/DROOLS-2063 > Project: Drools > Issue Type: Enhancement > Components: XLS Decision Table Editor > Affects Versions: 6.3.0.Final > Environment: BRMS 6.2.x > Reporter: Hiroko Miura > Priority: Minor > Attachments: errorWhenUploadingSpreadsheet.png > > > 1. Proposed title of this feature request > Request to improve error message when uploading spreadsheet as multi-bytes name > 2. Who is the customer behind the request? > Account: name and acct # > Fujitsu Systems East Limited(acct#5441134) > TAM customer: no > SRM customer: no > Strategic: no > 3. What is the nature and description of the request? > This is relevant to BZ#1320011. > In this issue, URL encoded Japanese asset name is shown in this error message, > which it is not user friendly and a bit hard to recognize problematic asset immediately. > Customer requests us to show human-readable asset name in such error message instead of URL encoded one. > 4. Why does the customer need this? (List the business requirements here) > As stated above, error message is not user friendly and bit hard to recognize problematic asset immediately. > 5. How would the customer like to achieve this? (List the functional requirements here) > Please show human-readable asset name. > 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. > check improved error message > 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? > No > 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? > No > 9. Is the sales team involved in this request and do they have any additional input? > No > 10. List any affected packages or components. > N/A > 11. Would the customer be able to assist in testing this functionality if implemented? > Yes -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2017