ESS Bottom-Up approach (Implementation)

[jzbmw]

Dependency

#307

User Story

As ESS responsible
I want the capability to determine all customers which are affected by an incident on supply-chain level
so that an incident company could inform the customers of an incident and thus meet the compliance.

Hints / Details

• Concept
• This shall be showcased
• Uploading IRS-90488556-130624-1615-1178.pdf…

Outcome / Acceptance Criteria

Outcome

• ...

Acceptance Criteria

Add API Endpoint /ess/customer/investigation

• Add API endpoint for single ess bottom up investigation executing specific ess-bottom-up-workflow
• Filter for parts related to given BPNS
• Filter for validity periode of part
• Get relationships one level up over SingleLevelUsageAsPlanned
• Aggregate results in new aspect model called "ESSCustomerNotificationsSubmodel "

Extend API Endpoint /irs/ess/orders (API Endpoints POST "irs/ess/orders" is updated for bottom up approach)

• Extend API Endpoint for batch processing of ess-bottom-up-workflow

Add API Endpoint /ess/customer/investigation/${id}

• Add api endpoint to request for a ess-bottom-up-workflow job results with submodel payload ESSCustomerNotificationsSubmodel

Testcases

• Add Test cases towards the expected behavior, including happy path and exception paths
• Add requests to the insomnia collection

Documentation

• API documentation is updated
• Payload samples in API are updated to current state
• Use case is described in documentation
• API documentation is comprehensible and completed including all possible return codes

Showcase

• The feature MUST be showcased in a suitable scenario
• Request asPlanned parts (> 5 parts ) from dTR
• Happy path scenario is shown
• Exceptional path - at least one upstream relations could not be determined
• The showcase COULD be demonstrated in a sequence where, however, each step could be paused to explain the scenario to the auditorium and make it comprehensible to understand.

Out of Scope

• ...