Bug 1037525

Summary: Data modeller should use an import widget for the imports
Product: [Retired] JBoss BRMS Platform 6 Reporter: Toni Rikkola <trikkola>
Component: Business CentralAssignee: manstis
Status: CLOSED CURRENTRELEASE QA Contact: Tomas David <tdavid>
Severity: low Docs Contact:
Priority: medium    
Version: 6.0.0CC: etirelli, manstis, mwinkler
Target Milestone: ER6   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:19:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Toni Rikkola 2013-12-03 10:29:28 UTC 
Description of problem:

Import suggestions should not be automatically imported to any screen. The route for importing (at this point) is:
Add to Import Suggestions
Add to editor's imports widget
The import shows up in the dropdowns.
Comment 3 Pedro Zapata 2013-12-03 13:55:22 UTC 
What is exactly an import widget? Is that a new type of widget that needs to be integrated?
Comment 4 Toni Rikkola 2013-12-04 07:34:46 UTC 
You can see import widget for example in the Guided Rule Editor. In the tabs that are in the bottom of the editor.

It simply lists the imports that the editor has. Each import in asset imports is usable in the editor dropdowns.
Comment 5 manstis 2013-12-04 17:06:13 UTC 
I'm investigating a fix to the underlying problem that lead to this BZ being raized that may not need any changes to Data Modeller itself. I'll assign this BZ to me.
Comment 6 manstis 2013-12-04 19:01:25 UTC 
This BZ was raised because "Import Suggestions" were appearing as classes in Data Modeller. The proposal was for them to be removed and Data Modeller have to import classes in "Import Suggestions". 

However upon examination "external" classes that are listed in "Import Suggestions" were being added to the DMO incorrectly. I have fixed that - so such classes are now shown as "external" and do not appear in the list of classes (but can still be used as a field type etc).

I believe this covers the issue for which this BZ was raised.
Comment 8 Tomas David 2014-01-16 14:02:01 UTC 
Verified on BRMS 6.0.0.ER7.