HandleMessaging Parameters and Valid Execution Modes

The valid execution mode for HandleMessaging is SYNCHR.

The parameters of HandleMessaging are as follows:

HandleMessaging Parameters
Name Semantics Type Valid Values Multi-plicity
Direction: In
CommandsPerMessage
(Optional) The number of related records (bundle) to be sent in a message. This determines the size of the payload going out.

In case of in-memory workflows, this parameter is ignored, and the entire record bundle is sent in one go. This does not impact performance in any way, since the size of the record bundle is small in case of in-memory workflows.

long Defaults to 50. 0..1
ProtocolMessagingCommand
(Optional) The command for the activity to execute. string START (default) 
CONTINUE
SUSPEND
ABORT
TIMEOUT
 0..1
ReferenceStepID
(Mandatory) Points to the StepID of the IdentifyProtocolOperations step. long   1
ResponseRequired
(Optional) This parameter decides whether the workflow should suspend and wait for responses. This parameter is ignored for Datapool-Marketplaces namely - WWRE, 1Sync. boolean True

False (default)

Defaults to false for non-Datapool marketplaces.

0..1
InDocument
(Mandatory) See Common Parameters.      
InRecordList
(Mandatory) See Common Parameters.      
FEDOption
(Optional) See Common Parameters.      
Direction: Out
OutDocument
(Optional) See Common Parameters.      
OutRecordList
(Optional) See Common Parameters.      
ProtocolMessageGenerated
(Optional) Flag to indicate if a message was generated. boolean True

False

1
ProtocolMessagingNextCommand
(Optional) The next command that the activity has identified for it to do. This usually becomes the ProtocolMessagingCommand on the next send cycle. string 
CONTINUE
SUSPEND
DONE
 1
RecordsProcessed
(Optional) Count of Number of Records processed by the activity. long   1