Website releases 2020

About this article

Note

This article only contains website releases for Templafy One

December 2020

Features

SCIM GET for users should always have primary eq true and type eq work if there is any address
We keep only 1 address for people in Templafy, therefore we were not setting the type of address in the response. However, some Identity providers including Azure Ad expect us to return the type. With this change we will always return type = work and primary = true

Templafy One User list export: Use ISO dates and add User Id in the export

Templafy has a feature for admins to download the list of their users as a CSV. In that list we were returning the following field

Id, Name, Email, DateCreated, LastSeen,UserRole, InternalOrExternal, PendingUser

With this release we also return the userId of the user.

Also, we have change the way that we format the dates to always return 4 digits for year and 2 digits for month and day (yyyy/MM/dd like 2020/06/05)

Adapt bridge in Templafy One to work with WebView2
For an upcoming version of the VSTO Add-ins, which will use WebView2 as a web rendering tool in Office, we are adding support for WebView2 in the application, to be able to call methods within the Add-ins

Create views in TemplafyOne database

The release contains ten view (AssetsView, AuthenticationMethodView, DamsettingsView, EditorDataSourcesView, TenantsView, UserAccessView, UserGroupsView, UserProfileSubscriptionView, UserSettingsView and UserView) that contain the columns we need in the data platform for reporting purposes

Move Templafy One access token cookie to subdomains
This release fixes a security finding about the Templafy access token cookie (TemplafyToken) being stored on the root domain (templafy.com ) so it can be intercepted by other sites on subdomains like support.templafy.com or videos.templafy.com if the user visits those.

The Templafy access token (TemplafyToken) is now stored on each subdomain instead and an additional flow called tenant reauthentication has been added to transfer tokens across when accessing a new tenant.

Remove MoveDemoUserToCorrectTenantInGlobalRegistryMigration

In the previous release today, we have ran the migration to move demo users to their correct tenant. Since this scenario should not happen again, we will remove the code from our code base.

Templafy One- Add suggested indexes to Database to improve performance

Templafy stores the main part of it's data in SQL Server and SQL server like other Relational database systems work on Indexes. We usually are good in adding indexes ourselves, but there are times that SQL server suggests some improvements that can be done in our database to improve performance. With the current release, we will dramatically increase the speed on fetching assets, deleted users and users to sync with Hive.

We also expect to increase the speed for fetching templates and user profiles but only a little.

Delete the migration for users that were deleted from one but not from global registry from code

We ran the migration to remove the remaining meta data of the deleted users in the #23123 . We can not delete the code from our code base.

Bugs

SCIM: Patch Doesn't work for CompanyName (organization)
There was a small bug in our SCIM API with HTTP-PATCH requests that caused us not updating the values of company name and department of people. This was a problem only if the provider used PATCH to update our data, but there was no problem when creating users (On HTTP-POST) or when updating a user with HTTP-PUT.

POST and PATH does not work for the country

There was a small bug in our SCIM API regarding country of people. The bug caused us not saving the country name in our system and it was on all type of SCIM request (HTTP POST, PUT and PATCH).

Issues with Imageshop/Bildebank Integration

The Imageshop external library would previously have problems navigating to subfolders when the library display name had been changed from the default value. This has now been fixed.

Sysop page fails with error instead of redirecting

This release fixes an issue of navigating to sysop resulting in an error page instead of redirecting to root domain when accessing without an acccess token.

Error message to end user revealing stack trace

Custom error was off in Templafy One before this release, causing some stack trace info on very specific cases. Since showing the stack trace has the risk of revealing sensitive code information to the hackers, it is suggested to enable custom errors which will disable code information in the response.

There are users in Global Registry that have demo as tenantId but the same user in One has a different tenantId

Templafy has a special type of user for demo tenants. In Templafy One there was a functionality to convert those users to a tenant's users when they got invited to a real tenant. However, we've forgotten to apply this change on Global Registry when moving the users. With this change we make sure that Global Registry will match what we have in One.

Upgrade Dynamics in Templafy One

Uploading/ Re-uploading sometimes doesn't complete successfully

When processing presentations, if blobs had snapshots created when deleting, a 409 would be thrown. Now, when deleting, we make sure to include snapshots and log if that is not the case.

November 2020

Bugs

Clean up users that are deleted from One but not from GlobaRegistry

In October we have added global registry to the system to keep track of where we have each user with their Ids. The code worked fine and we have added the users to the system. However, we have forgotten to remove the users from the global registry when we deleted the users from the system. With this update we add a code base to our system that we can run to remove all deleted users that has been removed from the system between 2020-08-01 an 2020-09-29.

Validator and charts(Templafy One)

This release addresses an issue with our Validator feature and presentations containing charts inserted into slides. We noticed an issue with such slides being wrongly flagged as changed by the user when using our Validator feature. This was incorrect behavior and has now been fixed. This fix does not require an update to our VSTO Addins.

Validator false positive on Presentations with Slide Notes

This release is related to a previous release from November 16th 2020 for the bug #24927 . With this release we are fixing the root cause of our Validator feature not working with presentations with slide notes. When only one slide of such presentation would be changed this would trigger Validator to detect changes in all slides that contained slide notes. This has now been fixed and again it does not require any update to the VSTO Addins version.

Delete users in Tempafy One fails

A few weeks ago, we have a concept for partner users in our global registry which is useful for accessing tenants in multiple cluster. However, We did not take care of the partner user deletion in Templafy One. With this release we made sure that when deleting a user, (s)he will also get deleted from partner users.

Assets with Inconsistent Blob Metadata - part2

This release fixes an issue related to saving Templates where old file metadata could be saved to the database despite it being update. Now, when saving, if the information about the blob of a template is more recent, that information is kept before updating.

Users can access a tenant even if the tenant state is canceled

We have introduced a small bug on November 17th when we fixed a the bug #24472 . To fix the original bug, we changed the whole deletion flow and added a grace period of 90 days to prevent tenant deletion by mistake or by social engineering. That change has changed a logic in our code that was preventing people from using the application when the tenant is marked for deletion. We have fixed the bug.

Delete Tenant fails if there is a orphaned asset children

When there is orphaned asset children data problems for a tenant, tenant deletion was failing because the task didn't know what to do with those assets. Since we are deleting the tenant as a whole we also made sure that we are deleting all orphaned asset children belonging to a tenant.

ISO date format when downloading user list as .csv from Admin Centre

We have noticed an issue regarding export user functionality where the dates where reported in an incorrect format. We have changed that so the date comes back in a standard unified way.

Privilege escalation admin can view super admin views in admin center

Added a check for forms, authentication methods and plugin configuration groups page to redirect to access denied when you don't have the required role.

Offline synchronisations runs in a loop causing 250.000DKK extra monthly bill

This release fixes the issue where TemplateItems could get wrong Blob Metadata information on the database, causing the respective assets to be downloaded every time if these templates are enabled in Offline. The Data Problem handler extended in this release will fix the Template Items that have outdated information.

Assets with Inconsistent Blob Metadata

When operations on Templates are made at the same time, if one of them is a Template replacement, it can cause the information of the Template to be desynchronized and therefore cause issues with the Offline synchronisation. The fix is to add an optimistic concurrency token, where if an operation is being made on a out-of-date template, the operation will abort and the user will be notified to try again.

Delete Tenant Throws not found exception while copying backups [One]

Since implementing Templafy Hive, we needed to change some of procedures to enable migration of tenants to the new platform. Those changes made the deletion of the tenants to break. With this new release, we made sure that we have considered all the changes for the new environment.

Also, to improve the tenant deletion we have added a guard to only let deletion of tenants that has been in Canceled or TrialEnded for more than 90 days. The delete tenant action then will delete all the data including the user accesses to other tenants

Default values no longer work in user profile
Before this fix, default values inside the user profile fields were not rendered to the user profile editor. After this fix they are set as in all the other form editors.

Validator false postive detection(Templafy One)

With this release we are fixing a bug regarding our Validator feature. When used with presentations containing VML(Vector Markup Language) drawing we would sometimes detect changes done to the whole presentation even when only one slide was changed. This has been fixed now and it does not require any update to the VSTO Addins.

Delete tenant action in One blocked by backups

In the task 12289Change Automatic Backup queuing to enqueue live tenants first and ignore canceled tenants, we have stopped backing up tenants that are in canceled state. However, when deleting a tenant, we are required to have a valid backup for some time unless the churned tenant asks us to delete it and therefore we do not let deletion of the tenant if we don't have a valid backup present.

With this fix, we let the backup job to take a back up from canceled tenants if there is no valid backup.

Features

Move partner users to deleted table in global registry when deleting user in Templafy One
When deleting a user we have to make sure to clean up the partner user data. With this task we make sure that it happens in Templafy one

Add priority to Aprimo file order in One

Previously, when downloading an image from an Aprimo library, there might be a noticable wait between clicking the image and the download starting. We now tell Aprimo that all such downloads should be treated as high priority, starting downloads faster.

Show prerequisites message when 2.5 is selected and no active version has been set

We have added a warning message when selecting Templafy Desktop client 2.5 or above. The message contains the new prerequisites for Templafy Desktop Client 2.5, and warns the admin to confirm they are in place in the customer's machines before saving.

Ignore deletion of global registery if the tenant is not there

We always expect to have a reservation record for Templafy One tenants in our global registry which keeps track of on which data center we keep the data of the tenants. When we delete the tenant, we make sure to delete these rows first so we completely wipe out tenant's data. However, sometimes for different reasons the actual tenant deletion might fail and therefore we need to let the delete action continue to do the job if it couldn't find the reservation record in the global registry.

Use DeleteTenantWithDependencies from global registry to delete tenants

The user deletion from out Global Registry was slow because we were doing it one by one. With this change we try to delete all tenant users in one go which should speed up the process dramatically

Revert Templafy.Website

Reverts an upgrade Dynamics and OpenXMLPowerTools. Too many changes at once were made. It will take some time to find out the root cause, so we are reverting to the previous state of Dynamics.

Send email to monitor group on special user invites in Templafy One

It was always possible to invite users to tenants using user invite page. However, we don't want the partner users to use that unless it is necessary since we have a separate flow for them. With this change when a partner user invites a user to a customer's tenant, we send an email to a special email and inform them about the action.

Format prerequisite message in Desktop settings page

We have formatted the predefined message for the missing prerequisites message when selecting Templafy Desktop client 2.5 or above in the Desktop settings page.

Add message in Desktop settings page

October 2020

Bugs

Tenant DNS records are not created from Templafy One

We have fixed a configuration issue that caused new DNS records to not be created when switching a tenant from Templafy One to Templafy Hive.

Fix dependency injection for Backup web job in Templafy.Website

Specific program dependencies were not bound correctly which made the computer vision tag web jobs fail. With this fix it will work again.

Asset file size inconsistency
Some assets, when replacing, keep the file size and checksum information of its previous version, that causes them, when those assets are used Offline, to be always synchronized despite no new changes on them. To address this problem, a new Data Problem Handler was created, that compares the file size and checksum information of all assets of a tenant with the corresponding information in the blob storage. If there is a mismatch, that can be addressed and the information on the database will be updated.

Updater fails silently on 2 Templates on ubsuat

The bug was located in VSTO addins. The document updater failed silently for 2 specific templates. After this fix, OpenXml program libraries are upgraded and the updater will succeed again on the given templates.

This upgrade affects Dynamics, VSTOAddins (here the bug will be fixed, but depends on Dynamics), Templafy One (depends on Dynamics).

Features

Upgrade Dynamics pipeline to 1.14 in Templafy.Website

Documents can have saved a proofing state, which tells the editor (Word) that spell and grammar checks were done before the last save, so there is no need to check when opening the document.

Before this fix we accepted all document proofing states, which is bad when your (as "clean" marked) template runs through Dynamics: content is added, which also has to be checked for errors. But since the checker is disabled by the CLEAN flag, the editor checker will not be triggered.

After this fix we will set the state to DIRTY on document creation.

With this release the feature will be applied to Templafy.Website.

Upgrade Website to the newest Dynamics version

This release upgrades program libraries that are handling the Office file format. This stabilizes and speedups the features around Dynamics.

Change Templafy One migration UI to display possible clusters

This release expands Templafy Hive tenant migration to allow cluster selection in preparation for Templafy Hive multi-cluster support. The migration options are currently visible to partners while the options to enable synchronization is limited to sysop members and complete migration to Hive is limited to sysop admins. Enabling migration is irrevocable and should still be discussed with the team responsible for Hive migration.

Make Hive releases available in Templafy One

Templafy Hive will from now on have a separate release track than Templafy One, which means different versions will be marked as internal, insider, and stable in the two systems. This change makes it possible to download Templafy Hive releases in Templafy One, so it is possible to upgrade to a stable Templafy Hive VSTO version before migrating to Hive.

September 2020

Bug fixes

Users deleted in Templafy One are not deteled from GlobalRegistry

Bug fix for user deletion in Templafy One. When we delete a User from One, we should also delete him from the GlobalRegistry which means that the user can be recreated to another tenant.

Fix build warnings in Templafy One

We had a lot of build warnings in Templafy One Website. This task was about to remove all of them in order to make the developer's life easy when developing and supporting Templafy One. Warnings are not necessary errors but are also an indication that something is not done in the most optimal way. Warnings can introduce subtle errors which are very hard to track.

Add content-security-policy header for saml2 authentication pages

This release enhances security of the website during the Saml2 authentication.

This release is purely a technical one and does not introduce any new functionalities.

Make `Templafy.Webite (IntegrationTests)` pipeline working

We have fixed internally an issue which was preventing the normal running of our Integration tests. This change is only related to tests and is not visible in any way for the normal users.

Remove temporary functionality for detecting duplicate users in GlobalRegistry

This is a technical release removing temporary functionality used to clean up duplicated users introduced last week.

Clean up duplicate users in GlobalRegistry

This is a technical release allowing for removal of duplicate users created due to a missing constraint.

Investigate SocketException in TemplafyOne

We have improved our setup when using external services. Previously, we were opening a lot of connections which were not handled correctly. Now, we ensure that the connections are re-used in a proper way and should not create the previous overhead.

This update improves the performance in the following areas in Templafy One: DAM integrations, Salesforce integration, Logging, TagsService, ExchangeOnlineIpRangeService.

SAML2 authentication redirect to IdP login page shows blank page in Safari
This fixes a problem for Saml2 authentication on Safari browser and browsers running on iOS.

Web add-in authentication broken in Office Online when using Saml2 authentication in Chrome browser

Sign-in for the Templafy web-addin inside Office Online was not working after updates by Google Chrome. We solved this in a previous release for AzureAd authentication, but the problem still persisted when using Saml2 authentication. We have found the root cause and solved the problem.

Web add-in authentication broken in Office Online when using Saml2 authentication in Chrome browser

We reverted the previous release, and will deploy it Monday during business hours:

Web add-in authentication broken in Office Online when using Saml2 authentication in Chrome browser

WebJobs are no longer working

Our webjobs stopped processing their tasks after release Templafy.Website_Release_2020.9.9.1 due to a dependency conflict.

Web Add-in authentication breaks (in the newest Google Chrome version and in Safari)

Sign-in for the Templafy web-addin inside Office Online was not working after updates by Google Chrome.
We have found the root cause and solved the problem.

Add-ins: Update feature browser emulation of IE from 10 to 11

Updated TemplatePackage browser emulation from IE 10 to IE 11 for Asset Explorer to align with the new "Hive" platform.

Colourbox integration - Search throws an error

We have fixed a data retrieval operation in Colourbox. Previously, it was possible fo fail when a given search string was used. The error was fixed by removing not used properties from the response. No adjustments are needed of already configured Colourbox integrations.

Email signature package doesn't load - dpdbelux tenant

Templafy Desktop was not updating Email Signature Add-in package to the selected version in admin.

Customers using the "Email Signature Outlook Add-in" beta feature, who manually selected a version that was already in use by another tenant, would not see their selected version distributed through Templafy Desktop. However, this was not reflected on the Desktop Settings page, which did have the correct version selected.
Any customer who has this feature enabled will have to verify that the correct version is reflected on the Desktop Settings page.

Form fields coming from text elements do not always get propagated on document creation

Before this bug there was an issue about auto selecting drop down fields. If a drop down selects a text element (with form fields again) it can happen that the form is requested again, because the selection matters to display more form fields (the ones from the text element). When auto-selection is enabled, you will ask the server a lot in a fast manner. When two requests are sent after another through the internet, their answers can come back in an other order. With the fix, we made sure that only the latest request is rendered.

August 2020

Bug fixes

Files disappearing upon using the "move function"

When moving assets or other similar operations, a background operation is triggered and processes those assets asynchronously.

If a user tries to delete a folder before that process is completed, it would delete the assets before the move is completed.

To fix this issue, when deleting, the application verifies if a background process is running for this tenant and if so, it will prevent the deletion and notify the user to try again later.

Validator detects changes on non modified slides with charts

We detected a problem regarding our Validator feature and slides containing inserted charts. It seems when a presentation was being replaced in the admin and we will split the slides to compare if anything has changed, we would detect changes even if the slide was not modified. This was due to the library we use to split this slides was doing changes to the slide with charts. We have fixed this now by saving the original presentation that is being replaced and comparing the two presentation with each other instead of a splitted slide and the new presentation.

July 2020

Tasks and features

Update Default Email Client signatures

We have updated the list of default email client signatures that we are looking for to replace in emails that are going through the Email Signature Server. This list now also contains the default signature appended by BlackBerry Work application.

Disable all pages in Templafy One once tenant has been migrated to Hive

When migration to Templafy Hive is enabled, users for tenants that have been migrated to Templafy Hive will be redirected to an error page if trying to access Templafy One.

Set up Tenant Migration Status in TemplafyOne

The next version of Templafy, Templafy Hive, is coming soon. We're adding the foundation for synchronizing accounts and users to Templafy Hive, and to migrate completely when the time comes. There will be no user interface changes for now. So no public release notes.

Include registry key for disabling roaming signatures in package template

Microsoft is soon going to release a new feature called "Outlook roaming signatures". When released, Outlook will load the signatures from a new place, ignoring the signatures synchronized by the Email Signatures Add-in.

In order to have our add-in work as expected at that point, we are now also including in the package template the registry key needed for disabling this new feature.
This registry key file, named Set DisableRoamingSignatures.reg, will needto be included in the VSTO packages that have the Email Signature Add-in.

Add UserId column to DeletedUsers in TempafyOne

This release includes a fix for keeping track of deleted users. Until now, we did not have a reference to which users were actually deleted and this was causing issues for user synchronisation done by SCIM.
The user facing behaviour has not been changed, as this is a technical release.
This is done for all tenants, no matter if SCIM is enabled or not

Bug fixes

Web Add-ins - pop-up window not closing, login interrupted due to MacOS Upgrade

We have found an issue that prevents the Single Sign On flow to complete when running inside web-addins on Mac version 10.15.5.

We have found the root cause and fixed the problem.

Templafy One Partner users are showing up in the admin list and external user list is empty

In the release that we had on July 22nd, we have updated the way that user page works to improve performance. There was a problem in the query that made it show partners in the admin list. With this fix the correct list will be shown to the users

Templafy Taskpane refuses to load in Office in Teams

Adjust security policies so that Office Web Add-ins can be loaded within Microsoft Teams web.

Users page in Templafy One causing request timeout for tenants with above 100K users

Templafy is getting more and more Enterprise companies and some of the queries are not efficient enough when the user list is too big. In one special query, we have experienced slowness and even timeout in the users page in admin area when they have a big user set (above 100k). In this, we have improved the performance so the user page can show up a lot faster.

Users list shows internal and external users differently depending on who is logged in

We have had a bug in users page in admin area that made the admins show up in the external users tab as well. With this task we have fixed it so only 2 groups of people show up in the external users:

People who has been invited via sending Email
People from another tenant

Validator detects changes on non modified slides with charts

Document XML dissappearing

Before this fix, creating a document from a template with a text element insertion was resulting in a document without the custom XML parts from the source template (for example SharePoint metadata). The fix makes sure that all custom XML parts of the template document are copied over to the resulting document.

June 2020

Features

Frontify Integration is using deprecated query objects
We have made technical improvements of the Frontify integration which are not apparent for the end users. The changes consist of: 1. Improvements of the query syntax of the requests to Frontify, 2. Stronger parameter validation

Register a DNS record when tenant is created
This release includes some technical changes that allow us to serve the old and new platforms on the same DNS zone.
It does not include any behavioural changes to the application.

Deprecate old way of adding customXml parts

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+.

Dynamic IP validation
This feature enhances the security of our Email signature solution for Office 365. The Email Signature Server validates the IP address of the sender based on a list of IP ranges belonging to Exchange Online. We encountered update problems on the list of IP ranges from spf.protection.outlook.com , causing rejection of valid IP addresses. Templafy now retrieves the list of IP ranges dynamically using an official Microsoft service.
Templafy servers run a daily job to get the valid Exchange IP ranges from Microsoft and synchronize them to every Tenant's Email Signature Server blob storage hourly. Manual synchronization of the IP ranges list is possible also by saving the Synchronization Settings. Changes in the list take effect in 30 days, leaving plenty of time to synchronize the list. From version 0.2.0.1600 the Email signature server is capable of using this dynamic list to validate the sender IP address of all incoming emails it processes.

Add support for setting up custom XML values (Website)
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.

Bug fixes

Frontify image integration doesn't work on Mac and Templafy One
We fixed a bug in our Frontify integration for Templafy One. Image insertion from Web Add-ins was not working. Existing integration should not take any action in order to get the fix working.

Images uploaded with "%" character in filename will not have previews generated
When uploading an image with percentage sign in the file name it sometimes resulted in the preview not being shown. This has now been corrected so the previews will be shown correctly regardless of the filename.

Some previews are not working after percentage fix

After the fix for previews with files that has percentage sign in the name other preview stopped showing. The previous fix has now been reverted.

Validator detects changes in slides that contain charts even when no changes have been made

We noticed multiple issue with the Validator feature where slides containing inserted charts will appear as modified even tough they were not changed by the user. This is due to:

The chart smart tag language being changed when the user saves the document using an office version that has a different language set
The xml namespaces in the chart being out of order when the document is saved a second time
Due to these not being actual changes that the user will see or care about we are now properly ignoring them when comparing two slides.

If someone deletes an asset and for some reason the assetSyncronization job doesn't work as it should and the assetChildren row remains in the database, the restore will fail
Fixed an issue when in certain cases restoring the backup of a tenant would fail because there were conflicting fields within the database, regarding assets that were previously deleted. Now, when restoring, the system clears leftover information of deleted assets before restoring.

May 2020

Features

Sort Kadanza images by uploaded date

The Kadanza DAM integration serves image assets in a new order. Recently uploaded files are shown first now. Previously the order was not specified.

Port Templafy.Website to hosted agent

We are changing the way our releases of the main website app are built. Previously, we were using self-managed virtual machine server and now we are switching completely to Azure-hosted build agents. This release does not have any whatsoever effect on the end-user and it should not be noticeable.

April 2020

Features

Trigger Email signature Synchronization for new SCIM users automatically

The automatic synchronization job for email signatures was triggered for a tenant in the following cases: Email Signatures are updated, Data Sources related to a user profile are updated or the User Profile form is updated.

Because we are now supporting user and AD claims provisioning through SCIM, we have extended the previous list of conditions and the synchronization job will also be triggered when a user is created, or when a user's User Profile had its Claims updated. For this last case, the synchronization is run only when the Automatic User Profile updates from AD Claims is enabled for the tenant.

Bug fixes

Fix to Frontify integration

We found a bug in our Frontify integration based on changes in the Frontify API. Now, we don't include the "/" (trailing slash) when doing requests. Also, we changed our error handling because the error messages of Frontify was structured in a new way. Existing integrations will continue to work without to be reinstalled.

Slides that change layout, order or add an image are reported as new when replacing a presentation

When considering if a slide was new or not, there was a bug on presentations with non-dynamic content where only the first tag of each slide was considered. If that slide had other content that added new tags, it would cause the slide to be considered New and would therefore discard previous information kept on it. Now, all tags are considered, allowing the system to find the SlideId.

Description wiped upon re-upload of .json file image library
The issue with description being removed during the archive upload was addressed

Ensure Enable email signature for office 365 button in Sysop can run
The button from Sysop to enable Email Signature for Office 365 can now be triggered by users with the Sysop Admin role, i.e. Support and Delivery.

Add warning dialog to Enable email signature for Office 365 for all current users button
To make sure that we don't enable Email Signature for Office 365 for all current users from the Sysop page by mistake, there is now a confirmation dialog just before running the migration.

Synchronization job not triggered on SCIM updates
The automatic synchronization job for Email Signatures was triggered only if the changes made by SCIM were made in the last hour. If the first synchronization job after making the SCIM update failed, then the next synchronization job wouldn't have been queued.
From now on, we always queuing up a synchronization job if there are changes that have to be synchronized.

Also, we now better monitor the cases in which the synchronization job for email signatures fails because the connection to the Blob Storage was not possible.

Improve error handling when uploading document to Salesforce

Error handling has been improved in the Salesforce integration so that a detailed error message is recorded whenever the upload of a document to Salesforce fails. Previously, only a generic error message (which did not include the exact reason why the upload to Salesforce failed) was recorded.

No user profile created when DefaultNewUsersEnableOffice365EmailSignature is set

We had a problem where the email signatures for Office 365 were not being generated for new users that never logged in (a new feature).
The issue was that there were no user profiles created for these users until they logged in for the first time.

In this release we made sure that user profiles are created at the same time as the users are created (either by auto-provisioning or synchronized through SCIM)

Edit user profile dialog cannot scroll when showing onboarding in taskpane

We updated the onboarding flow layout so that the scroll bar works on very small screens also when viewed within the VSTO add-ins. If the first time a user accessed Templafy was through the VSTO Add-ins, the user had a very small screen, and the user profile form had many fields, it might not have been possible for the user to see and fill out all the user profile fields during the onboarding flow.

March 2020

Features

Create checkbox in Settings page to enable office 365 feature by default for new users

The Email signature for Office 365 feature has now a new option to enable the feature for every "new user" in the tenant by default, without the need for each user to go through the onboarding flow. This option is available in the tenant settings page.
The functionality to enable the feature for all "existing users", released earlier, is a now migration job and can be triggered for a specific tenant from the Sysop area, by anyone in Engineering.
These two functionalities are helpful for large enterprises with a lot of employees, that cannot and do not want to rely on all their employees to go through the on-boarding flow. The on-boarding of the end-users is thus completely delegated to the customer.

Prerequisites: It is important to notice that these functionalities assume that: 1. users are provisioned in the tenant (e.g. using SCIM); 2. User profiles are automatically updated from AD claims or are otherwise kept up to date by the users; 3.The customer's Active directory has good/perfect data.

Create button in Settings page to enable Office 365 feature for all existing users

Added a button on the tenants settings page, to enable Email Signature for Office 365 for all current users in one click. This can only be triggered by Templafy and partners.

Add URL validation for trailing slash

We added a validation checking the Frontify URL for trailing slash character. It is a change about coding style consistency

Frontify integration

We added an integration to Frontify. The admin can choose between Icon, Image or Logo typed library during the setup. Currently, one tenant can only have one Frontify library type. This is a limitation by design.

Bug fixes

Updater does not update the document

In our last Website release, we updated Dynamics which included a minor change that accidentally broke Updater in VSTO, due to a non-backwards compatible change. We reverted this non-backwards compatible change to fix Updater, and have taken measures in the code that protects us from a similar mistake.
No action is needed after this fix has been applied to our Website. Updater will work again for all existing templates and documents created before the problem and before this fix.

Slides detected as changed without being tempered with- Add support to comparer

After users made changes to some of the Validator enabled slides they were met with all slides showing as "need to be updated". This meant that all slides were detected as changed which was unexpected behavior and a bug in one of our packages (OpenXmlComparer). This was triggered because we were detecting some changes on the inserted charts in the slides of the presentation. We have now fixed these issues.

Templafy Desktop download slots per tenant are not capped

We have identified a problem with Templafy Desktop not being able to update content. After investigating, it seems that the issue is that we have reached our total bandwidth limit on the storage account from the Microsoft side.
However, until now we were not limiting the amount of concurrent clients downloading content for one tenant, unless they were using the same IP. This lead into the issue of a single tenant eating up almost all bandwidth as long as clients were using different IPs.
To solve this problem, we have now both increased the total bandwidth allowed for our storage account as well as limiting the amount of total concurrent clients downloading for one tenant, even if they are using different IP's - so now we have more room for other tenants as well.
The new limits are: 10 concurrent clients for the same IP and 250 concurrent clients for the same tenant (as long as they use different IPs)

Brandworkz assets cannot be downloaded

We made much more robust the downloading of files in Brandworkz. Templafy admins does not require to do any changes.

Brandworkz can't switch settings configurations

We found misleading configuration problem when the Templafy admins were switching the settings between 2 accounts for Brandworkz. Previously, the entire integration had to be deleted in order the new settings to work correctly. This is not necessary anymore.

Svg`s blurry in preview due to small file size.

Previously, the preview generation would convert a Svg to an image and then scale it, causing blurriness if the Svg is originally small. The preview generation now properly draws the Svg in the target preview sizes, therefore maintaining its sharpness.

Bynder integration - Search fails and results in authentication error when special characters are used

Fixed a bug in the Bynder integration that caused the app to malfunction and show error messages when performing searches that contained non-letter characters such as " " (space) and "+". The bug was due to an incorrect encoding of the search string.

Brandworkz library integration fails

We found a problem with our Brandworkz integration. The base URL used for connection to the service was wrongly used. We made sure that we use "https://api.brandworkz.com " only when we are getting the initial configuration and afterwards to relay on the response coming from Brandworkz. We made sure to clean the base URL value on an update of the settings.

February 2020

Features

Start onboarding flow if everything is filtered away due to invalid user profiles

Some customers have set up Templafy, so that all templates are filtered on the user profile information. This works great when users have a user profile, since they will then only see the templates, that are relevant for them.

In most cases users will either have created a user profile in the onboarding flow or when they try are in the process of creating a document.

However, In some cases - like server installations - the user have not gone through the onboarding flow. In these cases, the user will not be able to access any templates, since all templates are filtered based on the (missing) user profile information.

To fix this, we have made a change, so that users who don't see any templates in the library because they don't have any valid user profiles, will see an onboarding flow in which they fill out their user profile. It will therefore look like in the gif below:

Bug fixes

Unknown error occurred when attempting to make changes in the Admin interface while the tenant is running a backup

When a tenant is being backed up and an admin tries to make changes to the asset library, they were met with a generic error message. This has now been changed so the message will instead indicate that the tenant is being backed up, and that changes can not be made while the backup is running.

Forms are removed from template if saved before options are loaded

We had a problem where forms and plug-in configurations could potentially be lost when saving a Template before it was fully initialized. This problem occurred only when the website was under heavy load, and the Admin was fast and clicked "Save" or "Save and next" before the initialization was done. This resulted in the forms and plug-in configuration being overridden with empty configuration.

In this release we fixed this issue by disabling "Save" and "Save and next" until all initialization is completed.

Parent folder is broken when replacing a presentation through the PublicApi while also moving it
When updating both the asset file and folder for Presentations, Slides, or Slide Elements through the Public API, the presentation would only appear moved in the admin module but not for the end-user in the app. This is now corrected so both the asset file and folder id can be updated simultaneously and be displayed correctly in the app.

More descriptive error message when adding a link that is too long

When adding a Link with a URL longer than 200 characters the frontend would just show a generic error message that did not describe what the error was. A new validation message is now shown, which says that the link is too long and the user could possibly try to shorten it with a URL shortening service.

January 2020

Bug fixes

SVGs with stroke-dasharray CSS property could not be uploaded

SVG files containing the CSS property "stroke-dasharray" could not be uploaded in the Image Library. This problem was due to us using 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 admins to upload SVG files containing this CSS property to the Image library.

In order to allow users to insert such SVG files from Images or any External Library into the VSTO Add-ins, customers must upgrade their VSTO Add-ins to version 5.8.0.1984.

Web Add-ins - Taskpane not receiving a message back from the dialogue - MAC OS

We previously fixed an issue that prevented the Single Sign On flow to complete when running inside web-addins on Windows version 1903 and 1909.

This only happened for tenants with a manifest that points to tenant.templafy.com.

However that fix introduced another problem that only occurs on Mac clients.
We have made sure that the previous fix now only applies for Windows clients.

Function.ticks stopped working

We noticed with the latest release that the default value binding {{Function.Ticks}} stopped working. This did not break any templates but instead it was not introducing any values into our create document form. We have now fixed this functionality to properly generate random numbers, as it was doing before.

Dynamics enabled slides cannot be inserted into a presentation

We noticed with our previous release that we broke insertion of dynamics enabled slides into presentation. Due to it being just a technical release we decided to revert it in order to fix this problem, and make sure this does not happen again.

Web Add-ins - Taskpane not receiving a message back from the dialogue

We have found an issue that prevents the Single Sign On flow to complete when running inside web-addins on Windows version 1903 and 1909.

This only happens for tenants with a manifest that points to tenant.templafy.com
It worked fine with the manifest published in the Microsoft Add-In store.

We have found the route cause and fixed the problem

Slide element library does not keep the tags upon replace

We had a bug in the slide element library that when replacing a presentation where its elements were tagged, the tags were not kept. The situation in which this was happening was if that presentation had some tags set on itself then all individual element tags were removed at replace. The reason for this happening is that presentation tags are propagated to all the elements, even though they are only visible in the UI on the presentation (in order to be able to search faster and show proper results).
We have fixed this bug so now we properly keep element tags at replace.

Slide Library inconsistently keeps tags for slides upon replacement
We had a bug when replacing a presentation where its slides have tags, the tags were not kept. The situation in which this was happening was if that presentation had some tags set on itself then all individual slide tags were removed at replace. The reason for this happening is that presentation tags are propagated to all the slides, even though they are only visible in the UI on the presentation (in order to be able to search faster and show proper results).
We have fixed this bug so now we properly keep slide tags at replace.

Image header does not get inserted as per specified dimensions
During a change, that has been deployed to the website on December 11th, 2019and 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.

Links are visible but do nothing in Outlook VSTO versions older than 5.7.5.1931
Customers reported seeing the Link Library in versions of VSTO Add-ins older than 5.7.5.1931, which don't support link insertion.

As part of this release, we remove the Link Library in versions of Outlook VSTO lower than 5.8.

We made this adjustment to ensure that the Link Library is shown only in the Outlook VSTO Add-ins that support link insertion. Moreover, we compare against version 5.8 and not 5.7.5.1931 to keep a maintainable and consistent version comparison strategy.

Customers on VSTO Add-in versions of 5.7.5.1931 or higher must update to version 5.8.x.x or above to continue using the Link Library.

Features

Upgrade Monolith to new Dynamics

When we started developing the Self Contained System, we created a new package of Dynamics specifically for this system. We have decided to merge these two packages into one. This means all new features and bug fixes will deploy to both systems and thus

this release is purely a technical one and does not introduce any new functionalities.

Allow app to be shown in iframes from any HTTPS domain
Templafy can now be loaded inside an iframe from any domain using HTTPS. Previously, this was not possible because of a wrong configuration rule in our back-end.
Please note that authentication through a third-party service might not work inside an iframe if the authentication provider prevents their website to be embedded inside iframes. For example, authentication via Azure Active Directory is not possible when loading Templafy inside an iframe because Microsoft prevents browsers from embedding their authentication page inside iframes.

Make it possible to download blobs from external system frontends
Previously, we have allowed external (DMS) systems to embed Templafy inside an iframe or popup window. However, the download links for the created documents were not accessible from a different domain. Now, we have enabled CORS (Cross-Origin Resource Sharing) over these links and they can be accessed from a different domain (e.g. the domain of the DMS system).

All existing external system integrations do not require additional setup. New to Templafy external systems need to be enabled via a new release.

Articles in this section

About this article

Note

December 2020

Features

Bugs

November 2020

Bugs

Features

October 2020

Bugs

Features

September 2020

Bug fixes

August 2020

Bug fixes

July 2020

Tasks and features

Bug fixes

June 2020

Features

Bug fixes

May 2020

Features

April 2020

Features

Bug fixes

March 2020

Features

Bug fixes

February 2020

Features

Bug fixes

January 2020

Bug fixes

Features

Comments

Articles in this section

About this article

Note

December 2020

Features

Bugs

November 2020

Bugs

Features

October 2020

Bugs

Features

September 2020

Bug fixes

August 2020

Bug fixes

July 2020

Tasks and features

Bug fixes

June 2020

Features

Bug fixes

May 2020

Features

April 2020

Features

Bug fixes

March 2020

Features

Bug fixes

February 2020

Features

Bug fixes

January 2020

Bug fixes

Features

Related articles