|1647||File names are case-insensitive during import||Improved file name recognition to be case-insensitive when importing attached files.
The system now checks for variations in capitalization when determining a match between the import file data and the attached file name.
|1687||Password related security options||Introduced new password security options, which are available in the Options tab of the Password field wizard:
1. Do not allow login and password to be the same. An additional option places a restriction on the password
from containing the login string at all.
2. Require user to change their password if it is reset.
3. Control reuse: If Yes, prevents users from reusing previously used passwords when entering a new one, for example when their old password expires.
|1696||Email-based ownership name parsing||
The options in the Store Sender's Address section of the Inbound Email wizard, located at Setup > Email and
SMS > Configure Inbound Email > edit or add new account > Record Mapping tab, now include the ability
to store the email address and name in separate fields.
This is especially helpful if ownership in some tables is based on email address and users may have different
names used for the same address; for example, "John Smith <firstname.lastname@example.org>" and "John G. Smith
<email@example.com>". Separating the name and email address will prevent errors due to name-sensitive
Additionally, when the second option is chosen, the system will parse email record ownership recognition in
cases where the recognition is based on the email address, and the address is displayed in both "AAA
<firstname.lastname@example.org>" and "email@example.com" forms. The system now recognizes that these two forms of email
address are synonymous. When the first option is chosen, the system will still expect strong matching of both the
name and email parts of the record.
|1714||Full-text search for Chinese words||Full word search is now available for the Chinese language. By including the Chinese dictionary in the Agiloft installation package and leveraging the Stanford Chinese Segmenter library (http://nlp.stanford.edu/software/segmenter.shtml.), full-text search is now possible for entire Chinese words, in addition to the previously supported character search.|
|1715||Improved conditional content capabilites in print templates||
A new formula for print templates now allows large sections of text to be inserted conditionally, based on a
formula or field values.
This helps simplify print templates when large sections of static text are only included if some criteria is met.
Below are examples of the applicable scenarios for this feature:
Scenario 1: If the condition is true, <PARAGRAPH1> and <PARAGRAPH2> are inserted; if the
condition is false, delete the paragraphs from the print template output.
Scenario 2: Assume condition1 is false and condition2 is true. The text following condition1 will be removed and the text following condition2 is retained.
$startif(condition1) <TEXT> <TEXT> $endif <MORE TEXT> $startif(condition2) <TEXT>$endif
Scenario 3: Assume condition is true. <MULTIPLE PARAGRAPHS> below will be retained.
Print templates can still utilize the simple formula $if ($case.priority == ""Critical"" ? ""Important issue"" : ""Normal priority"") to include shorter strings of conditional text. The new formula offers additional flexibility for print templates.
|1721||New field in Teams table: Allow emails to be sent to this team||
Added a new Allow emails to be sent to this team choice field in the Custom Fields tab of the Team wizard.
Available values are Yes and No. The default value for most existing teams is Yes. Teams which contain customer in the team name have a default value of No.
|1722||Currency conversions in formulas fields||Added the ability to perform currency conversion in fields. This converted amount can be used as a field's
default value formula, as well as during mass edit and in update actions.
The following formulas enable you to perform currency conversion calculations:
For example, the formula of a field to convert USD to Euro could look like:
convertCurrency("USD", "EUR", $amount_in_dollars, $payment_date).
This field would take the Amount in dollars field and convert the amount based on the currency conversion rate
on the date the payment transaction occurred, based on the Payment Date field. The new field would display the
result based on its settings and field type.
It is also possible to leave out the date from the field. If the formula excludes the date, the currency will be converted at the current rate. In the example above, this would look like:
convertCurrency("USD", "EUR", $amount_in_dollars).
Currency conversion formulas use the JSON API fixer.io to obtain exchange rates published by the European
Central Bank. These rates are updated daily at approximately 4pm Central European Time (CET).
|1725||Systemd Linux support||Added full support for systemd-based Linux systems. Although systemd does have legacy support for SysV
scripts, the Agiloft installer previously didn't work properly with systemd distributions.
|1727||FTS re-indexing optimization||Optimized the process of FTS re-indexing on record updates so that unchanged data is not re-indexed. This will
reduce the server load during record modification.
|1732||DocuSign documents attached with signature certificate||DocuSign integration added the ability to create signed documents combined with their signature certificate.
A new Combine with Certificate of Completion Yes/No choice field was added to Docusign Envelope table with a default value of No.
When an Envelope Status update with a status of Completed is received via DocuSign Connect, the Agiloft DocuSign extension checks if this envelope record's Combine with Certificate of Completion value is Yes and retrieves a PDF containing the combined contents of all documents and the certificate in one file.
|1735||Optimization of Calculated Fields recalculation||Calculated Fields recalculation has been optimized to avoid sending multiple requests for the same record/column after a record is saved. This significantly reduces the system load caused by background processes.|
|1736||Enhanced support for keyboard shortcuts||It is now possible to define shortcuts via Setup > Look and Feel > Shortcuts. KB admins may set shortcuts
to navigate to table views, open recent records and searches, etc., and then apply these settings to teams. For
complete details, click here.
|1737||Variable to define failed email resending||
Added two variables which enable users to configure whether, and how often, to re-send failed emails. The
variables can be found by navigating to Setup > System > Global Variables > Variables with Default
The new variables are:
|1738||Sort order for collated records when sending email||Changed the sort order of records which are collated on email sending. Records are now sorted by ID in
|1739||Calculated JMS (Java Message Service) queue optimization||Enabled an in-memory duplicate message collector for the calculated fields recalculation requests queue, which
uses a smaller disk load and doesn't have a disk space leak. This will reduce the risk of an unresponsive status
from the server when performing operations.
|1740||Improved ability to mass edit field properties||Improved the ability to mass edit field properties in the Table wizard and eliminated instances of unexpected
behavior. Please visit the Fields topic for a list of fields and their available mass edit functions.
|1745||Improvements to the user interface||
Made a number of improvements to the user interface:
|1747||Performance improvements in record conversion||
Made a number of optimizations to improve the performance of record generation via conversion actions.
|1751||Begin a Bomgar support session from Agiloft||A new script allows support representatives to launch a Bomgar session to a Jump Client that has been pinned
from within Agiloft.
To set up this functionality within a Bomgar-enabled KB:
|1753||Table view performance improvements||Table views were redesigned to not use iframes. This has resulted in a faster GUI, lower response times, and reduced in-browser memory usage. This will also improve the loading times of records which contain large numbers of related tables and multi-value linked fields.|
|1756||File field restrictions on attachment file type||
A new configuration script AttachedFileExtensionChecker.jar enables users to control the types of files that can be added to a file field by restricting file extensions. There are three options to configure file type restrictions:
1. In the Admin Notes section of a file field, add a note defining the allowed file extensions, using the following format:
<file_types_allowed>.docx, .jpg, .pdf</file_types_allowed>
This tag can coexist with other note items, and has precedence over the other restriction methods. However, it
would need to be added for each file field individually.
2. Create the following new global variables:
3. Leave the script defaults as they are without configuration. The default settings are:
|1762||Loop detection for API emails||API emails are now given loop protection along with other email types.
|1765||New functions "find" and "matches"||Two functions were added to the Formula Wizard. The find and matches functions can be used in
Variable Formula fields, print templates, mass edit, field default values, and update fields actions.
Find - finds a sub-sequence of the input sequence that matches the pattern and returns true if, and only if, a sub-sequence of the input string matches the specified pattern.
Syntax: find(pattern, text[,flags])
Syntax: matches(pattern, text[,flags])
Flags - Flags string for either function can contain 'i' which enables case-insensitive matching and 'm' which enables multi-line mode.
For example, the expression find("flour", $ingredients, "im") will return 'true' if the sequence 'flour' or Flour' is found, and 'false' if it is not. Case-insensitive matching and multi-line mode are enabled by the optional flags "im".
Note: The find and matches functions accept only strings as arguments. You can force the system to evaluate some non-string data types as strings by adding an empty string with +"". For instance, a link to single fields from other table with multiple values enabled (MVE) is not stored as a string. If the 'find' function is used to look for some value such as 'anonymous' in a multi-value linked field (MLF) called External CCs, the formula might look like the following:
By adding an empty string to the MLF value - using +"" - the MLF value is converted into a string for search purposes.
|1766||Help Redesign and Customization||
The Agiloft help system has been moved to a new, flexible web platform. We've also added the ability to
customize the help menu that appears to users from within a knowledgebase.
By default, all help links from within a KB now open to https://wiki.agiloft.com, and all of the contextual link icons open to their relevant topics in the new site.
The new help is designed to be more attractive and easier to navigate, search and find answers related to
high-level Agiloft functionality, as well as offer administrator and developer content. It will also be up-to-date with
Agiloft's development and the most current release versions.
For more information, see: Using the Wiki.
In addition, the help can be customized for different business environments. Navigate to Setup > System > Customize Help to open the Help Setup screen. The screen offers the following configuration options:
Primary Help Location - defines the location of the online help. By default this is set to https://docs.agiloft.com.
All help links in the system will take the URL base location. For instance, the End User Interface help link will
direct to https://wiki.agiloft.com/display/Help/End+User+Interface.
However, this location can be set to a custom help location, such as MyCompanyWiki.agiloft.com, which could
redirect the same topic to https://MyCompanyWiki.agiloft.com/End+User+Interface, and all references to Agiloft in
the help will be replaced with MyCompany. In addition the look and feel can be somewhat customized including
the company logo in the upper left. This customization requires some additional development work to ensure that
all of the elements appear correctly and that the new company name and the look and feel are correctly reflected
in the help with the new URL. This service is provided to Agiloft resellers only at this time. Please submit a ticket
via the Support Portal if you wish to rebrand your Agiloft help system.
In addition it can be set to the Local Server, which will provide the local help files that are distributed with the
application, and None which will remove the references to help altogether. Note that the local help files are no
longer being updated, so the contents will not reflect the most recent software releases.
Knowledgebase-Specific Documentation - allows you to add a link to any help documentation that relates to your
system. By default this is set to None. Adding a URL and Link Text will create the link in the Help drop-down in
the upper right.
Product Documentation/Support Login/Upgrade Download Page/About Agiloft - allows you to leave the additional
help links or remove them from the Help drop-down in the upper right.
|1770||More languages supported||
Added support for a number of new languages to the Language tab list in the Teams wizard. Each of these new languages also has a corresponding GUI properties file so that the whole interface may be translated and localized:
Please note that interface translations for these languages have not been provided.
|1771||ADFS SAML 2.0 support||
Added support for Active Directory Federation Services (ADFS) 3.0 in Agiloft SAML single sign-on.
To enable Agiloft SAML for ADFS, the current installer includes the jar files local_policy.jar and US_export_policy.jar, whose sizes are 3035 and 3023 respectively for verification purposes. The jar files are located at [Agiloft_Install_Directory]jre/jre/lib/security.
Follow these steps to integrate ADFS 3.0 and Agiloft SAML SSO:
At this point, ADFS is fully configured. In Agiloft, check that the user has been added and the email address has
been correctly set.
|1772||New data type to create Relationship Diagrams||
A new Relationship Diagram field type was added, which allows users to visualize the relationships between
linked records as tree diagrams. The possible uses of the Relationship Diagram field are numerous, as it can
model a large range of scenarios where there are dependencies and linked relationships between organizational
assets, tasks, contracts, and other items.
For instance, a business might support various clients with individual configurations of hardware and software,
and the relationship diagrams could enable them to keep track of these setups and the dependencies that they
require. As another example, software release versioning could include various functionalities and features,
breaking changes, and interdependent components - all of these could be represented in relationship diagrams
for a release version number and maintained in future releases.
The example below illustrates a simple relationship diagram showing assets, also called configuration items:
In this case, the company's Slack/Email/Calendaring system Uses a Slack Company Account, and Requires an
Exchange Server to run. This Exchange Server uses another set of components, which in turn have their own
The diagram is restricted to depicting the selected item's parent and child relationships, with the depth specified in the field wizard, but not siblings. The diagram for related assets looks different depending on which item (record) is selected when the relationship tree opens.
A relationship diagram field was added in the Configuration Items table of our out-of-the-box ITIL KB template.
To open the diagram, click the tree icon.
To set up a relationship diagram field, the following items must be present in the table:
In addition, you must choose how to label the item boxes and arrows in the diagram. When configuring the diagram field, select a field to identify and label the items in the diagram. You can also select a field to label the relationship arrows, or use hard-coded text labels such as 'Parent' and 'Child'.
|1775||Direct File Edit enhancement to edit Office files and save to URL||New options are available for File with Versioning fields that allow users to open MS Office attached field files,
edit them locally, and save them back to the Agiloft field. The following field types currently work with direct
Check back soon for complete documentation in the online help.
|1776||Group Permissions Ownership and Saved Search information||
In the Tables tab of the Group Permissions wizard, located at Setup > Access > Manage Groups > (edit
a group) > Tables tab, the information in the Record Permissions column has been significantly improved.
The Record Permissions column now shows how ownership is defined for the table. This makes it easier for the admin to configure permissions, as they do not need to navigate to the Table setup wizard's Permission tab to view ownership definitions.
In addition, the column now displays the names of any Saved Searches which are applied to the record permissions.
Previously, this column showed only the name of each active permission, for example Edit Own or View Other, for the table.
|1780||System choice list options can't be modified during import||During record import, it is no longer possible to modify system choices by adding new lines to the choice list,
even if the 'Create all missing choice values' option is selected. Users will see the following warning on import:
Problem importing field <Field name>. New choice value <Choice name> can't be added to field <Field name> that uses a <Choice type> system choice.
This enhancement does not interfere with the ability to add choices during import to user-added choice lists.
|1781||Global Variable for default date parsing||A new "Default day/month order for date/time strings" variable in the Global Variables wizard, available at Setup
> System > Manage Global Variables, was added to improve date parsing from inbound emails. The system
will parse date values according to the rules specified in this variable.
The variable options are:
Examples of the parsing results for each setting are shown below:
Date Value Email Content
Jul 20 2016
--Agiloft Parsed Info;
--Agiloft Parsed Info--Dec 11 2016
--Agiloft Parsed Info;
--Agiloft Parsed Info--Jul 01 2016
--Agiloft Parsed Info;
--Agiloft Parsed Info--Nov 12 2016
--Agiloft Parsed Info;
--Agiloft Parsed Info--
Date Value Email Content
Dec 11 2016
--Agiloft Parsed Info; en;--
--Agiloft Parsed Info--Nov 12 2016
--Agiloft Parsed Info; en;--
--Agiloft Parsed Info--Nov 25 2016
--Agiloft Parsed Info; en;--
--Agiloft Parsed Info--
The email field header can also contain the locale, which the Locale variable value will use. For instance:
--Agiloft Parsed Info; en;--
uses system locale
--Agiloft Parsed Info; en_NZ;--
uses New Zealand locale
--Agiloft Parsed Info; en_US;--
uses USA locale
|1788||Linked Field new columns auto-populate during sync||Improved the way that Linked Fields are updated during sync. Now, if a new column is added to the source field,
and contains data in the target, the values in the target will update immediately when the sync happens.
Previously, the new column would be empty even if it contained data in the target KB.
|1790||Ability to update locked records via conversion||
Record conversions can now be done even when the record is locked for editing. This will work when two tables
have a conversion mapping where an identifying field is mapped for conversion and also marked as the 'Primary
field used to display a match'.
As long as the field value matches between the records in the tables, the conversion will update the corresponding records. If a conversion action with these conditions is included in a rule which runs in the background, it will even update locked records in the background. Note that conversion actions should have the 'Silently with no confirmation' option selected.
Conflicts during conversion are resolved automatically, in cases where the same field is updated by the user when locked and also by record conversion. In these cases the value which is set by conversion takes precedence over user changes.
|1791||SAML Name field length increased||
The length of the "Value of either Name / FriendlyName Field of Attribute tag" field in the Service Provider Details tab of the SAML Configuration wizard has been increased from 65 to 255 characters. This will prevent errors saving the SAML configuration in cases where the length of the SAML Attribute Name is longer than 65 characters.
|1795||String search for email files with HTML||String searches now work for .msg and .eml attached files in cases where the files contain HTML code.
Previously, search only worked with plain text for .msg and .eml files.
|1796||Encryption of SAML Request/Responses||RSA 1.5, SHA-1, SHA-256, SHA-512 are now supported as SAML Assertion Encryption algorithms for Single Sign-On support. For more information, see here.|
|1802||Warning message when KB import will delete a KB||
A warning message is now displayed if a user attempts to import a knowledgebase with the same name as an existing knowledgebase on the same server, since this will cause the existing KB to be deleted and overwritten unless the user changes the imported KB name.
|1803||DDL propagation optimization||Optimized the Data Definition Language (DDL) propagation process so that the duration of DDL table lock is
now shorter in cases where the structure of large tables with links to other tables has been modified.
|1808||Workflow editor reworked for cross-browser compatibility||The graphic Workflow editor, which can be accessed on the Workflow tab of the Table wizard, no longer runs on
React to retain all the same features as the previous Workflow editor, and is mostly indistinguishable from the
previous editor, and all existing workflow configurations will be retained on upgrade. Users are no longer required
to download additional plug-ins or prompted to run Java on Chrome, Firefox, and IE browsers.
In addition, the Workflow Override window is now available as separate tab in the Table setup wizard called WF Overrides, which enables workflow override permissions to be set independently from the Workflow editor. Previously, the Workflow Override window opened as a pop-up window when workflow changes were saved. This tab enables you to define which groups can view workflow actions and override them.
The Workflow editor is described here.
|1809||New option 'Update the parent window when conversion is complete'||It is now possible to force a refresh of the parent window when conversion actions are launched from a record.
This option is available when setting up a Conversion action that shows users the interactive dialog or the
|1812||Encrypted KB backups||
In the Admin Console, KB backup files can now be encrypted automatically during the scheduled backup.
In the Admin Console, navigate to Backup > Edit or create new backup > Options tab to see the new Encryption section.
To enable KB backup encryption:
To import the encrypted backup, use EWIMPEX command line with the form: --decrypt [private key path] --file
[backup file name].
Note that decryption will now be impossible without the private key, meaning that if a new pair of keys is
generated, it will be impossible to decrypt backups that were created with the old key.
In addition, the Options tab of the Backup wizard also contains a new option: "After creating backup execute
script". This enables you to add a script for sending new backups to a different location such as an SFTP server.
The script must be placed in the /opt/server/Agiloft/data/admins/scripts directory.
|1813||NTLM version 2 support||Agiloft Single Sign-On now supports NT LAN Manager v2 (NTLMv2). For more information, see here.
|1814||Increased character limit for default file name formula field for Print actions||
In the Print Action wizard, the character limit for default file name formulas in the 'Define the default file name' input box was increased from 99 characters to 512. Previously, the character limit prevented complex file name formulas with long field names or regular expressions.
|1816||DocuSign access reset button added||
A Reset Access action button was added to the DocuSign configuration screen, at Setup > Integration >
DocuSign > Configure.
When the button is clicked, a confirmation dialog opens.
After confirmation, the button removes any connect ID and OAuth tokens from the KB. This is particularly useful
when the admin needs to disable DocuSign in a test copy of a production KB.
The button will only remove DocuSign credentials from the current KB, meaning that if access is removed from a
test KB DocuSign can continue to work in production.
|1817||Enhanced password reset functions||The following enhancements were made to the password reset process:
Users may reset their system password by clicking the password reset link on the login page. On the password retrieval form, the user enters their login or email address, then chooses whether to receive a reset code by email or SMS text message.
Previously, no SMS options were available and users were able to retrieve their original password instead of resetting it. Note that the user's group must have 'Allow Sending Password' set to Yes in the General tab of the Group wizard in order to receive email and text messages to reset passwords.
In addition, the Forgot Password? link has been removed from the default Agiloft GUI2 login screen for improved usability. Customized or KB-specific login pages can still use the Forgot Password? link.
|1821||Modified system login page and added 'Show KB Names' global variable||
Improved the security of the default server-wide Agiloft login page, which is available at https://<serveraddress>/gui2, by removing the drop-down box listing the names of the knowledgebases on that server. If a user wants to login via the gui2 page, they will need to type the KB name manually.
For on-premise or in-house installations of Agiloft, this behavior can be controlled in the Admin Console by a
new 'Security: Show KB Names' global variable. The default variable value is 'No'; selecting 'Yes' will display a
drop-down list of KB names on the server login page at https://<server>/gui2/
|1825||New option to control table border visibility||To maintain upwards compatibility while improving the Look and Feel options, we added an option in the Look
and Feel wizard that determines whether table cell border settings are determined by the user's View or by the
look and feel.
Table Borders Visibility
(x) Use view settings
() Override view settings and turn them (x) Off () On
|1830||Improved record processing in Time-Based rules||
Improved the logic of time-based rules to improve their accuracy, in cases where a time-based rule's start time is delayed due to a previous rule running past the second rule's scheduled start time. This could cause rule failure if the delayed start time caused records to no longer meet the rule's saved search criteria by the time it ran.
Now, the saved search will always run on time so that the list of records found by the rule criteria is ready for the time-based rule to act upon when it comes up in the processing queue.
|1831||Adobe Sign integration||Integrated with Adobe Sign to provide e-signature solutions for contract and document management customers.
An Adobe Sign account can be added to a knowledgebase, which enables sending documents to Adobe Sign
accounts where they can be signed by the account holder and updated automatically in the KB.
Read the full documentation in our wiki.
|1690||Link menu for All Communications table||The full Link menu is now available for the All Communication table. It's possible to link and unlink
communication records using the following menu items:
|1711||IP tracking for 'Login Failed' events||Improved IP tracking for 'Login Failed' type Activity Log entries.
The log now displays the correct originating IP instead of 127.0.0.1, which can enable users to locate the origins of a failed login, for instance after a DDOS attack or a hacker attempt to get into the system.
|1712||Exception on editing groups||Fixed an error which occasionally appeared during periods of heavy server load when the user tried to edit a
group from the Manage Groups screen.
|1717||Error when printing license usage||Fixed an exception which occurred when printing license usage. Now license usage records print correctly.
|1719||Changed action transfer behavior during sync||Changed the logic of action transfer during sync, in cases where both the source and target KBs contain actions
with identical names in the same table, but the actions have different UUIDs.
Previously the sync created duplicate actions in such cases, which made cleanup of the target KB complicated. Now, sync still transfers the duplicate action, appended with the suffix 'created by sync'.
|1720||Blank pages when saving records with NTLM||Resolved an issue where blank screens would appear after clicking the Save or Cancel buttons in a record in
cases where NTLM authorization was used.
|1726||Temp directory cleanup after running OCR actions||Files are now erased from the temp directory after running an OCR action to prevent storing unnecessary files
after the OCR process completes.
|1730||SAML connection issue due to space in KB name||Fixed a SAML connection problem which occurred when a knowledgebase contained a space in its name.
|1731||DocuSign signer role change tracking||DocuSign integration now tracks when a signer role changes in order to enable users to monitor cases when a
signer delegates their responsibility to someone else.
In that case the original signer's role is changed to CC, and the new signer is added to the DocuSign Recipients table.
|1734||SFTP connection issue with special characters||Fixed an SFTP connection problem which occurred when the password contained special characters. Export and
import actions will now be saved and work correctly when the password part of the URL contains special
In addition, an SFTP import problem was resolved where the action would fail if the user did not have permission to change to the root (/) directory.
|1742||Available Icons and Icons in Use display||
Resolved an issue where the icons in the Available (unused) icons and Icons already in use as Table Icons
sections of the Graphics tab in the table wizard were appearing in the wrong places.
|1743||Import timeout now set by global variable||
The Timeout: Record Update Time global variable is now used for Import to set a transaction timeout when importing a record. This will prevent import from failing in cases where a timeout caused by background processes on record creation happens, until the time specified by the record_update_timeout value.
|1744||Error when importing data from zip files||Fixed an error which appeared when attempting to import data from a zip file in cases where the compression
method is not supported. The correct error message now appears.
|1746||Error on data import||Fixed an error which appeared in cases where the user began uploading a file in the Import wizard while an
import of the same file was in progress. The import process has been separated from the Import wizard so when a
new file is uploaded, the import process can still read the original file.
|1748||Improved ESA connection security||
Added the ability to require an authorization key when connecting to an external ESA if the Secure API Calls section in the External Sync screen has been enabled in a sync configuration.
The Secure API Calls section enables you to generate a key that must be used when accessing the ESA API.
|1750||Record History and Table View performance optimizations||
|1752||Date/time indicator for attachments||Fixed a problem with incorrect date/time stamps in attachments which occasionally happened when the server
and knowledgebase time zones were different. Now, the date/time stamp in attached files is the same as the
corresponding History entry, using KB time.
|1754||Error when deleting Teams||
Resolved an error which occurred when deleting Teams when the Team had been selected in a chart/report
schedule in the "Run every <number of> minutes during working hours of <team name> team'. Now the
Team can be deleted, and the schedule in the chart/report will be automatically changed to 'Never'.
We made the following improvements to the sync engine:
Quick Search field selection list included in sync - The Quick Search field selection list, which can be managed
by clicking the Edit Quick Search Fields button in the Indexes tab of the Table wizard, will now be transferred
Added the ability to sync Alt Text and Notification Icons along with other View attributes.
Added the ability to transfer the 'Merge PDF Document' and 'Convert Document Format' actions when syncing.
|1760||Salesforce data transfer||Improved Salesforce sync so that out of memory (OOM) errors do not occur when large numbers of records are
transferred from Salesforce, or when there is a large amount of data in separate Salesforce records.
|1761||Bomgar integration fixes||Fixed the following Bomgar integration issues:
1. If the Bomgar password contained special characters that are used for URLs, the event listener failed.
2. Bomgar Chat summary did not work, due to a change in Bomgar API call behavior.
|1764||Conversion actions on versioned files||Resolved an issue where, when performing conversion actions on files with older versions, the action would not
use the most recent version of the file, resulting in records with empty file fields. The conversion now uses the
most recent file version.
|1769||Google OAuth hyperlinks||Ensured that all keywords used in SAML and Google OAuth hyperlinks are processed in the same way as with
regular hyperlinks. Previously, only the first hyperlink keyword was processed and the remainder were ignored.
|1773||MSSQL errors when modifying records||Resolved errors which appeared occasionally under MSSQL when updating records or clicking action buttons.
This error could occur when saving records after selecting many values in a link to selected fields with multiple
values enabled and was caused by a truncated HTTP request.
|1774||Missing Linked Field settings based on table subtype||Resolved an issue where the visibility and requirement settings of Linked fields could be lost when re-importing a
KB. This could occur when the conditions were based on the 'Type' field, which denotes a subtable; for instance,
if a linked field's visibility in the People table was based on Type=Employee.
Now Linked Field attributes are preserved after a KB export and re-import.
|1778||Dialogs not working in Firefox after update||Resolved an issue caused by a Firefox upgrade which prevented a number of dialog boxes from opening
correctly, including calendar inputs, date/time inputs, and multi-value linked field and choice list lookups.
|1782||Twitter integration update||
Twitter integration, which can be managed by navigating to Setup > Integration > Twitter, has been updated in line with recent Twitter changes so that users can integrate Twitter accounts into a KB, and can receive and reply to tweets within the KB.
For more information, see: Twitter Integration.
|1784||DocuSign envelopes for top-level domains||Made the following DocuSign improvements:
1. Updated the Commons Validator library to version 1.51 which includes new top-level domains, such as NYC.
2. Removed top-level domain (TLD) checks when sending DocuSign envelopes so that envelopes can be sent to top-level domains without issue.
|1785||Error when printing records with a truncated file||Resolved an error which appeared when printing records to a .docx file in cases where an image with a size that
was truncated to zero was attached for inclusion. Now the documents print without errors, and the truncated file is
included as a plain text file name.
|1786||Google Chrome login error||Resolved a "Requested action is in progress already" error message which appeared occasionally when the user
logged into a KB from Google Chrome and pressed Enter instead of the OK button on the login page.
|1789||Error when viewing and editing records||Resolved an error which occurred under various circumstances when viewing and editing records, due to a threading conflict with a race condition.|
|1792||Currency values export format||
Currency field values are no longer converted into scientific notation during export.
|1797||Printing multiple images||Image fields which contain more than one image will now correctly print out in Word 2016 templates that reference an image field variable.|
|1799||Printing HTML content via linked variables||Fixed HTML formatting and display of text inserted into print templates as a linked variable chain, for instance
$person.support_rep, rather than a local variable from the current record such as $support_rep. Now HTML
formatting is kept intact in printed documents when being inserted via a linked variable.
|1800||Outlook MSG Attachment Parsing||
Resolved an issue where emails with .msg attachments which were sent from Outlook were not correctly parsed. Now attachments with a .msg type are correctly parsed.
|1801||Error generating Charts / Reports with action buttons||Resolved an error which appeared when creating a Chart / Report in cases where the report view contained
action buttons. Reports with action buttons in the views are now displayed correctly in the report view. As before,
action buttons can not run actions from a report view.
|1804||Web service failure for multi-paged data retrieval||Fixed a problem with the web services SOAP method EWSearchTableWithQueryPaginated, which previously raised an error or returned an empty result set under some circumstances.|
|1815||Group permission to run saved reports||
Previously it was impossible to give user groups the permission to run their own saved Reports without giving
them access to all Published reports created by other users. The logic and wording of the options have been
modified slightly to resolve this inconsistent behavior.
Under Allow creating/editing/deleting Reports?, the middle option now reads: Allow group to modify/delete/run
saved reports that they created.
Report permissions are found on the Menu Permissions tab of the Table-specific wizard for group permissions.
This is accessed via Setup > Access > Manage Groups > edit a group > Tables tab > Edit a table,
then navigate to the Menu Permissions tab.
|1819||Email templates using localized field names and values||Resolved an issue where, when processing non-English email templates, some fields and choice list items returned in English rather than in the selected language when creating a template in languages other than English. Now, all items are returned in the language selected for the email template when a translation is available.|
|1820||Line breaks in file names created by actions now handled for attached files||
Resolved a problem where attached files would not be displayed as attachments until the user clicked the Attach/Manage button for a file field. This could occur when file names were generated from the name in the print action if the file name had a line break symbol. Line breaks are now properly handled by the action wizard and ignored on file generation, so that the attached file name does not contain line breaks.
|1823||OCR fixes and improvement||
Fixed the following issues related to PDF OCR attachment processing:
|1824||Sending DocuSign files with long filenames||Resolved an error which appeared during a Create & Preview action or when sending DocuSign envelope in
cases where filenames exceeded 100 characters. The system now truncates the filename to 100 symbols and
leaves the extension unchanged so that DocuSign can properly detect the file format.
|1828||Error processing locales in
||Resolved an error recognizing the country local for Brazilian Portuguese, _pt_BR, when creating translated
properties file in the EUI Templates table for use in the end user interface.
|1829||Action Buttons with line breaks in URL||In cases where the URL in an action button contains a line break symbol, which previously caused an error, the
symbol will now be trimmed so that the URL hyperlink works correctly.