Blog Posts | ||
---|---|---|
|
2023 Release
#1 Electronic Signature Engine
Extending the core Electronic Signature engine from Jira to Confluence content.
Apply Electronic Signatures to any confluence content
Signature verification to certify that the signed confluence content and attachments have not changed
Invite other users to sign and manage the signature process
#2 Confluence Specific Extensions
Allow and persist personal signing Pins within Confluence environment.
Supports optional autoLock of content and attachments to prevent editing once signing has commenced.
Add eSign Status tracking to show Open and Finalized signature pages
#3 Confluence Macros Blueprints
Includes inline macro to display and allow Signing from within pages.
Includes sample and extensible confluence eSign blueprints for Document Approval and Training Attendance forms.
Tip |
---|
We Love Feedback Leave feedback via the Contact eSign button in the Atlassian Marketplace |
Recent Changes
...
Update Index
Table of Contents | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Patch Update - 2025-01-29
Status | ||||
---|---|---|---|---|
|
Type | Description | ||||||
---|---|---|---|---|---|---|---|
| Added support for the new Atlassian Automation URL pattern and auth token required for webhook triggered rules. See Update on Incoming Webhooks Trigger for Atlassian ... - Atlassian Community for more information on the recent change. Configure the webhook URL and auth tokens in eSign Space Settings. |
Feature Update - 2025-01-11
Status | ||||
---|---|---|---|---|
|
Type | Description | ||||||
---|---|---|---|---|---|---|---|
| Lock Working Copy In Review - This new (optional) workflow mode permits the documents to be read-only during the review stage.
Additionally it is now configurable if the document owners should retain the edit privilege while locked. | ||||||
| Document Dates in ISO Format - Document dates and time formats can now be configured to use an ISO date format (e.g. 2025-01-15 18:45). If enabled, this setting will apply going forward to newly started documents and revisions. Existing (released) documents will not be affected. On page macros, document records and the PDF approval record will all use this format. If not enabled (default), the existing standard format based on the Confluence account (of the user that starts the document) will apply. Configure this setting in eSign App Settings. | ||||||
| Confirmation messages (e.g. Signature Completed, Training Assigned, Action Completed) are now displayed within the document dialog for improved visibility. | ||||||
| The Revision Summary is now a required field as part of the Assign Reviewers action that starts the review process. This change will help ensure that a meaningful summary is provided for the reviewers and the document history macro. This field can be updated at any time during the review process by revisiting the Assign Reviewers page. If there is no summary information, enter “N/A”. | ||||||
| User Title can now be set as a required during Signature Execution. EAs before, eSign will automatically save and pre-populate the last used title for each user. Enable this option in eSign App Settings. | ||||||
| eSign Space Settings configuration page now provides a Space picklist for choosing the Target Release Space. This will make it easier to select a valid space for release, instead of having to manually look up the space key. | ||||||
| Technical updates for several internal API’s. | ||||||
| A new standardized End User License Agreement (EULA) has been adopted. | ||||||
| 2025-01-21 Fix issue with console logger compatibility with Firefox browser. |
Change History
Historical change logs are available.