Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.Net Processes - Process builder semantics / design #9473

Open
crickman opened this issue Oct 30, 2024 · 0 comments
Open

.Net Processes - Process builder semantics / design #9473

crickman opened this issue Oct 30, 2024 · 0 comments
Labels
experimental Associated with an experimental feature .NET Issue or Pull requests regarding .NET code processes question Further information is requested sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)

Comments

@crickman
Copy link
Contributor

Is most cases for defining a process, the ProcessBuilder responds to an input event via ProcessBuilderOnInputEvent.

Since ProcessBuilder inherits from ProcessStepBuilder, it also exposes:

  • OnEvent
  • OnFunctionResult
  • OnFunctionError

We've generally avoided using these in association with process-level semantics.

Are there actually cases where these three step-level edges make sense at the process level?

@crickman crickman added .NET Issue or Pull requests regarding .NET code experimental Associated with an experimental feature processes question Further information is requested triage labels Oct 30, 2024
@evchaki evchaki added sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community) and removed triage labels Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
experimental Associated with an experimental feature .NET Issue or Pull requests regarding .NET code processes question Further information is requested sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)
Projects
Status: Backlog
Development

No branches or pull requests

2 participants