Roles and responsibilities in Configuration Hub

Important rules underpin the standard operating procedures for relating to maps and code lists. It is the responsibility of the Customer Administrators to ensure that all guidelines and processes enlisted here are followed by all users. Training details and links to mandatory training are provided in the specific sections. It is the responsibility of all Administrators and Users to participate in any training or enablement that is identified for the specific actions they might be doing within Configuration Hub.

Application users

Configuration Hub has the following two roles:

  • Customer administrator
  • Customer user

The Customer Administrator has the same access as a Customer User with the added capability to add other users. A company might have multiple people with the role of administrator based on their specific needs.

Until permissions are available to categorize user activity, a customer user can be provided access through an honor system. For example, when a specific user wants to view the maps, but not edit them. Without appropriate permissions, access to map-editing capabilities is not differentiated from view capabilities. IBM wants to provide as much value to the Customer as possible and the honor system approach can be allowed.

General rules about map edits

  • If you edit maps, take the following training:
  • You can edit only those maps that are deployed to production. Those maps that are not yet deployed to production by IBM Support are not eligible.
  • You can edit only those maps that are deemed eligible by IBM Support, due to the complexities within some maps or code lists. In such cases, IBM Support reserves the rights to not make such assets available to you for changes.
  • IBM Support can temporarily pick up the check-out of a map for troubleshooting issues that are raised by you. IBM Support might not pick up partially edited maps to complete updates that your organization does not want to complete. If you want IBM Support edit a map, open a Map Change Request (MCR) to revert it to the last version in production. For more information, see product documentation.
  • When deploying maps to the production environment, use Production deployment comments to enter your inputs. Ensure that you provide the Process ID (or “green light PID”) from Customer Test Environment (CTE) from InFlight, in which the map was used in a successful end-to-end test in CTE. It helps provide a scalable, full self-service experience. In the absence of which, your access might be revoked.
  • Do a map-flow analysis before you edit a map. The analysis might help understand any impacts that a map edit can have on downstream activities. This can be done by researching the document flow within InFlight to determine whether other changes are needed.

General rules about code lists

  • Review all videos and other material provided: https://mediacenter.ibm.com/playlist/details/1_ka788vqh
    • Code list introduction (mandatory)
    • Code list editing (mandatory)
  • Complete the B2Bi SaaS Hub mapping curriculum: https://learn.ibm.com/course/view.php?id=8324
  • Familiarize yourself with Configuration Hub documentation. For information on the code list create feature, see Creating code lists.
  • You can edit only those code lists that are deployed to production. Those code lists that are not yet deployed to production by IBM Support are not eligible.
  • You can edit only those code lists that are deemed eligible by IBM Support, due to the complexities within some maps or code lists. In such cases, IBM Support reserves the rights to not make such assets available to you for changes.
  • IBM Support can temporarily pick up the check-out of a code list for troubleshooting issues that are raised by you. IBM Support might not pick up partially edited code lists to complete updates that your organization does not want to complete. If you want IBM Support edit a code list, a Production Enhancement Request (PER) is to be opened and the code list must be reverted to the last version in production. For more information, see product documentation.

Other details

  • Ensure that the code lists you either create or edit are in a clean state (with Status set to FINAL) before the code lists are sent to IBM Support for editing. IBM Support is not to be held responsible for any issues that might arise if the code lists are not in a clean and final state with Status set to FINAL. However, you might get in touch with IBM Support, if needed, by creating an MCR or PER.
  • IBM resources, such as IBM Support, can create or edit maps (or the new or edited code lists) during the delivery cycle of a PER.
  • You can create or edit your existing code lists only after the PER team is finished with making the delivery changes. To edit an existing code list during the PER process, create a support ticket and get in touch with IBM Support.
  • Map Research (on Configuration Hub or self-service cases): IBM Support must verify that any issue that is reported by client is related to maps. If issue is determined to be related to client-edited map and the map was last modified by you, then:
    • IBM Support might research Configuration Hub or self-service maps that are in only the production environment. IBM Support might not research CTE Maps.
      • If you open a research case on a self-serviced map, an MCR must be submitted clearly stating the request of the research and detailing the intent of the changes made.
        • Quote the production PID creating an MCR.
        • MCRs for research on client-edited maps are billable at contracted hourly rates.
      • The research focuses on why a map is acting, running, translating, or failing.
      • If subsequent map changes are requested on client-modified maps, normal MCR processes are followed. And you must submit an MCR form with instructions.
    • If the client-modified map is not working in the production environment:
      • The self-service tool prohibits faulty maps from getting loaded into the production environment.
      • You must advise if the modified map worked in CTE, and is now not working in the production environment.
        • Provide adequate information on the case (for example, CTE or PID)
        • The issue might escalate to L2 and eventually L3 for investigation.
      • IBM Support can inquire if you want the map to be reverted to prior working version.
    • If you request IBM Support to research the nonworking map:
      • If the IBM Support team cannot determine the cause of failure, you are notified.
      • You can choose to open an MCR and IBM Support edits from the last working version of the map.
      • If you want to request IBM Support to fix the nonworking map, refer to the Fixing Self-Service Maps section.
    • If you did not modify the map, the usual standard operating procedures are followed on researching maps that are maintained by IBM.
  • How to map
    • IBM Support does not educate clients on how to map.
    • IBM Support can work on changing the map based on the specifications that are mentioned in MCR.
  • Fixing Self-Service Maps
    • IBM Support might not engage IBM map resources to fix a failing self-service map.
    • If deemed necessary, you can request through the MCR process to make the intended changes. IBM Support edits from the last-working version of the map.
    • You can request IBM Support to revert to the last working map.