DevonWay 2.38 Release
Who is this article for?
Administrators and Users who following Technical Updates
No elevated permissions are required.
For additional information on current releases, please review Navigating the platform release roadmap.
What's New in YourWay 2.38
The DevonWay Community page on LinkedIn has recent webinars discussing this release plus much more.
YourWay 2.38, which moved to Production on May 12, 2017, introduces the following major changes:
- Better ranking of search results.
- Cleaner display of search results in list mode.
- Improvements to the advanced search filtering panel.
- A new-look, easier-to-notice search bar and background.
- Faster performance viewing DevonWay BI charts and reports.
For details on the above and much more, please see the sections below.
Detailed Notes By User Type
For General Users
This section describes fixes and enhancements that affect general user-facing functionality, with the following exceptions: If the ticket applies only to users of the Tabbed Item Display (where the item detail screen appears as a tab on the Dashboard), the ticket is prefaced with (tabbed). If the ticket applies only to users of the Full Screen Item Display (where the item detail screen takes up the whole browser), the ticket is prefaced with (full).
TRAK-2015-5224/TRAK-2017-1078: We made the search bar at the top of the screen better looking, more functional, and more noticeable for users of the new login page.
As you can see in this screenshot, we made several changes to the top search bar and its surroundings. This applies to the new login page only.
The search box itself is larger to draw more attention to the search. It's also wider to give users more space to enter their search term.
Clicking the magnifying glass icon without entering a search term behaves just like clicking the Advanced link that previously appeared to the right of the magnifying glass icon.
We made the search box more functional by adding a feature that automatically runs searches as users enter their search term. The results appear in two sections - above the separator line and below the separator line.
The section above the line includes the top three results, as if you had opened and run a separate search. Clicking on a row in this section opens the item directly, bypassing the need to open the search-results tab and then select the item.
The section below the line includes an entry for each module that contains the search term, sorted by the module with the most results down to the one with the fewest results. Clicking on a row in this section runs a search where the results are limited to the specified module.
TRAK-2016-5504: We now prevent users from attempting to download attachment files that have not yet been saved.
(Released to our hosted Production area on April 3, 2017.)
TRAK-2017-0003: We now correctly treat child-level numeric fields that contain the value 0 as being non-empty.
(Released to our hosted Production area on February 13, 2017.)
TRAK-2017-0210: We made a series of changes to improve performance of viewing DevonWay BI charts and reports.
The extent of improvement depends on the nature of the individual chart or report. (The fewer fields displayed, the more significant the improvement.) Each chart or report should open at least thirty percent faster in view mode. In some cases, the improvement percentage will be much higher.
(Some, but not all, of these changes were released to our hosted Production area on March 15, 2017.)
TRAK-2017-0335: We modified the default search conditions for date and numeric fields.
As a result of user feedback and our own analysis, we now suggest the Is on or after condition by default (instead of Equals) for date fields. For numeric fields, we now suggest the Is between condition by default (instead of Equals).
TRAK-2017-0354: We now ensure that we check the latest role properties when determining the modifiability of non-workflow objects.
TRAK-2017-0513: We removed links to saved searches in system-generated emails for those not using the new login page.
Instead, we modified those links to go straight to the login page. We also added some fine print explaining that users can link directly to the search if they use the new login page.
(Released to our hosted Production area on February 13, 2017.)
TRAK-2017-0651: We no longer show inaccurate pagination controls for custom dashboard nodes.
We don't show pagination controls on dashboard nodes because the set of data displayed is determined by the module developer. Module developers define dashboard nodes by specifying custom SQL statements, or custom DXL that translates into SQL statements.
The fact that pagination controls appeared on dashboard nodes after the 2.37 release was an unintended side effect of another change.
TRAK-2017-0279: We no longer include change request events in workflow task history records that display in BI reports.
What we store in the search engine (and therefore display in BI reports) for each task is the workflow details history record for that task with the most recent "Created on" date, ignoring records with a status of "Skipped."
(Released to our hosted Production area on February 7, 2017.)
TRAK-2017-0604: You can now request multiple, concurrent exports (to PDF or Zip) of separate search-result grids.
You still cannot request concurrent exports from the same search-result grid, or from a separate grid based on the same module with the same fields visible.
TRAK-2017-0902: We made some changes to ensure that the advanced search panel renders in a timely manner.
Before this change, when modules contain multiple reference fields with static (independent of object-specific field values) search criteria defined, the panel was unexpectedly slow to render.
TRAK-2017-1085: We improved the display of search results in list mode.
Most visibly, we made the (blue) title text larger and added more space between results, as shown here:
We also made the text highlighting more accurate, especially in the Search Items popup.
Note that this updated display style appears both on the main search screen and the Search Items popup (when searching for referenced items).
TRAK-2017-1093: We made several improvements to the advanced search filtering panel.
We made several changes to make the advanced search filtering panel more intuitive and more functional.
We changed the 'Filter by' field label to 'Choose a field to filter by' to make its purpose clearer.
We now display the filter condition in a wider field, so users can see the full text of the condition. We also modified the filter condition values to be more natural, more readable. For example, this table shows the changes we made to the conditions that appear for numeric fields:
| Previous Condition | New Condition |
|---|---|
| >< (Between) | Is between |
| > (Greater Than) | Is greater than |
| >= (Greater or Equal To) | Is greater than or equal to |
| < (Less Than) | Is less than |
| <= (Less or Equal To) | Is less than or equal to |
| = (Equals) | Equals |
| != (Not Equals) | Does not equal |
| Empty | Is empty |
| Not Empty | Is not empty |
We made similar changes to the conditions associated with the other field types.
For picklist fields or reference fields displayed as picklists or radio groups, we now display the available values directly underneath the fields, as shown above in the Severity field. You can quickly modify your search results by selecting or de-selecting values, without having to open any popups.
For reference fields (like Primary Related CR shown above), we now open the Search Items popup as soon as you select the field from the 'Choose a field to filter by' list.
You can now collapse fields to make the panel easier to read. When you reopen saved searches, we hide fields that are not filtered to keep the panel cleaner.
TRAK-2017-1108: We now support all available filter conditions when searching datasets in list mode.
TRAK-2017-1151: Made several improvements to search result ranking.
We modified standard searches to prioritize results that contain the search term in key identifying fields. With this change, users are more likely to find what they're looking for at the top of the list of search results.
(Released to our hosted Production area on April 3, 2017.)
After April 3, we made a similar change to reference-field searches (in the Search Items popup) for TRAK-2017-1584.
TRAK-2017-1543: We changed the 'Expand by...' field label to 'Create a separate row for each...' to clarify its purpose.
TRAK-2017-1783: We modified the label, hover help, and dropdown options associated with the Attachments filter on the search panel to make its purpose clearer.
For Administrators, Interface Developers, Report Builders, and Data Analysts
This section describes fixes and enhancements to functionality affecting power users, such as administrators, interface developers, data analysts, and report builders.
TRAK-2017-0529: We repaired a corner case to ensure that RESTConnect correctly manages cached reference values.
(Released to our hosted Production area on February 7, 2017.)
TRAK-2017-0552/TRAK-2017-0816: We made several enhancements related to managing datasets.
You can now define SQL to count the number of objects that should be in your dataset. We run that SQL periodically, according to an interval you specify, and report any discrepancies between that count and the actual count.
We now track the number of failed feeds and if you exceed a pre-defined maximum, we'll make the dataset un-feedable. The maximum defaults to 3, but you can change that value on the Datasets screen.
We now track and display the 'Last Rebuild' date/time on the Datasets screen.
We added Searchable and Feedable checkboxes to the Datasets screen. Checking Searchable makes the search available for search, and checking Feedable tells us to update the dataset whenever contained data changes.
We also changed the dataset feed process to automatically flag unfeedable datasets, so they won't back up our Solr jobs. If a failure caused a dataset to become unfeedable, we show the error on the Datasets screen as well.
TRAK-2017-0639: We changed visibility rules for 'SSO Windows Domain\User' field on the Users admin screen.
Whereas 'SSO Windows Domain\User' was previously visible anytime 'Use new login page' was unchecked (on the Preferences screen), it is now visible if the subscriber is setup with IWA (Integrated Windows Authentication) as their SingleSignOn method. (Released to our hosted Production area on February 16, 2017.)
TRAK-2017-0814: We repaired a browser-specific error on reports using date fields for drill down in Internet Explorer.
(Released to our hosted Production area on March 15, 2017.)
TRAK-2017-0838: We modified dataset-update processing to correctly remove records from the search index in specific cases involving multiple child rows.
(Released to our hosted Production area on March 15, 2017.)
TRAK-2017-0906: We added safeguards to prevent the unlikely possibility of processing the same model object twice in the same batch run.
(Released to our hosted Production area on April 3, 2017.)
TRAK-2017-1086: We added safeguards to avoid rare cases where DevonWay BI reporting threads collide.
TRAK-2017-1135: We fixed some inconsistent behavior when saving Common Fields (on the Cross-Module Function screen).
(Released to our hosted Production area on April 3, 2017.)
TRAK-2017-1392: We now enforce that users with inactive or disabled accounts cannot login using Single SignOn (SSO).
TRAK-2017-1759: We now allow deletion of multiple records from the search index with the same ObjectId.
There are rare (but legitimate) cases where the search index contains multiple records that share the same ObjectId (if the module code changes, for example). In those cases, we should still allow deletions by ObjectId.
For Module Developers
This section describes fixes and enhancements to functionality affecting module developers, i.e. users of the YourWay IDE.
TRAK-2016-5864: We now respect the "Automatically brings back eligible items" checkbox when users click the gear icon on Autocomplete- and Picklist-style reference fields.
(Released to our hosted Production area on February 7, 2017.)
TRAK-2016-5877: In Module Builder, we now display the module code in bold and red text for old-world modules.
TRAK-2017-0089: We now ensure that we check both sides of two-way, cross-module reference validations.
(Released to our hosted Production area on January 26, 2017.)
TRAK-2017-0130: In order to avoid unexpected delays, we no longer check for existing values when module developers add new fields.
TRAK-2017-0131: We no longer attempt to generate subscriber views in the DEPOT (and EXTERNAL) databases for tables that do not exist in those databases.
TRAK-2017-0320: Module Builder now correctly save changes to the "Require that attachments convert to PDF" checkbox.
(Released to our hosted Production area on February 13, 2017.)
TRAK-2017-0404: We cleaned up some issues with importing and exporting groups of modules.
(Released to our hosted Production area on February 7, 2017.)
TRAK-2017-0410: We fixed the way we determine view names on imported modules to avoid issues if those names were modified in the source module.
(Released to our hosted Production area on April 3, 2017.)
TRAK-2017-0608: We enhanced the Module Tools screen to make it easier for administrators to delete data, particularly from the search index.
You can now search directly against the search index from the Module Tools screen and delete any search index data that matches the query you found (in a similar manner to how it worked from the old Define Module screen).
As a result, there is no longer a checkbox to specifically delete search index data on the Module Tools screen's Delete tab, but we will still delete that data when you delete an object.
Finally, we previously restricted you to only selecting one of Module, Category or Reporting Authority when deleting modules or object data, but you can now combine those options to further narrow your selection.
TRAK-2017-0924: You can now use DXL to create dynamic, custom button labels.
In the Button Behaviors popup, accessible from Module Builder, you can now specify DXL in the Label column (on rows where Behavior = "Label").
TRAK-2017-1649: We modified the SearchDelete() DXL function to delete records from the search index synchronously.
Previously, SearchDelete() would add items to the queue to be processed asynchronously.
Other
This section describes fixes and enhancements to our backend architecture. Tickets in this section primarily affect DevonWay personnel, such as our Operations group, or environment management personnel at our on-site customers.
TRAK-2017-0318: We no longer attempt to feed attachments with .sql file extensions to the search index.
(Released to our hosted Production area on January 26, 2017.)
TRAK-2017-1082: We made changes to ensure the accuracy of a person's LastLoginDateTime.
TRAK-2017-1386: You can now optionally require one or more lowercase or uppercase characters in system passwords.
TRAK-2017-1423: We now avoid the possibility of concurrency errors that can occur after updating a single record multiple times within the same second.