Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Not under consideration
Workspace API Connect
Created by Guest
Created on Apr 22, 2025

Provide Enhanced Pre-Delete Hook Functionality in APIC to Ensure Data Consistency Across Systems

Currently, when an application is deleted in the APIC Developer Portal, any pre-delete hooks are executed after the relevant application data has already been removed from the APIC database. This creates a significant problem for developers who need to perform actions in external systems (e.g., de-registering applications from SSO systems) based on the deleted application's data.   
As a workaround, developers are forced to directly query the Drupal database to retrieve the necessary information. This introduces tight coupling between the APIC and Drupal systems, making the solution brittle, difficult to maintain, and prone to failure if the Drupal schema changes.   

To address this, IBM should provide a mechanism to ensure that pre-delete hooks have access to the application's data as it exists in the APIC database prior to the deletion operation.

Idea priority Medium
  • Admin
    AARON Lieber
    May 2, 2025

    We've read the support case, and the pre-delete hooks work correctly when the delete is triggered from within the developer portal. However, if the delete is triggered from the API Manager, they won't fire -- and that's not something we can change.


    For this to work properly, the delete must be triggered from the developer portal. Apologies, but this isn't something we can help with.