Guide for power users re End-end flow for creating new Innovation Flows

alkem-io / server

Core server in the Alkemio platform, offering a GraphQL api for interacting with the logical domain model.

http://alkem.io

European Union Public License 1.2

25 stars 4 forks source link

Guide for power users re End-end flow for creating new Innovation Flows #2069

Open techsmyth opened 2 years ago

techsmyth commented 2 years ago

Description

As an admin I want to be able to create new Innovation Flow definitions and apply them to my challenges / opportunities

Acceptance criteria

[ ] Understand how to create a new XState machine definition (see link in additional context)
[ ] Create new machine definition based on Novum ways of working (see additional context)
[ ] Create a new InnovationFlow template in a test Hub on dev environment. Note: this may need to be via graphql for now as UI for uploading it is not there yet. As such a key hurdle will be to get the Innovation Flow machine definition encoded to be sent up with the Graphql
[ ] Update a challenge to use the new InnovationFlow template. Note: see sample mutation in the server repositor.

Additional Context

XState machine definition editor: https://stately.ai/registry/new?source=landing-page#

Novums ways of working: draft novum way of working.jpeg Cr

hoyterutteman commented 2 years ago

Talked with Evgeni about this one. I created a definition using Stately and exported it as a json.

Evgeni managed to get it on the dev/test environment, but it was not possible to visualize. On production, it's not possible to add a new state through graphql.

techsmyth commented 2 years ago

Good to hear you got a definition created.

When stating that it was put onto dev/test, I presume this means a new LifecycleTemplate was created? Which Hub?

It should also be possible then on dev/test to update the lifecycle definition of a a Challenge to use that LifecycleTemplate - and that way visualize it. Did that get tried? The sample mutation is: https://github.com/alkem-io/server/blob/develop/graphql-samples/mutations/update/update-challenge-lifecycle

The value of this exercise is to try out this end-end flow manually via graphql before it is supported via the client. And the usage of Stately will be near term the way to create new InnovationFlows.

Comoque1 commented 2 years ago

I mislead Hoyte, by trying to create new challenge, with newly created template. Updating existing challenge to use new innovation flow template, returns correct result.

techsmyth commented 2 years ago

Great!

Hoyte: this then would be an option for Wouter to get the lifecycle he wants across his opportunities....so it becomes a case now of designing the right Innovation Flow now on Stately, and when the functionality is deployed to production we can create a script to apply that Innovation Flow across all his Opportunities.