What's new
Change of macro name from HTML to Html-bobswift
To comply with Atlassian requirements, the HTML macro name is now changed to Html-bobswift in the HTML for Confluence app. From this release, the Html-bobswift macro name is available for use; however, the XSLT macro remains unaffected by this change. The existing pages that use the HTML macro name are not affected by this change.
Important information for Macro Security users!
Existing pages that use the HTML macro name with the Macro Security for Confluence app are unaffected. Any new macro additions to pages to render HTML content now use the Html-bobswift macro name. Thus, you must specify the same HTML configurations in Macro Security for Confluence Configuration for the Html-bobswift macro name as given for the HTML macro. Any entries made for the XSLT macro remain unaffected and hence, the entries made for this macro can be retained as-is in the Macro Security configuration. Refer to the Configuration page for more information.
Migrate HTML content from server to cloud
To support our customers who are migrating pages and templates that use the HTML macro to cloud, there is a new menu item Migrate to Confluence Cloud in HTML for Confluence Configuration. Due to restrictions in Confluence cloud, the HTML macro name was changed to HTML-bobswift, and this page allows you to initiate a process that automatically updates the macro name to prepare your content for migration. Once this process is completed, administrators must run the Confluence Migration Assistant to migrate all your content to Confluence cloud.
Important information:
- Administrators must run the HTML macro name updation process before migrating content to cloud. Once the process is completed, the Confluence Migration Assistant must be run to migrate all content to Confluence cloud.
- About use of Macro Security on Confluence pages:
The customers who have installed and use the Macro Security for Confluence app must add the relevant entries for HTML-bobswift along with HTML so that the existing HTML content is rendered correctly after data migration. Refer to the documentation for more information.
Access HTML or XML files from remote locations securely with profiles
Use profiles to access your HTML and XML files from external sources without exposing any sensitive and/or secure information such as passwords. Administrators define a basic set of parameters such as the base URL of the location where the files are present, user credentials, access token, or other relevant information to access the specified location. Users can then select the profile in the macro editor and only need to specify the relative URL to the actual location of the file. Refer to profile configuration and some tutorials for more information about profiles.
Enjoy seamless connection to other applications with application links
Link other Atlassian applications, such as Bitbucket or Jira, with Confluence using application links. If an application link is specified in a macro, user credentials are then verified just once; after this, users can skip authorizing with credentials entirely. Application links allow you to work seamlessly with applications and render your HTML/XML content on a Confluence page. To know more about linking apps with Confluence, refer to application links documentation.
