Rollback Scenario for recursive orchestration 99/130299/13
authorsreeja gattagouni <sg00744975@techmahindra.com>
Fri, 9 Sep 2022 10:46:30 +0000 (16:16 +0530)
committerLukasz Rajewski <lukasz.rajewski@t-mobile.pl>
Mon, 3 Oct 2022 19:50:00 +0000 (19:50 +0000)
commit5fd0452387ccff6995c19ec5eeb7866328e34cbc
treecffde0504b98e9ff22a46c279211bb665417ec91
parente4ae66db0d0e1bcfd19ef875491a236519be515d
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>
adapters/mso-catalog-db-adapter/src/main/resources/db/migration/R__MacroData.sql
bpmn/so-bpmn-building-blocks/src/main/resources/subprocess/BuildingBlock/DeleteChildServiceBB.bpmn
bpmn/so-bpmn-tasks/src/main/java/org/onap/so/bpmn/infrastructure/service/composition/DeleteChildServiceBB.java