EDM

---

Assumptions

The engineer has a good working knowledge of the EDM solution

---

General

If you are experiencing problems, tick off the following questions and check as appropriate. This is at quite high level, but taken from our years of support experience, common areas that have raised questions when debugging issues.

NOTE: EDM is shares many of the same processes as EDD, so it's a good idea to tick those off as well.

If having satisifed them and you are still having issues, contact the V1 Support Team with details of the issue.

Have you checked the log files?
The Administration > Logs (section on EDM) gives you details on all logs and in most circumstances tell you one way or the other what the problem is.

---

Archiving

Does the Sage installation meet the minimum Patch requirements for compatibility?

Although thoroughly tested, V1 cannot guarentee with 100% certainly a Sage X3 patch will be compatible, but given EDM is very 'light touch', it's unlikely you will have issues.

Has the Implement EDM section been followed in full?

When printing to the ARCHIVE destination or whe clicking one of the links in Sage X3 to archive a document:
Is Sage creating the image in the \V1\EDMIMPORT\TRANSACTION or ATTACHMENT dir(s)?

This is a common issue, it's usually caused by the RUNTIME\configRuntime.json not having network share added correctly.

NOTE: Only applies if the ARCTYPE Parameter is set to disk. Check the Sage Pre-Patching Tasks – Sandbox Settings chapter in the Install the Server Components section for guidance.

Is the DbArchive: EDM Import service running?

This is the service that periodically triggers EDMImport.def, so if it isn't running, nothing will archive

Is the X3EDM!ENDPOINTNAME! ClassicPool running?

This is the gateway allowing V1 to access to Sage X3. If it's not running / has stalled / Syracuse has been updated / any changes made to V1 web-services, it will need restarting.

Have the Endpoints been patched for EDM?

The best way to check is to log in to Sage, go to Development > Scripts > Web Services (GESAWS). Filter for those beginning XV1. If you see them, (such as XV1PIHLU) you've patched.

Are your DbLogin users uppercase, assigned their licences, access and email addresses assigned?

Is the DbArchive.DBA__FILTER_MAP SQL table populated?

Either using the setup program or using the FilterMapMaintenance addon, if this is empty / wrong, no users will be able to see any images via SmartRetrieve, deposit anything through SmartDeposit, or use PIA with DbCapture / SmartExtract.

Are the settings in \V1\DbArchive\V1_SETTINGS.def correct?

This include file is shared across all archiving activity. If any value is wrong / has been changed since it was originally implemented, it will result in connectivity and accessibility error messages. Any changes made to this file are immediately applied, so no need to restart any services.

Ensure the locale of the server and your browser is set to the language of choice so dates are displayed correctly in SmartRetrieve.