[JBoss JIRA] (WFLY-10697) Upgrade to Apache CXF 3.2.5
by James Perkins (JIRA)
James Perkins created WFLY-10697:
------------------------------------
Summary: Upgrade to Apache CXF 3.2.5
Key: WFLY-10697
URL: https://issues.jboss.org/browse/WFLY-10697
Project: WildFly
Issue Type: Component Upgrade
Components: Web Services
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: 14.0.0.CR1
Upgrade Apache CXF to 3.2.5
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2706) New "Scenario Test" asset list option (UX)
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi... ]
Liz Clayton reassigned DROOLS-2706:
-----------------------------------
Assignee: Stetson Robinson (was: Liz Clayton)
> New "Scenario Test" asset list option (UX)
> ------------------------------------------
>
> Key: DROOLS-2706
> URL: https://issues.jboss.org/browse/DROOLS-2706
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Stetson Robinson
> Labels: UX, UXTeam
>
> As a practitioner - I want to be able to distinguish the new Scenario Test tool option, from the existing one, within the Asset list so that I can quickly/easily create a test using the new editor.
> *Verification conditions:*
> The new Scenario Test tool is distinguishable from the existing test tool within the asset list, through visual inspection by the user (no hover/click required.)
> Notes:
> Need a way to identify "experimental" tools from existing (to be deprecated?) tools. Solution might include distinct names for each, or parenthetical append (e.g. "experimental, beta, preview...) Or visual indicator, such as an icon, flag, etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2728:
-------------------------------------
[~roger.martinez] [~mstevens1] Could either of you offer any more info about the Process Variable table/list widget in the Properties panel of the Process Designer. We're trying to figure out if we could re-use it here. ^^ Thanks!
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: 2018-07-12 11.41.43 AM.gif, DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2728:
--------------------------------
Story Points: 5
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: 2018-07-12 11.41.43 AM.gif, DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2656) PNGs for the toolbox icons for the different connector types.
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2656?page=com.atlassian.jira.plugi... ]
Michael Anstis commented on DROOLS-2656:
----------------------------------------
Hi [~bdellasc] IDK why the connector icons appear lighter; I used your PNGs unchanged. It is not intentional (on my part).
Furthermore the toolbox icons for Knowledge Source etc are the "Palette" SVGs (from https://issues.jboss.org/browse/BAPL-924) scaled. They are not bespoke icons designed for use with the toolbox (like the connector ones). Feel free to provide some if you like and I'll replace the current ones with them (although it might need to be a new JIRA). I'll investigate why the icons appear lighter.
> PNGs for the toolbox icons for the different connector types.
> -------------------------------------------------------------
>
> Key: DROOLS-2656
> URL: https://issues.jboss.org/browse/DROOLS-2656
> Project: Drools
> Issue Type: Sub-task
> Reporter: Liz Clayton
> Assignee: Brian Dellascio
> Labels: IconRequest, UX, UXTeam, VisualDesign, drools-tools
> Attachments: DROOLS-2656.png, association_toolbox.png, association_toolbox.svg, authority_requirement_toolbox.png, authority_requirement_toolbox.svg, edit.svg, info_requirement_toolbox.png, info_requirement_toolbox.svg, knowledge_requirement_toolbox.png, knowledge_requirement_toolbox.svg, toolbox_icons.png
>
>
> PNGs for the toolbox icons for the different connector types.
> Their appearance can be seen in https://www.omg.org/spec/DMN/1.1/PDF (page 30, "Association", "Information Requirement", "Knowledge Requirement" and "Authority Requirement"). They'll only be used as icons on the toolbox (see screenshot attached). Could you please also remind me of the BAPL for the new "Node" SVGs (I'll need to make PNGs of those too for the same "toolbox" purpose.. unless UX have a tool to convert SVG to PNG?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro edited comment on DROOLS-2728 at 7/12/18 10:57 AM:
----------------------------------------------------------------------
Hi [~uxdlc],
---
1) Simple (basic) data type
> wrt 1) one thing that's missing is if you look at the Process Modeler widget I believe it's not just a list of the added items, but also allows one to edit existing ones. Wdyt?
I just tried the Process Modeller widget:
!2018-07-12 11.41.43 AM.gif|thumbnail!
..but I'm not seeing how it solves in the problem of the _simple_ data type definition.
I think that the dialog handles only one data type, right?
The user would be creating one data type, or updating the selected one.
Am I missing something?
---
2) Structured data type
> 2) Ok, so both 2 and 3 are structured (or hierarchical?), it wasn't clear from you initial mockups - thanks for clarifying.
No problem :)
---
3) Deep structured data type
> 3) Michael Anstis, Guilherme Carreiro as I mentioned in my comments, I only starting working on this last night so didn't have time to work on this variant. But if you're good with this forms based approach I'll work on that next.
I'm good with the forms based approach :) One thing that I think we should try to avoid is having a "popup hell", due to this hierarchical scenario that we handling.
---
Thank you Liz :)
was (Author: karreiro):
Hi [~uxdlc],
---
1) Simple (basic) data type
> wrt 1) one thing that's missing is if you look at the Process Modeler widget I believe it's not just a list of the added items, but also allows one to edit existing ones. Wdyt?
I just tried the Process Modeller widget:
!2018-07-12 11.41.43 AM.gif!
..but I'm not seeing how it solves in the problem of the _simple_ data type definition.
I think that the dialog handles only one data type, right?
The user would be creating one data type, or updating the selected one.
Am I missing something?
---
2) Structured data type
> 2) Ok, so both 2 and 3 are structured (or hierarchical?), it wasn't clear from you initial mockups - thanks for clarifying.
No problem :)
---
3) Deep structured data type
> 3) Michael Anstis, Guilherme Carreiro as I mentioned in my comments, I only starting working on this last night so didn't have time to work on this variant. But if you're good with this forms based approach I'll work on that next.
I'm good with the forms based approach :) One thing that I think we should try to avoid is having a "popup hell", due to this hierarchical scenario that we handling.
---
Thank you Liz :)
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: 2018-07-12 11.41.43 AM.gif, DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2731) ArrayIndexOutOfBoundsException when updating the rules at the runtime
by Bhavneet Singh (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2731?page=com.atlassian.jira.plugi... ]
Bhavneet Singh commented on DROOLS-2731:
----------------------------------------
We still don't have exact steps to reproduce this. We are trying for the same.
We just have this stack trace.
> ArrayIndexOutOfBoundsException when updating the rules at the runtime
> ---------------------------------------------------------------------
>
> Key: DROOLS-2731
> URL: https://issues.jboss.org/browse/DROOLS-2731
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.6.0.Final
> Reporter: Bhavneet Singh
> Assignee: Mario Fusco
> Priority: Blocker
>
> We update rules at runtime. Sometimes the system reaches a state when it starts throwing error -
> java.lang.ArrayIndexOutOfBoundsException: 1
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:349) ~[drools-core-7.6.0.Final.jar:7.6.0.Final]
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:169) ~[drools-core-7.6.0.Final.jar:7.6.0.Final]
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:127) ~[drools-core-7.6.0.Final.jar:7.6.0.Final]
> at org.drools.core.phreak.RuleExecutor.evaluateNetwork(RuleExecutor.java:71) ~[drools-core-7.6.0.Final.jar:7.6.0.Final]
> at org.drools.core.common.DefaultAgenda.evaluateEagerList(DefaultAgenda.java:887) ~[drools-core-7.6.0.Final.jar:7.6.0.Final]
> at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1061) ~[drools-core-7.6.0.Final.jar:7.6.0.Final]
> at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1014) ~[drools-core-7.6.0.Final.jar:7.6.0.Final]
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1006) ~[drools-core-7.6.0.Final.jar:7.6.0.Final]
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1318) ~[drools-core-7.6.0.Final.jar:7.6.0.Final]
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1309) ~[drools-core-7.6.0.Final.jar:7.6.0.Final]
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1293) ~[drools-core-7.6.0.Final.jar:7.6.0.Final]
> at com.adobe.sophia.executionlayer.RuleEngine.client.RuleEngineSession.fireAllRules(RuleEngineSession.java:111) ~[Rule-Engine-0.5.4.jar:?]
> at com.adobe.sophia.executionlayer.RuleEngine.client.Evaluator.evaluate(Evaluator.java:416) ~[Rule-Engine-0.5.4.jar:?]
> at com.adobe.sophia.executionlayer.RuleEngine.client.Evaluator$$FastClassBySpringCGLIB$$cfed13fd.invoke(<generated>) ~[Rule-Engine-0.5.4.jar:?]
> at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) ~[spring-core-4.3.4.RELEASE.jar:4.3.4.RELEASE]
> at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720) ~[spring-aop-4.3.4.RELEASE.jar:4.3.4.RELEASE]
> at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.3.4.RELEASE.jar:4.3.4.RELEASE]
> at org.springframework.retry.annotation.AnnotationAwareRetryOperationsInterceptor.invoke(AnnotationAwareRetryOperationsInterceptor.java:156) ~[spring-retry-1.2.2.RELEASE.jar:?]
> at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.4.RELEASE.jar:4.3.4.RELEASE]
> at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655) ~[spring-aop-4.3.4.RELEASE.jar:4.3.4.RELEASE]
> at com.adobe.sophia.executionlayer.RuleEngine.client.Evaluator$$EnhancerBySpringCGLIB$$fb776e74.evaluate(<generated>) ~[Rule-Engine-0.5.4.jar:?]
> at com.adobe.sophia.executionlayer.psdk.RuleEngineEvaluator.RuleEvaluator.evaluate(RuleEvaluator.java:393) ~[RuleEvaluator.class:?]
> at com.adobe.sophia.executionlayer.psdk.RuleEngineEvaluator.CardRuleEvaluator.evaluate(CardRuleEvaluator.java:117) ~[CardRuleEvaluator.class:?]
> at com.adobe.sophia.executionlayer.psdk.content.service.ContentServiceImpl.fetchAllCardsUtilSophia(ContentServiceImpl.java:460) [ContentServiceImpl.class:?]
> at com.adobe.sophia.executionlayer.psdk.content.service.ContentServiceImpl.fetchContentGeneric(ContentServiceImpl.java:268) [ContentServiceImpl.class:?]
> at com.adobe.sophia.executionlayer.psdk.content.service.ContentServiceImpl.fetchContent(ContentServiceImpl.java:219) [ContentServiceImpl.class:?]
> at sun.reflect.GeneratedMethodAccessor269.invoke(Unknown Source) ~[?:?]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_51]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_51]
> at org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180) [cxf-core-3.1.3.jar:3.1.3]
> at org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96) [cxf-core-3.1.3.jar:3.1.3]
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:200) [cxf-rt-frontend-jaxrs-3.1.3.jar:3.1.3]
> at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:99) [cxf-rt-frontend-jaxrs-3.1.3.jar:3.1.3]
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59) [cxf-core-3.1.3.jar:3.1.3]
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96) [cxf-core-3.1.3.jar:3.1.3]
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308) [cxf-core-3.1.3.jar:3.1.3]
> at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-core-3.1.3.jar:3.1.3]
> at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:251) [cxf-rt-transports-http-3.1.3.jar:3.1.3]
> at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:234) [cxf-rt-transports-http-3.1.3.jar:3.1.3]
> at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:208) [cxf-rt-transports-http-3.1.3.jar:3.1.3]
> at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:160) [cxf-rt-transports-http-3.1.3.jar:3.1.3]
> at org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpringServlet.java:171) [cxf-rt-transports-http-3.1.3.jar:3.1.3]
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:293) [cxf-rt-transports-http-3.1.3.jar:3.1.3]
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:212) [cxf-rt-transports-http-3.1.3.jar:3.1.3]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:650) [tomcat7-servlet-3.0-api.jar:?]
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:268) [cxf-rt-transports-http-3.1.3.jar:3.1.3]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) [catalina.jar:7.0.85]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) [catalina.jar:7.0.85]
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) [tomcat7-websocket.jar:7.0.85]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) [catalina.jar:7.0.85]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) [catalina.jar:7.0.85]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219) [catalina.jar:7.0.85]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110) [catalina.jar:7.0.85]
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:498) [catalina.jar:7.0.85]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169) [catalina.jar:7.0.85]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) [catalina.jar:7.0.85]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) [catalina.jar:7.0.85]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:445) [catalina.jar:7.0.85]
> at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1115) [tomcat-coyote.jar:7.0.85]
> at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637) [tomcat-coyote.jar:7.0.85]
> at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318) [tomcat-coyote.jar:7.0.85]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_51]
> at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-coyote.jar:7.0.85]
> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_51]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro commented on DROOLS-2728:
--------------------------------------------
Hi [~uxdlc],
---
1) Simple (basic) data type
> wrt 1) one thing that's missing is if you look at the Process Modeler widget I believe it's not just a list of the added items, but also allows one to edit existing ones. Wdyt?
I just tried the Process Modeller widget:
!2018-07-12 11.41.43 AM.gif!
..but I'm not seeing how it solves in the problem of the _simple_ data type definition.
I think that the dialog handles only one data type, right?
The user would be creating one data type, or updating the selected one.
Am I missing something?
---
2) Structured data type
> 2) Ok, so both 2 and 3 are structured (or hierarchical?), it wasn't clear from you initial mockups - thanks for clarifying.
No problem :)
---
3) Deep structured data type
> 3) Michael Anstis, Guilherme Carreiro as I mentioned in my comments, I only starting working on this last night so didn't have time to work on this variant. But if you're good with this forms based approach I'll work on that next.
I'm good with the forms based approach :) One thing that I think we should try to avoid is having a "popup hell", due to this hierarchical scenario that we handling.
---
Thank you Liz :)
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: 2018-07-12 11.41.43 AM.gif, DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2728) UX for custom data-types modal
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-2728:
---------------------------------------
Attachment: 2018-07-12 11.41.43 AM.gif
> UX for custom data-types modal
> -------------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: 2018-07-12 11.41.43 AM.gif, DROOLS-2700.png, First-draft.png, Screen Shot 2018-07-11 at 7.37.12 PM.png, Screen Shot 2018-07-12 at 9.41.34 AM.png, Screen Shot 2018-07-12 at 9.41.40 AM.png, edit.png, grid-alt.png, triggerDataType.png
>
>
> As a practitioner I want to be able to define Data Types(ItemDefinition) throughDMN editor UI, by:
> - selecting an existing data type
> - creating a new one
> - editing an existing data type
> - deleting an existing data type
> so that I can use this data type to make some decision.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2656) PNGs for the toolbox icons for the different connector types.
by Brian Dellascio (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2656?page=com.atlassian.jira.plugi... ]
Brian Dellascio edited comment on DROOLS-2656 at 7/12/18 10:46 AM:
-------------------------------------------------------------------
Looking at the screen capture, it appears that the cluster of icons to the right of the "InputData-1" node are lighter. Is that intentional? I checked my source files and the color matches the Palette icon colors. Also, for me, the text annotation, tasks and knowledge source icons to the right of "InputData-1" are a bit tough to see. Those source files weren't intended to be used at that size. Are those placeholders for something else, or are those options actually there?
was (Author: bdellasc):
Looking at the screen capture, it appears that the cluster of icons to the right of the "InputData-1" node are lighter. Is that intentional? I checked my source files and the color matches the Palette icon colors. Also, for me, the text annotation, tasks and knowledge source icons to the right of "InputData-1" are a bit tough to see. Those source files weren't intended to be used at that size. Are those placeholders for something else, or are those options actually there? If so, I'd like to try and improve those icons for use at that size.
> PNGs for the toolbox icons for the different connector types.
> -------------------------------------------------------------
>
> Key: DROOLS-2656
> URL: https://issues.jboss.org/browse/DROOLS-2656
> Project: Drools
> Issue Type: Sub-task
> Reporter: Liz Clayton
> Assignee: Brian Dellascio
> Labels: IconRequest, UX, UXTeam, VisualDesign, drools-tools
> Attachments: DROOLS-2656.png, association_toolbox.png, association_toolbox.svg, authority_requirement_toolbox.png, authority_requirement_toolbox.svg, edit.svg, info_requirement_toolbox.png, info_requirement_toolbox.svg, knowledge_requirement_toolbox.png, knowledge_requirement_toolbox.svg, toolbox_icons.png
>
>
> PNGs for the toolbox icons for the different connector types.
> Their appearance can be seen in https://www.omg.org/spec/DMN/1.1/PDF (page 30, "Association", "Information Requirement", "Knowledge Requirement" and "Authority Requirement"). They'll only be used as icons on the toolbox (see screenshot attached). Could you please also remind me of the BAPL for the new "Node" SVGs (I'll need to make PNGs of those too for the same "toolbox" purpose.. unless UX have a tool to convert SVG to PNG?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years