For the service /v1/regard-application, the response-body contains two schemas.
Out of those two schemas , the second one's ((IF ( (NOT (200 OR 204)) OR (successfully-connected==false) OR (waiting>maximumWaitTimeToReceiveOperationKey) )' )) contains an attribute called "reason-of-failure" .
Out of the enumerations, the value _EATL_NOTREACHABLE has been updated to two values 'EATL_DID_NOT_REACH_ALT' and 'EATL_DID_NOT_REACH_NEW_APPLICATION'.
The above two values shall be formulated under following scenarios:
During callbacks of /v1/regard-application,
when EATL tries to reach ALT and if ALT is down, then "EATL_DID_NOT_REACH_ALT" shall be formulated
when EATL tries to reach the new regarding application and if the new application is down, then "EATL_DID_NOT_REACH_NEW_APPLICATION" shall be formulated in "reason-of-failure".
For the service /v1/regard-application, the response-body contains two schemas. Out of those two schemas , the second one's ((IF ( (NOT (200 OR 204)) OR (successfully-connected==false) OR (waiting>maximumWaitTimeToReceiveOperationKey) )' )) contains an attribute called "reason-of-failure" .
Out of the enumerations, the value _EATL_NOTREACHABLE has been updated to two values 'EATL_DID_NOT_REACH_ALT' and 'EATL_DID_NOT_REACH_NEW_APPLICATION'.
The above two values shall be formulated under following scenarios:
During callbacks of /v1/regard-application,