Document Actions
4.
Checking Engagement GUIDs
Up one level
Previous:
Uploading Files to Documents other than Engagements
When uploading a Working Papers client file to a new Engagement, or to an Engagement that does not currently have a Working Papers client file (i.e., it has a PDF file or some other file type), the OpenEngagement DMS does not check the GUID; if there is a GUID, the DMS simply extracts the GUID from the client file, and stores it in the DMS's Engagement object. But, when users upload a client file to an Engagement object that already has a client file, the OpenEngagement DMS then checks if the GUIDs match. It will not allow uploading a client file if the GUIDs do not match. That is, the OpenEngagement DMS will not allow users to overwrite one client file with another, but will allow users to overwrite one client file with another version of the same client file.
Working Papers client files from version 2004.00 and later have GUIDs that uniquely identify them. The GUIDs may be viewed by right-clicking on a compressed client file and viewing the custom file properties. They're a string of letters and numbers, such as adc5716a-e26b-4764-b99fd94a54b2. Where Engagements contain client files prior to Working Papers 2004.00, it is not possible to check the GUIDs. In this case, whenever another file is uploaded to the the Engagement, a warning message is presenting asking the user to confirm they wish to overwrite the file contained in the Engagement object. It is possible for the file in the Engagement to not have a GUID and a file later being uploaded to have a GUID, and for these to actually be the same client file. For example, it is possible that the first version of the client file was opened in a version of Working Papers prior to 2004.00, then the file was rolled up to Working Papers 2004.00 or later, so was given a GUID, and this is what is being subsequently uploaded to the Engagement.
Once an Engagement contains a Working Papers client file with a GUID, it is not possible to upload another client file unless it has the same GUID.
| Old File | New File | Action |
| has a GUID | same GUID | allow upload with no warning |
| has a GUID | different GUID | disallow upload |
| has a GUID | no GUID | disallow upload |
| no GUID | has a GUID | allow upload with a warning |
| no GUID | no GUID | allow upload with a warning |
OpenEngagement DMS also uses the GUIDs associated with CaseWare client files to check that the same client file is not uploaded to more than one location within the DMS.