Versions Compared

Key

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

...

  • Provisioning workflows are in place and are fully functional

  • Special pricing enabled via discounts/price plans or any non standard package structures are in place and working

  • Payment processing (Credit Card, eCheck, etc.) is configured and working

  • Web portals that integrate with EngageIP work as expected (e.g. a end customer portal that integrates with EngageIP)

    • Tickets can be created / edited

    • Customer reports work (e.g. usage tracking)

    • Online payments process

    • User signup is functioning in the portal and creating accounts, user-packages, etc. in EngageIP

    • Contact information can be added / updated

    • All EngageIP account data exposed in the portal is presented properly and accurately (account name, bill date, balance, etc.)

  • Custom Code / Page Extensions / Actions are in place and fully functional

  • Any regular data that is imported can be imported without issue

Note

Notice: Any process that provisions to an external system is critical for confirmation before going live.

Pick Multiple Diverse Accounts To Check

...

  • Login to the AdminPortal

  • Check event log for any errors

  • Check your list for provisioning requirements, did the system provision what it should have?

  • Check your list of ten or more diverse scenario accounts. Check that the balance and charges match what were billed in your production server which is on the previous release - also confirm that the numbers are accurate aside from what the production bill run processed

  • Check that you can process payments for all payment processors configured (credit card, echeck, etc.)

  • Check role permissions of the staff that will login after the upgrade - Can staff access all the functions they need and do they work correctly (example, workorders, tickets, adding accounts, adding packages?). Upgrades often bring new permissions and increased security so you'll want to reconfirm with each upgrade that your role permissions are correct

  • Finally, familiarize yourself with any new features listed in the release

    • Practice using any new features so that you know how they operate and what to expect from them - this may be required if you need to train personnel on new features after the upgrade to production

    • Search this knowledge base for detailed instructions on configuration or use of new features

    • Ask questions if you are not sure of the functionality

Info

Note: It's best to give the whole system a walk through based on these suggestions before upgrading production to limit the possible confusion of staff and any errors that might arise from improper use of a new feature or changed feature

...

Production Upgrade Request and SignOff

...

.