[JBoss JIRA] (WFLY-12329) ManagedScheduledExecutorService should be only available after server is ready
by nimo stephan (Jira)
nimo stephan created WFLY-12329:
-----------------------------------
Summary: ManagedScheduledExecutorService should be only available after server is ready
Key: WFLY-12329
URL: https://issues.jboss.org/browse/WFLY-12329
Project: WildFly
Issue Type: Bug
Components: Concurrency Utilities
Affects Versions: 17.0.1.Final
Reporter: nimo stephan
Assignee: Eduardo Martins
I use a *ManagedScheduledExecutorService* to execute tasks periodically:
{code:java}
@Startup
@Singleton
public class TaskScheduler {
@Resource
ManagedScheduledExecutorService executorService;
@PostConstruct
public void init() {
executorService.scheduleAtFixedRate(this::task, 0, 5, TimeUnit.SECONDS);
}
public void task() {
System.out.println("long running task:" + LocalTime.now());
}
}
{code}
Wildfly throws a few exceptions as long as server is not fully initiated and in "suspend"-mode:
{{
{code:java}
12:44:12,715 ERROR [org.jboss.as.ee] (EE-ManagedScheduledExecutorService-default-Thread-3) WFLYEE0110: Failed to run scheduled task: java.lang.IllegalStateException: WFLYEE0111: Cannot run scheduled task my.Task$$Lambda$1041/0x000000080240a040@5ee966ec as container is suspended
at org.jboss.as.ee@17.0.1.Final//org.jboss.as.ee.concurrent.ControlPointUtils$ControlledScheduledRunnable.run(ControlPointUtils.java:164)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383)
at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:835)
at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)
{code}
}}
I use "ManagedScheduledExecutorService" instead of "ScheduledExecutorService" in JEE because, *ManagedScheduledExecutorService* should be managed by jee. Hence, the server should also manage and guarantee not to fire the executorService until the server is ready (and EJBs are available).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4364) [DMN Designer] Download buttons UX (Development task)
by Guilherme Gomes (Jira)
[ https://issues.jboss.org/browse/DROOLS-4364?page=com.atlassian.jira.plugi... ]
Guilherme Gomes closed DROOLS-4364.
-----------------------------------
Resolution: Done
> [DMN Designer] Download buttons UX (Development task)
> -----------------------------------------------------
>
> Key: DROOLS-4364
> URL: https://issues.jboss.org/browse/DROOLS-4364
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Margot Menestrot
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: component-1.png, component-2.png, component-3.png
>
>
> h3. Need to update the DMN toolbar download buttons based on the context described in initial issue.
> Implementation suggestions can be found in this slide deck. https://docs.google.com/presentation/d/1uq3DZ95LWODhmdL8p9A-xaw8sufe3lBVC...
> Suggestions are as follows:
> 1. Remove download button that appears as icon dropdown, and leave the Download button that appears spelt out.
> 2. Make that download button a drop down meny that includes all possible downloading options, separated into two parts - download DMN model and download documentation.
> 3. Remove download button in the documentation sub tab (that appears on top right of documentation example) to avoid repetition, and just leave the print button there.
> ---------------
> h3. Context:
> Today users can:
> 1) Download the diagram picture by using this component:
> !component-1.png|thumbnail!
> 2) Download the DMN file by using this component:
> !component-2.png|thumbnail!
> 3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab):
> !component-3.png|thumbnail!
> 4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab):
> !component-3.png|thumbnail!
> ----
> h3. Problem:
> The "Download" concept is getting confusing for users.
> As a user, I want to be able to:
> - Download the documentation as a .PDF file
> - Download the documentation as a .DOC file
> - Print the documentation
> ----
> h3. Notice:
> This component can be removed (if UX considers that it's necessary):
> !component-1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4364) [DMN Designer] Download buttons UX (Development task)
by Guilherme Gomes (Jira)
[ https://issues.jboss.org/browse/DROOLS-4364?page=com.atlassian.jira.plugi... ]
Guilherme Gomes reopened DROOLS-4364:
-------------------------------------
> [DMN Designer] Download buttons UX (Development task)
> -----------------------------------------------------
>
> Key: DROOLS-4364
> URL: https://issues.jboss.org/browse/DROOLS-4364
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Margot Menestrot
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: component-1.png, component-2.png, component-3.png
>
>
> h3. Need to update the DMN toolbar download buttons based on the context described in initial issue.
> Implementation suggestions can be found in this slide deck. https://docs.google.com/presentation/d/1uq3DZ95LWODhmdL8p9A-xaw8sufe3lBVC...
> Suggestions are as follows:
> 1. Remove download button that appears as icon dropdown, and leave the Download button that appears spelt out.
> 2. Make that download button a drop down meny that includes all possible downloading options, separated into two parts - download DMN model and download documentation.
> 3. Remove download button in the documentation sub tab (that appears on top right of documentation example) to avoid repetition, and just leave the print button there.
> ---------------
> h3. Context:
> Today users can:
> 1) Download the diagram picture by using this component:
> !component-1.png|thumbnail!
> 2) Download the DMN file by using this component:
> !component-2.png|thumbnail!
> 3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab):
> !component-3.png|thumbnail!
> 4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab):
> !component-3.png|thumbnail!
> ----
> h3. Problem:
> The "Download" concept is getting confusing for users.
> As a user, I want to be able to:
> - Download the documentation as a .PDF file
> - Download the documentation as a .DOC file
> - Print the documentation
> ----
> h3. Notice:
> This component can be removed (if UX considers that it's necessary):
> !component-1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4364) [DMN Designer] Download buttons UX (Development task)
by Guilherme Gomes (Jira)
[ https://issues.jboss.org/browse/DROOLS-4364?page=com.atlassian.jira.plugi... ]
Guilherme Gomes edited comment on DROOLS-4364 at 7/26/19 4:20 PM:
------------------------------------------------------------------
[~mmenestr],
I already created an engineering JIRA for this [here|https://issues.jboss.org/browse/DROOLS-4355].
So, I've updated the description there, and I'm closing this one.
was (Author: karreiro):
[~mmenestr],
I already created an engineering JIRA for this [here|https://issues.jboss.org/browse/DROOLS-4355].
So, I've updated the description there, and I'm closing this one.
> [DMN Designer] Download buttons UX (Development task)
> -----------------------------------------------------
>
> Key: DROOLS-4364
> URL: https://issues.jboss.org/browse/DROOLS-4364
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Margot Menestrot
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: component-1.png, component-2.png, component-3.png
>
>
> h3. Need to update the DMN toolbar download buttons based on the context described in initial issue.
> Implementation suggestions can be found in this slide deck. https://docs.google.com/presentation/d/1uq3DZ95LWODhmdL8p9A-xaw8sufe3lBVC...
> Suggestions are as follows:
> 1. Remove download button that appears as icon dropdown, and leave the Download button that appears spelt out.
> 2. Make that download button a drop down meny that includes all possible downloading options, separated into two parts - download DMN model and download documentation.
> 3. Remove download button in the documentation sub tab (that appears on top right of documentation example) to avoid repetition, and just leave the print button there.
> ---------------
> h3. Context:
> Today users can:
> 1) Download the diagram picture by using this component:
> !component-1.png|thumbnail!
> 2) Download the DMN file by using this component:
> !component-2.png|thumbnail!
> 3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab):
> !component-3.png|thumbnail!
> 4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab):
> !component-3.png|thumbnail!
> ----
> h3. Problem:
> The "Download" concept is getting confusing for users.
> As a user, I want to be able to:
> - Download the documentation as a .PDF file
> - Download the documentation as a .DOC file
> - Print the documentation
> ----
> h3. Notice:
> This component can be removed (if UX considers that it's necessary):
> !component-1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4364) [DMN Designer] Download buttons UX (Development task)
by Guilherme Gomes (Jira)
[ https://issues.jboss.org/browse/DROOLS-4364?page=com.atlassian.jira.plugi... ]
Guilherme Gomes closed DROOLS-4364.
-----------------------------------
Resolution: Done
> [DMN Designer] Download buttons UX (Development task)
> -----------------------------------------------------
>
> Key: DROOLS-4364
> URL: https://issues.jboss.org/browse/DROOLS-4364
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Margot Menestrot
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: component-1.png, component-2.png, component-3.png
>
>
> h3. Need to update the DMN toolbar download buttons based on the context described in initial issue.
> Implementation suggestions can be found in this slide deck. https://docs.google.com/presentation/d/1uq3DZ95LWODhmdL8p9A-xaw8sufe3lBVC...
> Suggestions are as follows:
> 1. Remove download button that appears as icon dropdown, and leave the Download button that appears spelt out.
> 2. Make that download button a drop down meny that includes all possible downloading options, separated into two parts - download DMN model and download documentation.
> 3. Remove download button in the documentation sub tab (that appears on top right of documentation example) to avoid repetition, and just leave the print button there.
> ---------------
> h3. Context:
> Today users can:
> 1) Download the diagram picture by using this component:
> !component-1.png|thumbnail!
> 2) Download the DMN file by using this component:
> !component-2.png|thumbnail!
> 3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab):
> !component-3.png|thumbnail!
> 4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab):
> !component-3.png|thumbnail!
> ----
> h3. Problem:
> The "Download" concept is getting confusing for users.
> As a user, I want to be able to:
> - Download the documentation as a .PDF file
> - Download the documentation as a .DOC file
> - Print the documentation
> ----
> h3. Notice:
> This component can be removed (if UX considers that it's necessary):
> !component-1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4364) [DMN Designer] Download buttons UX (Development task)
by Guilherme Gomes (Jira)
[ https://issues.jboss.org/browse/DROOLS-4364?page=com.atlassian.jira.plugi... ]
Guilherme Gomes commented on DROOLS-4364:
-----------------------------------------
[~mmenestr],
I already created an engineering JIRA for this [here|https://issues.jboss.org/browse/DROOLS-4355].
So, I've updated the description there, and I'm closing this one.
> [DMN Designer] Download buttons UX (Development task)
> -----------------------------------------------------
>
> Key: DROOLS-4364
> URL: https://issues.jboss.org/browse/DROOLS-4364
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Margot Menestrot
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: component-1.png, component-2.png, component-3.png
>
>
> h3. Need to update the DMN toolbar download buttons based on the context described in initial issue.
> Implementation suggestions can be found in this slide deck. https://docs.google.com/presentation/d/1uq3DZ95LWODhmdL8p9A-xaw8sufe3lBVC...
> Suggestions are as follows:
> 1. Remove download button that appears as icon dropdown, and leave the Download button that appears spelt out.
> 2. Make that download button a drop down meny that includes all possible downloading options, separated into two parts - download DMN model and download documentation.
> 3. Remove download button in the documentation sub tab (that appears on top right of documentation example) to avoid repetition, and just leave the print button there.
> ---------------
> h3. Context:
> Today users can:
> 1) Download the diagram picture by using this component:
> !component-1.png|thumbnail!
> 2) Download the DMN file by using this component:
> !component-2.png|thumbnail!
> 3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab):
> !component-3.png|thumbnail!
> 4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab):
> !component-3.png|thumbnail!
> ----
> h3. Problem:
> The "Download" concept is getting confusing for users.
> As a user, I want to be able to:
> - Download the documentation as a .PDF file
> - Download the documentation as a .DOC file
> - Print the documentation
> ----
> h3. Notice:
> This component can be removed (if UX considers that it's necessary):
> !component-1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4364) [DMN Designer] Download buttons UX (Development task)
by Guilherme Gomes (Jira)
[ https://issues.jboss.org/browse/DROOLS-4364?page=com.atlassian.jira.plugi... ]
Guilherme Gomes updated DROOLS-4364:
------------------------------------
Sprint: (was: 2019 Week 29-31)
> [DMN Designer] Download buttons UX (Development task)
> -----------------------------------------------------
>
> Key: DROOLS-4364
> URL: https://issues.jboss.org/browse/DROOLS-4364
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Margot Menestrot
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: component-1.png, component-2.png, component-3.png
>
>
> h3. Need to update the DMN toolbar download buttons based on the context described in initial issue.
> Implementation suggestions can be found in this slide deck. https://docs.google.com/presentation/d/1uq3DZ95LWODhmdL8p9A-xaw8sufe3lBVC...
> Suggestions are as follows:
> 1. Remove download button that appears as icon dropdown, and leave the Download button that appears spelt out.
> 2. Make that download button a drop down meny that includes all possible downloading options, separated into two parts - download DMN model and download documentation.
> 3. Remove download button in the documentation sub tab (that appears on top right of documentation example) to avoid repetition, and just leave the print button there.
> ---------------
> h3. Context:
> Today users can:
> 1) Download the diagram picture by using this component:
> !component-1.png|thumbnail!
> 2) Download the DMN file by using this component:
> !component-2.png|thumbnail!
> 3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab):
> !component-3.png|thumbnail!
> 4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab):
> !component-3.png|thumbnail!
> ----
> h3. Problem:
> The "Download" concept is getting confusing for users.
> As a user, I want to be able to:
> - Download the documentation as a .PDF file
> - Download the documentation as a .DOC file
> - Print the documentation
> ----
> h3. Notice:
> This component can be removed (if UX considers that it's necessary):
> !component-1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4355) [DMN Designer] Implement new UX for downloading model assets
by Guilherme Gomes (Jira)
[ https://issues.jboss.org/browse/DROOLS-4355?page=com.atlassian.jira.plugi... ]
Guilherme Gomes updated DROOLS-4355:
------------------------------------
Description:
Fix *_Download buttons_* UX following these guidelines: https://issues.jboss.org/browse/DROOLS-4315
Implementation suggestions can be found in this slide deck. https://docs.google.com/presentation/d/1uq3DZ95LWODhmdL8p9A-xaw8sufe3lBVC...
UX suggestions are as follows:
1. Remove download button that appears as icon dropdown, and leave the Download button that appears spelt out.
2. Make that download button a drop down meny that includes all possible downloading options, separated into two parts - download DMN model and download documentation.
3. Remove download button in the documentation sub tab (that appears on top right of documentation example) to avoid repetition, and just leave the print button there.
---------------
h3. Context:
Today users can:
1) Download the diagram picture by using this component:
!component-1.png|thumbnail!
2) Download the DMN file by using this component:
!component-2.png|thumbnail!
3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab):
!component-3.png|thumbnail!
4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab):
!component-3.png|thumbnail!
----
h3. Problem:
The "Download" concept is getting confusing for users.
As a user, I want to be able to:
- Download the documentation as a .PDF file
- Download the documentation as a .DOC file
- Print the documentation
----
h3. Notice:
This component can be removed (if UX considers that it's necessary):
!component-1.png|thumbnail!
was:
Fix *_Download buttons_* UX following these guidelines: https://issues.jboss.org/browse/DROOLS-4315
This JIRA comprehends the following tasks:
- Remove stunner default download button;
- Remove KIE editor default download button;
- Create the the new download button following UX input;
- Remove the Documentation download button.
> [DMN Designer] Implement new UX for downloading model assets
> ------------------------------------------------------------
>
> Key: DROOLS-4355
> URL: https://issues.jboss.org/browse/DROOLS-4355
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: component-1.png, component-2.png, component-3.png
>
>
> Fix *_Download buttons_* UX following these guidelines: https://issues.jboss.org/browse/DROOLS-4315
> Implementation suggestions can be found in this slide deck. https://docs.google.com/presentation/d/1uq3DZ95LWODhmdL8p9A-xaw8sufe3lBVC...
> UX suggestions are as follows:
> 1. Remove download button that appears as icon dropdown, and leave the Download button that appears spelt out.
> 2. Make that download button a drop down meny that includes all possible downloading options, separated into two parts - download DMN model and download documentation.
> 3. Remove download button in the documentation sub tab (that appears on top right of documentation example) to avoid repetition, and just leave the print button there.
> ---------------
> h3. Context:
> Today users can:
> 1) Download the diagram picture by using this component:
> !component-1.png|thumbnail!
> 2) Download the DMN file by using this component:
> !component-2.png|thumbnail!
> 3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab):
> !component-3.png|thumbnail!
> 4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab):
> !component-3.png|thumbnail!
> ----
> h3. Problem:
> The "Download" concept is getting confusing for users.
> As a user, I want to be able to:
> - Download the documentation as a .PDF file
> - Download the documentation as a .DOC file
> - Print the documentation
> ----
> h3. Notice:
> This component can be removed (if UX considers that it's necessary):
> !component-1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4355) [DMN Designer] Implement new UX for downloading model assets
by Guilherme Gomes (Jira)
[ https://issues.jboss.org/browse/DROOLS-4355?page=com.atlassian.jira.plugi... ]
Guilherme Gomes updated DROOLS-4355:
------------------------------------
Attachment: component-3.png
component-2.png
component-1.png
> [DMN Designer] Implement new UX for downloading model assets
> ------------------------------------------------------------
>
> Key: DROOLS-4355
> URL: https://issues.jboss.org/browse/DROOLS-4355
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: component-1.png, component-2.png, component-3.png
>
>
> Fix *_Download buttons_* UX following these guidelines: https://issues.jboss.org/browse/DROOLS-4315
> Implementation suggestions can be found in this slide deck. https://docs.google.com/presentation/d/1uq3DZ95LWODhmdL8p9A-xaw8sufe3lBVC...
> UX suggestions are as follows:
> 1. Remove download button that appears as icon dropdown, and leave the Download button that appears spelt out.
> 2. Make that download button a drop down meny that includes all possible downloading options, separated into two parts - download DMN model and download documentation.
> 3. Remove download button in the documentation sub tab (that appears on top right of documentation example) to avoid repetition, and just leave the print button there.
> ---------------
> h3. Context:
> Today users can:
> 1) Download the diagram picture by using this component:
> !component-1.png|thumbnail!
> 2) Download the DMN file by using this component:
> !component-2.png|thumbnail!
> 3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab):
> !component-3.png|thumbnail!
> 4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab):
> !component-3.png|thumbnail!
> ----
> h3. Problem:
> The "Download" concept is getting confusing for users.
> As a user, I want to be able to:
> - Download the documentation as a .PDF file
> - Download the documentation as a .DOC file
> - Print the documentation
> ----
> h3. Notice:
> This component can be removed (if UX considers that it's necessary):
> !component-1.png|thumbnail!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4372) DMN Editor Data type usability study: design assets
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-4372?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton updated DROOLS-4372:
--------------------------------------
Description:
Description:
* Create a study plan outline.
* Review usability study materials.
* Create a click-thru wireframe prototype for a lightweight usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types.
was:
Lightweight usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types.
GOALS: Access the Data Type editor in terms of productivity and usability.
* Ease of use when creating a complex type (concern: minimizing the mouse usage.)
* Ease of use when saving a basic data type (e.g. age: number)
* Discoverability of actions in the kebab menu, especially, insert nested, delete.
* Ease of use/accuracy: Type-ahead of the data type selector.
> DMN Editor Data type usability study: design assets
> ---------------------------------------------------
>
> Key: DROOLS-4372
> URL: https://issues.jboss.org/browse/DROOLS-4372
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Environment: Version 7.4
> Reporter: Elizabeth Clayton
> Assignee: Elizabeth Clayton
> Priority: Major
> Labels: UX, UXTeam, Usability, drools-tools
>
> Description:
> * Create a study plan outline.
> * Review usability study materials.
> * Create a click-thru wireframe prototype for a lightweight usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months