Q: How do I open a spreadsheet that was onboarded into Apparity?
Open the file as you normally would. Opening an Apparity managed spreadsheet is no different from opening a spreadsheet that is not managed by Apparity. Simply locate and open the file on your Shared Drive, SharePoint, or ECRM.
Q: Does Apparity track files that were copied, renamed, or moved to different locations?
Yes, as long as it is an Apparity managed file that was copied, renamed, or changes locations (with the exception of desktop locations). Apparity will track these types files and will recognize them as being a part of the original file’s family. It will automatically register the files within Apparity, and the Version History pane will be updated accordingly. Apparity is able to do this through the fingerprinting technology used during onboarding.
Q: Why did my file automatically onboard when I opened it?
It is because the file was created as a copy of an existing Apparity managed file. Therefore, it was onboarded automatically into Apparity. This typically occurs when a new copy of the file was made, the location of the file changed, or the name of the file changed.
Q: I received the following message when trying to open an Apparity managed file, "This copy of an Apparity managed file could not be auto-onboarded because it was opened in read-only mode. To track this copy and have it auto-onboarded into Apparity it must be re-opened in edit mode."
This message appears when a new copy of an Apparity managed file opens as read-only. Common scenarios include when opening an Apparity managed file directly from your Outlook email inbox or when a copy of a read-only Apparity managed file is created and opened on a network drive.
To resolve this message, save the file in edit mode to a network location (i.e., not local C:\ drive) and re-open the file to have it auto-onboard in Apparity.
Q: When opening my file, I received a message that says, "Unrecognized Change Event Detected." What does that mean?
This message indicates that there were changes made to an Apparity managed spreadsheet outside of the Apparity control framework. The message is prompted if any of the following scenarios occur:
- A non-Apparity user modifies an Apparity managed spreadsheet. The "Unrecognized Change Event Detected" warning will be displayed when an Apparity user opens the managed spreadsheet.
- A user modifies an Apparity managed spreadsheet outside of the network, and then he or she reintroduces the spreadsheet back inside the network.
- A user completes a Copy and Paste over an Apparity managed file with the same name.
- A user completes Save-As with the same name as an Apparity managed file and chooses to replace the Apparity managed file.
- A user updates the file on shared drive while Apparity server is down.
- A user modifies the spreadsheet, saves it, continues to modify the spreadsheet, but upon close, chooses Don’t Save.
- A user protects the workbook with password encryption.
Q: What are my different options when I receive an "Unrecognized Change Event Detected’’ warning?
Users have two options when this warning appears. Before selecting either option, click on the Help button, then select Run Compare to see the changes made between this version and the last captured version in Apparity to determine if they should be kept or ignored. If you are unsure whether to keep the changes or not, it is recommended that you accept the changes and save the latest version in Apparity. You will be able to restore a previous version of the file, if you decide later the changes captured were not appropriate.
- Accept this version with the unrecognized change event and save this version in Apparity - This option will save any changes that were made since the last captured version in Apparity. The Version History pane will be updated to reflect a new tampered revision.
- Reject this version with the unrecognized change event and open the latest saved version in Apparity - This option will ignore any changes made since the last captured version in Apparity. It will replace the file with this last captured version. The rejected changes will be lost.
Q: Can I submit a change log for review against a tampered version of the file?
Yes. You are able to submit a change log for review against a tampered version of the file, as long as that tampered version was saved in Apparity.