Syndesis: Autosave

[gaughan]

See also https://issues.jboss.org/browse/ENTESB-11533

As a citizen integrator, I want to have my environment autosave.

DoD

• No save buttons are required/present.
• I can partially complete a connector or integration and come back to it later to complete.
• Standard names for entries are applied such as ‘Untitled Connector’, ‘Untitled Connector1’ etc
• The feature owner has confirmed one of the following:
  --There is an initial draft of the user doc for this feature.
  --The writer acknowledges receiving enough information from engineering to write the initial draft of the user doc for this feature.

[amysueg]

Goal:
The user will not need to manage the saved states of connections/integrations.

Questions:
How soon would "autosave" action kick in during creation of an integration? As soon as the user enters any data.
What is the impact on the idea of having just a single draft (current implementation)?
Autosave would save a draft; the user can leave, come back and continue the same draft. There is just one draft per integration.
User actions (leaving a field, eg) trigger the autosave. Need to determine what those are.

Split autosave connection and autosave integration into separate issues. There are more considerations for connection (wizard flow); if in a draft state, it probably shouldn't be able to be used in an integration; there is no draft state for connection yet.

[gashcrumb]

I would think basically any completed page flow through an integration
would be saved, i.e. whenever wind up at that 'save or add step' page for
starters would be a good point to automatically save the integration.

On Tue, Jul 17, 2018 at 3:51 PM, Amy Glass [e-mail] wrote:

Goal:
The user will not need to manage the saved states of
connections/integrations.

Questions:
How soon would "autosave" action kick in during creation of an
integration? As soon as the user enters any data.
What is the impact on the idea of having just a single draft (current
implementation)?
Autosave would save a draft; the user can leave, come back and continue
the same draft. There is just one draft per integration.
User actions (leaving a field, eg) trigger the autosave. Need to determine
what those are.

Split autosave connection and autosave integration into separate issues.
There are more considerations for connection (wizard flow); if in a draft
state, it probably shouldn't be able to be used in an integration; there is
no draft state for connection yet.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/syndesisio/syndesis/issues/3048#issuecomment-405706016,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVdrApK-UCl7Rodk_OHVa3qCk05XgCBks5uHkBDgaJpZM4VLpvd
.

[stale[bot]]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[stale[bot]]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[stale[bot]]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[zregvart]

@gaughan there I fixed it for you

[gaughan]

We need to talk about what defines a fix :)

[heiko-braun]

Migrated to https://issues.jboss.org/browse/ENTESB-11533