About this article
- 6.1.xxx versions
- 5.9.54 to 5.9.61 versions
- 5.9.4x versions
- 5.8.x versions
- 5.7.x versions
- 5.6.x versions
Technical information
|
6.1.xxx versions
6.1.59
Fixed an error which prevented removal of custom properties
6.1.58
Apply workaround for image inserting bug on Monthly Enterprise channel
To address a Powerpoint bug related to image inserting on the Monthly Enterprise Channel of Office, we are applying a workaround that prevents this bug. This workaround will be in place until a fix by Microsoft is rolled out to all release channels of Powerpoint.
6.1.57
Add VSTO fix for race condition to 6.1 branch
Fix an issue where document creation using the DMS flow would fail sometimes, this seems to be caused by the paste functionality not being available when a new document is being created in Word. The fix does not use the paste functionality and should consistently work.
Add work item and release notes policy to OfficeVstoAddIns build pipeline 6.X
Status of the associated work item and release notes are now checked when creating a Pull Request in the OfficeVstoAddIns repository for release 6.1.
6.1.56
Library reverts to root folder after slide insertion
When inserting certain slides into a presentation the user would be sent back to the root of the slides library. This has now been fixed, so the user will stay in the folder where the inserted slide was.
6.1.55
Updater not working when zip file or hyperlinks are inserted into Document
Fixed updating of documents containing big attachments
6.1.54
Enhance reporting of document update failure when word document contains malformed url (One)
Improved reporting of document updater failure when a broken link inside of word document is a cause.
6.1.53
Slide insertion causing logo to move behind background image
When inserting certain slides the images on that slide would change order after the insertion. This has now been fixed so the order of all the content on the slide will stay the same after insertion.
6.1.52
Release Templafy.Dynamics.One in VSTO 6.1
Technical release to install package Templafy.Dynamics.One in VSTO 6.1
6.1.51
Windows doesn't close when creating document from DMS
When setting custom properties in the context of opening a document from DMS, the windows would not close after applying custom properties. This has now been fixed, so properties are applied correctly and the window will close properly.
6.1.20
The Document Content Updater correctly updates content in a table, but increases the font size.
An issue with DocumentUpdater has been resolved where styling was not maintained in the updated part of the documet, mostly affecting tables.
This affects all versions of Dynamics and no changes in WebSite is needed.
6.1.19
The Document Content Updater correctly updates content in a table, but increases the font size.
An issue with DocumentUpdater has been resolved where styling was not maintained in the updated part of the documet, mostly affecting tables.
This affects all versions of Dynamics and no changes in WebSite is needed.
6.1.18
Blank Templafy taskpane when using Preview pane in File Explorer
There was an issue with Word running in compatibility for multiple displays mode when the user had opened a preview of a document in explorer and then opened Word, the Templafy task pane would not load properly.
The fix was to made task pane display content correctly in Word when it runs in compatibility for multiple displays mode.
6.1.17
Updater fails on InsertTextIntoContentControlTransformationStep - corrupted table
This update contains a fix for documents that make use of the Document Updater feature and were created using an Office version with a different language pack other than English (fx. Dutch or German). The bug was happening when setting a style name for the text to be updated. The style name used was "Normal" but it did not exist if an English language pack was not installed. We are now using the old text style present before updating the document.
6.1.16
Document update fails due to file size with an exception Unable to determine the identity of domain.
This fixes an error with an IsolatedStorageException being thrown when using the document updater on large Word documents. The update should now work as expected.
This affects all Dynamics versions.
It is not necessary with any changes to the Website.
It is recommended to use Word 2013 or newer, as the fix had to be implemented differently for Word 2010.
6.1.15
Powerpoint hangs when inserting slide
Prevent slide insertion from hanging PowerPoint
6.1.12
Remove local font configuration when disabled
When a font was configured for a tenant, we would set a registry key so that the configuration will be visible in Outlook. We are now introducing the ability to disable the font configuration. Because of that, we are now also handling the case in which the font was set and then the configuration was disabled, by cleaning up the font configuration registry keys.
6.1.11
Inserted slides are opened with next created presentation in PowerPoint 2002
Powerpoint VSTO Add-ins running with Office 2002 has the following bug: when inserting slides, and then creating a new presentation all previously inserted slides will be opened individually as well. This happens because all presentations which has been used are kept in memory by Microsoft, due to a reference to the inserted slide created when formatting it after insertion. This reference impeeds the release of the COM object of the inserted Slide. Therefore, when iterating over the presentations, they are opened.
In this release we have implemented a fix that only applies for the concrete Office build version that has the bug: 16.0.12527. We use a timer with an interval of 1 milisecond to provide Powerpoint the possibility of decrease that reference and release the COM object.
6.1.7
Server Error during Authentication in VSTO add-ins for ServerMode installations
There is an issue when the user is in Templafy Desktop in Server Mode, using Templafy One. VSTO previously checked the version of Templafy Desktop to assert if was running on Hive or One. In Server mode that version information is not present, so the application would default to Templafy Hive. The behavior was changed so instead it defaults to Templafy One, since currently there is no Server Mode available on Hive.
Versions from 5.9.54 to 5.9.61
5.9.61
Inserting PDFs from Outlook library renames the files
This change fixes a Templafy Hive bug in Vsto Add-ins. When inserting a PDF in Outlook, users see the attached PDF with the wrong name representing a random chain of characters obtained from the blob storage download URL. With this fix, we modify the attached PDF to use the asset name instead.
5.9.60
Task pane is automatically opening even if the setting is disabled
This change fixes a Templafy Hive bug in Vsto Add-ins. When opening Office PowerPoint or Word without a value for the setting "Open Automatically Taskpane" the Taskpane will be opened automatically but the setting in the Settings Menu appears unchecked.
After this release the checkbox will also reflect this behavior being checked in PowerPoint and Word if there is no custom setting. Excel and Outlook will remain unchecked and the Taskpane won't be opened if there is no setting.
5.9.59
Outlook Tasks get corrupted when sending through Email signature server
Vote functionality of Outlook on PC stops working when Email Signature Server is in the loop
The Voting functionality is only available when the message is using Transport Neutral Encapsulation Format (TNEF) and is only available inside the organization. When the email message is routed through the Email Signature Server, this one attempts to decode the TNEF format, convert it to html and attach a signature, however this causes the voting buttons to disappear. To avoid this we will not route email messages containing voting buttons to the Email Signature Server. Unfortunately in Exchange it is not possible to identify if an email message contains a voting button, since this is encapsulated in an attachment called Winmail.dat. This is why a new header is added from VSTO, that signals Exchange Online that the message type sent is not supported by Email Signature Server and therefore it should not be routed to it. This header is called X-UnsupportedFomatByTemplafy and it needs to be added as an exception for mail rules. Detailed instructions about this are added to the Email Signature Server installation guide.
5.9.57
Document creation fails offline on InsertImageIntoHeaderTransformationStep
Before this fix, offline document creation failed, because the user profile was read as in Hive and not like in One. The fix repairs the way of reading this configuration such that Offline works again. Only the Offline feature in Templafy One was affected. Besides that, the same bug pattern was discovered in the document updater for slides (One+Hive) - which is also fixed now.
5.9.56
Redesign the side panel to include a link to the Composer
This change is only for Templafy Hive: Renamed New Document Dialog to Composer. Added endpoints to provide information the LibraryApp if Composer is enabled and to be able to open the Composer dialog from the Library App.
5.9.55
3rd party security application add-in, just endlessly loops the Templafy loading UI (in offline mode)
When using certain third-party applications on the computer, such as Zscaler, it would not be possible to activate Templafy in Offline mode. This has now been resolved, so these types of applications will no longer block the use of Offline mode. Furthermore, the add-in will now also go to offline mode if the requests fail for other reasons, that was previously not detected.
5.9.54
Checkbox default value is not working in Create Document form
In Hive we wanted to be able to specify the default value of form check boxes, by either typing in a boolean binding or by choosing true or false as constant values. Before this bug fix it is was not possible.
For One there are no changes.
5.9.4x versions
5.9.49
Incorrect aspect ratio query
This change is only for Templafy Hive: in PowerPoint slides are not shown when the user changes the aspect ratio due to a wrong calculation of the ratio. It should be calculated with an x separating height and width dimensions, instead of with a dash (-) like it was previously in Templafy One.
This release fixed this bug, allowing the user to see the right Slides for the selected aspect ratio.
5.9.48
Blank screen after closing and opening task pane on a different tenant
This change is only for Templafy Hive: After switching to another tenant from inside the VSTO Add-in the app would no longer load correctly when restarting the Add-in by closing and reopening the taskpane. This issue is resolved in this release.
5.9.47
This bug is caused by an endless loop in the calculation of the position in the Z axys of the inserted image. PowerPoint assigns a Z order position to every shape in a slide, allowing only one shape per Z position and having as many positions as shapes the Slide where the image is going to be inserted contains, starting in 1 for the one in the back.
During the insertion process we remove empty placeholders, insert the image in the selected placeholder and re-recreate the deleted placeholders. During this process the Z order position of the non-deleted shapes are dicreased based on the previous deleted placeholders. However, the Z position of the inserted image is calculated before we delete placeholders and this could lead in a Z order position that does not exist because the amount of remaining shapes is smaller.
In this release we have fixed the bug changing when the Z order position of the inserted image is calculated, doing that after the placeholders are deleted and we know how many shapes remain in the slide.
5.9.46
When starting the VSTO Add-In on Templafy Hive in combination with the authentication method registry key the user would be logged in to the tenant with this authentication method and not the configured tenant. This issue is resolved in this release.
5.9.44
This change is only for Templafy Hive: in version 5.9.43 was introduced the API call to check whether a user is online or not in Templafy Hive. The path used for this endpoint was /online, not following our conventions.
In this release we have updated the path to call the following endpoint /api/library-app/online/check.
5.9.43
This change is only for Templafy Hive: it does not introduce any new functionalities and it does not contain any breaking changes.
In order to determine whether a user is online or not, a new endpoint has been created in Templafy Hive. This endpoint, called /online is used for the VSTO Add-in when the TaskPane is opened and it also tracks the TaskPane Opened action.
5.9.42
In version 5.9.35 a bug was introduced while porting the automatically open taskpane functionality to Templafy Hive. This bug causes that the taskpane always appears when opening Microsoft Word or Powerpoint regardless the setting value.
This release fixes this bug, showing the taskpane when the setting is enabled and hiding it if the user disables it.
5.9.41
When working with VB in Excel the previously closed workbooks would still appear in the project window. This has now been corrected so workbooks will disappear in the VB project window as soon as they are closed.
5.9.40
The Document Management System flow in our VSTO addins now support multiple sections with separate headers and footers in the template document.
5.9.3x versions
5.9.39
In version 5.9.22 a bug was introduced by removing the AddInConfiguration.Json file. Not having the file was causing a problem with the communication with the Productivity Addin and opening and closing the task panes was hanging. The problem has been resolved by re-engineering how the configuration is read from the file or created from scratch in case the file is not there.
5.9.38
VSTO Authentication fails for Templafy One
In version 5.9.24 of Add-ins we have introduced support for Authentication tailored for Templafy Hive.
As part of that release, we have also changed how we read and set the cookies stored by Templafy Desktop.
We had a bug where the cookie in Templafy One was set on the specific subdomain for the configured tenant instead of the top-level domain cookie.
This had the effect of double cookies to be set, one for the top level domain and one for the subdomain, causing blank task pane behaviour in our Add-ins.
This release fixes it so now we set the cookie on the top level domain only as expected
5.9.35
Add user setting to open automatically the taskpane handler
This change is only for Templafy Hive: it does not introduce any new functionalities and it does not contain any breaking changes.
Automatically open TaskPane setting is now stored in the registry under \HKEY_CURRENT_USER\Software\Templafy\OfficeAddIns\{application}\16.0 as AutomaticallyOpenTaskPane, where application possible values are Word, PowerPoint, Excel or Outlook. This setting, if exists, is used to decide whether the task pane shows or hides when creating a new document that is not a Templafy template.
5.9.34
Deprecate old way of adding customXml parts in VSTO addins
In Dynamic Version 1.13 we introduce the ability to add and update values in the CustomXML of Office templates.
This means that existing way of setting CustomXML values where a whole part would be added no longer is needed. In this release we are therefore deprecating this functionality to not create confusion between the different functionalities.
This feature will no longer be available to tenants with Dynamics Version 1.13+.
5.9.33
Add tracking in offline mode
This change is only for Templafy Hive: it does not introduce any new functionalities and it does not contain any breaking changes.
Offline racking for the following custom events has been added based:
OpenNonTemplafyDocument
CreateNonTemplafyDocument
OpenTemplafyDocument
5.9.32
Document fails on InsertImageIntoHeaderTransformationStep upon Updater when the CC in the header is locked
There was an issue when updating the document from Templafy: When the image was inside a locked ContentControl we could not change the image, but could only delete it due to the lock.
We fixed this problem by temporarily releasing the lock, changing the image and acquiring the lock again.
5.9.31
Use Tracking document endpoint in VSTO Add-ins
This change is only for Templafy Hive: it does not introduce any new functionalities and it does not contain any breaking changes.
Tracking for the following custom events has been added based:
OpenNonTemplafyDocument
CreateNonTemplafyDocument
OpenTemplafyDocument
5.9.30
Port open taskpane logic to Vsto Add-ins
This change is only for Templafy Hive: it does not introduce any new functionalities and it does not contain any breaking changes.
If the user has not set that the taskpane should open automatically when a new template is created or opened, the Add-in will decide if it should open or not based on if is a new document and a template document. Before this was decided in an API call.
5.9.2x versions
5.9.29
Fix copy-paste error during form value extraction (VSTO)
Before updating a document the form gets populated with the data that where used before. One new source is the metadata (SharePoint for example, using Custom XML value configuration), which was not determined in the correct manner. Updating the document was not affected.
With this bug fix the user can update the document starting with the recent values of the document's metadata.
5.9.28
Image insertion causes VSTO and Office application to freeze
When inserting an asset the content is now downloaded in the background to prevent Office from hanging and to give the possibility to the user to continue working
5.9.27
Add support for setting up custom XML values (VSTO)
Many of our customers are using metadata from their template management systems. This is key for large enterprises to keep track of their documents across the organization's document management system. One of these systems is SharePoint. With this release, we are enhancing our possibilities of how Templafy can work with metadata, by making it possible to set and read SharePoint metadata. This makes sure that the documents are always set with the proper metadata while sparing the users from adding the metadata later on the document creation process.
We are doing this by adding a new feature in Dynamics where a template can be configured to set values of custom XML parts during document creation.
This functionality is available for Dynamics version 1.13 for Word documents, spreadsheets, and presentations. It is supported since VSTO version 5.9.27.
The metadata can be set using the Dynamics designer by adding a new "Custom XML value" configuration. The desired metadata value must be addressed using the namespace of the custom XML part and an XPath expression that points to the element or attribute. The value that has to be inserted can be expressed as binding.
5.9.26
Image insertion via Templafy changes the z-order
The Z-Order of the newly inserted image is now calculated correctly to be the same as the shape in which the image is inserted into
5.9.25
Insertion of assets broken in Offline Mode
Users were unable to insert assets in offline mode. This bug was introduced in version 5.7.5.1931 due to a modification in the asset insertion functionality.
This issue has been fixed by upgrading the Offline WebApp Package to the latest version.
5.9.22
In preparation for the migration to the new self-contained systems the following files has been removed from the add-in packages:
- Set BrowserEmulation Excel.reg
- Set BrowserEmulation Outlook.reg
- Set BrowserEmulation PowerPoint.reg
- Set BrowserEmulation Word.reg
- Trust Templafy certificate.reg
- AddInConfiguration.json
These files are now included in the package templates instead.
5.9.23
Binding is inserted before element configuration when using Dynamics Designer
In the template designer in PowerPoint, the Alt text view includes the binding:
This fixes the issue so only the json is displayed in the alternative text (the {{Form.Name }} is removed).
This affects both the monolith and the self-contained systems.
5.9.0.x versions
5.9.0.2034
Remove libraries from the ribbon
We have removed the feature to open a library directly from the ribbon. The only available option under the Templafy button is About.
5.9.0.2005
Non-templafy CustomXML parts are not copied to DMS document
We improved our DMS flow. Now, the DMS-enabled documents will contain the Custom XMLs which are in the Templafy template. The feature is working in PowerPoint and Word. All current templates which contain Custom XML are compatible with the released feature and they don't need adjustment.
To create a template with a Custom XML from scratch: In the Templafy template opened in Word/PowerPoint go to "Developer -> XML Mapping Pane -> (Add new part...)" and select a valid XML file. The template file will contain the XML as Custom XML part which will be copied on document creation in the DMS flow.
To enable DMS flow on a given document check here: https://support.templafy.com/hc/en-us/articles/115000767425-How-to-configure-DMS-integrations-in-Templafy-Word
5.8.x versions
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.x versions
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
External System flow fails on in line level content controls
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.
5.7.5.1949
Updater fails: corrupted table
We noticed further scenarios where Updater for Word was failing to remove tables from content controls.
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.
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.
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.
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
Add new custom document property flag for communicating with ExternalSystem
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.
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.
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.
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.
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}}".
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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
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.
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.
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.
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.
5.6.x versions
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).
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.
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.
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.
5.5.x versions
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.
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.
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
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.
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.
Comments
0 comments
Article is closed for comments.