[jboss-jira] [JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI

[Jozef Marko (Jira)]

     [ https://issues.jboss.org/browse/DROOLS-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jozef Marko updated DROOLS-4694:
--------------------------------
    Description: 
Consume the service provided by DROOLS-4680 and create Data Types in the UI.

⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.

h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels (/) acceptance criteria updated
- Class B extends Class A (/)
- Classes added as dependencies (x) we do not follow acceptance criteria
- Classes from different package than dmn (/)
- Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-552776488] RHDM-1144
- simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-552783105] RHDM-1145
- static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-552784229], decided to nor report
- Import, rename original java class, import again (/)
- Import, delete import, import (/)
- Import, add field  in original java class, import (/)
- Import, change field type in original class, import (/)
- Import, import (/)
- Import, pick also types needed for fields (/)
- Import, do not pick types needed for fields (x)  [^do-not-pick-fields.webm] , (/) works in re-review
- Use imported type in dmn, test scenario (/)

  was:
Consume the service provided by DROOLS-4680 and create Data Types in the UI.

⚠️ Notice:
- Respect the nesting logic
- Use the data types manager for creating type (just like the "Add" button)
- The new data types must be added in the end of the list
- If a Data Type with the same name already exists, remove it, and add the new one.

h2. Manual Scenarios
- No fields in data object (/)
- Nested data objects, more than 5 levels (/) acceptance criteria updated
- Class B extends Class A (/)
- Classes added as dependencies (x) we do not follow acceptance criteria
- Classes from different package than dmn (/)
- Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-552776488]
- simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-552783105]
- static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-552784229]
- Import, rename original java class, import again (/)
- Import, delete import, import (/)
- Import, add field  in original java class, import (/)
- Import, change field type in original class, import (/)
- Import, import (/)
- Import, pick also types needed for fields (/)
- Import, do not pick types needed for fields (x)  [^do-not-pick-fields.webm] 
- Use imported type in dmn, test scenario (/)



> [DMN Designer] BC DOs as DMN DTs - Create import action into the UI
> -------------------------------------------------------------------
>
>                 Key: DROOLS-4694
>                 URL: https://issues.jboss.org/browse/DROOLS-4694
>             Project: Drools
>          Issue Type: Task
>          Components: DMN Editor
>            Reporter: Guilherme Gomes
>            Assignee: Daniel José dos Santos
>            Priority: Major
>              Labels: drools-tools
>         Attachments: convert-15-fields.webm, do-not-pick-fields.webm
>
>
> Consume the service provided by DROOLS-4680 and create Data Types in the UI.
> ⚠️ Notice:
> - Respect the nesting logic
> - Use the data types manager for creating type (just like the "Add" button)
> - The new data types must be added in the end of the list
> - If a Data Type with the same name already exists, remove it, and add the new one.
> h2. Manual Scenarios
> - No fields in data object (/)
> - Nested data objects, more than 5 levels (/) acceptance criteria updated
> - Class B extends Class A (/)
> - Classes added as dependencies (x) we do not follow acceptance criteria
> - Classes from different package than dmn (/)
> - Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-552776488] RHDM-1144
> - simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-552783105] RHDM-1145
> - static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-552784229], decided to nor report
> - Import, rename original java class, import again (/)
> - Import, delete import, import (/)
> - Import, add field  in original java class, import (/)
> - Import, change field type in original class, import (/)
> - Import, import (/)
> - Import, pick also types needed for fields (/)
> - Import, do not pick types needed for fields (x)  [^do-not-pick-fields.webm] , (/) works in re-review
> - Use imported type in dmn, test scenario (/)



--
This message was sent by Atlassian Jira
(v7.13.8#713008)