Open jjeroch opened 1 month ago
Late delivered. Reason: Go-Live Task Force decision with Association
Special Request!
@MaximilianHauer & @jjeroch Please add test cases ++ Deep Dive needed! Monday: 8am
Test Cases added ✅
Open discussion: with the deactivation the SD endpoint could get deactivated (e.g. managed by policy) - security is given by the workflow validations (CH is not allowed to submit data for a application in an invalid status - process worker) @MaximilianHauer
++ further specification of the runtime impact (https://github.com/eclipse-tractusx/portal-backend/issues/855) ++ re-trigger impact for closed application process workers/application checklists to be discussed/designed and correctly implemented. (https://github.com/eclipse-tractusx/portal-backend/issues/813)
Detail sessions to be planned
Committers: @evegufy @Phil91 @ntruchsess @oyo
@MaximilianHauer I've added the ticket https://github.com/eclipse-tractusx/portal-backend/issues/903 to handle the retrigger process
Summary:
This epic encompasses the development of a feature toggle to enable or disable the clearinghouse connectivity for Self-Description (SD) functionalities and the creation of a backend job to retrigger SD document creation for customers affected by the toggle's disablement. The need for such features arises from the current portal's implementation, which mandates the clearinghouse compliance process for creating signed json.ld for the SD legal person. Due to the instability and immaturity of the job handling SD creation, a toggle is planned for deactivation to allow users to continue with registration without the SD step. Additionally, a mechanism is needed to retrospectively generate SDs for customers who registered while the toggle was disabled.
Why:
The toggle provides an immediate workaround to bypass the current mandatory clearinghouse compliance process, which is not stable enough for reliable operation. By introducing this toggle, administrators can mitigate the impact of the job's instability on registration flows, ensuring business continuity. The subsequent job retriggering capability ensures that once the system is stable or the feature is re-enabled, the necessary SD documents can be generated for compliance and completeness.
Acceptance Criteria:
Implementation Notes:
Implementation Steps:
Test Cases for Feature Toggle
CLEARINGHOUSE_CONNECT_DISABLED
Toggle Accessibility
Toggle Functionality
System Stability
Test Cases for GET API Endpoint
API Accessibility and Security
API Functionality
Error Handling
Test Cases for Administrator-Triggered Job
Job Triggering
Job Execution
Test Cases for UI Notifications
Notification Design and Delivery
Notification Content
Additional Test Scenarios
Linked Tickets
High Prio
Medium Prio
Improve the system/user experience