diff options
| author |   sreeja gattagouni <sg00744975@techmahindra.com> | 2022-09-09 16:16:30 +0530 |
|---|---|---|
| committer |   Lukasz Rajewski <lukasz.rajewski@t-mobile.pl> | 2022-10-03 19:50:00 +0000 |
| commit | 5fd0452387ccff6995c19ec5eeb7866328e34cbc (patch) | |
| tree | cffde0504b98e9ff22a46c279211bb665417ec91 /bpmn/so-bpmn-building-blocks/src/main/resources/subprocess/BuildingBlock/DeleteNetworkCollectionBB.bpmn | |
| parent | e4ae66db0d0e1bcfd19ef875491a236519be515d (diff) | |
Rollback Scenario for recursive orchestration
-Child Services may fail in any of the BB's while creation of composite services, to handle in efficient manner, it is complied with existing rollback logic.
-In case of Child Services >1 , when Workflow fails, the instantiated child remains in COMPLETED status, thus rollback changes ensure that such services are Deleted by triggering DeleteChildSvcBB.
-Parent Service is ROLLED-BACK in case of any child service failing in the workflow. Instantiated child services are Deleted from AAI as well.
Issue-ID: SO-3982
Change-ID:I73f97f986a817d423f92f8d922dcd9647b8a2503
Signed-off-by: sreeja gattagouni <sg00744975@techmahindra.com>
Diffstat (limited to 'bpmn/so-bpmn-building-blocks/src/main/resources/subprocess/BuildingBlock/DeleteNetworkCollectionBB.bpmn')
0 files changed, 0 insertions, 0 deletions