Python: [Breaking] Remove Python-only declarative actions and rename alias kinds to C# canonical names (#6126)

* Remove Python-only declarative actions and rename alias kinds to C# canonical names

* Address PR comments.

* Address PR comments.

* Reduce verbose and duplicate output from sample workflow.
This commit is contained in:
Peter Ibekwe
2026-05-28 03:16:22 -07:00
committed by GitHub
Unverified
parent 55dc3ce734
commit ded17b178c
15 changed files with 577 additions and 771 deletions
@@ -51,19 +51,16 @@ actions:
### Variable Actions
- `SetValue` - Set a variable in state
- `SetVariable` - Set a variable (.NET style naming)
- `AppendValue` - Append to a list
- `ResetVariable` - Clear a variable
### Control Flow
- `If` - Conditional branching
- `Switch` - Multi-way branching
- `ConditionGroup` - Multi-way branching
- `Foreach` - Iterate over collections
- `RepeatUntil` - Loop until condition
- `GotoAction` - Jump to labeled action
### Output
- `SendActivity` - Send text/attachments to user
- `EmitEvent` - Emit custom events
### Agent Invocation
- `InvokeAzureAgent` - Call an Azure AI agent
@@ -74,4 +71,4 @@ actions:
### Human-in-Loop
- `Question` - Request user input
- `WaitForInput` - Pause for external input
- `RequestExternalInput` - Request external data/approval
@@ -27,6 +27,7 @@ trigger:
input:
messages: =Workflow.Inputs.input
output:
autoSend: false
response: Local.agentResponse
responseObject: Local.orderData
@@ -37,6 +38,7 @@ trigger:
arguments:
order_data: =Local.orderData
output:
autoSend: false
result: Local.orderCalculation
# Invoke another function tool to format the final confirmation
@@ -47,6 +49,7 @@ trigger:
order_data: =Local.orderData
order_calculation: =Local.orderCalculation
output:
autoSend: false
result: Local.confirmation
# Send the final confirmation to the user
@@ -2,7 +2,6 @@
This sample demonstrates control flow with conditions:
- If/else branching
- Switch statements
- Nested conditions
## Files
@@ -1,12 +1,11 @@
# Human-in-Loop Workflow Sample
This sample demonstrates how to build interactive workflows that request user input during execution using the `Question`, `RequestExternalInput`, and `WaitForInput` actions.
This sample demonstrates how to build interactive workflows that request user input during execution using the `Question` and `RequestExternalInput` actions.
## What This Sample Shows
- Using `Question` to prompt for user responses
- Using `RequestExternalInput` to request external data
- Using `WaitForInput` to pause and wait for input
- Processing user responses to drive workflow decisions
- Interactive conversation patterns