[JBoss JIRA] (WFWIP-9) Elytron permission-set should throw exception for non-existent permission
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFWIP-9?page=com.atlassian.jira.plugin.sy... ]
Brian Stansberry commented on WFWIP-9:
--------------------------------------
Can this be closed as a dup of WFCORE-3956? If not should it be moved to WFCORE now?
I'm doing a bit of WFWIP cleanup to move out issues that are no longer about feature branches.
> Elytron permission-set should throw exception for non-existent permission
> -------------------------------------------------------------------------
>
> Key: WFWIP-9
> URL: https://issues.jboss.org/browse/WFWIP-9
> Project: WildFly WIP
> Issue Type: Bug
> Components: Security
> Reporter: Ondrej Lukas
> Assignee: Farah Juma
> Labels: WFCORE-3596
>
> When non-existent permission (e.g. when there is a typo in class-name) is added to Elytron permission-set then exception should be thrown. It should throw exception for wrong class-name as well as wrong module.
> See issue WFCORE-3796 for more details.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFCORE-3796) Incorrect Elytron permission class-name or module should throw exception
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3796?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-3796:
------------------------------------------
This should not be done by any management code that runs in Stage.MODEL. Checking runtime state should only be done in Stage.RUNTIME, and only in processes that are certain to have the correct runtime state. You should assume code running in Stage.MODEL has no clue as to the actual runtime state. And in a domain, the DC definitely has no clue as to what its servers support, and even an HC might be uninformed in some cases (e.g. the HC is running JDK 11 but the server is JDK 8.)
If the code doing the check in Stage.RUNTIME wants to force rollback regardless of any rollback-on-runtime-failure setting by the user, OperationContext.setRollbackOnly can be used. This is a valid approach for doing configuration correctness checks outside of Stage.MODEL.
> Incorrect Elytron permission class-name or module should throw exception
> ------------------------------------------------------------------------
>
> Key: WFCORE-3796
> URL: https://issues.jboss.org/browse/WFCORE-3796
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 5.0.0.Alpha4
> Reporter: Ondrej Lukas
>
> When non-existent class-name or module (e.g. when there is a typo) is added to any Elytron permission mapper (constant-permission-mapper or simple-permission-mapper) then exception should be thrown. Otherwise it can result to situation when due to a typo some permission is granted to any identity instead of denying it - when permission in used on 'deny' side.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10850) smallrye-config: Allow configuration of per-deployment DirConfigSource
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10850?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFWIP-70 to WFLY-10850:
----------------------------------------------
Project: WildFly (was: WildFly WIP)
Key: WFLY-10850 (was: WFWIP-70)
Component/s: MP Config
(was: MP Config)
> smallrye-config: Allow configuration of per-deployment DirConfigSource
> ----------------------------------------------------------------------
>
> Key: WFLY-10850
> URL: https://issues.jboss.org/browse/WFLY-10850
> Project: WildFly
> Issue Type: Enhancement
> Components: MP Config
> Reporter: Michal Jurc
> Assignee: Jeff Mesnil
>
> With the current integration of {{smallrye-config}} with WildFly, it is possible to add a {{config-source}} management element that will hold a location of property directory. In cloud environments, it would be handier to allow this configuration to be committed from deployment itself.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10849) Allow for configuration of Converter SPI implementations via management in microprofile-config-smallrye subsystem
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10849?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFWIP-71 to WFLY-10849:
----------------------------------------------
Project: WildFly (was: WildFly WIP)
Key: WFLY-10849 (was: WFWIP-71)
Component/s: MP Config
(was: MP Config)
> Allow for configuration of Converter SPI implementations via management in microprofile-config-smallrye subsystem
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10849
> URL: https://issues.jboss.org/browse/WFLY-10849
> Project: WildFly
> Issue Type: Enhancement
> Components: MP Config
> Reporter: Michal Jurc
> Assignee: Jeff Mesnil
>
> MicroProfile configuration specifies three SPIs:
> * {{org.eclipse.microprofile.config.spi.ConfigSource}}
> * {{org.eclipse.microprofile.config.spi.ConfigSourceProvider}}
> * {{org.eclipse.microprofile.config.spi.Converter}}
> {{ConfigSource}} and {{ConfigSourceProvider}} services both can be exposed by WildFly management. We recommend providing the same capability for {{Converter}} services.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10848) smallrye-config: Unable to deploy component using automatic converter on injected properties
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10848?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFWIP-66 to WFLY-10848:
----------------------------------------------
Project: WildFly (was: WildFly WIP)
Key: WFLY-10848 (was: WFWIP-66)
Component/s: MP Config
(was: MP Config)
> smallrye-config: Unable to deploy component using automatic converter on injected properties
> --------------------------------------------------------------------------------------------
>
> Key: WFLY-10848
> URL: https://issues.jboss.org/browse/WFLY-10848
> Project: WildFly
> Issue Type: Bug
> Components: MP Config
> Reporter: Michal Jurc
> Assignee: Jeff Mesnil
> Priority: Blocker
> Fix For: 14.0.0.CR1
>
>
> MicroProfile Configuration specification states the following:
> {quote}Automatic Converters
> If no built-in nor custom Converter for a requested Type T, an implicit Converter is automatically
> provided if the following conditions are met:
> • The target type \{@code T\} has a \{@code public static T of(String)\} method, or
> • The target type \{@code T\} has a \{@code public static T valueOf(String)\} method, or
> • The target type \{@code T\} has a public Constructor with a String parameter, or
> • The target type \{@code T\} has a \{@code public static T parse(CharSequence)\} method{quote}
> Consider deploying an application with the following injected property:
> {code} @Inject
> @ConfigProperty(name = "convertedOne", defaultValue = "2007-12-03T10:15:30")
> LocalDateTime localDateTimeProperty;{code}
> Deployment of such application fails with the following:
> {code:title=jboss-cli}[standalone@localhost:9990 /] deploy ~/testing/mock-artifacts/smallrye-config-playground/ejb-smallrye-config/server/target/server.jar
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"server.jar\".CdiValidatorFacto
> ryService" => "Failed to start service
> Caused by: org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getReference() is not available during application initialization. Container state: DEPLOYED"}}}}
> {code}
> {code:title=server.log}12:46:19,263 ERROR [stderr] (MSC service thread 1-5) org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type LocalDateTime with qualifiers @ConfigProperty
> 12:46:19,263 ERROR [stderr] (MSC service thread 1-5) at injection point [BackedAnnotatedField] @Inject @ConfigProperty ejb.HelloBean.localDateTimeProperty
> 12:46:19,263 ERROR [stderr] (MSC service thread 1-5) at ejb.HelloBean.localDateTimeProperty(HelloBean.java:0)
> 12:46:19,263 ERROR [stderr] (MSC service thread 1-5)
> 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:378)
> 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:290)
> 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:143)
> 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:164)
> 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:526)
> 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:64)
> 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:62)
> 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
> 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
> 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at java.lang.Thread.run(Thread.java:748)
> 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> 12:46:19,270 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."server.jar".CdiValidatorFactoryService: org.jboss.msc.service.StartException in service jboss.deployment.unit."server.jar".CdiValidatorFactoryService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getReference() is not available during application initialization. Container state: DEPLOYED
> at org.jboss.weld.bean.builtin.BeanManagerProxy.checkContainerState(BeanManagerProxy.java:234)
> at org.jboss.weld.bean.builtin.BeanManagerProxy.getReference(BeanManagerProxy.java:85)
> at org.jboss.as.weld.CdiValidatorFactoryService.getReference(CdiValidatorFactoryService.java:122)
> at org.jboss.as.weld.CdiValidatorFactoryService.start(CdiValidatorFactoryService.java:83)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> ... 6 more
> 12:46:19,288 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("deploy") failed - address: ({"deployment" => "server.jar"}) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"server.jar\".CdiValidatorFactoryService" => "Failed to start service
> Caused by: org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getReference() is not available during application initialization. Container state: DEPLOYED"}}
> 12:46:19,289 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "server.jar" was rolled back with the following failure message:
> {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"server.jar\".CdiValidatorFactoryService" => "Failed to start service
> Caused by: org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getReference() is not available during application initialization. Container state: DEPLOYED"}}
> {code}
> This failure is not produced if the automatically converted property is optional.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10848) smallrye-config: Unable to deploy component using automatic converter on injected properties
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10848?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-10848:
------------------------------------
Fix Version/s: 14.0.0.CR1
> smallrye-config: Unable to deploy component using automatic converter on injected properties
> --------------------------------------------------------------------------------------------
>
> Key: WFLY-10848
> URL: https://issues.jboss.org/browse/WFLY-10848
> Project: WildFly
> Issue Type: Bug
> Components: MP Config
> Reporter: Michal Jurc
> Assignee: Jeff Mesnil
> Priority: Blocker
> Fix For: 14.0.0.CR1
>
>
> MicroProfile Configuration specification states the following:
> {quote}Automatic Converters
> If no built-in nor custom Converter for a requested Type T, an implicit Converter is automatically
> provided if the following conditions are met:
> • The target type \{@code T\} has a \{@code public static T of(String)\} method, or
> • The target type \{@code T\} has a \{@code public static T valueOf(String)\} method, or
> • The target type \{@code T\} has a public Constructor with a String parameter, or
> • The target type \{@code T\} has a \{@code public static T parse(CharSequence)\} method{quote}
> Consider deploying an application with the following injected property:
> {code} @Inject
> @ConfigProperty(name = "convertedOne", defaultValue = "2007-12-03T10:15:30")
> LocalDateTime localDateTimeProperty;{code}
> Deployment of such application fails with the following:
> {code:title=jboss-cli}[standalone@localhost:9990 /] deploy ~/testing/mock-artifacts/smallrye-config-playground/ejb-smallrye-config/server/target/server.jar
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"server.jar\".CdiValidatorFacto
> ryService" => "Failed to start service
> Caused by: org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getReference() is not available during application initialization. Container state: DEPLOYED"}}}}
> {code}
> {code:title=server.log}12:46:19,263 ERROR [stderr] (MSC service thread 1-5) org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type LocalDateTime with qualifiers @ConfigProperty
> 12:46:19,263 ERROR [stderr] (MSC service thread 1-5) at injection point [BackedAnnotatedField] @Inject @ConfigProperty ejb.HelloBean.localDateTimeProperty
> 12:46:19,263 ERROR [stderr] (MSC service thread 1-5) at ejb.HelloBean.localDateTimeProperty(HelloBean.java:0)
> 12:46:19,263 ERROR [stderr] (MSC service thread 1-5)
> 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:378)
> 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:290)
> 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:143)
> 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:164)
> 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:526)
> 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:64)
> 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:62)
> 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
> 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
> 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at java.lang.Thread.run(Thread.java:748)
> 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> 12:46:19,270 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."server.jar".CdiValidatorFactoryService: org.jboss.msc.service.StartException in service jboss.deployment.unit."server.jar".CdiValidatorFactoryService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getReference() is not available during application initialization. Container state: DEPLOYED
> at org.jboss.weld.bean.builtin.BeanManagerProxy.checkContainerState(BeanManagerProxy.java:234)
> at org.jboss.weld.bean.builtin.BeanManagerProxy.getReference(BeanManagerProxy.java:85)
> at org.jboss.as.weld.CdiValidatorFactoryService.getReference(CdiValidatorFactoryService.java:122)
> at org.jboss.as.weld.CdiValidatorFactoryService.start(CdiValidatorFactoryService.java:83)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698)
> ... 6 more
> 12:46:19,288 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("deploy") failed - address: ({"deployment" => "server.jar"}) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"server.jar\".CdiValidatorFactoryService" => "Failed to start service
> Caused by: org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getReference() is not available during application initialization. Container state: DEPLOYED"}}
> 12:46:19,289 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "server.jar" was rolled back with the following failure message:
> {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"server.jar\".CdiValidatorFactoryService" => "Failed to start service
> Caused by: org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getReference() is not available during application initialization. Container state: DEPLOYED"}}
> {code}
> This failure is not produced if the automatically converted property is optional.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-10846) OpenTracing modules need jboss-api=private in module.xml
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10846?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-10846:
------------------------------------
Fix Version/s: 14.0.0.CR1
> OpenTracing modules need jboss-api=private in module.xml
> --------------------------------------------------------
>
> Key: WFLY-10846
> URL: https://issues.jboss.org/browse/WFLY-10846
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing
> Reporter: Brian Stansberry
> Assignee: Juraci Paixão Kröhling
> Priority: Blocker
> Fix For: 14.0.0.CR1
>
>
> The 3 modules added in https://github.com/wildfly/wildfly/pull/11454 need this in their module.xml:
> {code}
> <properties>
> <property name="jboss.api" value="private"/>
> </properties>
> {code}
> This ensures that we log a WARN if the user tries to _directly_ use these modules as application dependencies. (Directly == via their own deployment configuration, not via our subsystem wiring them in as a dependency. See [1] for the impl.)
> These log WARNs and the setting in the file itself are important both to prevent the user making mistakes and as the formal the mechanism by which we control how we support use of the various libraries we ship in the appserver. Marking modules private, deprecated etc gives us the freedom to rework implementations without worrying about breaking unexpected uses of things.
> [1] https://github.com/wildfly/wildfly-core/blob/master/server/src/main/java/...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2888) Data Type UX - dialog enhancements: Add and Reorder
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2888?page=com.atlassian.jira.plugi... ]
Liz Clayton edited comment on DROOLS-2888 at 8/15/18 11:31 AM:
---------------------------------------------------------------
[~karreiro] [~tirelli] [~manstis] I have an initial click-thru demo for Add (bottom) and reorder row. There are some instructions for this one:
*Demo *
https://cdn.rawgit.com/lclay2/bxms-uxd-sandbox/b37bf9de/design/DataTypeDe...
Click-thru Steps
*Setup:*
* Click “Pages” button to hide this panel and resize browser window to approximate a dialog.
-
* Note: Font awesome icons should load if they don’t please let me know.
*Step 1. Add a new data type.*
* Click the “Add” button.
* In the new row provide the name “Data Object” and select the type as “Text” then click “Save.”
*Step 2. Search*
* In the search input box type “Name”
[select enter in reality, but not needed for demo]
*Step 3. Add row inline.*
* Click the kebab menu of the selected row
* Select “Insert Row”
* Provide a name the new row “New,” select the type “Boolean” and click “Save.”
*Step 4. Reorder row item.*
* Click the kebab menu for the selected row [“New(Boolean)”]
* Select “Row Down”
That’s all for now, please send feedback, thanks.
was (Author: uxdlc):
[~karreiro] [~tirelli] [~manstis] I have an initial click-thru demo for Add (bottom) and reorder row. There are some instructions for this one:
*Demo *
https://cdn.rawgit.com/lclay2/bxms-uxd-sandbox/b37bf9de/design/DataTypeDe...
Click-thru Steps
*Setup:*
* Click “Pages” button to hide this panel and resize browser window to approximate a dialog.
-
* Note: Font awesome icons should load if they don’t please let me know.
*Step 1. Add a new data type.*
* Click the “Add” button.
* In the new row provide the name “Name” and select the type as “Text” then click “Save.”
*Step 2. Search*
* In the search input box type “Name”
[select enter in reality, but not needed for demo]
*Step 3. Add row inline.*
* Click the kebab menu of the selected row
* Select “Insert Row”
* Provide a name the new row “New,” select the type “Boolean” and click “Save.”
*Step 4. Reorder row item.*
* Click the kebab menu for the selected row [“New(Boolean)”]
* Select “Row Down”
That’s all for now, please send feedback, thanks.
> Data Type UX - dialog enhancements: Add and Reorder
> ----------------------------------------------------
>
> Key: DROOLS-2888
> URL: https://issues.jboss.org/browse/DROOLS-2888
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> As a user I want to:
> * Add fields first to last, not last to first, in an ordered list to support the "reading" order of the fields so that I can simplify my workflow.
> * Reorder the list of Custom data types so that I can arrange data types in a logical order.
> * Add list items in such a way that added Fields will be presented at the bottom of a structured list by default.
> Functional considerations/ pre conditions:
> * Fields will be presented at the bottom of a structured list by default.
> * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table
> * Drag-n-drop be evaluated with regard to accessibility.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months