Test InSite in the copy environment

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.

Add a test site in AFAS Online

You create a copy environment in AFAS Online and you test the site from this environment.

New customers have two URLs by default:

• https://12345.afasinsite.nl
• https://12345.afasinsite.nl/test

'12345' is the participant's number. If your user code is, for example, 12345.BKR, your participant number is 12345.

Create a test site:

1. Open the environment for which you want to create a backup.
2. Go to: General / Environment / Management / Copy.

   If this menu option is not available, you may first need to authorise it.

3. Do not select the New environment will function as test environment  check box so that you create a complete copy of the environment. This requires greater performance and it will take longer until the test environment is available.
4. Add a description for the copy environment.
5. Click on: Finish.

   You see the name of the new environment.

6. Click on: OK.
7. Open the environment.
8. Go to: General / In & OutSite / Site.
9. Open the site.
10. Go to the tab: Publish.
11. The path of the test site, therefore https://12345.afasinsite.nl/test.

    Note:

    NEVER select the URL of the live site here.

12. Click on: OK.

Create a test site in a local Profit installation

To create a test environment, reset a backup using a different name.

Create a test site:

1. Make a backup.
2. You restore the backup using a different name.
3. Execute a site default installation.

   Note: 

   Enter a new URL in the installation wizard.

4. Open the new environment.
5. Go to: General / In & OutSite / Site.
6. Open the site.
7. Go to the tab: Publish.
8. Select the path of the test site.

   Note: 

   NEVER select the URL of the live site here.

9. Click on:  OK.

   Note: 

   If you do not want to use the default installation, carry out the steps below.

Add a virtual path for the test site:

1. Open the central logon environment. The function below is only available in this environment.
2. Go to: General / In & OutSite / Configuration / Domain.
3. Open the domain properties.
4. Go to the tab: Virtual paths.
5. Click on: New.

   You now see the domain and internet address where this is accessible.

6. Enter a value in Virtual Path, example InSiteTest.

   Behind the Accessible via URL field you see the full path where the site can be reached.

7. Select the login method in Authentication method.

   If you are using application authentication for Profit Windows, you can only select Profit (enter the Profit username/password). Users must log on using their Profit user name and password. Using this method, a user can log on with his e-mail address on condition that the e-mail address is recorded for the user in the General / Management / Authorisation tool.

   If you are using Windows authentication for Profit Windows, both methods are available.

   • Windows (integrated)

     A user is logged on automatically when launching InSite.

   • Windows (enter Windows user name/password)

     Users must log on using their Windows user name and password.

8. Click on: Next.
9. Select the communication type: Connection with the Profit Application Server on the web server.
10. Click on: Next.
11. Click on: Finish.
12. Execute the Site Deployment Tool.

Link InSite to the copy environment

1. Open the test environment.
2. Go to: General / In & OutSite / Site.
3. Open the properties of the site.
4. Go to the tab: Publish.
5. In Web location, select the test server (such as http://domein/InSiteTest).
6. Click on: OK.
7. Open the browser and enter the web location.

   If the authorisation has been configured properly in the production environment, you can test the site.

8. Always check the points below for 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.