Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • For TRIRIGA issues, perform these activities before submitting a case:

  • For Maximo issues, collect data before submitting a case.

  • After gathering the data above, Create A Case with as much of the following information as possible:

    • Environment affected (eg. DEV, TEST, TRAIN, QA, PROD, etc.)

    • Steps to reproduce the issue, expected result, & actual result. If IBM Support team cannot reproduce issue with out-of-the-box functionality, the issue is likely related to configurations or data that are not covered by IBM Support.

    • All information gathered from the activities performed above. Attach logs and copy/paste relevant log errors into case.

    • When the issue began

    • New or recurring issue? If recurring, what is the frequency of the issue? (specific days & times)

    • Any recent changes in configurations, workflows, network, etc.

    • What activities were being performed in the affected environment immediately prior to experiencing the issue? These activities could be generated by end users, project team members, and/or automated activities (eg. integrations, cleanup agent, crons, etc.)

    • Impact assessment for project and/or business

    • Use the MustGather tool in the TRIRIGA Admin Console to submit basic information required for SaaS and product support.

  • For cases involving TRIRIGA or Maximo requests (not performance or product issues):

    • Review Request Lead Times.

    • Plan for these lead times in your project plan.

    • Submit request cases based on lead times noted.