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

YourWay 2.37 introduces the following major changes:

• New and improved display of object attachments, with thumbnail-sized images.
• More intuitive advanced search range queries.
• DevonWay Feedback, a forum for sharing ideas to improve DevonWay software.
• The ability for users to automatically aggregate child-level number fields when building ad hoc reports.
• Cleaner, nicer-looking system-generated emails.
• Improved mobile user interface, particularly for ObservationWay.

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-2013-1593: We improved performance of the Change Requests and Assists views by displaying no more than one page of items at a time.

You can easily navigate between pages when there are more than 25 items.

TRAK-2013-2372: We made advanced search range queries more intuitive and added several new filter conditions.

To make searching across a range of values more intuitive, we introduced several new conditions for date and numeric fields. The new conditions for date fields are:

• > (After)
• >= (On or After)
• < (Before)
• <= (On or Before)
• >< (Between)

And the new conditions for numeric fields are:

• > (Greater than)
• >= (Greater than or Equal to)
• < (Less than)
• <= (Less than or Equal to)
• >< (Between)

When >< (Between) is selected for either field type, you have two fields available in which to enter your range criteria. When = (Equals), != (Not Equals), or any of these new conditions other than >< (Between) is selected, you have one field available to enter your filter criteria. (Previously, you could enter a range of values for = (Equals) and != (Not Equals) conditions.)

For all other conditions, like Empty, Not Empty, Today, Tomorrow, et cetera, where the condition requires no additional context, you have no fields available in which to enter criteria.

We automatically convert existing (saved) searches that contain two range filter values to use the new >< (Between) condition.

TRAK-2015-1122: You can now share tiles that display chart thumbnail images.

Please be aware that all users with access to a shared tile see the same thumbnail image, regardless of their reporting-authority access.

What this means is that it is possible, albeit uncommon, for users to see thumbnail images that represent data to which they don't have access. Before sharing, please consider if a chart is appropriate to be seen by those with whom you are sharing.

Keep in mind that clicking a thumbnail image opens a full-size version of the chart that accurately represents the data to which the user has access.

TRAK-2015-1589: In DevonWay BI reports, concatenated child-level text values are now separated by line breaks and "Row #" indicators instead of commas.

For example, note how the multiple child-level comments in the Comment column are separated by line breaks and "Row #" indicators:

TRAK-2016-1284: You can now automatically aggregate child-level number fields when building ad hoc reports.

By checking a few checkboxes, module developers can now configure modules to provide you with an option to display the sum, average, minimum, or maximum value when building ad hoc reports. You do not need to expand a child level for these options to be available.

TRAK-2016-1451: We now automatically close single quote marks (") in searches, and we cleaned up the error message dialogue.

Previously, if a user attempted to search for an exact term wrapped in double quotes, but only included the first quote mark, we would ignore the quote mark or sometimes display an error message. Now we automatically supply the trailing quote.

We also cleaned up the error message pop-up so that screen shots will include technical details that are useful for DevonWay employees when trying to track down future errors.

TRAK-2016-2993: We resolved an issue where saved searches, and any corresponding live tiles, could behave incorrectly if they referenced fields that were no longer valid.

TRAK-2016-3969: The contents of Dashboard tiles no longer wrap lines in Firefox or IE.

TRAK-2016-4088: Users now have access to DevonWay Feedback.

We are pleased to announce DevonWay Feedback, a forum in which users from any and all subscribers can share suggestions to improve DevonWay software. Users who sign on with the new login page simply click a new button on their Dashboard to access this forum, where they can submit their own ideas or vote for (or comment on) other ideas.

Users should be aware (and the application will remind them) that ideas and associated comments and attachments are visible outside their own organization. Users should not include private or sensitive data.

DevonWay will consider and review ideas and provide feedback in a timely manner. DevonWay's feedback will come in the form of comments and status updates.

TRAK-2016-4285: (tabbed) We repaired a boundary case so fields that dynamically change screen location now appear as expected in certain conditions.

TRAK-2016-4372: You can now save searches with the same names as those on shared tiles to which you don't have access.

You will still get an error if you attempt to save a search with a name that matches an existing search on a tile that is shared with you.

Note that it is possible for tile-sharing (or team membership) to change so users have access to multiple, identically named searches on different tiles.

TRAK-2016-4534: We now display a loading indicator when BI reports are rendering (in either view or edit mode).

Displaying a loading indicator blocks screen actions (clicks) that could potentially lead to unexpected behavior.

TRAK-2016-4549: We made some improvements to tile and search sharing to prevent unexpected results.

To prevent users from accidentally removing access to tiles and searches that they've previously shared, we will now warn them when they're attempting to change that access. We also explicitly prevent users who are not owners of a tile or shared search from removing access to the tile or shared search.

TRAK-2016-4586: Changed the sort behavior for messages on the new login page so that newer messages appear at the top of the list.

TRAK-2016-4627: Standard emails now look cleaner, nicer, and more consistent.

We modified our standard, system-generated emails to have a consistent look and feel. System-generated emails include those sent as the result of search notifications, new item assignments, forgot-password notifications, tile sharing, search sharing, and other custom module notifications. You'll notice the standard title bar and consistent display, which should look similar across the wide variety of email clients.

TRAK-2016-4690: (full) We no longer send duplicate print requests (for old-architecture objects) when the original request runs longer than five minutes.

TRAK-2016-4691: Pressing Ctrl+S now triggers [Save] for objects without change-request handling enabled.

In the 2.35 release, we disabled the Ctrl+S keyboard shortcut to avoid potential interference with change-request handling (TRAK-2016-2239). Now, we re-enabled Ctrl+S for the typical case where change-request handling is disabled.

TRAK-2016-4692: You can now re-order live tiles on the Dashboard just like other tiles.

TRAK-2016-4694: When users change the sharing properties of a shared tile, we take that opportunity to clean up any missing tile attributes.

TRAK-2016-4728: (tabbed) Closing a tabbed item no longer removes newly added child rows with empty reference fields and two-way reference validations.

TRAK-2016-4837: We removed the pagination option when exporting BI reports to Excel or CSV format.

TRAK-2016-4916: Selecting the "Clear Value" action for reference fields now clears the existing value as expected.

This includes both header-level and child-level reference fields displayed in any style - autocomplete, picklist, or search pop-up.

TRAK-2016-5027: (tabbed) The standard attachment grid now has a new-and-improved display that includes thumbnail-sized images.

Instead of seeing a list of attached files, users will now see thumbnail-sized images representing the attached files. For file attachments that aren't images, users will see icons representing the file type.

From this new Icons view, users can click on the thumbnail image to download the file, or they can hover over the information icon to view additional information about the file (like when it was uploaded).

Users can click [Details] to switch to the previous grid view. Here, they can modify file names and delete files, just like they can today.

Note that users must sign on using the new login page to use this feature.

TRAK-2016-5048: After you clear selected search filter values, you now get accurate results on subsequent searches when you enter a value in the filter text box.

TRAK-2016-5194: We no longer add superfluous history rows on certain date fields.

TRAK-2016-5319: We no longer trigger redundant screen refreshes when radio-group picklist field values change on a button click.

TRAK-2016-5328: (tabbed) Anonymous users can now close tabs as long as one tab remains open.

TRAK-2016-5337: We changed the region visibility behavior so focus will remain on an active region instead of switching to a region that recently became visible.

TRAK-2016-5412: Numeric fields with "empty value text" now allow entry of numeric values without having to manually remove the initially displayed text.

TRAK-2017-0012: Search Notifications now handle field-name substitutions where the field names are common across modules (like "Name" or "Synopsis").

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-2015-1122: Administrators can now delete a user's tiles from the Tiles grid on the Maintain Persons screen.

TRAK-2016-0448: We added a FileSize column to the auto-generated Attachments view.

TRAK-2016-2647: We correctly set display preference values (like 'Required field background') whether or not the preference record already exists.

TRAK-2016-3807: We now suppress pagination in BI reports exported to CSV format (to avoid repeated column headings).

Note that you may have to re-save existing BI reports for this change to take effect.

TRAK-2016-4118: We now support custom prefixes for report-book- and archive-style pdf exports.

Report developers can optionally set "outputPrefix" in the report book parameters to override the default "ObBook" prefix. (Note that the "outputFileName" parameter is obsolete; it does not affect the generated file name.)

TRAK-2016-4586: We changed the behavior of the Login Page Preferences screen so that the Message column is more easily editable.

TRAK-2016-5215: Administrators can now assign users to a new "Module administrator" role, which gives them limited Module Builder access.

Users with the "Module administrator" role can export, import, and view modules, but they cannot save changes in Module Builder. Typically, administrators would assign the "Module administrator" role in place of the "YourWay developer" role to avoid inadvertent changes in Production (or other critical) areas.

TRAK-2015-5467: We now wait until search indexing is finished before reporting a data import job as complete.

TRAK-2016-5804: We now ensure that Data Import jobs populate reference fields with data from the appropriate reporting authority (when filtered).

For Module Developers

This section describes fixes and enhancements to functionality affecting module developers, i.e. users of the YourWay IDE.

TRAK-2015-2760: We added a DXL function called ElapsedDays, which returns the number of days between two dates.

TRAK-2016-0448: We added a FileSize column to each subscriber's Attachments view, which is visible in QueryBuilder.

TRAK-2016-1284: You can now enable automatic aggregation of child-level data in DevonWay BI reports.

Module Builder has these new properties available for child-level fields: - Reports - Concatenate Fields - Reports - Calculate Sum (available on Numeric fields only) - Reports - Calculate Avg (available on Numeric fields only) - Reports - Calculate Min (available on Numeric fields only) - Reports - Calculate Max (available on Numeric fields only)

After you check Reports - Concatenate Fields for a child-level field, users see that field in the list of available fields when building ad hoc reports. After you check any of the other numeric-field properties for a child-level field, users see corresponding instances of that field in the list of measures. For example, if you check Reports - Calculate Sum and Reports - Calculate Avg for a child-level field with a prompt of "Amount," users will see "Amount (Sum)" and "Amount (Avg)" in the list of measures when building ad hoc reports.

Remember to click [Update BI] after changing any of these field properties.

TRAK-2016-4335: The Module Tools screen now provides more options for deleting modules, module data and search-index data.

You can now delete module data associated with a specified reporting authority. You can also specify batch size (how many objects to delete at once) and pause time (how many seconds to pause in between deletion batches) when deleting high volumes of data.

Clicking [Delete] the first time will generate a report of what will be deleted, if you click [Delete] again we will kick off the actual delete process. Refer to the online help text or documentation for more details on the different options available on the screen.

TRAK-2016-4366: We now correctly show reference and picklist fields in Module Builder's Where Used view.

TRAK-2016-4604: Module Builder now reports a warning message if developers use SQL reserved words as field names.

This warning message advises developers to reconsider their usage of that reserved word. If they choose to proceed, then they'll need to use quoted or delimited identifiers (like '' or []) in SQL statements that reference that field.

TRAK-2016-4738: You can now customize child-level [Add] button labels.

In the Level Behaviors popup in Module Builder, you can select a new "[Add] Label" behavior and enter a custom label for the selected child level.

TRAK-2016-4794: You can now configure modules to run rules to determine task assignees when rolling back to a previously completed task.

The Task Assignments popup in Module Builder now has a new checkbox "Rollback to most recent assignee". If this is checked, then we will continue the old behavior of rolling back to the prior assignee. If it is unchecked, then we will run rules to determine the assignee.

The checkbox will be set to check for all tasks in existing modules as part of the release process so that behavior doesn't change unexpectedly.

TRAK-2016-4795: You can now configure modules to prevent rollback to specific tasks.

In the Workflow Management popup in Module Builder, you can now select "Prevent rollback to task" as a type of behavior for a specific workflow task. When end-users attempt to reopen tasks, the specified task will not appear in the list of tasks available for rollback if the associated rule is true.

TRAK-2016-4848: Clicking [Compile] in Module Builder no longer clears unsaved changes when there are validation errors.

TRAK-2016-5013: Changes made to the Help URL screen behavior in Module Builder now take effect as expected after clicking [Compile].

TRAK-2016-5070: We now hide items that match the "Do not allow selection" criteria in Autocomplete and Picklist reference fields.

It is possible that users unknowingly relied on the fact that we previously ignored "Do not allow selection" criteria for these reference fields. The 50-60 potential cases (across all subscribers) are itemized in a spreadsheet attached to TRAK-2017-0118. In the cases we looked at, this change shouldn't have any effect.

TRAK-2016-5072: Resolved an issue with saving modules that have inherited roles in Module Builder.

ModuleBuilder still does not support defining Inherited Roles as we plan to use Subscriber Roles instead of Inherited Roles going forward. This fix is for modules that were defined with DefineModule and still contain Inherited Roles.

TRAK-2016-5081: We now ensure that "Save first" buttons behave as expected after being hidden and then made visible.

TRAK-2016-5105: The "Hide [Add]" behavior now works as expected for the Attachments grid.

TRAK-2016-5146: Export module no longer reports an error when you add a single step on the Group tab.

TRAK-2016-5739: The AddMonths() DXL function now accepts field values (or any other expression that returns a number) for the offset (second) parameter.

TRAK-2016-5205: We now generate a subscriber view containing details about the newest "dirty-object" queue.

TRAK-2016-5317: We now run rules to determine whether to run static search criteria behaviors and now support DXL that runs SQL in these behaviors.

TRAK-2016-5377: We now include Person fields referenced through Virtual Reference fields (just like we do for Reference fields) when selecting Person fields as Change Request assignees in Module Builder.

When administrators generate subscriber views, we now generate a new view (named v_CleanObject) with columns such as: ObjectID, ObjectIdentifier, ModuleCode, ObjectState, FutureDirtyFlag, RuleID, and Priority.

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-2016-1534/TRAK-2016-4269: We made sweeping improvements to our underlying code to improve efficiency, make things more reliable and lay the groundwork for speedier development and better overall application performance.

TRAK-2016-4791: The ManageLocks batch job now runs as expected in (rare) cases that previously caused errors.

TRAK-2016-4890: For improved performance and application stability, we changed the location where we store overflow text data on large character fields.

TRAK-2016-4894: We added an automatic retry to reduce the incidence of concurrency errors when cleaning dirty objects.

TRAK-2017-0040: We added support for some additional time zones to support on-premises installations in those regions.