Uses of Class
org.camunda.community.bpmndt.api.CallActivityHandler

Packages that use CallActivityHandler

Package	Description
org.camunda.community.bpmndt.api

Uses of CallActivityHandler in org.camunda.community.bpmndt.api

Methods in org.camunda.community.bpmndt.api that return CallActivityHandler

Modifier and Type	Method	Description
CallActivityHandler	CallActivityHandler.customize(Consumer<CallActivityHandler> customizer)	Customizes the handler, using the given Consumer function.
CallActivityHandler	CallActivityHandler.verify(BiConsumer<org.camunda.bpm.engine.test.assertions.bpmn.ProcessInstanceAssert,CallActivityDefinition> verifier)	Verifies the definition of the call activity and the state before it is executed (actually before the mapInputVariables method of a possible DelegateVariableMapping is invoked).
CallActivityHandler	CallActivityHandler.verifyInput(Consumer<org.camunda.bpm.engine.delegate.VariableScope> inputVerifier)	Verifies the state after the mapInputVariables method of a possible DelegateVariableMapping was invoked. Please note: This method can also be used to simulate the behavior of a called process.
CallActivityHandler	CallActivityHandler.verifyOutput(Consumer<org.camunda.bpm.engine.delegate.VariableScope> outputVerifier)	Verifies the state after the mapOutputVariables method of a possible DelegateVariableMapping was invoked.
CallActivityHandler	CallActivityHandler.withErrorMessage(String errorMessage)	Sets the error message, which is used when the next activity is an error boundary event.

Methods in org.camunda.community.bpmndt.api with parameters of type CallActivityHandler

Modifier and Type	Method	Description
protected void	MultiInstanceHandler.registerCallActivityHandler(CallActivityHandler handler)	Registers the given call activity handler at the test case instance, so that it will be executed when the custom call activity behavior is applied. Since there can be multiple handlers (one for each loop index), it is necessary to register the correct one before the next multi instance loop is executed.
protected void	MultiInstanceScopeHandler.registerCallActivityHandler(String activityId, CallActivityHandler handler)	Registers the given call activity handler at the test case instance, so that it will be executed when the custom call activity behavior is applied. Since there can be multiple handlers (one for each loop index), it is necessary to register the correct one before the next multi instance loop is executed.
protected void	TestCaseInstance.registerCallActivityHandler(String activityId, CallActivityHandler handler)

Method parameters in org.camunda.community.bpmndt.api with type arguments of type CallActivityHandler

Modifier and Type	Method	Description
CallActivityHandler	CallActivityHandler.customize(Consumer<CallActivityHandler> customizer)	Customizes the handler, using the given Consumer function.