Delay organisation confirmation page until a new service has been added.

[Mike-Heneghan]

At the moment users add their Organisation but often seem not to progress to the next step and add their first service.

To try to improve the workflow it might be best to delay the Organisation confirmation page until after a user has had the chance to add a new service. Then both confirmations can be done. This would mostly involve redirects rather than fundamental changes.

[Mike-Heneghan]

[Mike-Heneghan]

At the moment the organisation create view redirects to the organisation_confirm although for this change in the workflow it would need to link to service_create which would then redirect to organisation_confirm.

[Mike-Heneghan]

Now adding an new org redirects to add a service_create which then redirects to organisation_detail.

We need a way of knowing a organisation confirmation page hasn't been hit before so it should redirect back there first.

[Mike-Heneghan]

With automatically going straight to add a service after adding an organisation the confirmation page doesn't seem as relevant? Or at least we need a more dynamically generated one.

[Mike-Heneghan]

Also, we need a way to check that the organisation hasn't just been created.

Maybe we could count the number of services? Rather than redirecting to the organisation detail page if it's the first service regardless of organisation age, we could redirect to an updated confirm view.

Hey @digitalwestie, I've got a few ideas of how we could redesign the workflow but it would be good to discuss them before I crack on.

[Mike-Heneghan]

As the organisation confirmation is no longer relevant in its current state we need to update it to reflect the new workflow.

The current plan for ideal flow:

1. User Adds their organisation.
2. They are redirected to add a service.
3. They add a service
4. As their organisation only has one service i.e. the one they just created they are redirected to a confirmation page.
5. The confirmation page shows the organisation and service with buttons to edit the service or organisation as well as adding another service or completing the process.

The plan for when org was added in the past but first service just added:

1. The user decides to add their first service after adding their organisation in the past.
2. They are redirected to the organisation and first service confirmation page.
3. Although the org was added some time ago the details may have changed so there is still value in reviewing them. They also get a chance to review the service they just added.

The plan for when an org is added but a user decides to navigate away before adding a service:

1. The user starts completing service details but decides to navigate away from the page.
2. They are not redirected to a confirmation page which would be not what they expected. The confirmation of their organisation would be delayed until they add their first service which would, for the most part, be the point when their organisation would appear in search results.

A user adds their second service:

1. The user adds a second service to the organisation.
2. They are redirected back to the Organisation detail as normal. No confirmation page.

A user deletes the only service related to their organisation and then adds another:

1. The user add their service.
2. As the condition of having one service is met they are redirected to the confirmation page.
3. As the user has made a big change of deleting their only service it might not be a bad thing for them to get a chance to review the organisation details. They also have the opportunity to review the new service details which seems logical.

[Mike-Heneghan]

Noticed there was an instance where I went back during an organisation create and created another instance which then caused issues. Had to delete through the shell. Unsure why this happened and whether it's something we'll need to watch out for.

[Mike-Heneghan]

To Do List:

• [x] Add tests for the new redirects.
• [x] Update organisation confirm page to also include the service details.
• [x] Update the organisation confirm buttons to reflect the changes made.
• [x] Abstract the confirmation detail for the organisation and service into a partial.

[Mike-Heneghan]

[Mike-Heneghan]

Merged into master