About this article
- December 2019
- November 2019
- October 2019
- October 2019
- September 2019
- August 2019
- July 2019
- June 2019
- May 2019
- April 2019
- March 2019
- February 2019
- January 2019
Note
|
December 2019
Features
Use TLS 1.2 for outbound calls in the monolith
We have updated our service to use TLS 1.2 when making HTTP calls to external systems to improve the security of our system. The previously allowed TLS 1.0 and TLS 1.1 protocols are being deprecated by most browsers in 2020 and many of the external systems Templafy use are also phasing them out. This change only affects the underlying communication and no changes should be observable elsewhere in the system.
HTTP Verb Tampering - HEAD Verb Bypass
This is a technical task for us to improve the standards compliance of the website by only responding to appropriate HTTP methods when requesting index and Salesforce pages. It should not result in any changes for users.
Bug fixes
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
Remove office address on email template
In some emails we sent to end users about the email signature server, we included the Copenhagen office address. We have decided to remove it.
Create Aprimo integration
With this release, we are adding Aprimo to the list of available integrations.
This integration is using the classifications terms in Aprimo as browsable folders in Templafy UI. We display every crop of every image as an individual downloadable asset in the UI. The search functionality works in the same way as in Aprimo.
Change Automatic Backup queuing to enqueue live tenants first and ignore canceled tenants
Templafy's automatic backup feature, checks backups of tenants every night and take a new backup if there is a change. Also, on the first day of month or when there is a change in our database schema, the backup job would take a backup for all tenants to have a safe returning point for every one and it did that in an alphabetic order.
However, backing up terra bytes of data may take several hours and thus for tenants in the end of the list (like the ones starting with z) it would have happened in working hours. With this update, we make sure to prioritize our backups based on tenants state and also not to take backups for tenants with state TrialEnded or canceled although we don't have many.
Based on the new rules we take backups with following order:
- Live
- Implementation
- Trial
- Test
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.
SCIM-Allowing ForwardSlash in PATCH requests
With this Update, we let PATCH requests on our SCIM API to contain forward slash (/).
Show UserId in sysop-users
SCIM requests are done using the Id of the user. With this feature, we let our support to check the userId in our Database to follow the flow of requests.
Update Microsoft.ApplicationInsights.SnapshotCollector to 1.3.5
There is no behavioral change with this release. This is just for upgrading a Microsoft package to maintain our tracking in Application Insights.
Make client send link to VSTO for insertion
Update old Icon.png files and add LinksIcon.png.
Set Link as a valid AssetType for the OutlookVSTO Client, adding it to the Ribbon and also showing in the TaskPane.
Enable validator for not locked slides
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 editing a Dynamics 1.11 presentation template, a Template Admin will have a new checkbox for each slide where he can decide if the slide should be locked or not. However, a slide can only be locked if Validator is enabled for the slide.
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. In this way, if the user has made modifications to the validator-enabled, non-locked slide, his changes will not be lost. He will be able to copy the changes over to the updated slide and then manually delete his outdated slide.
To use this feature, a template needs to be Dynamics Version 1.11, and a user needs to update their VSTO add-ins. If a user has not updated their VSTO add-ins, the slides will be ignored and not updated.
Bug fixes
Assets cannot be inserted on older addIns
We found a problem where assets could not be inserted on AddIns older than 5.5.1.1006 (released on August 15th 2018). This was due to a change of what we were sending from our website to the addIn when inserting an asset such as images or slides. This has been fixed in a way so it now should work on all addIns. No new VSTO addIns are required for this fix to work.
Open task pane automatically option not operating as expected in Word, Excel and Outlook
When changing the option to open automatically the task pane for a non-default tenant in Excel the option was not saved correctly.
The bug is now fixed by making sure that the setting is stored and read for the default tenant as it was originally designed.
Tags and External data is no set for slide and slide-elements in Public API
When uploading slides or slide elements in the Public API the defined tags and external data would not be set on the slides or slide elements. This has now been corrected so that tags and external data will be set on slides and slide elements when uploading through the Public API.
SCIM- Our PATCH does not support Arabic comma ,
We were not supporting Arabic comma and that made some of the requests to fail. With this Pull request we are supporting the special character
Unable to replace SVG images
When trying to replace an SVG image the user would get an error saying SVG was not a valid format.
This has now been corrected so it's possible to use SVG images when replacing.
SCIM-Patch Does not support & character
Until now, In our SCIM API we were not supporting some special characters includeing &, [], % and some more in our update requests. From this version we support those characters as well.
October 2019
Features
Create Getty Images integration
Templafy integrates with Getty Images now. By default, the integration is showing images based on the search term "work" when no search phrase is provided. When browsing, searching and downloading images we take into account the current Getty Images subscription and apply it to the parameters of each request.
Add the reason for moving a message to dead letter in backup restore service
Until now, we checked the state of our tenants for taking a backup or restoring one so we do not run 2 jobs at the same time. The gaurd works as it should and fails the second request with some description. However, we did not log the reason for failing the request completely. With this feature, we add the reason for failing it to the logs.
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.
Generate Trace Logs for SCIM when the request is not a valid request
Until now, we were not collecting any trace logs if there was an structural problem in the SCIM requests. This made us calling our clients to collect their logs if they had a request structure mismatch. With this feature, we collect a masked version of all SCIM requests so we can trace the problems and help our customers. It is important to note that there is no personal data, name or Api key in the traces since we are anonymizing the values.
Delete TemplafyReader user and TemplafyAnalyticsReader from database project
With this release, we made sure that we don't have anyone connecting to SQL server as SQL users (username and password). Instead, we hired a much secure way that has recently become available on Azure SQL which is using SSO.
Public API support for SVGs
The documentation for uploading images in the Public API did not include SVG as a supported format, even though SVG images are now supported in Templafy. The documentation has now been updated so it correctly states SVG as a supported format for images.
Bug fixes
Bynder integration fails
We have made some improvements to the Bynder OAuth1 flow. Now, we have precise handling of the error messages sent by the Bynder server. Also, we removed our internal dependency to the Bynder's SDK binaries. The current integrations should not change anything to work with the changes.
Search returns 400 in Widen integration on Ecolab tenant
We improved the error logging in Widen. When a request fails we will log the exact server error message in the log. Additionally, we improved the search string escaping to prevent Widen from throwing errors. Everything that is matched below will be removed: - all non-alphanumeric characters - the word "and" in any casing - the word "or" in any casing The last improvement changes the search strategy in Widen integration. Now, we are using Widen's default search (available in the Widen's backend). Previously, we were trying to match against specific fields - category, description and keywords only.
SCIM Api does not support "–" and " _" in the PATCH requests
Until now,our PATCH API only supported words, numbers, space and these special characters \-,.@?!*;'. However, some of our customers use dash (–) which was not supported in their values. With this fix, we allow – and _ in the allowed characters.
Widen integration shows non-image assets
The Widen integrations now only shows image assets. Previously it was showing also other file types such as PDFs.
SCIM- Support Patch request for phone numbers containing + in their value
We have noticed that a few patch requests to our SCIM API are failing. Following up the problem, we have figured that we are not supporting + in the patch requests values. This fix is simply supporting that.
Unable to create documents that use dynamic text elements - Endless loading
We had an issue which in some cases was causing infinite loading when showing the create/update document form. It was caused by having a default value on a dropdown participating in dynamic forms. We have fixed the issue and now support this configuration. Customers need to update their VSTO Addins for the fix to apply to offline.
Slow loading time when opening build template
When viewing the edit page for a build template with a lot of text elements, the same list of text elements would be retrieved for each dropdown list on the page, which would cause excessive load time for the page. This has been corrected so now the list of text elements will only be retrieved one time when viewing the edit page. If a tenant has a lot of text elements this page will still be a bit slow to load, but this is because each dropdown contains all text elements for that tenant, which takes time for the browser to construct.
Document update form does not correctly fetch values from the document
We noticed a problem caused due to a network timing with dropdown form elements filtered based on user profiles. On clicking of the Update Document button for the first time the values in those dropdowns weren't displayed correctly . This issue has now been fixed the values now matching the ones selected in the create document. (Obs. This does not require a new version of VSTO Add-ins).
Wrong error message when trying to update a not Dynamics enabled template
When updating a non-dynamics enabled asset with a dynamics enabled one, the error message that was returned would incorrectly refer to the asset being transformation enabled. This error message has now been corrected.
Users page timeout
We had a performance issue with the user page in the admin portal. The page was slow for the tenants with more than 100,000 users and in some cases it was timing out. With this patch, we have tried to improve the performance of the queries.
September 2019
Bug fixes
Email signature add-in cannot be found
The installation of the new Email signature Add-ins could not be performed properly due to how the new package was generated. This caused Templafy Desktop updates to fail and the email signature add-in to not being installed. The issues in package generations are now fixed. For existing configurations it is required to re-save the Templafy Desktop settings page (a new version of Templafy Desktop client is not required).
Don't report duplicate tags when uploading images
When uploading images with tags in both IPTC Keywords and tags as file properties, but where one tag would have a preceding space, the upload would fail with a message about duplicate tags. This has now been fixed so it is possible to upload images that have the same tags in both places.
Replace should not change url
When uploading a presentation, the navigation path for that presentation would end in a number equal to the number of slides within that presentation. This has been changed so the presentation will not end in a number unless there are name conflicts in the folder. This also means that navigation paths will change for all existing presentations, so they in the future will have the correct navigation path.
Generic error message when trying to upload a template of 0kb size
Uploading an asset with a size of 0kb would give a generic error that wouldn't explain what the issue was. Uploading an asset of 0kb will now give an error that indicates what the problem is.
Access Widen sub-categories throws error
Widen integration supports correctly sub-categories. The sub-categories appear in Templafy as folders. Previous integration should not do changes in the settings in order to get the latest functionality.
Widen search does not scope the results based on the current category
Widen integration only searches in the current folder (category). Global search can sill be made from the root navigation folder. Previously installed integration should not do configuration changes in order the change to work.
Widen search does not work always
We found that the Widen search could behave strangely by submitting strings which could be interpreted as another search condition. We changed the behaviour by escaping the input (changing the quotes " to single quotes ' ). We also consider each word as a single search term and, finally, we wrap the search strings in special command for searching keywords (tags), filenames and description.
Root folders can be renamed through the PublicApi
It was currently possible to change the name of a root folder with the Public API. The root folder should only inherit the name of the library and should not be changed, so this is no longer possible.
Navigation path is handled as collision if name casing is changed
When using the Public API to rename folders the navigation path would change when changing the casing of a folder name. This has now been fixed so navigation path will remain the same when changing casing in the folder name.
Investigate re-authorization issue
We fixed a logical bug which was preventing the refresh of the authorization token in the Kadanza DAM integration. The settings of the existing Kadanza integration should not be changed in order for the fix to work.
Moving folders does not respect offline settings
When an asset folder which inherits offline setting would be moved to a new parent folder it would still be marked as inheriting, but the offline setting would maybe not be the same as the new parent folders setting. This has now been corrected so if the new parent folders offline setting is different than the previous parent folder, inheritance for the folder will be disabled and it will keep its offline state.
Error when trying to upload .zip files on Mac
We had a bug where uploading a .zip file was not properly identified when using macOS. We have now strengthened the mechanism from which we detect the file types and will identify zip files correctly no matter which OS or browser the client is using.
Features
Enable SVG in presentations and slides
Previously, we did not support presentations, slides or slide elements with SVG and they were rejected when uploaded in the Admin Center.
We have now added support for SVG and allow them in presentations, slides and slide elements.
VSTO Add-In update is not mandatory. Online and Offline mode both work even without latest update.
Create Public API endpoint for checking synchronization state
A new operation has been added to the Public API, which makes it possible to check is the asset synchronization is up to date for a tenant. This is relevant for when we want to test the Public API.
August 2019
Features
Make "dynamic forms" work if the text element binding is based on a form binding
We now support dynamic forms when a template has text element insertion configured with form bindings. The sought 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. For now it only works for dropdowns and it doesn't require a new Dynamics version. However, to work with both Offline and DCU it requires VSTO version 5.7.5.1837.
Various improvements for Kadanza integration
We made the following changes to Kadanza DAM integration: added new Kadanza logo added category groups added category hierarchy added user-based access fixed authorization issue Current Kadanza integrations can update the DAM settings by adding an optional category group or/and by removing the single user email.
Public API for static assets
The Pubic API of Templafy now is supporting all asset types. The functionality for each asset type (documents, presentations, spreadsheets, slides, slide elements, text elements, pdfs, images and folders) is the same and the client can do Create, Get, GetAll, Update and Delete for each asset type.
There are no breaking changes in this release of the Public API. However, there are a few changes in the following endpoints:
- GET /folders - "libraryId" query string parameter accepts all possible library values
- POST /{routeAssetPath} - "folderId" URL-encoded body key-value parameter is not mandatory. When it is missed, it is used the root folder for the library
- PATCH /{routeAssetPath}/{assetId} - "folderId" URL-encoded body key-value parameter is new. When it is used the assets can be moved in different folders in the library
Note 1: It is still not possible to update individual slides or slide elements. The endpoints for asset type slides and slide elements work on a file-level only.
Note 2: The public API can only upload "static" (non-Templafy enabled) files
Log tenantId on Authentication failed when requesting the token
We have released the SCIM api for some times now. In our system, the admins have the ability to refresh the API key to use for SCIM. If by mistake the admin refresh the SCIM api key but does not set it on the SCIM client (like Azure AD) all calls from the SCIM client will fail because the key is not valid anymore. With this update we log the tenantId and the AuthenticationMethod so if the tenant does not know about the incident our support should be able to help them
Allow form bindings in Template binding fields
With this feature release, we are introducing a new Dynamics version 1.10, which allows using form field references, when inserting text using the TemplateBinding property.
In Dynamic versions 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
Meta information is not updated if file is also updated
When updating assets with the public API it was only possible to either change the file or update the meta data in one API call. This has now been changed so when using the update action for an asset both the file and meta data will be updated if these are changed.
Templafy's Sharepoint integration throws a server error when attempting to launch Templafy from within Sharepoint
We had a bug that made the SharePoint integration incompatible with the Automatic UserProfile Updates from AD Claims feature. The reason is that we don't receive any user claims when SharePoint forwards the request to Templafy, thus updating AD Claims failed. We have added a check so it does not fail anymore
Cannot select Email Signature add-in version in Desktop Settings page
When the Email Signature Add-in versions were retrieved, we were looking for the artifacts in the wrong place. The only versions that were listed, were those already compiled. Now, this is fixed and all the available versions of the add-in are listed
OpenXmlComparer detects changes when presentation has charts based upon embedded excel sheets
With this fix we are making improvements in OpenXml comparer for presentation slides having charts and embedded excel sheets. It now detects per slides changes more accurately then before. More precisely, Chart Parts in slides and slide configuration related changes are detected accurately
July 2019
Features
Distribute Email Signature Add-ins by user group (feature is in Beta)
On July 31st we released a new feature that allows enabling the Email signature VSTO add-ins for Outlook separately from the Library VSTO add-ins and to distribute them by user group, as well as be maintained centrally in Templafy like other features such as Check and ProductivityPlus add-ins.
In the Settings page, we added a checkbox to enable the new email signature add-in. When the add-ins are enabled, the package is automatically set to the latest stable version. This version can be manually changed in the Desktop Settings Page from a dropdown. The new Email signature add-ins must be enabled for one or more user groups. In the user groups Edit Page there is now a new option to enable the Email signature add-in and this option is shown in the User groups page.
The required Templafy Desktop version to run this functionality is Templafy Desktop Client v. 1.4.
This feature can only be enabled by the implementation partner or Templafy technical support.
Show folders in Brandmaster
Until now, we have not been showing folders in our BrandMaster integration. This meant that all images were shown under BrandMaster library regardless of their folder, making it difficult to find an image if the BrandMaster solution contained a lot of images. This has now been changed so that we support folders for the BrandMaster integration. We support what Brandmaster call Global Categories.
Add the description field for asset libraries
We added a Description field to the Asset Library items. Assets can be searched based on it as well. For slides and slide elements the description can only be set on a presentation level, but it applies to all the child slides.
Kadanza
Kadanza DAM integration is like every other DAM integration in Templafy. The users of the integration: can see all categories as a flat list on the loading of the integration tab, can search a free text as in the Kadanza's "Asset Manager" UI, can insert the selected image in Word and PowerPoint.
Bug fixes
Invalid access when clicking on Brandworkz library
The DAM system Brandworkz has changed the way their API works, and therefore we had to do some changes on our side as well in order to get the DAM integration to work. Specifically, Brandworkz has now changed to use OAuth2 for authentication. This also means that configuration has to be changed for the tenants that are using the Brandworkz integration, since a few additional parameters are required by Brandworkz. This is unfortunately not something we can do automatically since it's specific to their Brandworkz account.
Google Taskpane cannot be opened from not localhost site
Our Google AddIns are still under development. In this process, we found a bug where it wasn't possible to open the Templafy website from within the Google task pane if the server wasn't localhost. We have fixed this by allowing Templafy website to be opened in an iFrame if it's opened inside Google. This will help us in our ongoing project of getting a working Google task pane.
system.UserEmail filter renders content in the filtered folder unusable when Offline
Offline content under folders with security filters was unusable because we incorrectly applied these security filters on the user profiles, resulting in disabled user profiles and documents. We fixed this problem by removing security filters from offline content metadata. Since we apply security filters before syncronizing offline content, it is not necessary to pass along these filters. Once users go offline, we only apply user profile filters.
Uploading images with invalid tags (that includes 1 character tags, only white space tags or ",") is permitted, which causes issues afterward
Admins were receiving errors when editing assets and uploading images with invalid tags. For example, tags with less than two character or duplicated tags are invalid. We tackled this problem in Admin Center by restricting upload of images with invalid tags. Existing invalid tags should be updated by admins to avoid future errors.
Fix Comboboxes placeholders not using the set value on admin.
Placeholder text on Comboboxes would not be displayed even if set on the form. We have fixed that, as well as changing the default placeholder from "Choose..." to "Choose or type..." to reflect what the user can do.
Colourbox: Eps images are available in library but cannot be inserted from add-ins
The Colourbox Dam Integration would show some assets that we do not support for insertion (.eps). We have now filtered out those assets from being shown, so we make sure to only present to the users the assets they can use
Search in slide library does not apply on text inserted into a table
It was not possible to search for slides and slide elements based on content within tables. This behaviour was due to a constraint we added where we only looked up text inside shapes. We updated the search functionality by looking up text in the entire slide instead. Since we extract the searchable text when uploading the presentation, existing slides and slide elements still have the old searchable text. Therefore, admins must re-upload existing presentations with this bug so Templafy can reprocess them and get the correct searchable text
June 2019
Features
Automatically update user profile fields and lock them for editing
We have added a new feature that allows client's to opt in for automatically update their user's profiles from the AD claims.
There is a new checkbox under tenant settings - if that is enabled - then we now allow configuring user profile form fields to automatically update their value from the mapped AD claim.
- Until now, users would still be able to get the value from the AD claim, but they had to manually fetch the updated values when editing a user profile. If we now enable the automatic updates - users will get their profile updated automatically whenever the AD claims update (on every sign in), and the user profile field will be locked (disabled) - so users cannot manually change the values anymore.
- This should only be used for tenants where the Active Directory data is fully up to date and maintained properly.
Note: This behavior only happens for the first (primary) user profile that is also used for the default email signature
Support Dynamics for headers and footer on document update
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.
Widen DAM integration is available in Templafy now
This integration can display the Widen's categories and assets available for the configured credentials. The search function is working with filenames, keywords and the description of the image assets. All standard DAM features for Templafy like browsing, inserting and downloading images are working as usual in this integration.
Support Dynamics for headers and footer on all worksheets
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.
Support Update for Custom Document Properties in spreadsheets
With DCU in Excel available we could make Custom Document Properties work with DCU too, which will require the new Dynamics Version 1.9.
Add warnings in validation rule for email signature image size
We added two validation rules related to images for our email signature HTML editor. The admin user is now informed with errors if images could not be found (in Company Data) or warnings if images are larger than 10KB when validating the HTML of the email signature. The image size warning is related to Gmail. Gmail shows attachment icons for inline images that are bigger than 15KB. The email signature server does not perform compression of images, so the emails sent through it will often result showing attachment icons in Gmail (even if the image is inline).
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.
Bug fixes
Preview of email signature uses wrong signature part when based on user profile filters
In case an Email signature template contains filters and the user profile was modified so a different signature template should be used, the preview would not reflect the modification. This has now been corrected.
DAM integrations can be added twice and not deleted
We don't allow multiple integrations to the same DAM systems, i.e. Dropbox, Bynder and the like, except for Generic DAM integrations. Despite that, if one would open a tenant's admin site on two different tabs and add a DAM integration on both of them without refreshing, there was no error/block for it. We have now fixed that.
.eps image type not supported
.eps files could be uploaded as logos under Company data but we were unable to use such files for Email Signature or from VSTO add-ins. We have blocked them on the front-end so they can't be uploaded anymore.
Upload of empty presentations gives error
Previously, Admins could upload empty presentations, i.e. presentations without slides, which caused some minor issues when processing and generating previews for it. We have now blocked such kind of presentations from being uploaded.
Dropdowns are not filled with values from Document when DCU'ing
We had a bug in document contentupdate 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.
Comboboxes do not populate the right values in Email Signatures
We introduced a bug that made combo-boxes from user profile output the wrong value when resolved in email signatures and documents. This bug only affected users that had made a change to a combo-box field only in their profile since this was introduced: 21.06.2019. Issue is fixed, so now the bindings are correctly resolved.
May 2019
Features
Templafy Desktop 2.1: Allow user to download host 2.1 from Settings page
A new version of Templafy Desktop Host is released (v 2.1), the Desktop Settings page is now giving administrators the new .msi version when the active Templafy Desktop Client is set to 2.1 or higher. Changing the .msi version to the new one is performed when having the client set to a version of at least 2.1 and the .msi is downloaded for the first time - a confirmation model is shown. After setting the .msi version to 2.1, only Desktop Client versions of 2.1 or above are available in the client version list.
Show list of users with Email signature for Office 365
A new list has been added to the email signature synchronization page under Email settings that show which users have enabled email signatures for Office 365. This list can be filtered by users which have it Enabled/Disabled and it is possible to search for specific users.
Support Dynamics for core file properties (Document Properties)
Templafy admin can configure document properties through Dynamics in Template Designer for Word, PowerPoint, and Excel. This means that metadata such as title, subject, company, etc. can be dynamic and contain bindings. NOTE: This function requires Dynamics version 1.6
Outlook add-in - Option to attach PDF from digital asset library
It is now possible to attach PDF in Outlook from your digital library. NOTE: VSTO Add-in must be least 5.6.X.X
Support insertion of dynamic text element from the 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. NOTE: This is available in VSTO Add-in 5.5.3.1604 The following dynamics configurations are supported: Text configurations Group configurations Image configurations Date configurations
Bug fixes
WebAddin custom manifest (SSO):
With this fix, the automatic SSO should work the same way for Office Online and Office Windows as is has been doing for the past months on iOS (Mac)
Preview failed to generate a preview for images with % in their name: This is now fixed
Box DAM integration: We experienced challenges with Box thumbnails for images. This is now fixed.
Cancel option when deleting package did not work: This is now fixed and when canceling a package deletion will package not be deleted.
Unable to download .zip with include "/" and "+" in this name: This is fixed
Unable to delete inactive Templafy Desktop Package: This is now fixed
Slow application with big data sources
Clients with large data sources did experience slow application. We have made a fix to this - and it no clients are running slow anymore. If a client is experiencing slow application please contact the Delivery department at Templafy.
April 2019
Features
New layout for the settings tab in Templafy Designer
We have improved Templafy Designer and made it easier for users to create templates.
- Visual interface for modifying template configuration: Previously, users had to write JSON to create templates. To improve the user experience, we replaced the "JSON" tab with the "Settings" tab which contains visual options for editing relevant parts of the template configuration. This means that users now can enable DCU and select dynamics via a UI instead of writing JSON code.
- 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.
- Convert to a 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.
- Backward 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.
Refine Active Directory (AD) Groups filtering
We have now added a tooltip to each group in the AD dropdown menu, where name, id, type, and description will be shown. At the same time, the API used for retrieving the groups has been switched from Azure Active Directory Graph to the new and recommended Microsoft Graph. By doing so, we have better control over what we retrieve from the Active Directory and performance is generally better.
Update Iconfinder signup process to include getting the token automatically
From now on Templafy Admins can enable Iconfinder DAM integration without to use extra tools e.g. Postman. The new setup process is as follows:
- Create an account on https://iconfinder.com
- Create new application under "API Applications"
- Open the following link in a browser: https://www.iconfinder.com/api/v3/oauth2/authorize?client_id=[YOUR_CLIENT_ID]&client_secret=[YOUR_CLIENT_SECRET]&response_type=code
- Click the "Allow" button. Copy the "code" value which will appear in the browser URL after the link is opened.
- Create new Iconfinder library integration in Templafy Admin Center and use the "client id" (from Iconfinder website), the "client secret" (from Iconfinder website) and the "code" (received in the previous step)
- Go to the app and open the Iconfinder library. This step is very important because it will trigger the token generation which finalizes the setup flow.
If everything is completed successfully the "token" value in the Iconfinder integration will be populated and you will see it when you try to edit the integration in Templafy Admin Center. Once the "token" is generated the rest of the settings ("client_id", "client_secret" and "code") are not used and they cannot be reused for another integration setup. If you need to set up again the same integration start from step 3.
Previous Iconfinder integrations which were completed before this release will continue to work without any further changes required.
Automate VSTO release
Prior to this release was part of the VSTO release a manual process, which now is changing so the entire process is automated. Releasing VSTO will be operated in three stages: Internal stage (internal validation), insider stage (testing and early preview for partners) and stable stage (release is ready to be distributed to all customers). When the release is ready for all customers it can be downloaded from Desktop Settings in the Templafy Admin Center
Multiple languages have been added to Templafy
Multiple languages have been added to a different part of the Templafy application, which covers: the main web application, stand-alone pages, error messages (server-side) and the Document Content Validator (DCV) application. The added 5 new languages are Italian, Spanish, Portuguese, Swedish and Norwegian.
Bug fixes
Error retrieving Azure Active Directory groups
For tenants not using AzureAD, we would incorrectly log an exception when editing user group filters. This has now been fixed by no longer throwing an exception.
Infinite loop when saving user profiles with invalid email signature configuration
When updating the user profile during the Templafy Desktop flow an invalid configuration could trigger an infinite loop. This is now fixed and an error will be displayed to the user - where the user can try again or close the window.
Save & Next broken
The "Save & Next" button was missing when editing a template. This bug was affecting all tenants. The bug is now fixed Templafy Desktop onboarding flow shows a blank screen for Windows 8.1 The <meta> compatibility property for Internet Explorer was not correctly interpreted because it was not first property. It is now the first <meta> property in the <head>. Furthermore, we also added compatibility options to HTTP requests headers
Multiple signature instances generated for the same Email account
In case we had the same signature valid for more than one domain and the same signature was used for both new and reply then the signature would actually get duplicated, although its content was the same. This fix addressed the problem and makes sure that as long as the signatures are equal only a single copy is generated.
The claim "address" from AzureAD might contains "\r\n" instead of line breaks
We had a bug that made new lines stored in the street address field in the Active Directory claims being wrongly dynamically inserted into Templafy's processing engines (documents, presentations, email signatures, etc.). Instead of correctly inserting new lines those were replaced with \n characters. It has now been fixed and new lines are correctly inserted. This was affecting all tenants who had new lines in their street address claim field in their Azure AD tenant setup.
Fallback thumbprint check failed with WS Federation authentication
We had a bug regarding our authentication method of WS Federation. When inserting a Signin Certificate 2 Thumbprint (the fallback certificate) this was not taken into account making users unable to to login anymore until the main certificate was updated. This was affecting all our tenants who had WS Federation as their main authentication method and it is now fixed.
March 2019
Features
Email signature
Improved consistency of Email Signatures which includes several new added features to the Email Signature. The new Email Signature addresses the challenges working with Email Signature in preview mode and in an Email application. It requires a manual migration process to go from version 1 to version 2. All new Email Signature clients will automatically be prompted to used version 2. To support admins in this task we created a set of new tools:
- A “Duplicate” button A “Migrate” button with migration results
- A “Validate” button and a more thorough validation
- A “Format HTML” button to fix markup indentation
- A Rich Preview area
- Full screen for HTML editor
Box DAM integration
The Box DAM integration is the newest integration in Templafy. Tenants who have Box account can add this integration to their Templafy solution. The DAM integration supports: folder browsing, searching images globally, viewing images, downloading images, showing tags on images.
Bug fixes
Entering email address twice when logging in via AzureAD
When accessing app.templafy.com and entering an email address, this could redirect to Azure AD, where the email had to be entered again. We now pass the entered email address to Azure AD as login hint, so the user only have to enter the password.
Double scrollbar in the Email Signature Preview
Two vertical scrollbars was shown in the Email Signature Preview. This is now fixed and only one scrollbar is active and will be visible to the user.
Signatures do not get updated when a data source change
If an email signature contained a binding to the data source that had no DataSourceSelectionId (not having it set or not being a drop-down type), the email signature was not updated in Outlook because no change was detected. This is now fixed and when verifying if data sources updated, it is also looking for bindings built with the form name.
Slide compare detects changes to presentation
We had a bug where all slides in a presentation always appeared as changed when uploaded to Templafy. This was a problem for Validator since it detected all the slides as changed, and prompted users to update all the slides - even the slides that were not modified. This was caused by structural changes in the presentation, which were invisible for users. We've updated our slide comparer so we now ignore such structural changes.
Keyboard shortcuts in drop downs did not read letters after a space
We noticed that dropdowns in our website did not search properly with space or special character such as "å" or "ø". Dropdowns will now understand this input and search the content accordingly.
February 2019
Features
Library: Filters based on User profile improved
Many customers are using filters based on the user profile date to only show content that is relevant to the users. A common case is to filter assets and folders based on the country that the user has chosen in her/his user profile. For users that for instance are working in multiple offices and therefore have multiple user profiles, they would only see the content of the assets which the last used user profile gave access to. To see other content it was therefore necessary to go through the document creation flow and change the user profile through the dropdown in this flow. 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 from US and EU offices 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.
Dynamics: Documents generated via dynamic templates blocked from upload
This is implemented to avoid admins accidentally uploading documents that contain user specific information and also looses the dynamic capabilities of the template. Link to new error message.
Custom document properties are no longer removed from a uploaded templates.
Improved messages when SSO login fails
When errors happens on single sign-on, we now provide a specific error page towards single sign-on providing more information about the issue. The user is now shown an error page guiding them to restart their browser or application depending on if they experience the issue via our Add-in or from the web. If the issue persists users should contact their internal help desk. We also pass on the error message from the service to enable their internal help desk to resolve the issue if possible before contacting Templafy support.
Option for Admins to export all users to a CSV file via the admin interface.
Support for SCIM (System for Cross Domain Identity Management)
Support for industry standard protocol called SCIM (System for Cross-domain Identity Management). Using SCIM our customers are now able to automatically sync their users and groups from their AD so user accounts does not exist in Templafy when a user leaves the client organisation.
Supported authentication methods:
- Azure Active Directory
- OneLogin
- Okta
When set up, Templafy automatically adds new users and remove them when they leave the tenant. For more on how to set-up SCIM can be found here: How to set up SCIM
Bug fixes
Dynamics: admin Combo boxes now show in bindings in Template Designer
Library: performance improvements for DAM libraries Colourbox and Skyfish.
January 2019
Features
Improved SSO for Web Add-ins
With this feature the Add-in will automatically try to log the user into Templafy when the Add-in is opened. That way the user will get access to documents and assets right away then they open the Add-in, without having to writing their email first. The automatic logon should work with all of our SSO-authentication methods. However to get this feature to work it is necessary for the user to be using a specialised version of the manifest file containing the right Tenant ID (like with Templafy Desktop). This can be distributed through the Office Admin Center.
Support for group bindings for row level content controls in Word
Users experienced that adding or updating a binding on a row level would be allowed even though it was unsupported. This would result in unintended and inconsistent behavior. 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, users 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.
New DAM integrations added
- Iconfinder
- Pexels
- TheNounProject
- Unsplash
Comments
0 comments
Article is closed for comments.