- Created by //SEIBERT/MEDIA employee, last modified on Jul 31, 2020
Documentation's navigation
Patch Release We fixed a problem with linked Jira issues when the current disclaimer had not yet been accepted. We also improved the handling of custom Confluence logos and cleaned up the logging behavior. Patch Release We fixed a problem with Oracle databases when configuring Terms of Use. We fixed a problem with PostgreSQL and migration tasks. We're happy to announce Confluence 7 compatibility! Fix for a MySQL issue with the migration from usernames to user keys. The migration task didn't handle deleted users properly. Now it does. FeaturesVersion 1.9.5
Version 1.9.4
Version 1.9.3
Patch ReleaseVersion 1.9.2
Compatibility Release Please note, that this version does not contain any further fixes or features.
If you are not using Confluence 7, there is no need to update.Version 1.9.1
Bugfix releaseVersion 1.9.0
New editor and translation possibility
Fixes We are now compatible with Data Center compatibility release We are happy to announce Data Center and read only mode compatibility This was an internal release The PDF uses the styles of the disclaimers html view. Furthermore some special chars are handled correctly. You may have designed a clear disclaimer so your PDF should look the same way. This was done in 1.8. Empty Terms should not be displayed If you installed the plugin in a version < 1.6 and did not configure any disclaimer, it might happen your users get an disclaimer showing ''undefined'. This disclaimer is not shown anymore in 1.8 and will be deleted once and for all.Version 1.8.5
Compatibility ReleaseVersion 1.8.4
Version 1.8.3
Bugfix releaseFixes
Version 1.8.2
Version 1.8.1
Improve PDF view IISome more adjustments for the PDF view
Version 1.8
Improve PDF viewDesktop vs. PDF view
The administration section can now always be accessed, even if the disclaimer is not accepted. This enables administrators to deactivate the plugin in case of an error. Administrators are now able to see the user's status regarding the terms, such as "revoked" or "no action yet". You can therefore see which users have already accepted the terms. Version history of previous terms Previously, when you changed the terms, all user agreements and the previous version of the terms were deleted. To comply with the GDPR, there is now a version history for the terms and agreements. Administrators can now see the actions users took (or didn't take) to previous terms and and review earlier version's of the terms' content. By revoking the terms after a user has accepted them once means that they are logged out of the system and, if configured, the administrator gets an email notification. Users will see an additional warning so they don't revoke their agreement by mistake. Your users need to be able to accept the terms even when they are using the Linchpin Mobile app. We have implemented the backend API, and our Linchpin Mobile team will use this to implement the interface in the app. We have added the context path for accepting and revoking the terms. First feature set for GDPR compliance Terms of use are disabled when disclaimer is emptyVersion 1.7.1
Hotfix Release
Version 1.7.0
The GDPR ReleaseAgreement log for user activities
User information when revoking the terms
API for Linchpin Mobile
Bugfixes
Version 1.6.0
Features
Enhancements
Version 1.5.0
See who has accepted the disclaimerFeatures
Enhancements
Version 1.4.0
Fixes
Version 1.3.5
We are Confluence 5.9 ready and fixed some major bugs.
Features
Fixes
Version 1.3.4
We fixed a bug with case insensitivity and usernames
Enhancements
Fixes
Version 1.3.3
Features
Enhancements