Skip to main content

Staging environment

Before an IrisX App reaches customers, you will want to try it out in a controlled Staging environment: a sub-account you own, with a QA version of your app installed and a few users invited to test it.

This guide shows the recommended QA-first flow: create a private QA app owned by your Staging account, submit it for review, verify it in your Staging environment, and then submit the real app when everything works as expected.

The end-to-end flow​

  1. Enable the developer console. Make sure your Trackunit representative has enabled the developer console for your Manager user, and confirm it is active. See Prerequisites.

  2. Create a Staging sub-account. Set up a sub-account under your hierarchy to act as your Staging environment. This account will also be used as the QA account for testing your app before it reaches customers. See Create a Staging sub-account.

  3. Log in as the Staging account before creating the QA app. The QA app must be submitted while you are logged in as the Staging account. This ensures that the Staging account owns the QA app - and the app is therefore treated as a private app.

  4. Create a QA version of your app. Before submitting your real app for approval, we recommend creating a duplicate IrisX App to use as your QA app. Because you are logged in as the Staging account, this QA app will be owned by the Staging account.

  5. Make the QA app private. Configure the QA app with installation.accountIds set to the Staging account ID. This makes the QA app private and only available to that account. If your app depends on specific pricing plans, also configure installation.pricingPlanPolicy. See Controlling marketplace behavior.

  6. Submit the QA app for review. Build and submit the QA app package for review from the Staging account login. This lets you verify the review and approval flow before submitting the real app. See How to submit an App SDK.

  7. Install and verify the QA app. Once the QA app is approved, install it in your Staging environment and verify that it works as expected in a production-like setup.

  8. Invite users to test. Add testers to your Staging sub-account so they can use the QA app and validate the experience. See Invite users to test.

  9. Submit the real app. When the QA app has been approved and tested, submit the real customer-facing app for approval using the intended production marketplace configuration.

  10. Understand review & approval. Learn what triggers automatic approval versus manual review, and what to expect on timelines. See Review & approval.

Assumptions​

This guide assumes you are already on the platform and have access to an account, or can ask an admin to create a sub-account under the same hierarchy. Getting an account in the first place is outside the scope of these docs — talk to your Trackunit representative if you do not yet have access.