Documents

Dev Notes

Important information when upgrading Document Automation and Upgrading to Graph.

At the point you need to upgrade, you will need to update the Sage addons in the normal way, please ensure that Documents and Common Components are on the same version.

It is vital that you clear all your cache’s once the upgrade has been completed, otherwise this may cause unexpected issues when importing documents from Exchange 365. All Sage 200 users must perform a Local Application Cache rest below.

Admins will need to do the following after upgrading to Document Automation v26.0.8:

Prerequisites

Please ensure this is done with your IT providers and an administer as you will need:

• Access to an administrator account on your Sage 200 Server.
• Access to the Sicon WebAPI user on your Sage 200 Server.
• Access to an Azure Active Directory administrator who can amend tenants.

Local Application Cache Reset

1. Close Sage 200
2. Win + R
3. Type in %LocalAppData% and select Go
4. Find the sage folder and right click it
5. Select Rename
6. Change it to Sage200.old

Sage 200 Self Service Cache Reset

1. Go to IIS (Internet Information Services) in Windows Search
2. In the Connections pane, expand the selection where it displays the name of the server and select Application Pools
3. Select Sage 200 Self Service and Press Stop on the right-hand panel.
4. Now, select CTRL + R
5. Type in C:\inetpub\Sage 200 Self Service\Sage200SelfService\AddOns\Sage
6. Select the Sage 200 folder and right click it
7. Select Rename
8. Change it to Sage200.old
9. Now, go back to IIS and restart the application pool.

If you’re using the WebAPI to automatically import documents.

Stop Sicon WebAPI Services

1. Win + R
2. Type in services.msc and go
3. Find Sicon WebAPI Service for Sage 200c
4. Right Click and Stop
5. Find Sicon WebAPI Updater Service
6. Right Click and Stop

Sicon WebAPI ISS Cache Reset

1. Go to IIS (Internet Information Services) in Windows Search
2. In the Connections pane, expand the selection where it displays the name of the server and select Application Pools
3. Select SiconWebAPI and Press Stop on the right-hand panel.
4. Now, select Win + R
5. Type in C:\inetpub\wwwroot\Sicon.Sage200.WebAPI\AddOns\Sage
6. Select the Sage 200 folder and right click it
7. Select Rename
8. Change it to Sage200.old
9. Now, go back to IIS and restart the application pool.

Sicon WebAPI Local User Sage Cache Reset

1. Log into the Sicon WebAPI user
   1. If you are unsure on which user account is used, this can be found by going into Services.
   2. Win + R
   3. Type in services.msc and go
   4. Find the Sicon Web API Service for Sage 200c
   5. Right click and select Properties
   6. Go to the Log On tab and it will tell you the user account

1. Ensure Sage 200 Client and Admin is off.
2. Win + R
3. Type in %LocalAppDATA% and go
4. Find the sage folder and right click it
5. Select Rename
6. Change it to Sage200.old

Start Sage 200 Services

1. Win + R
2. Type in services.msc and go
3. Find Sicon WebAPI Updater Service
4. Right Click and Stop – this will start both services.

Once you have done this you can now open Sage 200.

 Changes needing to be done in Document Automation

Now all the binary files have updates, we can now ensure that Sage 200 will be using the latest version of Document Automation. There will be a few extra steps to ensure Document Automation runs as expected:

• Ensuring Document Automation Exchange has updated.

To ensure Document Automation is pointing to the correct area, you will need to check the path within Automation Settings. You can do this by:

1. Within Sage 200, got to Sicon Documents > Document Automation > Automation Settings.
2. Select E-Mail Integration tab.
3. Select Exchange 365 tab.
4. Ensure the MS Graph URL shows ashttps://graph.microsoft.com/v1.0/users/

If this is not showing the right information, please retry the steps above as this likely due to a mismatch in version within the binary files.

If it’s showing as graph:

1. Use the Email Address for Testing field to input an email address previously working to ensure the connection is working correctly.
2. If you receive an error message, then select the Auto Configure button to create a tenant and connection to Document Automation. Then re-test the email address and then it will allow you to connect to the tenant.
3. If you are using the WebAPI to pull through documents from your emails, you will need to restart the WebAPI within Services. Use Stop Sicon WebAPI Services and Start Sicon WebAPI Services.

Once this has been completed, you can now continue as before.