[JBoss JIRA] (DROOLS-3482) Terminology for DMN import
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-3482?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-3482:
---------------------------------------
I still think "models" in this case is better than "artifacts" or "assets", but assets would be my second choice, since we call a "file" in the project and asset, and we call the compiled project an artifact.
> Terminology for DMN import
> --------------------------
>
> Key: DROOLS-3482
> URL: https://issues.jboss.org/browse/DROOLS-3482
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Stetson Robinson
> Priority: Minor
> Labels: drools-tools
>
> Define best term to use for importing a DMN file, from the project directory. Importing a .dmn file will include file nodes, data types, etc. The term will be used for a tab label, button labels, and the like.
> UX mockups currently use "import" but other terms such as "include" have been discussed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3455:
--------------------------------
Attachment: range-redo3.png
> Data type constraints: Year/Mos Duration
> ----------------------------------------
>
> Key: DROOLS-3455
> URL: https://issues.jboss.org/browse/DROOLS-3455
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: enumeration.png, expression.png, range-redo3.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3455:
--------------------------------
Attachment: (was: range-redo.png)
> Data type constraints: Year/Mos Duration
> ----------------------------------------
>
> Key: DROOLS-3455
> URL: https://issues.jboss.org/browse/DROOLS-3455
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: enumeration.png, expression.png, range-redo3.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3455:
--------------------------------
Attachment: (was: range-redo2.png)
> Data type constraints: Year/Mos Duration
> ----------------------------------------
>
> Key: DROOLS-3455
> URL: https://issues.jboss.org/browse/DROOLS-3455
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: enumeration.png, expression.png, range-redo3.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration
by Guilherme Carreiro (Jira)
[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro commented on DROOLS-3455:
--------------------------------------------
[~uxdlc] Looks great to me. Regarding the placeholders, could we use a value as example, or even zero? Just a personal opinion, the current version looks great :-)
> Data type constraints: Year/Mos Duration
> ----------------------------------------
>
> Key: DROOLS-3455
> URL: https://issues.jboss.org/browse/DROOLS-3455
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: enumeration.png, expression.png, range-redo.png, range-redo2.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3455:
--------------------------------
Attachment: range-redo2.png
> Data type constraints: Year/Mos Duration
> ----------------------------------------
>
> Key: DROOLS-3455
> URL: https://issues.jboss.org/browse/DROOLS-3455
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: enumeration.png, expression.png, range-redo.png, range-redo2.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3455:
--------------------------------
Attachment: (was: enumeration.png)
> Data type constraints: Year/Mos Duration
> ----------------------------------------
>
> Key: DROOLS-3455
> URL: https://issues.jboss.org/browse/DROOLS-3455
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: expression.png, range-redo.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months
[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3455:
--------------------------------
Attachment: enumeration.png
> Data type constraints: Year/Mos Duration
> ----------------------------------------
>
> Key: DROOLS-3455
> URL: https://issues.jboss.org/browse/DROOLS-3455
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: enumeration.png, expression.png, range-redo.png
>
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.)
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 3 months