.Net: Processes State Management Part 2

[esttenorio]

Description

• Moving ProcessStateMetadata logic to factory/extension to try to keep clean existing core components
• Adding check of step name when adding new steps/processes to process - names must be unique so when applying saved state it propagates properly. Currently there are issues if multiple steps have the same name
• State versioning initial support:
  • Processes with 1:1 step match previous and new version (step name change and/or step logic change) - minor changes on process steps and not in root process itself

Fixing #9358

Out of scope but will be addressed in next PRs

• Processes with N:M steps (process flow changed and potentially also step logic changed)
• New samples showcasing how to make use of N:M mapping

Contribution Checklist

• The code builds clean without any errors or warnings
• The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
• All unit tests pass, and I have added new tests where possible
• I didn't break anyone 😄

[alliscode]

I really like the centralized serialization logic. I'll be able to integrate this to the map-step change much more easily.

I like the depth with which the Step03 sample was updated, but I wonder if there isn't an opportunity for a more targeted starting point to introduce the serialization patterns. Demonstrating these patterns is a more real case is wonderful evidence on how these patterns scale-out...but I wonder if a more simple sample that only targets serialization and versioning would be useful.

I agree but I wonder if the learn site is the place for this tutorial style walkthrough?

[crickman]

I really like the centralized serialization logic. I'll be able to integrate this to the map-step change much more easily.
I like the depth with which the Step03 sample was updated, but I wonder if there isn't an opportunity for a more targeted starting point to introduce the serialization patterns. Demonstrating these patterns is a more real case is wonderful evidence on how these patterns scale-out...but I wonder if a more simple sample that only targets serialization and versioning would be useful.

I agree but I wonder if the learn site is the place for this tutorial style walkthrough?

Sure, or both