[JBoss JIRA] (DROOLS-4503) "Error" popup report java literal for suggested number
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4503?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4503:
-----------------------------------
Sprint: 2019 Week 35-37, 2019 Week 38-40 (was: 2019 Week 35-37)
> "Error" popup report java literal for suggested number
> ------------------------------------------------------
>
> Key: DROOLS-4503
> URL: https://issues.jboss.org/browse/DROOLS-4503
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.26.0.Final
> Reporter: Gabriele Cardosi
> Assignee: Yeser Amer
> Priority: Major
> Labels: ScenarioSimulation
> Attachments: ErrorPopup.png, FollowError.png, InsertedValue.png
>
>
> When the expected value for a field is a java long, the error popup reports
> "The expected value is '2' but the actual one is '3L'."
> !ErrorPopup.png|thumbnail!
> That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._
> This is a little bit inconsistent and confusing, especially for someone not knowing java.
> The worst consequence is that when user click "Apply", that literal is put inside the cell,
> !InsertedValue.png|thumbnail!
> and when sent to server it raise error (because server is expecting a number, not a string)
> !FollowError.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-3954) DM UX solutions for communicating errors in graphs & grids.
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3954?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3954:
-----------------------------------
Sprint: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 35-37, 2019 Week 38-40 (was: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 35-37)
> DM UX solutions for communicating errors in graphs & grids.
> ------------------------------------------------------------
>
> Key: DROOLS-3954
> URL: https://issues.jboss.org/browse/DROOLS-3954
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor, Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: ScenarioSimulation, Stunner, UX, UXTeam, drools-tools
>
> Scenario and DMN editors share design solutions for displaying errors in graphs (models) and grids (scenario test, dmn boxed expressions.) Support design consistency where applicable, while also documenting unique solutions per context.
> Current DM context specific "design pattern" document: https://docs.google.com/document/d/1fX9K_fDjEO4_wDLK9EDDb0OtEFir7S6nFH9cn...
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-3957) Make verifier panel use docks
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3957?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3957:
-----------------------------------
Sprint: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 35-37, 2019 Week 38-40 (was: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 35-37)
> Make verifier panel use docks
> -----------------------------
>
> Key: DROOLS-3957
> URL: https://issues.jboss.org/browse/DROOLS-3957
> Project: Drools
> Issue Type: Enhancement
> Components: Guided Decision Table Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
> Attachments: v&v.webm
>
>
> Pretty sure we had a ticket for this, but could not find it. Here it is.
> h3. Acceptance test
> On both Firefox and Chrome (x)
> - Opening multiple decision tables, switching between them
> - Repeated reopening of guided decision table
> - Opening other asset that uses docks - scenario, data object
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-3680) Explore HA CEP design and architecture
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-3680?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-3680:
-----------------------------------
Sprint: 2019 Week 08-10, 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 35-37, 2019 Week 38-40 (was: 2019 Week 08-10, 2019 Week 11-13, 2019 Week 14-16, 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28, 2019 Week 29-31, 2019 Week 32-34, 2019 Week 35-37)
> Explore HA CEP design and architecture
> --------------------------------------
>
> Key: DROOLS-3680
> URL: https://issues.jboss.org/browse/DROOLS-3680
> Project: Drools
> Issue Type: Task
> Reporter: Mario Fusco
> Assignee: Massimiliano Dessi
> Priority: Major
> Labels: HADrools
>
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (DROOLS-4368) HACEP Refactor DefaultKafkaConsumer -Testing
by Kris Verlaenen (Jira)
[ https://issues.jboss.org/browse/DROOLS-4368?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-4368:
-----------------------------------
Sprint: 2019 Week 35-37, 2019 Week 38-40 (was: 2019 Week 35-37)
> HACEP Refactor DefaultKafkaConsumer -Testing
> ---------------------------------------------
>
> Key: DROOLS-4368
> URL: https://issues.jboss.org/browse/DROOLS-4368
> Project: Drools
> Issue Type: Task
> Components: core engine
> Reporter: Daniele Zonca
> Assignee: Massimiliano Dessi
> Priority: Major
> Labels: HADrools
>
> Try to uniform leader/replica flow:
> - If I'm the leader it invokes `defaultProcessAsLeader` -> `processLeader` -> `process/processWithSnapshot`
> - If I'm a replica it invokes `defaultProcessAsAReplica` -> `consumeEventsFromBufferAsAReplica` -> `processEventsAsAReplica` -> `process`
> Try to remove most/all boolean and use proper method parameter
> Verify defaultProcessAsAReplica else branch. This should never happen because if leader sent a message about process a specific event, it should be available
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months