Versions Compared

Version Old Version 10 New Version 11
Changes made by

Francesco Fiora

Francesco Fiora

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add a flag to support major versioning:

...

Code Block
languagejava
var automationComposition = participantIntermediaryApi.getAutomationComposition(instanceId);
var compositionId = automationComposition.getCompositionId();
var acElementDefinitionsFrom = participantIntermediaryApi.getAcElementsDefinitions(compositionId);
var acElementDefinitionFrom = acElementsDefinitionsFrom.values().stream()
    .filter(el -> el.getAcElementDefinitionId().getName().equals(element.getDefinition().getName())).findFirst().get();
var outPropertiesFrom = acElementDefinitionFrom.getOutProperties();

var acElementDefinitionTo = participantIntermediaryApi.getAcElementDefinition(compositionTargetId, element.getDefinition());
var outPropertiesTo = acElementDefinitionTo.getOutProperties();


Migration precheck

Assumptions:

  • Only the participants can execute a precheck.
  • Precheck is executed before the migration, if it fail the migration will be not executed.
  • User needs to receive the result of the precheck.
  • Acm-runtime needs to handle the precheck fail in a different way it handles migration fail.

Solution 1: create a new flow for migration-precheck.

User can send the action migration-precheck POST. The user can do the action migration POST after that. The migration flow is still backwards-compatible.

...