Release notes in this article reflects all add-in releases that are considered stable. If you're looking for release notes for VSTO add-ins in an earlier stage, please go to our release note article specifically for that. Release notes below are separated into features and bug fixes per month and year.
Latest stable add-in version: 5.8.0.1984
January 2020
5.8.0.1984
SVG files containing the CSS property "stroke-dasharray" could not be inserted in VSTO Add-ins through the Images Library or any External Library in office applications. This problem was due to uing an outdated SVG library (version 2.4.3).
In this release we are upgrading the version of the SVG library to 3.0.102, which is the latest stable. The upgrade fixes issues caused by the "stroke-dasharray" property and allows users to insert them from Images and any External Library into the VSTO Add-ins into their documents.
5.8.0.1980
This is a purely technical release in order for us to upgrade one of our package in the VSTO Addins. This release does not introduce any new functionalities and it does not contain any breaking changes.
5.8.0.1972
We have implemented the groundwork to support OAuth2 authentication for external libraries. This will have no impact on the existing OAuth1 implementation for Bynder.
5.8.0.1968
Templafy Logo blurry when clicking on "about" section from the Add-in dropdown
This release fixes the resolution of the Templafy Icon both in the Ribbon and the "About" Dialog.
The Templafy Icon had been incorrectly modified in version 5.7.5.1913 to a smaller size (32x32 instead of the original 256x256 pixels) as part of upgrading icons to a new design. The resolution has been fixed in this release as you can see in the attached screenshots, bringing back the correctly sized icon and avoiding the blurry effect when the "About" Dialog is shown.
5.8.0.1966
Image header does not get inserted as per specified dimensions
During a change, that has been deployed to the website on December 11th, 2019 and VSTO Add-ins version 5.7.5.1935, a new bug was introduced causing the image header to be inserted with incorrect dimensions.
The bug caused images that have a bottom and right alignment and also have a top and left offset to be too big in size.
When this bugfix is deployed, the issue is fixed and customers only need to update their VSTO Add-ins.
5.8.0.1959
File header information is not used when downloading files in VSTO add-ins
It was experienced that nothing happened when inserting SVG assets through the Papirfly integration in VSTO Add-ins.
During asset insertion, we save the files to disk and then rely on them having a valid name and extension. Thus, if a file is saved under an incorrect extension, the insertion might fail. The problem was that Templafy relied on the URL of the asset to determine the file name and extension.
For example, for https://domain/images/logo.svg the file name is logo and the file extension is .svg
This caused some assets to have an incorrect or missing extension given URLs such as:
https://domain/images/logo.aspx which has a different ending than the file extension or
https://domain/images/logo which has no extension at all.
Our solution was to use the content-type specified in the response headers of an asset to determine their extension. For example, we can determine that a document with image/svg-xml content-type has the .svg extension. We support the following content types when inserting images:
image/png
image/jpeg
image/gif
image/tiff
image/bmp
image/svg+xml
If the content-type does not match any of the supported extensions we fallback to the extension specified in the URL
5.8.0.1955
Bump the VSTOAddIns minor version number to 5.8
With this release, we now make the Link Library available inside Outlook using version 5.8. It has been requested to have a feature to be able to easily insert links to e.g. support website, articles, guides.
When clicking a link in the WebApp a new browser tab is opened. In Outlook this works slightly different, as clicking the link will insert a hyperlink with the asset name into the body of the email. As shown here: https://share.getcloudapp.com/9ZuWpYyo
Until this release Link Library was available in the WebApp (running in a browser) and in the versions of the Outlook Vsto Add-in higher than 5.7.5.1931. Changes to our Website (will be released shortly) will remove access to the Link Library for all VSTO Add-ins under 5.8.x.x.
It's necessary to update Outlook VSTO Add-ins to version 5.8.x.x to be able to select the Link Library in the ribbon and task pane and to be able to insert Links into their emails.
5.7.5.1953
Image gets blurred on update
We noticed an issue with Document Updater where EMF images became blurry after being updated. With this bug fix, Updater now updates EMF images properly without making them blurry.
Customers are required to update their VSTO add-ins, but no other actions are necessary.
5.7.5.1951 January 3rd, 2020
13187 External System flow fails on in line level content controls
Closed
When creating a document as part of the Document Management System (DMS) flow, we insert content from the DMS into the created document. This would fail when the DMS supplied rich content, for example tables or images, to be inserted into plain text content controls, which do not support rich content. We now only copy plain text into plain text content controls.
December 2019
Bug fixes
5.7.5.1949
Updater fails: corrupted table
We noticed further scenarios where Updater for Word was failing to remove tables from content controls.
December 2019
5.7.5.1937
Updater fails: corrupted table
We noticed an issue where our Document Updater was misbehaving when it was removing contents from Text Element with a table and it was resulting in a corrupted table. With this bug fix, Updater cleans up Text Elements properly even when it contains tables without corrupting document/table.
5.7.5.1935
Document with section breaks set with "same as previous" on the header - configuration is removed after creating document from Templafy if Text Element is inserted into Content Control
We had an issue where the “link to previous” functionality of headers in word documents didn’t work when adding images into headers via Dynamics. As soon as this Dynamics functionality was used, the settings of link to previous would be lost, meaning that some of the expected built-in functionality of Word would be lost.
We have solved this, by making sure that header configurations in documents are always retained if it’s configured, even though an image is inserted into the header through Dynamics.
This fix requires and introduces a new Dynamics version 1.12.
November 2019
Features
5.7.5.1931
Enable link library insertion in Outlook VSTO
We enabled proper link insertion in Outlook VSTO Add-in. Previously when selecting a link asset, it would open the link in a new window in the browser. We updated the insertion method so that a hyperlink with the asset name is now inserted inside the email.
5.7.5.1916
Resize image when inserted & activate crop (use fit width or height to container)
Outlook: Inserted images inserted into image placeholders are now resized correctly and put into in crop/resize mode afterward.
5.7.5.1913
Make client send link to VSTO for insertion
Updated old Icon.png files and added LinksIcon.png.
Set Link as a valid AssetType for the OutlookVSTO Client, adding it to the Ribbon and also showing in the TaskPane.
5.7.5.1909
Visualise that old slide is old
With the new Dynamics Version 1.11, the Validator feature for presentations has now been updated to make it possible to enable validator without locking slides.
When an unlocked slide is updated by Validator, the existing slide in the users presentation is kept, and the updated slide is inserted after the existing slide. A noticiation is added to the existing slide to make it clear that it is outdated. This allows the user to copy his changes over to the new slide if he has made modifications to the existing one, and then he can manually delete the existing slide afterwards.
To use this feature, a template needs to be Dynamics Version 1.11.
Bugs
5.7.5.1922
Outlook: Popup with error when inserting a text element with a textbox within a textbox
Inserting a text element that contains a drawing object (ex: a textbox or a hand drawing) inside a textbox result in an error. Since this is a limitation of Office itself that does not allow the insertion of a drawing object inside a textbox we have improved the message shown to the user and the pop up will now state the following: "The text element you're inserting contains a drawing object, and therefore cannot be inserted into a text box, callout, comment, footnote or endnote".
The changes have been done both in Outlook and Word.
5.7.5.1918
Undoing "insert text element" in Outlook is required to be clicked twice
Outlook: Undoing "insert text element" now requires only one undo step
5.7.5.1911
Insert text element event is not raised
AssetInsertedSucceded event is now triggered and reachable throw dotnet Named Pipes when a Text Element from the Library is inserted into a document using the Word Vsto Addin
5.7.5.1907
Excel task pane does not open automatically in some cases
In some cases even if the option "Open task pane automatically" was set the task pane was not being opened after starting Excel.
The problem has been resolved by making a more reliable check to understand if the task pane must be opened or not.
October 2019
Bugs
Add-in version 5.7.5.1903
Excel background process never ends requires
When inserting an Excel object into Word, there is an Excel process generated on the background. Such process would not close if Templafy add-ins were enabled, because Templafy would load the task pane on the embedded Excel instance, hence, impeding it from ending. Down the line, this was causing some issues with some 3rd party tools for Excel.
We have now made sure that the Templafy Excel Add-in is not fully loaded when Excel is running in the background so that it can be disposed correctly by Word.
5.7.5.1873
11546 Switch to Newtonsoft.JSON
The parsing of the configuration during the startup of the add-in is now done using Newtonsoft.JSON to improve the loading time
5.7.5.1866 October 16th 2019
11553 Add new custom document property flag for communicating with ExternalSystem
Closed
Fetching data from a Document Management Systems (DMS) and filling it into the document creation form now requires a TemplafyRequestExternalSystemData Custom Document Property in addition to the existing TemplafyExternalSystem property.
The existing "DMS flow" is not changed and does not require additional configuration.
October 2019
Features
Add-in version 5.7.5.1863
Prefill form data from External system
We now support fetching data from Document Management Systems (DMS) and filling it into the document creation form in Word and PowerPoint. This requires an external add-in which acts as a bridge between Templafy and the DMS. The existing "DMS flow" is not changed and does not require additional configuration.
Add-in version 5.7.5.1850
Make it possible to open Templafy Taskpane with .net named pipes
We added the possibility to open the Task pane from another add-in by calling the OpneTaskPane end point. This is done through .net named pipes, the same way as our other APIs work in VSTO. This feature makes it possible in a larger degree to automate functionality inside Office.
August 2019
Features
Add-in version 5.7.5.1837
We now support dynamic forms when a template has text element insertion configured with form bindings. The saught after use case for this feature, is gating questions.
The feature allows template admins to create templates where the user can make selections (Using drop downs), and based on their selection, new questions (Form fields) will appear, allowing the user to customize the document created to an even greater degree.
Add-in version 5.7.4.1823
We're introducing Dynamics version 1.10, which allows using form field references, when inserting text using the TemplateBinding property.
In Dynamics 1.0 - 1.9, you cannot reference form fields in the TemplateBinding property, but we've removed that restriction from Dynamics 1.10, for both word processing and presentation documents. When we removed the restriction, we also added support for text extraction from the places where text is inserted using TemplateBinding, but only if the expression binding 1) contains only one binding and 2) if there's no literal text being concatenated with the binding.
In other words, we only support text extraction for TemplateBinding, if the expression binding looks like this: "{{Form.FieldName}}".
Bug fixes
Add-in version 5.7.5.1840
We had an issue where our add-in would stop working if a spreadsheet was set up for updating a document property that was not set. We've fixed it so we just ignore it if a document property is not set.
Add-in version 5.7.5.1837
We had an issue with text element insertion, where form fields coming from a text element was not being pre-filled when showing the document update form. We've fixed this issue, so form fields are correctly pre-filled.
July 2019
Features
Add-in version 5.7.3.1788
Since we already separated the EmailSignature and VSTO Add-ins code base, this story continues the separation and also creates separate artifacts for each add-in. That means from now on we will have a package containing the Library add-ins and another lightweight package containing the Email Signature add-in.
Note:
- The folder structure has also a slight change, the add-ins are not deployed directly under the %LocalAppData%/Templafy/Addins folder, but another extra folder is added, so the new path is %LocalAppData%/Templafy/Addins/Library and this is where all content, including the AddinConfiguration.json is placed.
- The Library package at the moment still contains the EmailSignature functionality, so if it is enabled from configuration then the EmailSignature functionality will work. The Email Signature functionality will be removed in the near future from the Library add-ins.
- At the moment Templafy Desktop settings UI does not support choosing an EmailSignature addin, so if a customer needs to have both Email Signature and Library functionality then we have two choices:
- Install the Library Add-ins and enable the Email Signature functionality, as it was done until now. This is the recommended solution for now, until the Email Signature functionality is removed from the Library Add-ins.
- Manually create a package that contains both Library Add-ins and Email Signature Add-in and make sure the Email Signature functionality is disabled in the Library Add-ins.
- The zip name has been updated and now is
Templafy Library Add-ins 5.7.xx.zipinstead ofTemplafy VSTO Add-ins 5.7.xx.zip. So this is the name that will be displayes in the Admin/Desktop-Settings page.
Bug fixes
Add-in version 5.7.3.1815
We updated the way we retrieve custom document properties. Now we use a case insensitive approach when finding a custom document property key. An effect of our new approach is a more reliable extraction of form values from custom document properties when updating documents.
Add-in version 5.7.3.1812
In some rare cases, VBA code could make Templafy unresponsive when opening a new document. The problem was caused by the VBA code which closed the document. We fixed it by ensuring that we open the document.
Add-in version 5.7.3.1810
For some users with a G Suite integrated outlook profile the signatures were not generated and instead a warning message was displayed: "No email signatures found for your Outlook Accounts". This is now fixed and users will get their correct signatures.
Add-in version 5.7.3.1805
Our DMS integration would only transfer data present in content controls, ignoring custom and built in document properties. Now those are also copied over from the Templafy document to the DMS document, both static and dynamic values.
Add-in version 5.7.3.1794
When the email signature onboarding dialog was shown, it would stay on top of all windows.
This has now been changed, so the dialog is only on top of the Outlook window.
Please note: This fix is only implemented in the new email signature add-in.
Add-in version 5.7.3.1790
We have improved the quality of our source code by splitting some of the logic related to creating documents in VSTO Add-ins. This splitting allowed us to introduce more automated tests increasing our code coverage. Hopefully, these changes will help reduce the number of bugs relates to document creation in VSTO Add-ins.
Add-in version 5.7.3.1777
We had an issue where the VSTO Add-in could not create documents that didn't have a template configuration. We fixed this problem by checking whether a template configuration was present.
Add-in version 5.7.3.1770
When creating a document as part of the DMS flow, we would merge the selected template with any data from the DMS. In this process, we only copied plain text within the content controls or bookmarks, losing rich content, e.g. tables or images. We have changed it so that it now supports rich content.
Add-in version 5.7.3.1766
We fixed an issue occurring when creating a document in VSTO Add-ins. Word and Excel were overriding the Author document property which was set through Dynamics. We solved this problem and it is working in Offline mode also. The fix does not require re-upload of existing templates.
Add-in version 5.7.3.1761
We improved the code related to bug 8957. There's no behavioral changes as such, however we fixed a potential bug where content controls are incorrectly retrieved.
No action is required except for updating the VSTO add-ins.
Add-in version 5.7.3.1759
In Word, when a document contains a lot of content controls, the update process could take a longer time to complete. We changed the behavior by caching the content controls while we are applying the updatesteps into the document. In some documents this can increase the performance with about 150%.
Templafy Admins should not reupload existing templates in order for the fix to work.
June 2019
Features
Add-in version 5.7.2.1745
Support SVG images in image library
Our current image library supports many different image formats of so called bitmap images like Jpeg, Png and Gif. Many of our customers are however also using so called vector files for icons and logos, since these can be scaled indefinitely. The most popular of these vector-based image formats is SVG.
To support the many customer requests about icons in the image library, from today on, we support the SVG file format in the image library.
SVG is still a relatively new format, meaning that not all platforms support SVG yet. When the image library is used on a platform, that doesn't support SVG, then we will convert it to PNG when inserting.
The known support per application is:
WebApp: SVG
VSTO AddIn in Office 2016: SVG
VSTO AddIn in Office 2013 + Office 2010: PNG
Web AddIns: PNG
This feature requires VSTO version 5.7.2.1745 - for older versions we will show an error message to the user if he/she tries to insert an SVG.
Add-in version 5.7.2.1737
Extract Email Signatures Add-ins from Office VSTO add-ins
This is the first step for distributing Email signature and Library add-ins separately and by user group.
The goal of this step is to create a new VSTO add-in for Outlook, the Email Signature Add-in, that only contains the email signature and email font generation functionalities.
This story is restricted to code changes and does not yet publish this new Email Signature add-in, leaving the deployment package to only contain the existing VSTO add-in package.
The CI/CD pipeline to generate the new VSTO package will be covered in upcoming stories, when we will also remove the email signature functionality from the current Outlook VSTO add-in.
5.7.1.1727 June 25th 2019
Add-in version 5.7.1.1716
Improve detection of Outlook accounts
For some integrated Outlook profiles the signatures were not generated because the profile was not being detected and instead a warning message was displayed: "No email signatures found for your Outlook Accounts". We improved the detection of Outlook accounts.
Add-in version 5.7.1.1711
We recently created the infrastructure to support DCU for Excel. With that available we could make Custom Document Properties work with DCU too, which will require the new Dynamics Version 1.9.
This is a technical task which improved the quality of our source code and did not change the behaviour of the VSTO Add-in. As part of this task, we decoupled VSTO specific logic (e.g. retrieving document data) from business logic related to the extraction of form values in update modal. This decoupling will facilitate developers to implement automated tests and thus, overall increase velocity in future sprints.
Add-in version 5.7.0.1703
We have improved our test code for a feature which we shipped recently. The new tests allow us to have better maintainable code with less duplication and less possible mistakes in the future.
This task is related to changes in Dynamics, in particular, changes in the Dynamics applier SetHeaderFooter for version 1.8. However, the changes do not change behaviour.
Add-in version 5.7.0.1699
Dynamics headers and footer feature was something we already had, and now it applies it to all worksheets.
These does not need any changes to template configuration nor the tenant settings.
We slightly changing the contract but we will not bump the dynamic version because it has not been deployed to any customer.
Add-in version 5.7.0.1691
Dynamic headers and footer were already available on creation, and now when DCU is supported on spreadsheets we could complete the feature by making updates working as well.
This feature works with Dynamic 1.8 which is available for the first time in this release (requires VSTO release).
Templafy is now also present in Outlook Calendar appointment/meeting requests. It has the same functionality we have when sending regular emails. On the ribbon, the Templafy button appears and when clicked the task pane opens. From the task pane you can insert Text Elements, attach PDFs or use Images from Templafy or DAM integrations.
We changed the behaviour of form values in the update document content (DCU) modal. Now we populate form fields with values from document properties (built-in and custom), which allows us to better integrate with external systems that might change documents. For example, if an external system changes any document property, we show that new value in the update form, instead of the original value (the one used when creating the document).
This feature works only with simple bindings (meaning single binding without other text). Moreover, if the same binding appears in multiple places, we extract values in the following priority:
- Custom document properties
- Core file properties + extended properties
- Content controls
- Original form value
Bug fixes
Add-in version 5.7.3.1755
Document Update fails on InsertDocumentIntoContentControlTransformationStep with Value out of range exception
We had a bug which meant we couldn't replace text elements in headers and footers when doing DCU. This issue has been fixed, but it requires a new VSTO version for our customers to get the fix. No changes or actions are required by our users or customers, they just need to update their VSTO add-in.
Add-in version 5.7.2.1752
Periodic check time for Email Signature changes is incorrect
In VSTO release 5.7.2.1737 the periodic check for email signatures was set to an incorrect value, so the check was done less frequent than intended. This has now been corrected.
Add-in version 5.7.1.1727
Dropdowns are not filled with values from Document when using DCU
We had a bug in document content update consisting of dropdown fields not being populated with form values extracted from the document. We fixed this issue by setting these dropdowns to values extracted from document content in the same way we set text fields.
Add-in version 5.7.0.1695
We had a bug where DCU stopped working if a custom document property or document property were set through Dynamics to a value that didn't contain any bindings. This has now been fixed, so that it's possible to do DCU on templates where static values are set for the document properties through Dynamics.
Add-in version 5.6.17.1675
We have previously created the infrastructure to support DCU in Excel. However, this feature was failing in the offline mode due to missing implementation. We now support DCU in offline for Spreadsheets.
Admins don't have to change any existing templates.
We support all DCU enabled templates (in Excel that's dynamics version 1.6 or higher).
May 2019
Features
Add-in version 5.6.0.1664
Support Dynamics offline for header and footer
Supports Dynamics for headers and footers in Excel. This means that the templates created in Templafy Designer can be configured to include or replace some of the following additional data:
all pages headers and footer
first page headers and footer
even / odd pages headers and footer
Each of these can be further configured to set:
left section
center section
right section
Limitation: The headers and footers configuration through Dynamics is supported only for the first sheet in Excel. When configuring in Template Designer consider that templates which already have header/footer for all pages you cannot configure headers/footers for odd and even pages (even though this is allowed in the UI of Template Designer). This limitation is valid also the other way around.
Note: Document Content Updater (DCU) is not supported in this version. This will require new VSTO release in future.
Offline mode is supported in this version of VSTO.
Add-in version 5.6.0.1652
Create Document Content Updater infrastructure in Spreadsheets
The infrastructure for Document Content Updater in Spreadsheets is the first step of upcoming stories where we will support DCU on document level configurations. However, for now, we allow updating only a few select Templafy custom document properties (e.g. TemplafyLanguageCode) and updating other Dynamics features will come in a future release.
Notes:
Previously it was not possible to upload templates with DCU enabled in Spreadsheets Library. Now we allow DCU enabled templates if their version is 1.6 or higher.
This feature also requires the add-in to be updated to the latest version.
Support Dynamics for core file properties (Document Properties)
Templafy Admins can configure document properties through Dynamics in Template Designer for Word, PowerPoint and Excel. This means that document metadata such as the Title, Subject, Author, Manager, Company, Category, Keywords, Comments and Hyperlink Base can be dynamic and for example contain bindings. The document properties can also be multi-line text.
The dynamics part works on document creation, DCU and offline.
NOTE: DCU support for Excel will be available in a later release.
Add-in version 5.6.0.1638
Support Dynamics for core file properties
Templafy Admins can configure document properties through Dynamics in Template Designer for Word, PowerPoint, and Excel. This means that document metadata such as the Title, Subject, Author, Manager, Company, Category, Keywords, Comments, and Hyperlink Base can be dynamic and for example contain bindings. The document properties can also be multi-line text.
The dynamics part works on document creation, DCU and offline.
NOTE: This functionality requires Dynamics version 1.6 but that will only be available on a later release.
Outlook add-in: option to attach PDF
Previously, it was not possible to use the PDF library content other than in the browser. We have added the PDFs library to the Outlook VSTO Add-ins, and PDFs can be inserted as attachments to emails. To have this feature available, it needs to be enabled in Templafy Admin settings page and a Add-ins VSTO version of at least 5.6.x.x.
Enabling this feature must be done by implementation partners, as they have access to the settings.
It is now possible to attach one or more custom XML parts to a template. Admins can add one or multiple custom XML configurations in Templafy Designer > Document tab.
Admins can add a name for each custom XML part. The custom XML itself can either be static or contain bindings, allowing for even more dynamic metadata. The custom XML must be valid and written on 1 line.
When creating a document, the Dynamics pipeline adds custom XML, which can be useful for storing document metadata or other custom functionality.
The feature is only available when creating a document and will work for documents, presentations, and spreadsheets. To use this feature, the tenant must upgrade the dynamics version to 1.5 in the Admin Center and use a compatible VSTO Add-in. Support for Document Content Updater will come in a later release.
Add-in version 5.5.3.1604
Support insertion of dynamic text element from text element library
This feature enables support of Dynamics in "Text Elements" library. Dynamics enabled text elements (aka "Dynamic Text Elements") will work as they are templates placed in the "Documents" library. The feature works in Word and in Outlook.
Use cases
Templafy Admins can upload templates in the "Text Element" library in the same way as in the "Documents" library. The relevant forms should be also attached to the uploaded template.
Templafy Users can insert the dynamic text elements in documents in the same way as before - just select the starting point of insertion, click on the text element item, select profile, fill in the required form fields and insert the text element.
Supported dynamic items
The following dynamic configurations are supported in the dynamic text elements:
- Text configurations
- Groupconfigurations
- Imageconfigurations
- Dateconfigurations
Headers, footers and sections in the text elements are not supported in dynamic text elements
Remarks
The following rules apply for when the creation form dialog is shown for Dynamics Text Elements:
- The text element is not enabled for dynamics:Don't showcreationdialog
- The text element has no form fields and is inserted in Word, and there is a available user profile fromthe activedocument:Don't show creation dialog
- The text element has form fields: Always show the creationdialog
- The text element has no form fields, and is downloaded from WebApp: Always show creationdialog
- The text element has no form fields, and is inserted in Outlook: Always show creationdialog
In order the Dynamics text elements to work, the Templafy Admin should attach the referenced forms in Templafy Admin.
The DocumentLanguage form field for the inserted text element is chosen by the following priority (highest to lowest):
- Inserted Dynamics text element has a DocumentLanguage form field
- Active document has a TemplafyDocumentLanguage file property
- User profile has a DocumentLanguage form field
- English (Invariant language)
Note that the DCU functionality is not supported for Dynamics Text Elements.
Bug fixes
Add-in version 5.6.0.1625
Add-ins authentication throws script error for Google Authentication
Customers using Google authentication were experiencing script errors when signing in because script errors would first be suppressed after a successful sign in. This was done to support potential proxy prompting, because the webbrowser hosted inside Office would treat proxy authentication as a script error.
To alleviate this, the sign in will now suppress any non-proxy script errors, unless ShowScriptErrors is explicitly set to true.The behaviour of the ShowScriptErrors registry entry has not been changed.
Update document does not apply visibility options on bindings in the master (Powerpoint)
This issue was related to presentations with bindings on the slide master only. In some cases, bindings to images that also had the visibility setting configured would behave incorrectly, when using the Document Content Updater. Depending on the visibility configuration, it caused images to be visible when they should actually have been hidden. This visibility settings will now be correctly applied to slide masters when using the Document Content Updater. This fix will not require changes in templates, and will work on both new and existing templates.
Text element is not replaced
There was an issue where text elements were not replaced when using Document Content Updater in Word, even though the "replaceOnUpdate" flag was properly checked. This caused the document to never have its dynamics text elements replaced. The error should now be resolved by getting the newest version of the VSTO add-in, and will work for both new and existing documents.
DMS fails when template contains multiple sections
We experienced a problem in the DMS flow when the template in Templafy contained section breaks meaning that the update flow would break, and the document would not be updated properly.
This was due to the fact that some settings related to headers and footers were not set when the template contained multiple sections. We now do a check that the values are set before trying to set them.
April 2019
Features
Add-in version 5.5.2.1593
We have added more telemetry data when tracking UseAsset such as DestinationSlideId and DestinationTemplateId. DestinationSlideId corresponds to the slide id of the slide where an asset is inserted, while DestinationTemplateId is the id of the template of the presentation/document. If no SlideId is available no value is logged fx. Word, Excel, Slides with no template configuration. This will now appear in Application Insights custom events.
New settings tab
Improved Templafy Designer now have replaced teh "JSON" tab with a "Settings" tab which contains visual options for editing relevant parts of the template configuration. The user can now toggle the "Document Content Updater" feature and select the "Dynamics Version" of the template from a dropdown. The option to view and edit the template and form configuration in JSON format is still available when selecting the "Advanced Configuration".
Enable a document as a template
Previously, users had to load and save a template configuration to create a template. These steps were necessary before users could start working with the template (e.g. adding element configurations). We improved and automated the way we enable templates so users can start editing templates right away.
Now users can enable documents as templates in three different ways:
-
Manually, by toggling on the "Enable as Template" option in the "Settings" tab.
-
Automatically, by creating an element configuration
-
Automatically, by creating a document configuration
All three methods add a default template and form configuration to the document.
Convert template to regular document
This feature is beneficial because it allows users to convert a template or a document with a template configuration back to a regular document. By doing this, users remove all template, form and slide configurations, as well as all Templafy document properties. Previously, this was not possible because creating a template was a one-way process.
Backwards compatibility
The new changes are compatible with older versions of VstoAddins. However, there are some notable differences.
In VstoAddins versions older than 5.5.3.0 the document is automatically enabled as a template when the user opens the Templafy Designer.
Besides this, VstoAddins versions older than 5.5.3.0 do not support converting to a regular document.
March 2019
Bug fixes
Add-in version 5.5.1.1565
When we were inserting assets(example: Text elements or Images) in Word with Templafy we were creating many undo actions that confused the end user. We now create only one action called "Undo Image Insertion" and "Undo Text elements Insertion".
When using DCU, we had an issue with slides inserted which were not Dynamics enabled slides. Such slides could be inserted from the slide library or pasted from another presentation. Such slides would cause our VSTO add-ins to throw an exception, making DCU not work.
Non-Dynamics slides no longer cause DCU to stop working.
February 2019
Features
Add-in version 5.5.1.1535
Row level bindings are now supported when choosing a group binding in the template designer, while all other bindings will be blocked by displaying a message to the user. Since these changes will be available in the template designer, tenants need to update their VSTO add-in to the newest version. If a user modifies an existing disallowed row level binding, the binding will be removed and the user will be notified that the binding is not supported.
With this release we are showing all assets and folders that might be relevant to me based on my user profiles. This means that we show assets that any of the user's user profiles give access to. AN example of this would be a person that works in both the US and Danish office and therefore have user profiles accordingly to that. He/she will now see a combined view of the assets filtered to either the Danish or the US office.
In case an assets is filtered to only be valid for the Danish office, all other user profiles which are not valid for the asset will be disabled. This way it should not be possible to create documents with a wrong user profile
Bug fixes
In this specific case, Document Content Updater (DCU) was unable to update a document, due to some special set up in the template. Even though the "Set Paper Size" transformation configuration in the specific template was not set up to change the orientation of the pages, the updater would still set the orientation of all pages, but to the same value as it already was. Because of the special section, Microsoft Word returned an error, and this aborted the whole update.
After completing the Validation (DCV) flow in a presentation the user profile bindings on the DCV enabled slides were lost. This caused a bug when users attempted to update the document (DCU) because the user profile bindings on the DCV enabled slides failed to update. The users need the latest Vsto Add-ins in order to get this fix.
Corrected the error message that Templafy VSTO Add-in displays when the document update fails due to a change in the Dynamics version.
January 2019
Features
Add-in version 5.5.1.1476
Short cuts
Support for "Escape" key when trying to close down a modal view like the document creator or the user profile editor. If there are multiple modals opened, they will be closed one by one by pressing the "Escape" key. This works for all modal views on our platform.
Support for keyboard shortcuts in dropdowns so that a user can navigate and scroll to a specific option by typing the starting letters of the label. For example, if the user types in "De" and there is a dropdown option with the label "Denmark" somewhere out of the available space, it will scroll down and highlight it. This works whenever the dropdown is in focus, even if it is or not expanded
Fixed links in the app menu on the client application as well as menu items in the admin center so that they all work with mouse-wheel click, control click and right-click > open in new tab options
Fixed navigation history to now properly use the back and forward buttons in the browser.
This feature enables presentations that have Document Content Validator (DCV) enabled for one or more slides, so that it is now possible to use do Document Content Updater (DCU) on all slides no matter if they DCV enabled or not.
DCU doesn't update images on the master
Fixed issue where using Document Content Updater (DCU) in PowerPoint on bindings on a Slidemaster would not be updated. This would work fine when creating a document, but the update functionality failed to apply on the slide master. This issue was also present on Document Content Validator (DCV) enabled slides. Both scenarios have been resolved - existing documents (and new ones) should now be able to do update with DCU once the client has received this update. No additional changes are required for existing documents, and the feature will also work when in offline mode.
Now it is possible to use DCU enabled templates created through DMS.
Release notes from 2018
Add-in version 5.5.1.1417
When both SlideProof and Templafy VSTO Add-ins are installed and both of them were opened at the same time they consumed much of the users screen. For fixing this we made sure that only one of them can be opened at a time. So if we open Templafy task pane SlideProof task pane will be closed and the other way around.
We have improved the "undo" functionality by adding a single step when inserting a new slide or a new slide element in Templafy.
To prevent this we check if the header is empty and insert a blank space while inserting the file.
In this release we always insert Text Elements in a separate paragraph. Because we now always start by creating a blank paragraph, we also solved an issue where Word was importing the header from the file being inserted. This change is in both Word and Outlook.
This fix ensures that the default helper text is removed during the document creation when processing content controls.
If the user had third party VSTO Add-ins installed for word which displayed prompt messages when word was starting then these could cause failure of the email signature generation. Signature generation could only continue if the user located the prompt and acknowledged it. This is now fixed by disabling for a very short period all the VSTO Add-ins for word, starting word application in invisible mode and re enabling the VSTO Add-ins. Since this happens almost instantly we don't expect it to have any side effects on using word with third party Add-ins. Enabling, disabling VSTO Add-ins should never fail, however if by any chance it does then it is configured so we receive a message in our slack error channel. This feature is not enabled by default, we need to set the following registry key to enable it: DisableAllAddinsOnRtfConversion=true, under Computer\HKEY_CURRENT_USER\Software\Templafy\OfficeAddIns.
Add-in version 5.5.1.1312
FIxed an error where bindings where only updated on the first master slide, when updating using Document Content Updater (DCU). DCU now correctly updates on all master slides.
Our Add-ins did not work with remote services that has blocked support for older security protocol standards (less than TLS 1.2).
To fix this we changed the add-in to by default use the newest security protocol standard (TLS 1.2) and fallback to older versions (1.1 and 1.0).
Color themes uploaded in Templafy can now be used in dynamic templates.
Requires "Supported transformation version" 1.3 or higher.
Bynder DAM integration supports personalized images instead of common content for all users. A user can authenticate via OAuth1 login flow and have a content different from the default provided by Bynder for the account. An administrator can activate the option from the Templafy Admin panel. When this is done, all user will see a login notification bar in the bottom of the Bynder library in the Templafy VSTO plugin. Once clicked it will open a native window pop-up which will require the user to authenticate inside the Bynder portal. The same option is accessible from the "Settings" menu in the top-right corner in Templafy VSTO plugin. The users can also choose to disconnect from the personalized content by choosing "Disconnect" from the "Settings" menu.
Prerequisites
Bynder DAM integration with the enabled OAuth1 authentication option. Additional user rights management on the Bynder portal (in order to show personalized content).
Add-in version 5.5.1.1176
This is the first version of our Document Content Validation for slides. With the Document Content Validation feature we keep track of all slides enabled for validation to make sure that they will stay up to date even after they have been created.
This will make it possible for company admins to ensure that all produced presentations will always be up to date with the latest company standards.
Also, we make sure that all slides and presentations that are controlled by the company is locked, and therefore cannot be changed by the user.
This first version is still in beta state.
Pre-requisites
Transformation version 1.2
Support for special characters in email signature with plain text
In PowerPoint VSTO Addins the shapes with image bindings no longer lose their names and order when DCU (Document Content Update) action is performed
Convenience filters on folders are now also handled on offline mode
Convenience filters are now synchronized to offline mode
The custom document property TemplafyExternalSystem is now removed completely when a DMS has been completed
Add-version 5.5.1.1071
The log out button has been added to the current version of the VSTO add-ins. If the user is on a computer that does not have seamless SSO (i.e. a private computer with Templafy Desktop) (s)he can try to log in with another user.
: Plain text email signatures for Outlook didn't support certain special characters.
: Breadcrumbs display names of folders reflect the real folder names.
: Fixed a bug where a user with a very long Windows profile name and Templafy user profile name would be unable to install Email Signatures locally due to a maximum path length restriction in Windows.
Add-in version 5.5.1.1006
Templafy Designer: Validation that Content Controls are set on block/pararaph level for TextElement insertion
Templafy Designer: Insert image header with "Numbered Sections" now take precedence over "Named Sections", if "Numbered Sections" is used
Offline mode can now only be initialized when all offline content have been downloaded
Ensured that previews are always shown when switching from offline to online
Values from dropdown that are filtered on other dropdowns are now kept when updating the document
Text Elements will now only show up in Word/Outlook if they can be inserted (No longer shows Text Elements used for dynamic insertion)
Add-in version 5.5.1.877
Pre-requisite: these add-ins must be used with new Templafy Desktop 1.7.0.X
Performance improvement. Only sign-in once a day - speedup loading Templafy in Office Apps
In this release we made substantial performance optimizations when staring the Task Pane. This is done by having Templafy Desktop do an invisible SSO signin in the background every 24 hours. If a successful SSO is completed we don't have to sign in when starting the Task Pane, which can be rather slow. This performance optimization requires minimum Templafy Desktop 1.7.x.x.
Add-in version: 5.5.0.867
Support for transformation version 1.1
Add-in version 5.4.3.745
Allow Outlook to run only email signatures even when no libraries are enabled.
Bug fix: If an Outlook account was renamed we were unable to find the matching registry entry which is needed to retrieve the default email signatures. So the email signature feature would be unavailable in this situation.
Add-in version 5.4.3.734
Option in "Settings" menu in the add-ins to force Templafy to use offline mode.
Add-in version 5.4.2.716
Support latest features in the Template Designer.
Support for combo box fields (a dual purpose field in a form, that can be both a drop down or a free text field)
Add-in version 5.4.1.550
Optimized compression for images inserted via add-ins (Templafy image library and external DAM libraries.
Add-in version 5.4.1.526
Offline webapp artifacts included in VSTO addins rather than a separate package
Support for "Calculated Default Values" in Forms
Add-in version 5.4.0.515
Improved handling of Offline mode in Word
Add-in version 5.4.0.511
On boarding flow removed from add-ins (on boarding flow is handled by the Templafy Desktop)
Add-in version 5.4.0.481
Template Designer - create dynamic templates directly from MS Office with a graphic user interface that lets you add dynamic fields (content controls) and metadata to the template.
Add-in version 5.4.0.480
Improved event log handling
Add-in version 5.3.0.430
Document content update enabled (DCU)
Offline enabled
Add-in version 5.0.0.307
Fixed Outlook VSTO display date bug
Email Signature enhancements
Minor UI fixes for high reolution displays
Add-in version 5.0.0.161
Email Signature performance improvements
Support for DMS: WorkZone
Added VSTO Events
Minor bug fixes
Add-in version 5.0.0.44
Email signature bug fix
Fixed issue with no email accounts found even though email is correctly setup
Minor bug fixes
Add-in version 5.0.0.32
Fixed the delay when searching for User Profiles
Email Signature enhancements/bug fixes
DMS improvements
UI bug fixes
Add-in version 5.0.0.0
New architecture
Requires Templafy Desktop to be installed
Comments
0 comments
Please sign in to leave a comment.