May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4084) Export to Excel for decision tables 7.5

by Jozef Marko (Jira)

Jozef Marko created DROOLS-4084: ----------------------------------- Summary: Export to Excel for decision tables 7.5 Key: DROOLS-4084 URL: https://issues.jboss.org/browse/DROOLS-4084 Project: Drools Issue Type: Epic Components: Guided Decision Table Editor Affects Versions: 7.23.0.Final Reporter: Jozef Marko Assignee: Michael Anstis h1. Requirement - As a user of the feature I want to convert guided decision table by single click to xls (Excel) format. - The converted table should have the same format as is supported for importing into business central. - The converted table should visually differentiate column and row types (constraint vs. action, metadata vs. data) - The conversion should support Simple GDT column - The conversion should support Brl GDT column - The conversion should support Attribute and Metadata columns - The converted table can be opened on Windows and Linux - The converted table split lines - The converted table support multibyte characters - The conversion of GDT graph is possible - User is prompted to save changes before conversion - Converted table is not stored in kie project, just downloaded via browser h1. UX design - Placement of the conversion button - Text of the conversion button - Dialog for case we support save changes before conversion h1. Documentation - Replace picture of GDT editor where they become obsolete - Comprehensive doc is probably not needed h1. Acceptance test - Convert table that -- Has more that 100 lines -- Has one Metadata column -- Has one Attribute column -- Has three constraint columns( two over same fact ) -- Has three action columns( two over same fact ) -- Has not all cells filled in -- Operates over String, Number, Boolean fields -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1836) Guided Decision Tables should use XLS as the save file format

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1836?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-1836: -------------------------------- Labels: drools-tools (was: ) > Guided Decision Tables should use XLS as the save file format > ------------------------------------------------------------- > > Key: DROOLS-1836 > URL: https://issues.jboss.org/browse/DROOLS-1836 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > We can already export the Guided Decision Tables to XLS, this Jira will first determinate what is needed for importing XLS to the current Guided dtable model. > h2. Visual differences > * XLS colored cells, the colors usually have a meaning > * XLS Font sizes, types, text color and bold/italic/overlined > * XLS Cell allows the user to set text aligment > * XLS lets the user to change cell size > h2. Differences in functional specification > * The Drools XLS format allows the user to add Guided rules to more than one Excel tab, each tab can have a different kind of table > * GDST requires each pattern to have a variable name, XLS does not > * GDST requires each column to have a title, XLS does not > * GDST stores the value type > * GDST does not support the XLS forall template > * GDST has "inner enums" that can be set for columns > * GDST file contains authoring history > * XLS does not support generic DRL fracments > * XLS does not support otherwise > * XLS does not support Workitems > * XLS does not support any Guvnor Enums or DSL > * XLS allows more than one $variable to be used for a single column. For example $param1, $param2 for method($param1,$param2) > * XLS allows the DRL functions to be declared inside the XLS file > * XLS can contain XLS formulas > h2. Some random thoughts > * If we go full XLS, then we lose the information about the value type that is set into each cell, but then again, maybe this is not that big of a loss since the information can be regained from the DMO. > * To get the XLS formulas and styles to work we need to write our own GWT Excel > * GDST file contains authoring history, in XLS form this would be openly editable. Then again, you can text edit the file anyway you want to if you git checkout the GDST XML file > * A XLS file can also be a rule template or anything else than a dtable. File ending like dtable.xls or gdst.xls would of course fix this. > * ^ The Guided rule templates might have to move to XLS too. Just to keep things simple, but the XLS templates are made out of two files DRL+XLS > * There is a need for some kind of migration tool or we keep allow the user to open .gdst and save .xml. This means we need to keep the codes for the old model in our workbench codebase forever and ever. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-712) Ability to create 2nd bookinfo via operator

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-712?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan reassigned SWSQE-712: ------------------------------------ Assignee: Hayk Hovsepyan > Ability to create 2nd bookinfo via operator > ------------------------------------------- > > Key: SWSQE-712 > URL: https://issues.jboss.org/browse/SWSQE-712 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: infrastructure > > Currently our https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/bookinfo-operator/ > jenkins job allows to create only one bookinfo namespace. > But UI Automation framework requires bookinfo2 namespace for parallel running. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1943) [DMN Editor] Association: Add support for AssociationDirection

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1943?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-1943: -------------------------------- Labels: drools-tools (was: ) > [DMN Editor] Association: Add support for AssociationDirection > -------------------------------------------------------------- > > Key: DROOLS-1943 > URL: https://issues.jboss.org/browse/DROOLS-1943 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Edson Tirelli > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > > The DMN Editor only supports creating {{Association}} *from* a DRG Element *to* a {{TextAnnotation}}. The DMN Specification however provides for the {{Association}} to have a direction (either from-DRG-to-TA, or from-TA-to-DRG or both). > When implementing the UI model {{AssociationDirection}} was omitted as I thought it's direction could be inferred from the source and target nodes. However this may not be entirely accurate (for the "both" direction). Furthermore the UI currently does not support creating an {{Association}} from a {{TextAnnotation}}. > [~tirelli] [~tari_manga] FYI -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1944) [DMN Editor] Toolbox: Only one arrow for generic "connector". Type of connector depends on type of target node

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1944?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-1944: -------------------------------- Labels: drools-tools (was: ) > [DMN Editor] Toolbox: Only one arrow for generic "connector". Type of connector depends on type of target node > -------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1944 > URL: https://issues.jboss.org/browse/DROOLS-1944 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > > The "Toolbox" currently has a number of different "connector" icons; one for each type of connector that can emanate from the selected "source" node. [~tirelli] requested we have only one generic "connector" icon and the type of the created connector depends on the target node. This probably has an impact on the command being executed during drag move and drag complete. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1941) [DMN Editor] ToolBox: Add support for creating "source" nodes from a "target"

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1941?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-1941: -------------------------------- Labels: drools-tools (was: ) > [DMN Editor] ToolBox: Add support for creating "source" nodes from a "target" > ----------------------------------------------------------------------------- > > Key: DROOLS-1941 > URL: https://issues.jboss.org/browse/DROOLS-1941 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > The "Toolbox" (see {{DMNFlowActionsToolboxControlProvider}}) currently supports creating "target" nodes from a "source" node and automatically joining "source" to "target" however [~tirelli] has requested the ability to select an existing "target" node and create a new "source" node from the Toolbox with the resulting connector joining "source" to "target". I.E. support creating the inverse of what is currently supported. > * Should be able to create a BKM from Decision (connection from BKM to Decision). At the moment you can select BKM and add Decision, but need to support selecting a Decision and making an incoming BKM > * Should be able to create a KnowledgeSources from bothh Decisions and BKMs. At the moment you can select a KnowledgeSource and adda Decision or BKM, but need to support selecting either a Decision or BKM and making an incoming KS -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4495) Upgrade wilfly-openssl from 1.0.6.Final to 1.0.7.Final

by Ingo Weiss (Jira)

Ingo Weiss created WFCORE-4495: ---------------------------------- Summary: Upgrade wilfly-openssl from 1.0.6.Final to 1.0.7.Final Key: WFCORE-4495 URL: https://issues.jboss.org/browse/WFCORE-4495 Project: WildFly Core Issue Type: Component Upgrade Components: Modules, Server Affects Versions: 9.0.0.Beta8 Reporter: Ingo Weiss Assignee: Richard Opalka https://github.com/wildfly/wildfly-openssl/compare/1.0.6.Final...master -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4495) Upgrade wildfly-openssl from 1.0.6.Final to 1.0.7.Final

by Ingo Weiss (Jira)

[ https://issues.jboss.org/browse/WFCORE-4495?page=com.atlassian.jira.plugi... ] Ingo Weiss updated WFCORE-4495: ------------------------------- Summary: Upgrade wildfly-openssl from 1.0.6.Final to 1.0.7.Final (was: Upgrade wilfly-openssl from 1.0.6.Final to 1.0.7.Final) > Upgrade wildfly-openssl from 1.0.6.Final to 1.0.7.Final > ------------------------------------------------------- > > Key: WFCORE-4495 > URL: https://issues.jboss.org/browse/WFCORE-4495 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Modules, Server > Affects Versions: 9.0.0.Beta8 > Reporter: Ingo Weiss > Assignee: Richard Opalka > Priority: Major > > https://github.com/wildfly/wildfly-openssl/compare/1.0.6.Final...master -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-690) UI Automation - Add missing Health checks

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-690?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-690: -------------------------------------- All UI and REST related Health data are already added. The missing part is only in OC API which currently is not available how to do that. Keeping in a backlog. > UI Automation - Add missing Health checks > ----------------------------------------- > > Key: SWSQE-690 > URL: https://issues.jboss.org/browse/SWSQE-690 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > There are a lot of TODO Health comments in UI tests. > These all should be done. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-690) UI Automation - Add missing Health checks

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-690?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-690: --------------------------------- Sprint: (was: Kiali Sprint #23) > UI Automation - Add missing Health checks > ----------------------------------------- > > Key: SWSQE-690 > URL: https://issues.jboss.org/browse/SWSQE-690 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > There are a lot of TODO Health comments in UI tests. > These all should be done. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 May 2019