You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When exporting a CApp, there is a view to select what you should include to the CApp. When an integration project is considered, there can be aa lot of artifacts coming from registry, datasources, and config project. See the screenshot below.
Describe your problem(s)
The list is large. Every artefact has integration name prefixed. Thus, it is hard to find if a particular artefact is included or not. I think, if we can have a search capability here, it will be better.
Furthermore, this view cannot be extended. It always appears as a small box when exporting, making it hard to navigate.
Another spect to consider is, when I am exporting CApp for project X , why it is showing all the artifacts in project Y and Z? If we can get rid of them this view will be cleaner.
Description
When exporting a CApp, there is a view to select what you should include to the CApp. When an integration project is considered, there can be aa lot of artifacts coming from registry, datasources, and config project. See the screenshot below.
Describe your problem(s)
The list is large. Every artefact has integration name prefixed. Thus, it is hard to find if a particular artefact is included or not. I think, if we can have a search capability here, it will be better.
Furthermore, this view cannot be extended. It always appears as a small box when exporting, making it hard to navigate.
Another spect to consider is, when I am exporting CApp for project X , why it is showing all the artifacts in project Y and Z? If we can get rid of them this view will be cleaner.
Describe your solution(s)
No response
Related issue(s) (optional)
https://github.com/wso2-enterprise/wso2-mi-internal/issues/707
Suggested label(s) (optional)
version 8.2.0
Environment : Windows
Suggested assignee(s) (optional)
No response
The text was updated successfully, but these errors were encountered: