Integration
Hide about this portal


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.


Add a new idea Subscribe
Status Functionality already exists
Workspace App Connect
Created by Guest
Created on Dec 6, 2024

RELATED IDEAS

Proposal for Enhancing IBM App Connect Designer: Custom Naming for Generated Accounts

See this idea on ideas.ibm.com

Currently, IBM App Connect Designer automatically assigns generic names to accounts, such as Account 1, Account 2, Account 3. While functional, this naming convention can create challenges for users managing multiple integrations, especially in environments with numerous accounts tied to different stages, environments, or providers.

 

Key Points:

Challenges with Current Naming Convention:

  • Lack of Context: Default account names do not provide meaningful context, making it difficult to identify the purpose or usage of each account (e.g., distinguishing between staging and production environments).
  • Error-Prone Configurations: When users manage multiple accounts, confusion caused by non-descriptive names can lead to errors in selecting or managing the correct account for a given flow.

Proposed Enhancement:

  • Allow users to assign custom names to accounts created in the App Connect Designer, either during creation or as part of the account editing process.
  • Examples of custom names:
    • AWS-HML-1
    • AWS-PROD-2
    • Salesforce-Staging
    • Azure-Production-1
  • Ensure these custom names are reflected consistently throughout the interface (e.g., in flows, logs, and debugging tools).

Benefits:

  • Improved Clarity: Custom names provide immediate context, reducing ambiguity when managing accounts in complex environments.
  • Increased Productivity: Simplifies workflows by allowing users to quickly identify and select the correct accounts.
  • Enhanced Usability: Improves the overall user experience by aligning account management with organizational naming conventions.

Implementation Considerations:

  • Add an optional field for custom names during account setup.
  • Validate names for uniqueness to prevent duplication and confusion.
  • Provide a mechanism to rename existing accounts without disrupting active integrations.
Idea priority Urgent
  • Admin
    Ben Thompson
    Reply
    |     Jan 29, 2025

    Hi @Joerg thank you for the feedback ... and sorry to hear that you think the positioning of the Rename Account option is non-intuitive. Given that the Catalog page is where we list the available accounts (grouped by the name of the third party application), and that the menu option to Update/Remove/Rename is immediately next to the account name, we'd be interested to hear (or receive a marked up diagram if easier for you?) whereabouts in the UX you were expecting to find the option so that we might be able to consider potential alternative placements. Regarding the comment that the user does not see the name of the connection object, nor does Designer ask about it, this was actually one of the original design intentions (!) which was made in an attempt to simplify what can appear to be a complex process when making connections ... it was felt that if we can avoid forcing the user to dream up names for things then the first use experience becomes somewhat simpler (less typing for the user, and less worrying about meeting any required naming conventions for account names etc). We continue to listen to feedback - perhaps we could find a way to better highlight the generated default accout name and make it more obvious to the user that they can change it (perhaps by placing a cursor in to the field when initially created?) - as ever ... specific suggestions welcome!

    1 reply
  • Guest
    Reply
    |     Jan 17, 2025

    Hi,

    I think this is more a usability issue. (This Idea item indicates, that those user just have not found this Renaming feature. It also took me a while to stumble over it).

    When creating a connection, the user does not see the name of the conneciton object, nor does Designer ask him about it.

    So afterwards it can be cumbersome to correct this account name, especially if the account is used in multiple flows.

    A very easy fix in my opinion would be to force the user to set an account name by the time he creates the connection. Or at the very least, to show him the default account name and let him change it at creation time.

  • Admin
    Ben Thompson
    Reply
    |     Dec 20, 2024

    Thank you for taking the time to raise this requirement ... it is already possible to rename accounts from the Catalog section in Designer (both Designer shipped in ACE software and in the managed public cloud solution ACEaaS on AWS):

    image.png
    image.png

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.