[JBoss JIRA] (DROOLS-3024) [DMN Designer] Data Types - Add nested data types
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3024?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3024:
--------------------------------
Description:
- The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu:
!options.png|thumbnail!
h2. Manual Acceptance Test
h3. Insert above
- on top level
- on the nested level
- on the deepest level
- no warning in browser console
h3. Insert below
- on top level
- on the nested level
- on the deepest level
- no warning in browser console
h3. Insert nested
- on top level
- on the nested level
- on the deepest level
- no warning in browser console
h3. Build and deploy
- Build and deploy model that uses new created data type
was:
- The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu:
!options.png|thumbnail!
h2. Manual Acceptance Test
h3. Insert above
- on top level
- on the nested level
- on the deepest level
- no warning in browser console
h3. Insert below
- on top level
- on the nested level
- on the deepest level
- no warning in browser console
h3. Insert nested
- on top level
- on the nested level
- on the deepest level
- no warning in browser console
h3. Build and deploy
- Build and deploy model that uses new created data type
> [DMN Designer] Data Types - Add nested data types
> -------------------------------------------------
>
> Key: DROOLS-3024
> URL: https://issues.jboss.org/browse/DROOLS-3024
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: options.png
>
>
> - The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu:
> !options.png|thumbnail!
> h2. Manual Acceptance Test
> h3. Insert above
> - on top level
> - on the nested level
> - on the deepest level
> - no warning in browser console
> h3. Insert below
> - on top level
> - on the nested level
> - on the deepest level
> - no warning in browser console
> h3. Insert nested
> - on top level
> - on the nested level
> - on the deepest level
> - no warning in browser console
> h3. Build and deploy
> - Build and deploy model that uses new created data type
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3024) [DMN Designer] Data Types - Add nested data types
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3024?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3024:
--------------------------------
Description:
- The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu:
!options.png|thumbnail!
h2. Manual Acceptance Test
h3. Insert above
- on top level
- on the nested level
- on the deepest level
- no warning in browser console
h3. Insert below
- on top level
- on the nested level
- on the deepest level
- no warning in browser console
h3. Insert nested
- on top level
- on the nested level
- on the deepest level
- no warning in browser console
was:
- The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu:
!options.png|thumbnail!
> [DMN Designer] Data Types - Add nested data types
> -------------------------------------------------
>
> Key: DROOLS-3024
> URL: https://issues.jboss.org/browse/DROOLS-3024
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: options.png
>
>
> - The user must be able to insert a new field (Data Type) above, below and nested, as the options listed in the kebab menu:
> !options.png|thumbnail!
> h2. Manual Acceptance Test
> h3. Insert above
> - on top level
> - on the nested level
> - on the deepest level
> - no warning in browser console
> h3. Insert below
> - on top level
> - on the nested level
> - on the deepest level
> - no warning in browser console
> h3. Insert nested
> - on top level
> - on the nested level
> - on the deepest level
> - no warning in browser console
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3022) [DMN Designer] Data Types - Validations - Validate the uniqueness of a Data Type name
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3022?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3022:
--------------------------------
Description:
The Data Type name must be unique at the level that it's defined; e.g.
- tPerson
-- uuid
-- name
-- city (Structure)
--- uuid
--- name
The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels.
----
Prototype:
!validation.png|thumbnail!
h2. Manaul Acceptance Test
Try to put same name by
- Typing
- Copy and paste
- Do not allow empty name
- Allow spaces in name
- Allow multibyte chars in name
- Allow special characters in name (?)
- Allow lower upper case in name
was:
The Data Type name must be unique at the level that it's defined; e.g.
- tPerson
-- uuid
-- name
-- city (Structure)
--- uuid
--- name
The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels.
----
Prototype:
!validation.png|thumbnail!
> [DMN Designer] Data Types - Validations - Validate the uniqueness of a Data Type name
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-3022
> URL: https://issues.jboss.org/browse/DROOLS-3022
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: validation.png
>
>
> The Data Type name must be unique at the level that it's defined; e.g.
> - tPerson
> -- uuid
> -- name
> -- city (Structure)
> --- uuid
> --- name
> The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels.
> ----
> Prototype:
> !validation.png|thumbnail!
> h2. Manaul Acceptance Test
> Try to put same name by
> - Typing
> - Copy and paste
> - Do not allow empty name
> - Allow spaces in name
> - Allow multibyte chars in name
> - Allow special characters in name (?)
> - Allow lower upper case in name
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3022) [DMN Designer] Data Types - Validations - Validate the uniqueness of a Data Type name
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3022?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3022:
--------------------------------
Description:
The Data Type name must be unique at the level that it's defined; e.g.
- tPerson
-- uuid
-- name
-- city (Structure)
--- uuid
--- name
The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels.
----
Prototype:
!validation.png|thumbnail!
h2. Manaul Acceptance Test
- Try to put same name by Typing
- Try to put same name by Copy and paste
- Do not allow empty name
- Allow spaces in name
- Allow multibyte chars in name
- Allow special characters in name (?)
- Allow lower upper case in name
was:
The Data Type name must be unique at the level that it's defined; e.g.
- tPerson
-- uuid
-- name
-- city (Structure)
--- uuid
--- name
The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels.
----
Prototype:
!validation.png|thumbnail!
h2. Manaul Acceptance Test
Try to put same name by
- Typing
- Copy and paste
- Do not allow empty name
- Allow spaces in name
- Allow multibyte chars in name
- Allow special characters in name (?)
- Allow lower upper case in name
> [DMN Designer] Data Types - Validations - Validate the uniqueness of a Data Type name
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-3022
> URL: https://issues.jboss.org/browse/DROOLS-3022
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: validation.png
>
>
> The Data Type name must be unique at the level that it's defined; e.g.
> - tPerson
> -- uuid
> -- name
> -- city (Structure)
> --- uuid
> --- name
> The Data Type above is valid, because _tPerson.uuid_ and _tPerson.city.uuid_ are in different levels.
> ----
> Prototype:
> !validation.png|thumbnail!
> h2. Manaul Acceptance Test
> - Try to put same name by Typing
> - Try to put same name by Copy and paste
> - Do not allow empty name
> - Allow spaces in name
> - Allow multibyte chars in name
> - Allow special characters in name (?)
> - Allow lower upper case in name
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3025) [DMN Designer] Data Types - Set a Data Type as a collection Data Type
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3025?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3025:
--------------------------------
Description:
- A Data Type must be set as a collection data type;
- Interaction:
!interaction.gif|thumbnail!
- When edit mode is closed, it should show "✔ Yes" for a collection data type and none for a non-collection data type:
!edit-mode-closed.png|thumbnail!
- PatternFly base element for the switch button https://www.patternfly.org/pattern-library/widgets/#bootstrap-switch
h2. Manual acceptance test
- Construct top level item definition
- Use in other structure as list
- Build and deploy
- Interact with kie-server
was:
- A Data Type must be set as a collection data type;
- Interaction:
!interaction.gif|thumbnail!
- When edit mode is closed, it should show "✔ Yes" for a collection data type and none for a non-collection data type:
!edit-mode-closed.png|thumbnail!
- PatternFly base element for the switch button https://www.patternfly.org/pattern-library/widgets/#bootstrap-switch
> [DMN Designer] Data Types - Set a Data Type as a collection Data Type
> ---------------------------------------------------------------------
>
> Key: DROOLS-3025
> URL: https://issues.jboss.org/browse/DROOLS-3025
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: edit-mode-closed.png, interaction.gif
>
>
> - A Data Type must be set as a collection data type;
> - Interaction:
> !interaction.gif|thumbnail!
> - When edit mode is closed, it should show "✔ Yes" for a collection data type and none for a non-collection data type:
> !edit-mode-closed.png|thumbnail!
> - PatternFly base element for the switch button https://www.patternfly.org/pattern-library/widgets/#bootstrap-switch
> h2. Manual acceptance test
> - Construct top level item definition
> - Use in other structure as list
> - Build and deploy
> - Interact with kie-server
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3023) [DMN Designer] Data Types - Warnings - User must be warned when some operations affect other Data Types
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3023?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3023:
--------------------------------
Description:
1) When a Structure Data Type (with fields) is updated to a simple type (e.g. String, Number, Date, etc), a warn message must appear informing the user that the fields will be lost.
- tPerson
-- uuid
-- name
-- city (Structure) <-- If this data type is updated to "String", the "uuid" and "name" fields will be lost.
--- uuid
--- name
----
2) When a Data Type is removed, a warn message must appear informing the user that data types with the removed type will be removed too.
- tCity <-- If the user removes this Data Type
-- uuid
-- name
- tPerson
-- uuid
-- name
-- city (tCity) <-- This field will be removed too..
--- uuid <-- ..and consequently..
--- name <-- ..these two will be removed too.
h2. Manual acceptance test
Check warning list all occurrences:
- Remove item definition used as part of other item definitions
-- Top level, all occurences removed
-- Nested level, top level definition remains
- Remove item definitions used as output data-type for decision node
- Remove item definition used as data-type for expression element (column, parameter, ...)
was:
1) When a Structure Data Type (with fields) is updated to a simple type (e.g. String, Number, Date, etc), a warn message must appear informing the user that the fields will be lost.
- tPerson
-- uuid
-- name
-- city (Structure) <-- If this data type is updated to "String", the "uuid" and "name" fields will be lost.
--- uuid
--- name
----
2) When a Data Type is removed, a warn message must appear informing the user that data types with the removed type will be removed too.
- tCity <-- If the user removes this Data Type
-- uuid
-- name
- tPerson
-- uuid
-- name
-- city (tCity) <-- This field will be removed too..
--- uuid <-- ..and consequently..
--- name <-- ..these two will be removed too.
> [DMN Designer] Data Types - Warnings - User must be warned when some operations affect other Data Types
> -------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3023
> URL: https://issues.jboss.org/browse/DROOLS-3023
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
>
> 1) When a Structure Data Type (with fields) is updated to a simple type (e.g. String, Number, Date, etc), a warn message must appear informing the user that the fields will be lost.
> - tPerson
> -- uuid
> -- name
> -- city (Structure) <-- If this data type is updated to "String", the "uuid" and "name" fields will be lost.
> --- uuid
> --- name
> ----
> 2) When a Data Type is removed, a warn message must appear informing the user that data types with the removed type will be removed too.
> - tCity <-- If the user removes this Data Type
> -- uuid
> -- name
> - tPerson
> -- uuid
> -- name
> -- city (tCity) <-- This field will be removed too..
> --- uuid <-- ..and consequently..
> --- name <-- ..these two will be removed too.
> h2. Manual acceptance test
> Check warning list all occurrences:
> - Remove item definition used as part of other item definitions
> -- Top level, all occurences removed
> -- Nested level, top level definition remains
> - Remove item definitions used as output data-type for decision node
> - Remove item definition used as data-type for expression element (column, parameter, ...)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (DROOLS-3023) [DMN Designer] Data Types - Warnings - User must be warned when some operations affect other Data Types
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3023?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-3023:
--------------------------------
Tester: Jozef Marko
> [DMN Designer] Data Types - Warnings - User must be warned when some operations affect other Data Types
> -------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3023
> URL: https://issues.jboss.org/browse/DROOLS-3023
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
>
> 1) When a Structure Data Type (with fields) is updated to a simple type (e.g. String, Number, Date, etc), a warn message must appear informing the user that the fields will be lost.
> - tPerson
> -- uuid
> -- name
> -- city (Structure) <-- If this data type is updated to "String", the "uuid" and "name" fields will be lost.
> --- uuid
> --- name
> ----
> 2) When a Data Type is removed, a warn message must appear informing the user that data types with the removed type will be removed too.
> - tCity <-- If the user removes this Data Type
> -- uuid
> -- name
> - tPerson
> -- uuid
> -- name
> -- city (tCity) <-- This field will be removed too..
> --- uuid <-- ..and consequently..
> --- name <-- ..these two will be removed too.
> h2. Manual acceptance test
> Check warning list all occurrences:
> - Remove item definition used as part of other item definitions
> -- Top level, all occurences removed
> -- Nested level, top level definition remains
> - Remove item definitions used as output data-type for decision node
> - Remove item definition used as data-type for expression element (column, parameter, ...)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months