Single Development Account Environment Method
You can use a single development account environment to develop one version of a bundle at a time. Three development accounts are used for developing, testing, and releasing a single version of a SuiteApp. In this method, a bundle developer works in one account, stages the bundle for release in another account, and tests in a third account.
The following diagram shows the process flow for the bundle development:
Process
The following table describes the basic steps for developing a SuiteApp with a single development account environment:
|
Step Number |
Description |
|---|---|
|
1 |
Develop the customization in the develop account. Use Customization and SuiteScript to develop the customization. For more information, see Customize Your NetSuite Account. Then, in the develop account, use the Bundle Builder to create a bundle with the customization. See Creating a Bundle with the Bundle Builder. |
|
2 |
Copy the bundle to the release account. Copy a bundle to a release account to support your release process. See Copying a Bundle to Other Accounts.
Note:
This account should only contain copied bundles, and not any objects created as part of the customization. |
|
3 |
Install the bundle from the release account into the test account. You can create sample data to support testing of the customization. See Installing a Bundle. If you want to make changes to the customization during testing, make the changes on the develop account and repeat steps 1 to 3 above. |
|
4 |
After the bundle has been tested on the test account and all desired changes are incorporated into the bundle and copied to the release account, install the bundle into a sandbox account for additional integration and user acceptance testing with production data. If you want to make changes to the customization after testing in the sandbox, make the changes on the develop account and repeat steps 1 to 4 above. |
|
5 |
After the bundle has been completely tested in the sandbox account, install the bundle from the release account into the production account.
Note:
At this point, you can begin developing a second version of the bundle on the development account, using the objects from the previous version as a starting point. If you want multiple simultaneous versions of the same bundle, see Multiple Development Account Environments Method. |
Single Development Account Environment Method — Benefits and Drawbacks
The following table lists the benefits and drawbacks to this approach:
|
Benefits |
Drawbacks |
|---|---|
|
|