Interface IFcWhileLoopDescriptors
- All Superinterfaces:
IExecutionResultDescriptor
- All Known Implementing Classes:
FcWhileLoopHandler
The result descriptors for the data returned by the
EWorkflowNodeType.FC_WHILE_LOOP action.- Since:
- 8.2.0
- Author:
- XIMA MEDIA GmbH
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final StringName of the corresponding property of thegetCurrentValueDescriptor(IValueDescriptorFactory)static final StringName of the corresponding property of thegetSuccessValueDescriptor(IValueDescriptorFactory) -
Method Summary
Modifier and TypeMethodDescriptiondefault IValueDescriptor<?, ? extends IValueBuilder<?>> Creates the value descriptor for the data that is made available to the workflow while the node is being executed.default Map<String, IValueDescriptor<?, ?>> The descriptors for the different error types that may occur when the node is executed.default IValueDescriptor<?, ? extends IValueBuilder<?>> Creates the value descriptor for the data that is made available to the workflow when the node was executed successfully.
-
Field Details
-
CURRENT_ATTR_INDEX
Name of the corresponding property of thegetCurrentValueDescriptor(IValueDescriptorFactory)- See Also:
-
SUCCESS_ATTR_COUNT
Name of the corresponding property of thegetSuccessValueDescriptor(IValueDescriptorFactory)- See Also:
-
-
Method Details
-
getCurrentValueDescriptor
default IValueDescriptor<?, ? extends IValueBuilder<?>> getCurrentValueDescriptor(IValueDescriptorFactory f) Description copied from interface:IExecutionResultDescriptorCreates the value descriptor for the data that is made available to the workflow while the node is being executed.- Specified by:
getCurrentValueDescriptorin interfaceIExecutionResultDescriptor- Parameters:
f- Factory that may be used for creating the descriptor. Instead of the factory passed in to this method, you may also useValueDescriptorFactory.getInstance()if you wish to cache the descriptor in a static or instance field.- Returns:
- The descriptor for data published by the node while it is being executed.
-
getErrorValueDescriptors
default Map<String, IValueDescriptor<?,?>> getErrorValueDescriptors(IValueDescriptorFactory factory) Description copied from interface:IExecutionResultDescriptorThe descriptors for the different error types that may occur when the node is executed. Each discriminator of the union represents an error or exception type.var connectTimeoutError = factory.recordBuilder().requiredProperty("connectTimeoutMs", factory.integer()); var readTimeoutError = factory.recordBuilder().requiredProperty("readTimeoutMs", factory.integer()); return Map.of("CONNECT_TIMEOUT", connectTimeoutError, "READ_TIMEOUT", readTimeoutError);The example above uses a different set of data each type of error.Note that you do not have to include a general error code. When the
executemethod of a node handler throws an unhandled (runtime) exception, the error codeCmnConst.Workflow.ERROR_CODE_GENERALis set automatically.- Specified by:
getErrorValueDescriptorsin interfaceIExecutionResultDescriptor- Parameters:
factory- Factory that may be used for creating the descriptor. You may also useValueDescriptorFactory.getInstance()if you wish to cache the descriptor in a static or instance field.- Returns:
- The value descriptor for the data that is made available to the workflow when the execution of the node failed (such as by throwing an exception).
-
getSuccessValueDescriptor
default IValueDescriptor<?, ? extends IValueBuilder<?>> getSuccessValueDescriptor(IValueDescriptorFactory f) Description copied from interface:IExecutionResultDescriptorCreates the value descriptor for the data that is made available to the workflow when the node was executed successfully.- Specified by:
getSuccessValueDescriptorin interfaceIExecutionResultDescriptor- Parameters:
f- Factory that may be used for creating the descriptor. Instead of the factory passed in to this method, you may also useValueDescriptorFactory.getInstance()if you wish to cache the descriptor in a static or instance field.- Returns:
- The data provided by the node after having been executed successfully.
-