This action might not be possible to undo. Are you sure you want to continue?
RELEASE PREVIEW – SAMPLE ACTION PLAN
NetSuite is pleased to provide a Release Preview of our upcoming release, Version 2010 Release 2. The Release Preview is an opportunity for your company to become familiar with the new features in the release as well as verify that your existing workflows function as expected prior to the release upgrade. This document has been created to help you get the most out of your Release Preview. The following sections are provided: Accessing your Release Preview Account describes how to access the Release Preview and become familiar with the new features and changes in this release. Functionality Available for Testing provides a table of the features that can be tested in the Release Preview. Recommended Testing Plan lists the product features you should test and steps to take to do so. Creating Workflow Tests tells how to document workflows and includes a simple workflow test example. Reporting Issues explains what to do if you encounter an issue.
We hope that by providing this information, working with you to make sure you perform the recommended tests, and giving you other needed guidance, we will avoid any major problems or surprises when you go live with the new version. Our goal is to provide a smooth and seamless transition to this new release. Thank you.
1 ACCESSING YOUR RELEASE PREVIEW ACCOUNT
1. Go to http://beta.netsuite.com. 2. Log in using your normal email address and password. 3. Read the NetSuite Release Preview Agreement and click Continue to accept the terms and access the Release Preview software. Read the Sneak Peak and Release Notes documents provided in the New Features Portlet so that you have time to review new or changed functionality well before the release. 4. Review the Key Workflow Example and test your normal, day-to-day workflows as suggested in the following sections to make sure there's nothing unexpected in the new version. Note: The Release Preview account runs separately from your standard NetSuite account. Please continue to use your regular NetSuite account for your daily company processes.
** Offline Client config file can be edited to point to a different environment *** Online Bill Pay is automatically disabled in Release Preview Memorized Transactions do not fire in Release Preview Page 2 of 9 .Sample Action Plan Release Preview 2 FUNCTIONALITY AVAILABLE FOR TESTING The following table describes functionality available for testing in the Release Preview. Only modules that you have purchased and enabled in your live account will be available in your Release Preview. no campaigns executed. no payments processed. * Feature available but no action will be taken: no emails sent.
Custom Record Types. 3. AND OTHER CUSTOMIZATION 1. Save this list as your checklist for testing. cut and paste it into an Excel file. Note: It is not necessary to test custom forms that you no longer use. Go to Setup > Customization > Entry Forms. export the lists to use as checklists during testing. Pay particular attention to any Customized Reports. fulfillments. forms. Since this data cannot be exported. Export this list to CSV or xls. Note any form that is linked to SuiteScript and/or Script Libraries and make sure to test this. shipping. Page 3 of 9 . Your testing goal is to ensure that the filtering. Review the list and remove any forms named ‘customize’ as those are NetSuite default forms. Custom Searches or bulk operations such as billing. formulas. 2. If desired. reduce the date ranges for those searches/reports. run the identical report in your live account and in the Release Preview. Make a list of all of your customized reports. Test each form/report/search against your checklists to ensure they behave as expected. Make a list of these types so that you can test each and check it off after testing. We recommend that you generate reports using date ranges that can be compared between both accounts. Tip: Release Preview is a copy of your live account as of a certain date. If any customized form/script/report uses a formula. FORMS. cut and paste it into an Excel file. Compile lists of reports. Review the list and remove any forms named ‘customize’ as those are NetSuite default forms. etc from your live account to test: Go to Setup > Customization > Transaction Forms. Save this list as your checklist for testing. For example. Since this data cannot be exported. so the data in it may not be the same as in your live account. Since this data cannot be exported. and sorting of each report/search functions as expected. Go to Setup > Customization > Record Types. Go to Reports > Saved Searches > All Saved Searches. Compare formula columns from the two reports to verify that the results are identical. cut and paste the list into an Excel file. If your reports/searches run more slowly in the Release Preview. Drill down on each type of custom field in this menu. Make a list of all of your customized searches. Also test that all scripting and libraries are work as expected. Most of these lists will be visible when testing your forms but take note of them for reference. Export this list to CSV or xls. Go to Reports > Saved Reports > All Saved Reports. etc.1 TEST CUSTOM REPORTS. 4.Sample Action Plan Release Preview 3 RECOMMENDED TESTING PLAN 3. Note any form that is linked to SuiteScript and/or Script Libraries and make sure to test this. Customized Forms. Check each item off of your printed checklists after testing. Performance in the Release Preview account may differ from your live account because it runs on different hardware. Go to Setup > Customization > Lists. Records & Fields menu area. record types. ensure the formula results are the same as in your live account.
In order to test pages available from Custom Center links in the Release Preview. If you are still engaged with a NetSuite Partner we recommend that you notify them of your Release Preview dates and request their assistance in testing the custom work. when you click custom center links in the Release Preview.3 TEST OTHER CUSTOMIZATIONS How you test other customization depends on who implemented the customization and whether you are still engaged with that company: NetSuite Professional Services Customization If you are still engaged with NetSuite Professional Services on this work. If the custom work has been signed off by you and you use it in your day-to-day routine. KPI Scorecards. If you are still engaged with the third party we recommend that you notify them of your Release Preview dates and request their assistance in testing the custom work. please contact them or inform NetSuite Support. engage your internal person who maintains the customization to test it out in Release Preview. Support will make Professional Services aware of your Release Preview dates so that they can coordinate testing with you. the links do not include beta. For example. Page 4 of 9 NetSuite Partner Customization Third-party (hired contractor) Customization . 7.com/pages/customerlogin. i. Verify that any custom fields or custom record types function as you expect. Therefore. for each custom record.beta. Test your custom workflows from start to finish. Check Dashboard functionality: KPIs.com/pages/customerlogin.jsp?country=US to: https://system. Custom Center links are hard coded from your live account. 3.e. etc.netsuite. in the domain name as is found in the Release Preview URL. add beta to each link in the Release Preview as follows: Change https://system. those links will load pages from your live account instead of the pages from the Release Preview.2 TEST CUSTOM CENTERS In the Release Preview.netsuite. See Creating Workflow Tests below for more information.Sample Action Plan Release Preview 5. engage your internal person who maintains the customization to test it out in Release Preview. Report Snapshots. ensure that you can: Add and delete behavior is the same as in the live account Record is linked appropriately to parent record Formulas and forms function as expected 6. If the custom work has been signed off by you and you use it in your day-to-day routine. engage your internal person who maintains the customization to test it out in Release Preview. If the custom work has been signed off by you and you use it in your day-to-day routine.jsp?country=US 3.
netsuite.com/wsdl/v2010_1_0/netsuite. Make sure to test any operational SuiteScripts you have for backward compatibility.5 TEST WEB SERVICES INTEGRATIONS Test any operational Web Services Integration processes for backward compatibility.com/wsdl/v2_5_0/netsuite. Read the SuiteScript release notes for details on API changes.beta. Go to Setup > Customization > Scripting > Script.beta.com/wsdl/v1_3_1/netsuite.wsdl https://webservices.beta.com. to test your web service application in the Release Preview account.1 WSDL in production https://webservices.wsdl https://webservices.com/wsdl/v2_0_0/netsuite. Perform necessary tests on each of them to make sure they are still working as expected.com/wsdl/v2009_1_0/netsuite.wsdl Page 5 of 9 .com/services/NetSuitePort_2010_1.netsuite.netsuite. If you are engaged with a Partner for any of your Web Services Integration please contact them and inform them of your Release Preview dates so that they can provide a time and test plan to test the integration.wsdl https://webservices.wsdl https://webservices.netsuite.beta.netsuite. If you find any issues with your Server SuiteScripts you can put the script deployment in Testing mode and use the debugger on the beta domain to investigate the problem.wsdl https://webservices.beta. if you are using the 2010.netsuite.wsdl https://webservices. 4.netsuite. 3.wsdl https://webservices. 2.wsdl. The SuiteScript Debugger URL for your Release Preview account is: https://debugger. Modify the endpoint reference that you are using in your application to point to the release preview endpoint.com/wsdl/v2008_2_0/netsuite.beta.beta. 3. 5.4 TEST SUITESCRIPT 1.Sample Action Plan Release Preview 3.netsuite.netsuite. Changes you make to your account while in the Debugger Beta domain will affect your Release Preview account only and will NOT affect your live account.com/wsdl/v2010_1_0/netsuite.netsuite.netsuite.wsdl https://webservices.beta.com/wsdl/v2_6_0/netsuite. Script Records and note of all the scripts you have.com/wsdl/v2009_2_0/netsuite. you must use https://webservices.netsuite. The currently supported Web Services versions are: https://webservices. Script Deployment.beta.com/wsdl/v2008_1_0/netsuite.beta.beta. For example.
com 2. 2.7 TEST YOUR WEB STORE 1 Ping the shopping server in the Release Preview to determine the correct IP address: 2.Sample Action Plan Release Preview 3.1. Page 6 of 9 . make sure you test these bundles during the Release Preview program. Make sure you test all the critical workflows that rely on the third-party solution and inform the solution provider of any issues you may find.2.6 TEST INSTALLED SUITEBUNDLES If you have SuiteBundles installed in your account. 3.4 Edit the hosts file on your C drive: 1.2 Type cmd and click OK.1 Choose Start > Run.netsuite. 2. type cd Windows/system32/drivers/etc/ 1.3 Type ping shopping.beta.com and press enter to return the IP address for Shopping. please contact the solution provider and inform them of your Release Preview dates.netsuite.beta.1 In the command prompt window.1 Press Enter. For third-party bundles installed in your account.
3 above.5 Add a line to hosts file with the IP: For example: 10.Sample Action Plan Release Preview 1.1 Choose File > Save. 2 Login to your NetSuite Account and choose Setup> Website > Domains with the following properties: Domain name = www. 2.1.5.yourdomain.4.1 Choose File > Exit.1 Edit the hosts file by typing edit hosts then press Enter.com Hosted as = Web Store HTML Hosting Root = Live Hosting Files The site or page should populate with the company name Page 7 of 9 .com Note: Use the IP address returned from the ping in step 2.yourdomain.79. 1.14 www. 1.3.
and click Configure. Click View > Source (or Page Source). double-click Administrative Tools. and double-click Data Sources (ODBC).Sample Action Plan Release Preview 3 Save these settings. Page 8 of 9 . 2. Verify that your custom domain is the option selected for the Primary URL. 3. Confirm that you are viewing your site on the Release Preview shopping server: 1. Visit the web store on your custom domain. 3. At the bottom of the source code page you should see the new version number for the release (for example: 2010. In the Windows Control Panel.2. In your browser. Note: You may have to clear cookies if you visited this domain recently. 4 Go to Setup> Setup Web Site. Important: Remove the line you added to the hosts file after you finish testing.0. Log out of your current ODBC connection.8 TEST ODBC To test ODBC access in your Release Preview account: 1. 2. 5 6 Open a browser.xx). In the ODBC Data Source Administrator dialog. select the User DSN for the Netsuite ODBC driver.
5 REPORTING ISSUES Report any issues you encounter by calling Support or by submitting an online case. 3. To submit a case: 1.netsuite. 2. Result: Sales order saves with no errors. each workflow document should contain the following components: Workflow Name: Provide a unique name for the workflow Role: specify the role to use when testing the workflow Email: specify the email address to use for testing Navigation: Provide the detailed steps required to accomplish the desired task Results: List expected results Below is an example of a documented workflow. On the custom subtab (if one exists) "subtab_name" enter value abc123 in Custom Field 1.Sample Action Plan Release Preview 4. 5.beta. 4 CREATING WORKFLOW TESTS In order to test successfully with the Release Preview. 5. Go to the Support tab of your Release Preview account. Compile a list of the critical workflows your employees follow to get their jobs done and create a document (or worksheet in Excel) for each workflow. Add Item 123. change the Service Host entry from odbcserver. At minimum.com in order to connect to your live account. Choose customer xvz. 2.com. Choose Transactions > Sales > Enter Sales Order. Workflow Name: Create Sales Order Role: Administrator Login Email: userx@yourdomain. A case will be created in our system under your accounts that will be flagged as a problem in the Release Preview environment. Click Save. Page 9 of 9 . you should identify and document the key workflows in your live account and test them. We recommend that you create an excel spreadsheet with worksheets for each common daily workflow and use this spreadsheet during testing. 4. 6. After you finish testing in the Release Preview account you must switch the IP Address back to odbcserver. Click the "Contact Support Online" link and provide details of your issue.netsuite. Reconnect your ODBC connection.com to odbcserver.com Steps 1. In the Driver Setup dialog. Click OK in both dialogs.netsuite.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.