|21635||Add support for a hotlink that will take the user to a particular FAQ||Support has been added for a hotlink that both logs a user into the FAQ interface and opens a particular FAQ for viewing.|
|21584||Add full text indexing for MS Word 2007 / 2010+ (*.docx) format files||The system now creates full text indexes for MS Word .docx files as well as .doc, .rtf, .pdf, .htm, .txt and other formats.|
|21060||Fixed Linked Field propagation on deletion for fields that allow non-source values||Previously, if a Contact record was used as source data for a field that was configured with "Allow non-source value=Yes" and that Contact was deleted, the data values in the linked fields were set to NULL. Now the data values are retained and and they are simply unlinked from the record that is being deleted.|
|21023||Add support for explicit searching of multi-value linked fields.||Previously it was possible to search for whether a multi-value linked field contained a particular value, but it was not possible
to search for records that only contain that value.
For example, if the Members field in a record contained entries for Frank, Joe and Sue a search for Members Contains "Frank" would find it. It was not possible to search for records where the field included Frank, but not Joe or Sue.
Now it is possible to search for records that only contain a specific value.
The old "Contains" operator has been renamed to "Contains string" and functions as before.
A new "Contains Item" operator has been added that only returns records that provide an exact match.
|20952||Improved the look of empty related tables||Column headings no longer appear in related tables that are empty of records. Now only the action bar appears. This reduces the amount of space taken by the table and looks better.|
|20895||It is now possible to leaving email on the server for more than 24 days||Previously it was only possible to "Leave email on the server for" for up to 24 days. It is now possible to eave it there for longer periods.|
|20885||Required records are created and additional information provided during conversion||If a linked field is mapped for conversion, but a matching record cannot be found, the system now creates the necessary record and provides the following information: New record <ID> was created because the mapped values for <some> linked fields: <Linked fields> did not match an existing record.|
|20683||Smart population of linked fields using partial field values||Added a feature that allows you to automatically fill linked fields without needing to enter the entire field value. If your search
term finds only one match, the system will automatically select it and fill corresponding fields.
For example, if you type Sarah into the search box while filling out a Linked Field and Sarah Connor is the only record beginning with Sarah, the system will use her record automatically without needing to go through the entire search process.
|20543||Added asynchronous rules option||Added a new option under the rules tab for running record-based rules in the background to improve interactive response
times and allow looping.
If "When a Document is created/edited/deleted." is selected, then another option becomes active below it:
"Run in background"
This rule will run asynchronously and non-interactively.
Note: Validation action cannot be run asynchronously because the rule may execute after the record has been saved. The 'Priority' setting has no effect for asynchronous rules because they run independently and in parallel to one another.
It is recommended that you do not mix interactive and non-interactive rules when trying to edit the same record, as they may conflict with each other.
|20505||Added an 'Add Comment' feature for If-Then-Else Actions||It is now possible to add comments to any conditions and actions within an If-Then-Else action.|
|20275||Changes to the logic for 'From' fields and email maintenance||For outbound emails, enhanced logic will be applied to populating these fields based on whether the email is manually sent or
automatically generated by the system.
If the email is manually sent, the person who creates the email will be put into the 'From Login' and 'From Company' fields.
If the email is system sent, the from address determines the 'From Login' and 'From Company' fields. The system then looks for a user with that email address and, if it can find one, uses that user to populate the 'From Login' and 'From Company' fields. If it finds more than one user with that address, it uses the first user it finds. If it finds no user, it leaves the two fields blank.
Processing of personal inbound emails still populates the 'From Login' and 'From Company' fields using the original from address of the email.
When the 'From Login' field is set as the ownership field, no changes to permissions are necessary other than the changes to the search filters that are used for permissions to remove the creator login.
The 'Creator Login' field is still populated by the person whose session causes the email to be generated.
|20254||Optimized the email sending process||Improved the speed of mass emailing. Optimized the communication records creation process so that mass emails are generated approximately seven times faster.|
|20108||Added a new type of summary report||Added the ability for customers to combine multiple data summaries from the system into a single report. For instance, a
report could show both the number of tickets created last month and the number of tickets open longer than 3 months.
It's also possible to show data from multiple tables on the same report, such as showing the number of leads created last month, the number of campaigns run last month and the number of deals resulting from leads last month all together in a single report.
The HTML editor can lay out and create the report and populate it with new variables that identify the summary calculated data resulting from specific saved searches. Formula wizard makes it easy to insert the kinds of calculations that we offer in the “Calculation on Multiple Linked Records” data type.
On the 'New Variable' tab, users can create a new variable that will display summary characteristics for the whole data set or the results of a saved search.
Empty values may be set to read either as zeroes or as SQL nulls.
Naturally, permissions for custom summary reports behave just as they do for normal reports, the person running the report will see statistics for only the subset of records to which he has view permission.
|20006||Fixed a Saved Search problem in IE8||Work around for a bug in IE8 that caused users to see an empty Saved Search page after editing a Saved Search that was being used to restrict table-level permissions for a group.|
|19793||Added the ability to hide the table label from end users||For sales automation it becomes important NOT to show the table heading when people are registering as leads
This is addressed by a new option in the table wizard that can hide table labels from end users.
The option is available through the table wizard General tab:
Omit the table label from members of the following groups when they view the table or create or edit records in it.
<multiselect list of groups>
This option allows an admin to hide table labels, such as leads, while still showing the label for support cases and other tables.
|19721||Security Improvements: Redirection URLs control, user enumeration prevention||Introduced a new KB specific global variable: Allowable_Redirection_Hosts.
This parameter increases security by preventing redirection based phishing attacks.
If this variable is not set, or is empty, then command line parameters such as ExitURL may specify redirection to any host.
If it is set, the system will only allow redirection to URLs at one of the specified hosts. Multiple hosts may be specified, delimited by spaces, comma or semi-colons.
If an invalid host is specified, the system will behave as if no parameter were supplied and, on logout, will redirect the user to a default URL such as that specified by the ExitURL global variable.
Introduced a new KB specific global variable: "informative_password_messages".
If this variable exists and is set to YES, a message is shown on the forgotten password process:
"A new password will be generated and emailed if a user with the specified [login | email address] exists, unless that user is a member of a group that is not allowed to receive passwords via email"
Otherwise, no real login names would be given in the information message in order to prevent an attacker from determining valid user accounts based on the error messages returned during the forgotten password process. This information could be used to find usernames that would be useful targets in a brute force password guessing or a denial of service attack.
|19120||Added ordering for items in the My Items menu of EUI||The order of menu items under My Items is now defined by the explicit tab layout order set in Setup/Look & Feel/Edit Tab
The sub-tables within one head sub-type (i.e. Employees and End Users under Contacts) are ordered by the alphabetical order of the labels.
|18999||Added the ability to right align fields in views and reports||Added the ability to right align any field in the view. Added a special column to the 'Field' tab of the View wizard next to the
columns for Column Width/Edit/View called "Right Align". Any fields that are checked in this column will be aligned to the right
instead of the left.
Print formats, html reports, embedded tables and anywhere else the view is used base their alignment on the checkbox setting for that view.
|18928||Added support for a global variable to limit the number of History entries for a single record||Mis-configured time-based rules could create a huge number of unwanted History entries that made the record cumbersome
Added support for a new admin console global variable, "MAX_HISTORY_ENTRIES_PER_RECORD", with a default value of 500.
If more than the specified number of changes are made to a record, then any additional changes do not create History records. The update is still valid, but is not reflected in History.
|18927||Added ability to delete History records||Added support for eliminating old history records. Delete Action wizard has been reworked, and a new option has been
added to Mass Edit.
When "Add Delete Action" is selected, it brings up a wizard that shows two rows:
[ ] Delete the record itself
Use this option to delete the record itself
[ ] Delete History entries
[ ] All but the most recent  history entries per record
[x] Do not delete the first history entry for record creation
[ ] All history entries created by rule <list of rule names>
[ ] All history entries more than [ ] <days/weeks/months/years old>
[x] Do not delete the first history entry for record creation
Use this option to delete any history entries. It is not necessary to select these options if the record itself is being deleted because any history entries are automatically removed when their parent record.
A clean up of History entries may also be implemented on a per-record basis, using the Action Button with the Delete Action with the 'Delete History records' option selected.
Added support for the above to the Mass Edit wizard so that the user can clean up old history entries manually.
|18922||Widget-Based End-User Interface||In the new release we provide an easy-configurable, flexible, attractive and user-friendly end-user interface, which is based
If you want to switch a team's EUI to the new EUI, just edit the default 'Look and Feel' scheme for this team or create a new one. Then change the first tab, EUI Version, from 'Horizontal Toolbar' to 'Widget-Based Home Page'. Team members will see default Home Page instead of horizontal toolbar upon login.
All main types of widgets are available for the EUI home page: Table widgets, Chart, Hotlinks, Launch Chart, Show FAQ, Google gadgets etc. Users' access to widgets, hotlinks, tables, Saved Searches and other elements is handled according to the general group permissions for particular tables and fields.
|18828||Added ability to execute an action if zero matching records are found||Extended the possibilities for rules of the type "When some summary condition based on multiple Support Cases has/hasn’t
been met." Now a rule may be executed if zero matching records are found.
Changes on the 'Condition' tab of the Rules wizard:
(x) Execute Actions once if the search is met
( ) Execute Actions once for each record found by search
Now it can specify zero records for the 'Number' row on the 'Condition' tab.
|18709||Chaned 'Inbox' title in left pane||Changed left pane 'Inbox' title to 'My Assigned', which is clearer for users.|
|18617||Improved elapsed time fields||Changed the behavior of elapsed time fields so that any entry in any field would fulfill the requirement for a non-default value.
Previously, if a user had a required elapsed time field showing hours and minutes box, they could not only put minutes into the minutes box. They would receive a message demanding that they enter something into the hours box as well.
|18419||Added a New NLS Wizard||Completely reworked the Localization wizard in order to simplify the localization process.
The default property value is now visible in comments in different languages.
Improved and fixed several issues of the process of uploading a localization file.
Introduced a new engine for determining untranslated properties.
|18374||Added #ew_languages_all for EUI2 macro||Introduced a new macro #ew_languages_all, which shows all available languages. This macro has the same parameters as the #ew_languages macro, which shows only the languages available to the current user.|
|18253||Added Single Sign-On (SSO) Service for Google Apps||Added a SSO service, which allows end users to securely sign into the EnterpriseWizard Knowledgebase using their Google
Apps user account.
To activate this feature:
1) Enable the 'Google SSO' under Staff interface/Setup/Access/Enable Google SSO
2) The EnterpriseWizard user login must be the same as their Google login. For example, if user has the email address firstname.lastname@example.org, then his EnterpriseWizard login KB must be 'user12345'
Users can login via the hotlink:
The first attempt to login via Google SSO hotlink will redirect the user to a Federated Login page for the Google Apps account. The user can then sign into their Google Apps account. Google Apps then displays a confirmation page and asks the user to confirm or reject a set of authentication requests from the EnterpriseWizard application. If the user approves the authentication, then Google will return the user to the Knowledgebase.
|18176||Added Russian and Chinese language support for localized installers||Added downloads for localized EnterpriseWizard installers for Russian and Chinese speakers. Downloads include localized installers, localized demos and ITIL Knowledgebases, localized EnterpriseWizard User Interfaces and localized EnterpriseWizard Help.|
|18120||Added visibile runtime search criteria to Runtime Charts||Added visible runtime search criteria to Runtime Charts. All runtime filters are now displayed just below the Title and
Description on the Chart and on the Report. For example: Employee Name=John Smith, or if there are two runtime filters
Company Name=IBM and Date Created < 31 mar 2010
Only runtime filters are automatically displayed below the Title and Description. Other criteria, can be included in the title.
|18025||Added a new permission to the File and Image fields||Added a new permission: Allow group to delete files and add new files when editing <records>
The permission is at the bottom of the normal permissions on the permissions tab, similar to the special permissions for Append-Only Text.
This permission controls which groups see the garbage bin icon after clicking on the Attach/Manage button in the ticket edit form.
If a user deletes a file while versioning is on, then the file is removed from the list of current versions but is not removed entirely from system. It is retrievable from the History or the View Version History button.
|17994||Added ability to find and eliminate duplicates||Added a new 'Duplicate Filter' filter type to the search wizard. This filter allows the user to obtain a list of records that can be
selected and deleted to remove duplicates.
Also added a heading above the existing buttons that reads:
And then the button labels are changed to:
Simple, Time, Calendar, Advanced, Duplicate, First/Last, Run-Time, Related Table (removed the word Add and the word Filter from each one to save space).
When someone clicks on the Duplicate filter button, they will see the following:
Match on fields "<multiselect list of fields>". Only report if  or more matches. Exclude first  records  Exclude NULLs <Help>
A search for 2 or more matches that excludes the first record will provide a list of duplicate records that may be deleted, leaving only non-duplicates. The determination of which record is "first" is based on the Sort criteria.
The effect of 'Exclude NULLs' is that records that have a NULL value or empty string in any of the fields that are being searched for duplicates will not be included in the search results.
When someone clicks on the First/Last filter, they will see the following:
Match on fields "<multiselect list of fields>". Report first [ 1 ] matches<Help>
This search finds a set of records with a unique combination of values for the specified fields if the number of matches is set to 1. The determination of which record is "first" is based on the Sort criteria.
When this kind of criterion is combined with other criteria, the other criteria is used first to reduce to a filtered set, and then the duplicate filter is applied to remove non-duplicate values from the found set.
Matching results are returned to the user, sorted as per the search setting.
|17728||Validation messages appear in popups||Set validation messages from validation actions, such as requests to fill required fields, to appear in popups in order to ensure that they are visible.|
|17293||Added Attachment Functionality that supports versioning||Added support for versioning the fields of the attachment type. This allows users to retrieve any previous state of any field
of attachment type. In accordance with common customer request, users may also add new attachments even when unable
to delete or modify existing ones, as this is a common customer request.
Added fields for the File and Image types to the new sections to the table wizard and Options tab
( ) Yes
[ ] Show version numbers
Specifies whether the system should track changes for this field.
(x) No check-in/checkout restrictions
() Check-in/checkout implemented, with just warnings for concurrent edits
() Check-in/checkout implemented and fully enforced.
Separated the ability to add new files from the ability to delete files.
Added a new permission at the bottom of the Permissions tab: "Delete any file in the field: " This permission controls which groups will see the garbage bin icon when they click on Attach/Manage button in ticket edit form.
If a file is trashed and versioning is on, the file is removed from the list of current versions but is not removed entirely from system. It is retrievable from the History or View Version History buttons.
If versioning is on, then users can be set to have the right to view and update documents while being able to see earlier versions or they can be set to only have the right to view the latest version of any uploaded documents. A new permission is introduced that can control who can view earlier versions: "Allow group to view previous versions of attached items". Groups without this permission only see the current versions of all files.
Changed Attach/Manage window to implement the control buttons for the following operations:
When the user clicks on the Delete file icon, the system presents a file deletion dialog, which asks the user to select a file version for removal. The user may delete either the latest version of the attachment or entirely remove all versions.
Users who have the permission to view the earlier versions can see a Plus Icon besides the file link in the record form. Clicking the Plus icon besides a file brings up the previous versions. The user may click on a previous version to see it.
The following information is in the File History module:
Time stamp (The date and time of the corresponding modification)
Type of the change (Updated/Created)
Name of the user who made this change
When a user clicks on the Update icon, the system first checks whether the file is in a checked out state. If so, then the system checks whether the user who checked the file out is the same as the current user. If the user is the same, then the system proceeds; otherwise, it checks whether the current user belongs to the group that is allowed to do forced update. If so, then the system proceeds. Otherwise, it presents an error message and does not move forward. Finally, if the system decides that the update is possible, then it presents a file choose dialog for the file to upload, performs an upload and creates a new version.
Clicking on a file hyperlink presents the current user with a file open/save dialog and allows them to download either the current version or any of the previous versions without checking them out.
Added a 'particular field' option for versioned docx files. If this option is enabled, changes to these files may be displayed in the particular chosen field. To enable this option for the file field with versioning, select Yes for 'Display changes to .docx files' in the Options tab of the table wizard. You will be asked to create an additional field of type 'Append-Only' with the HTML option selected. The field label can be anything, but the field name must be <versioned attach field name>_changes.
|16015||Improved user field selection in Email Wizard||Changed the user lookup principle to make user selection easier.
Previously the lookup searched All Fields and the option was greyed out. As a result, if the user tried to find user 'admin', it found all users the admin had ever updated.
It now searches just the login by default and returns the expected result instead of the list of users. If a user wants to search for an email address or a full name, it is now enough to switch the Linked Field search option from 'This field' to 'All text fields'.
|15446||Unifying Communications||Added a Unifying Communications feature that allows user to work with emails in a well known Outlook style. A user sees all
emails that were sent by him in the Sent folder. Inbox folder contains all emails that were sent to the user and received by EW.
In addition to unifying email communications, this new interface also permits the user to see all other kinds of communications, such as calls, faxes, and chats.
All Communications are linked to a user contact record field, such as a user email address, user telephone number. The system will store this as a “user address”. If the address is used by more than one user, all users with that user address will share the same Sent and Inbox folders. This will function like a shared email account in Outlook.
Added a new left pane toolbar tab, 'Comunications', above the Tables tab, called Communications.
The Communications Tab shows any saved searches that are defined to be shown on the left pane. There are two default saved searches that are accessible, active, and visible in the left pane for all groups. Users can search, manage searches, and add searches to their left pane in the same way that they would if they were accessing the table directly.
We also created saved searches for each subtype, which are accessible, but not active, for all groups:
Faxes – Type=Fax
My Notes – Type=Note and Creator Login = $global my login
Calls Received– Type=Voice Call and To contains $global-my-login
Calls Made – Type = Voice call and From contains $global-my-login
Within the Communications tab on the left pane, there is a general filter in addition to the normal table permissions filter. The general filter affects what users will be able to see, even when they click 'Show all from a saved search run' in the table view within the Communications tab. This filter is defined in a new group permission option in the general tab of the group permission wizard.
Added a new user preference to Home/Preferences to define what to show when the user clicks the Communications tab. By default, this preference is set to show the results of the search: Email Inbox.
The table toolbar contains a few additional menu buttons, including 'Send an email', 'Reply', 'Reply to all' and 'Forward'. By default, the sent email is not associated with a data ticket, but rather with sender and receiver contacts. It also includes the ability to reply to, reply to all or forward a selected email.
When viewing communications in this interface, users who are senders or receivers of these emails may see communications that were sent from other tables, such as a support case, a change request, users, and so on. Users can reply to or forward such emails in this interface. The subject line ID encryption will be maintained so that the reply will be linked to the same record as the email that it replies to.
Top Communication table has the following subtypes:
When users upgrade to the new unified communications setup, a new data type called Communications Search Result is created. The field wizard for this new data type is the same as the field wizard for Embedded Search Result. It allows the user to create matching filters on any field in the communications table and the fields in the current table, and it will therefore be able to show any communication, whether or not it is linked to the current record.
The found records are not linked, but they are displayed in an embedded table that has the addition of the sending/reply/forward/view options.
Emails may be sent in several different ways.
1) By selecting one or more records in a table and clicking the email icon above the table view.
2) By editing a record, navigating to the Communications Search Result field, and clicking the Send email button, or selecting a communication and clicking the Reply or Reply All, or Forward button.
3) By clicking the Communications left pane tab and then clicking the Send Email button on the table view
4) By editing a record that causes an automatic email to be triggered by a rule or workflow action.
|14080||Personal Email Inbounds||Added a Personal Inbounds feature that makes EnterpriseWizard a centralized information store and allows reps to share
information with each other.
"Inbound Email Accounts" is renamed to "Inbound Email Ticket Accounts". This is to emphasize that current email inbounds create and update tickets, not just store emails.
In addition, under "Inbound Email Ticket Accounts" section, a new section, "Inbound Email Personal Account" is added.
When an admin clicks "Configure Personal Email Inbound", he is taken to a wizard similar to the New/Edit Email Ticket Inbound.
In addition to the standard settings (server, account etc) the user defines the tables to search and their order. This includes Email fields and Saved Search options. On the Access tab, the user defines what will happen if the sender is not recognized.
When an email comes through Personal Inbound, the system searches for the relevant record as described in the wizard.
The algorithm functions as follows:
1. Identify the sender
2. If unable to do so, discard an email.
3. Try to find the relevant record to attach using the exact "From" address
4. If unable to do so, try the other identified sender addresses.
5. If unable to do so, use the sender contact as the relevant record
6. Create a communication record.
The sales rep may want to store many emails while sharing only some of them. It is therefore possible to control access rights. There is an easy way to "publish" (or "un-publish") an email to a team or to everyone.
|13861||Optimized staff home page layout||Made the following changes to the staff home page layout:
1) The default value of the number of rows has been changed to 2, since that looks best on most monitors.
2) Space has been based on the number of rows with actual widgets. When laying out the page, empty space will not be added for rows with no widgets.
3) The sizing method for charts and other widgets has been changed. Scrolling is now used instead of truncating. This allows the widgets to look good at any resolution.
|13327||Added MS Outlook Integration||Added the ability to send mails, contacts and other information from local MS Outlook applications to the appropriate
To enable this feature, begin by configuring the inbound addresses. Then, go to the 'preferences' press 'MS Outlook Plugin download'. Install the downloaded plugin for any of the configured addresses.
An additional button will appeared in the local MS Outlook application. Now, users may send contacts and emails, both new or existing, to the corresponding EnterpriseWizard inbound account in one click.
|12759||Added fine-grained control of embedded table printing in print formats||Added new options for controlling table formatting in Word printouts. See the updated documentation files for details.|
|7822||Added support for SSL for connection to SMTP hosts||Added support for TLS (SSL). This allows for connection to mail servers which require connection via TLS (SSL) while sending email, including Google.|
|4502||Added support for local numeric and currency formats||Added an option to each of the numeric datatypes - percentage, integer, floating, currency, elapsed time fields in decimal
value, calculation on related data fields, and billion fields - allowing users to define how the numeric data is displayed.
The option appears on the display tab of the Field wizard. Users may choose a locale from a drop-down list. Each field requiring configuration will have a separate drop-down list.
Customers are now able to configure in which language style numbers in these fields will be displayed.
|21831||Resolved a problem with the display of formula values in the action wizard||Previously the filled formula value of an update action was not visible on the next action edit.|
|21496||Problem fixed with deleting teams that contain users||Previously it was not possible to delete a team if that team contained users, now the Integrity Manager provides all the appropriate notifications and allows the deletion to go forward.|
|21198||Allow teams to be selected for dashboard email distribution||Previously it was only possible to select individuals for the email distribution of dashboards, now teams may also be selected.|
|21098||Add support for setting the default display to be All My Assigned Records||It is now possible to set the default table that is displayed on login to be "My Assigned Records/All My Assigned Records".|
|20971||Fixed problems in generating
||Fixed a bug that sometimes caused duplicate processing of related tables that were wrapped into a word table.
Fixed the alignment of related tables in docx templates.
The currency symbol and the first number now print correctly.
Fixed an error where blank values in table templates printed as null. Fields in a related table template with no value are now printed blank.
|20961||Google Apps / Docs integration||EnterpriseWizard now supports Google Single Sign-On
If your EnterpriseWizard login matches your Google account name, you can now login automatically.
It is now possible to create and edit Google documents from within EnterpriseWizard and attach them to a record.
|20907||Fixed multi-value linked fields export in scheduled exports||Fixed a bug in the scheduled export functionality that omitted some multi-value linked fields from the resulting file.|
|20858||Non-latin characters in license requests||Fixed a bug that replaced non-latin characters with '?' symbols in license requests.|
|20544||Fixed staff users' ability to send Charts/Reports through email||Fixed a bug in Charts/Reports emailing. Staff users may now send Charts and Reports using the email icon, as long as they have the corresponding group permissions.|
|20527||Fixed scheduled export of localized tables||Scheduled exports did not show column headers, when the localized label was empty. The default column label is now used as the header in such cases.|
|20485||Fixed the ordering of non-English alphabetical listings||Fixed a bug in the sorting of some non-English alphabetical listings for the drop down lists that showed possible values of related records.|
|20410||Fixed field label wrapping||Fixed a bug which caused very long field labels to wrap differently from the settings specified on the Layout tab. They now wrap strictly according to the 'Layout' setting.|
|20335||Performance improvements||Made several code changes in order to avoid cases where process ewjbossjava.exe would hog CPU resources.
Fixed the memory usage and increased the speed of the export to xlsx format.
Improved the variable resolving engine, which speeds up reports and searches.
|19925||Fixed 'Import/Search Again' button||Corrected the behavior of the 'Import/Search Again' button in the Linked Field search window. It now properly appends the selected value/values onto the existing ones, and then reopens the Linked Field search window.|
|19923||Fixed a hole in staff vs end-user licensing||Fixed a bug which end-users to continue acting as staff users if the general role of a group was changed from Staff to Customer without any making explicit changes to their access permissions.|
|19884||Added last visited home page redirection on login||Improved home page redirection control.
The default home page for user's team is shown the first time they login.
If they change to a different home page, that is now set as the default page on their next login.
|18616||Fixed population of linked fields through email parsing||Fixed a bug which would cause only specifically named fields of a linked set to be populated when it was updated by an email. Now all the fields in the linked fields set are updated.|
|18371||Fixed Parent Team import issue||Importing teams from a file now correctly populates linked Parent Team values.|
|18027||Improved table views behavior with saved searches||Fixed a bug which would cause table view changes after a record edit if a saved search was used for records selection.|
|17908||Fixed errors with external database links||Fixed a bug which made it impossible to change a source table from another database for previously saved linked fields.
Solved problems with external links using MSSQL as a source.
|17409||Fixed Action buttons functionality in End User Interface||Previously Action buttons were only executable from the Table view in the staff interface, now they are also active from tables within the End user Interface.|