Test a site

If you want to test a InSite site, create a backup and put it back using a different name. You create a full copy environment in InSite.

Note:

In the case of AFAS Online, you must create a copy of the environment. In this environment, the New environment will function as test environment check box cannot be selected. If you do this, the InSite and OutSite files will not be included.

Test InSite:

You should test InSite before the site goes live. You check if the configuration is correct and complete. In doing so, you also check the look and feel thoroughly.

  1. Create a test environment.

    Because entries in InSite directly result in entries in Profit Windows, for example after the approval in a workflow, you test the site in a test environment. For this, make a backup of your production environment and restore it as a test environment.

    Note:

    For AFAS Online, you get two URLs: https://12345.afasinsite.nl and https://12345/afasinsite.nl/test. We recommend you use the latter in the test environment.

  2. Open the test environment.
  3. Go to: General / In & OutSite / Site.
  4. Open the properties of the site.
  5. Go to the tab: Publish.
  6. In Web location, select the test server (such as http://klantnaam.insite.nl/InSiteTest).
  7. Click on: OK.
  8. Open the site by entering the web location in the web browser (Internet Explorer, Google Chrome, Firefox or another browser).

    If the rights have been configured properly in the production environment, you can test the site.

  9. At least check the following:

    Note:

    Check the below issues in combination with all authorisation roles.

    1. Is the InSite presentation (the theme) to your liking? Pay attention to the colours, style, fonts, etc.
    2. Do the views have the correct columns and fields? Are the names correct?
    3. Go through the workflows step-by-step and logged on as different types of users (for example, employee, manager, board member and HR staff member).
    4. Check the functionality you are using, for example: Declarations, absence, leave, workflows you created yourself and changing name and address data;

Because InSite is platform-independent, you need to test InSite in different web browsers. Check the above issues with other web browsers than Internet Explorer too. For example, on a Mac and/or on an iPad. If changes are necessary, make sure that the changes are implemented in the production environment too.

Directly to

  1. Install InSite
  2. IIS
  3. Set up InSite for AFAS Online
  4. InSite system requirements
  5. Default InSite installation using the installation program
  6. One application server with a local web server
  7. Multiple application servers, with a web server on each
  8. One or more application servers with a separate web server
  9. Link a web server to a domain
  10. Test a site
  11. Configure InSite on a test server
  12. Publish InSite in another language
  13. InSite displays a message after the installation of a Profit Update
  14. Reset the password for the Profit Application Service
  15. Unblock a web server
  16. Unblock a domain