StepArguments Properties

An object defining properties for the StepArguments class.

Id

Gets the unique identifier of the workflow step.

Type: long

The Id property provides the primary unique identifier for the workflow step. This numeric identifier is used to uniquely distinguish the step within the workflow system and is essential for tracking and referencing specific workflow steps during execution.

---

Key

Gets the unique key identifier for the workflow step.

Type: string

The Key property provides a string-based unique identifier for the workflow step. This key is used as an alternative identifier to the numeric Id, often providing a more meaningful or human-readable way to reference the step within the workflow system.

---

TypeCode

Gets the type code that categorizes the workflow step.

Type: WorkflowItemTypeCode
Accepted Values:

Name	Value
FlowComment	-1
FlowStart	10
FlowEnd	11
FlowPosition	15
FlowAssign	21
FlowCompare	22
FlowOr	24
FlowAnd	25
FlowMail	26
FlowProfession	27
FlowDepartment	28
Variable	30
FlowScript	31
FlowNode	33
FlowGroup	37
FlowTimer	39
FlowTimerStarter	40
FlowTimerStopper	41
FlowApprovalCancellar	42
Pauser	44
SubFlowCall	51
SubFlowBegin	52
SubFlowEnd	53
FlowPushNotification	54
FlowDocument	56
FlowCreateDocument	57
FlowDocumentSynchronizer	58
FlowStarterPosition	59
FlowDocumentState	63
FlowUniqueIdCreator	65
FlowSetDocumentId	66
FlowDeleteDocument	67
FlowPDFExport	68
FlowXMLExport	69
FlowMailSender	75
FlowParallel	79
FlowContinue	80
FlowTrigger	81
FlowActionCreator	82
FlowDigitallySigning	83
FlowGptPrompt	84

The TypeCode property specifies the category or type of the workflow step using the WorkflowItemTypeCode enumeration. This classification helps determine the behavior and processing requirements of the step, allowing the workflow system to apply appropriate handling based on the step's type.

---

Name

Gets the display name of the workflow step.

Type: string

The Name property provides the human-readable display name for the workflow step. This name is used for presentation purposes in the user interface and for logging, making it easier for users and developers to identify the step during workflow execution and debugging.