Offer Change Process - Offer Deletion Flow

[jjeroch]

Description: This issue outlines the development of a new flow for deleting offers within portal-marketplaces. The Offer Deletion Flow will allow offer providers to remove offers that are no longer valid or needed. This functionality must be implemented with careful consideration to prevent accidental deletions and to maintain data integrity.

Objectives:

• To provide a user-friendly interface for deleting offers.
• To ensure that deletions are intentional and authorized.
• To maintain system integrity and prevent orphaned records by updating all related components.

Pre-requisites:

• User must have the necessary permissions to delete offers.
• Offer must not be associated with any ongoing or completed transactions.

Tasks:

1. Backend Development:

   • Create an API endpoint for offer deletion (DELETE /api/offers/{offerId}).
   • Implement logic to check user permissions and offer status before deletion.
   • Ensure cascading updates/deletions are handled for related entities (e.g., offers linked to promotions).

2. Frontend Development:

   • Design and implement a 'Delete' button in the offer management interface.
   • Add a confirmation dialog to prevent accidental deletions.
   • Connect the frontend with the backend deletion API.

3. Database Updates:

   • Update database triggers or stored procedures if necessary to handle the deletion process.

Acceptance Criteria:

• Users with the correct permissions can delete offers through the interface.
• A confirmation step is present to prevent accidental deletions.
• Deletion of an offer correctly updates or removes all associated data (where applicable; some need to be kept for auditing).
• The system logs all deletion actions for audit purposes.
• The deletion process does not negatively impact system performance.

Test Scenarios:

1. Delete an offer with no active transactions and verify it is removed from the system.
2. Attempt to delete an offer with active transactions and ensure the process is blocked.
3. Verify that users without deletion permissions cannot remove offers.
4. Confirm that all related data is either updated or deleted as appropriate.
5. Check that the system logs the deletion event with sufficient details for auditing.

Dependencies:

• User authentication and authorization service.
• Database integrity constraints and relationships.

Notes:

• The deletion flow should be thoroughly tested in a staging environment before deployment.
• Backup and recovery strategies should be reviewed to ensure they align with the new deletion capabilities.

Tags: [Backend], [Frontend], [Database], [Permissions], [Deletion]

[stephanbcbauer]

Was presented in the open planning ⇾ developing is done by portal, committer are defined

[stephanbcbauer]

Hello @jjeroch , @jjeroch

Since the feature is a 24.08 feature and the development phase is coming to an end, we need a status on the feature.

• [ ] Currently you are assigned (Responsible) → Is this correct? If not, please assign the correct contact person
• [ ] Please check whether the status (backlog, work in progress ...) is set correctly
• [ ] Please check whether there is an assignment to a committee or expert group (supported-by) to be found on the board
• [ ] Please comment on the current status of the feature
• [ ] Are all SubTasks (issues from other repositories that deal with the feature) linked? → The easiest way is to mention the feature here in the issue (via the ID) so we can see which teams/repositories are involved.

If you need any clarification, please get in touch, thank you very much. Stephan

[jjeroch]

Back to backlog. No commitment for delivery Removed the milestone