…

Motivation and Context

Required:
I would like to have a process framework with a simplified process and steps, showing how simple, easy and straightforward it can be. I want this example to take away the fear and reduce the cognitive load as a "first super-easy step".

Problem solved:
Excessive cognitive load on the first example. There Should be a super-easy step that is and feels easy. I believe this gets close to it :)

Scenario:
Learning, taking the fear out. Helping in making it easier.

Simplification added:
Also to simplify it even further i added the feature that the Function event name gets resolved when there is a single function
When declaring the process, instead of:

        startStep
            .OnEvent(StartStep.OutputEvents.Executed)
            .SendEventTo(new ProcessFunctionTargetBuilder(doSomeWorkStep));

        doSomeWorkStep
            .OnEvent(DoSomeWorkStep.OutputEvents.Executed)
            .SendEventTo(new ProcessFunctionTargetBuilder(doMoreWorkStep));

        doMoreWorkStep
            .OnEvent(DoMoreWorkStep.OutputEvents.Executed)
            .SendEventTo(new ProcessFunctionTargetBuilder(endStep));

        endStep
            .OnEvent(EndStep.OutputEvents.Executed)
            .StopProcess(); 

I would like to do the following:

      startStep
           .OnFunctionResult()
           .SendEventTo(new ProcessFunctionTargetBuilder(doSomeWorkStep));

       doSomeWorkStep
           .OnFunctionResult()
           .SendEventTo(new ProcessFunctionTargetBuilder(doMoreWorkStep));

       doMoreWorkStep
           .OnFunctionResult()
           .SendEventTo(new ProcessFunctionTargetBuilder(endStep));

       endStep
           .OnFunctionResult()
           .StopProcess();

So that the Function is inferred by the framework, reducing verbosity and cognitive load.

Fixes: #9647
Fixes: #9648

Description

• Added example Step00 (process, steps )
• Added documentation
• Added the small refactoring on the StepProcessBuilder to support Function resolution when "there is only one"

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 😄