|AppsFidelity Documentation (no license required)|
|• AppsFidelity 4.2 manual (pdf) (Revised May 25, 2018)|
|AppsFidelity 4.2a Software (requires 3.x license, CoexEdit license will not work)|
|• AppsFidelity Version 4.2a for Notes/Domino 6.5x to 9.x on Windows 32-bit (Released June 5, 2018)|
• AppsFidelity Version 4.2a for Notes/Domino 8.5x to 9.x on Windows 64-bit (Released June 5, 2018)
• AppsFidelity Version 4.2a for Notes/Domino 6.5x to 9.x on Linux 32-bit (Released June 5, 2018)
• AppsFidelity Version 4.2a for Notes/Domino 8.5x to 9.x on Linux 64-bit (Released June 5, 2018)
AppsFidelity 4.2a is available for Windows 32-bit/64-bit and Linux 32-bit/64-bit. If your company has a need for AppsFidelity on any other platform, please let us know.
Previous versions of AppsFidelity are available at the bottom of this page in case of the need to revert back.
|Sample integration databases|
|• AppsFidelity Integration databases (Released June 5, 2018 for use with AppsFidelity 4.2 and above.|
The AFIntegration.nsf should be put in an AppsFidelity folder under the Domino data directory, whether or not Classic or XPages use is intended, as it contains both the Classic demonstration files and the files which are used in other databases. The Discuss.nsf database is not required, but demonstrates how AppsFidelity can be used in XPages with the extra doclink and attachment plufins.
Sample databases will not work without a valid AppsFidelity license file, which can be requested here, and the AppsFidelity software and the web editor software, both of which can be downloaded from this page. It is usually best to get the integration database working on your server first, and only then try to integrate with your own database. This helps identify any configuration issues quickly.