Skip to content

Allow to install missing contributions during app import #509

Open
@fcastill

Description

@fcastill

I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[X] feature request
[ ] support request

Current behavior
When importing an app if the app references an activity or trigger that is not currently installed in the flogo instance then the import is rejected.

Even though the missing contributions are listed as import errors you need to manually go back and install them one by one.

The feature to install a new activity is hard to find when you're in a context different from the flow designer because you have to open an existing flow and then click on installing an activity.

The feature to install a trigger is even harder to find because you can only do it from an empty flow, even though this will be mitigated by #501.

Expected behavior
When importing an app if the app references contributions that are not installed yet in the flogo instance then the UI can detect them and prompt for confirmation to the user to install them automatically.

What is the motivation / use case for changing the behavior?
Better user experience for importing apps and installing contributions.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions