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.

YourWay 2.33 Update 1 (12Nov2015)

YourWay Updates are no-downtime mid-cycle releases to apply impovements and fixes that are useful to apply prior to the next major upgrade.

** Various tickets covering several improvements to the Data Import screen: **

• The overall process is now faster, more reliable, and more scalable.
• You can now specify the starting and ending rows to import or preview.
• The error message for rows that fail is displayed next to the failed row in the Retry file.
• Handling for header rows with special characters.
• Handling for empty rows and/or columns.
• Fields that are always required now appear with asterisks next to their prompts.
• Added hover help for fields.

** TRAK 2014-4575: New (unread item) counts now show on Dashboard for My Assignments shortcuts **

We fixed a problem that caused shortcuts based on My Assignments to not display the number of new (unread) items.

** TRAK 2015-4591: Resolved an issue with creating new Admin Audit Trail records **

Under certain special circumstances, we didn't correctly create new Admin Audit Trail records. We fixed this problem.

** TRAK 2015-4596: Better handling for [Save+Print] requests directly following changes to fields with refreshes **

We now handle the situation where you click a [Save+Print] after changing a value in a field with refresh-on-change enabled but you do not first tab out of the field.

** TRAK 2015-4623: Clicking [Save Search] with the Notifications screen open can blank out your BI report **

If you clicked [Save Search] instead of [Save] while creating a notification for a BI report, we mistakenly reset your report definition. We fixed this problem by hiding the criteria panel, which contains the [Save Search] button, whenever you're focused on the Notifications screen.

** TRAK 2015-4688: We no longer throw an error if admins try to create teams with more external members than internal members **

** TRAK 2015-4709: Fixed display issue with Notifications admin screen displaying more than 10 notifications **

We fixed an issue that would prevent the display of schedule information on the Maintain Notifications screen when there were more than 10 notifications with schedules.

** TRAK 2015-4841: Resolved boundary condition issue with fields in multiple regions **

We fixed a problem with the display of dynamically placed fields.

** TRAK 2015-4929: Faster, more scalable server-side data operations **

To support the improvements to Data Import, we made some architectural changes that make our platform's data access faster and more scalable.

** TRAK 2015-5062: Support for more explicitly defined SQL statements through an ExecuteSql() DXL API **

** TRAK 2015-5183: Printing from grid search results now supports Attachment Only prints **

What's New in YourWay 2.33 (25Sep2015)

For a 30-minute webinar overview of YourWay 2.33, please click here.

• You can now share tiles and searches with both teams and individuals
• Search Notifications now display more prominently as an option in search results, and there are more triggering options
• We made many improvements to existing admin screens, and created a new Admin Audit Trail screen
• We significantly improved the performance and usability of the Data Import screen
• From Grid search results you can now export a subset of specific items, and you can export to a ZIP file
• You can issue a SingleSignOn request directly from the new login page if you have SAML SSO enabled
• If you choose to let them, users can specify a reporting authority when logging in through the new login page

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-2014-0284: (tabbed) Better handling for empty attachments **

We now trap for and successfully handle opening objects with attachments that are empty.

** TRAK 2014-0714: Support for sharing tiles and searches with both teams and individuals **

You can now share a personal tile with individual persons, in addition to teams. More importantly, you can now share a search directly with a person or team as well, without having to drag it first to a tile and then share the whole tile. You access this ability throught Options .. Share.

Note that when you search for a team, results are limited to teams to which you belong. Please see the help topic Saving and Sharing Searches for more details.

** TRAK-2015-0468: More prominent display for the option to create a Notification from a saved search **

We moved the [Notification] option from the Options menu to the saved search toolbar. This eliminates issues related to the size of the pop-up we had before and makes it easier for you to manage any notification you may have set up with a saved search.

See the Notification help topic for more details about search notifications.

** TRAK-2014-1589: New notification trigger options **

We added three new trigger options that you can use to alert you when your data changes in ways that are meaningful to you:

The Value field for each of these options is not required; however, you may populate it if you wish to specify the exact number of items that have been added, removed, or added or removed.

** TRAK-2015-1731: (tabbed) Child-level, referenced-in date fields now apply custom date formats **

We now correctly apply custom date formats to child-level, referenced-in date fields.

** TRAK-2015-2247: (tabbed) Resolved an issue with html formatting not being applied for fields that switch from visible to invisible and then back to visible again **

We fixed a problem that could cause fields with html to not display correctly after toggling their visibility twice.

** TRAK 2015-2414: The Change Requests screen now handles users with thousands of assigned change requests **

The Change Requests panel now gracefully handles displaying hundreds or thousands of change requests.

** TRAK-2015-2722, TRAK-2015-3606: (tabbed) New ZIP export type and Grid search Export options now respect checkbox selections **

If you select specific rows in a Grid search display and choose any of the export options, we now only export those specific selections. If you do not specify any rows to export, we will attempt to export all rows returned by the search like we did before.

In addition, we now support a new export type of ZIP. This produces detail prints (PDFs) of the items we're printing, but instead of collating everything together into a single PDF, it packages the different objects together into a ZIP archive.

** TRAK 2015-3064: (tabbed) Search engine feeding and history generation now accounts for very rare failures **

In certain extremely unusual failure scenarios, the history generation and search engine queue feeding logic could fail to run. We moved both of those pieces of logic into the synchronous portion of committing changes to an object, so the only way they can now fail is if the entire update of the object also fails.

We also made an improvement to the asynchronous portion of committing changes to an object so that it no longer depends on the initiating session still being active.

** TRAK-2015-3205: (tabbed) Visibility of [Save] and [Complete] buttons now considered when deciding whether to lock an object **

We now only lock an object if it's not read-only and either the [Save] or [Complete] button is invisible.

** TRAK 2015-3212: (tabbed) Improved reference field sorting **

We improved sorting on reference-field searches where the search values are numeric and contain decimal points.

** TRAK-2015-3257: The new login page now includes an SSO link if appropriate **

If you have SAML 2 SingleSignOn enabled, and you navigate to the new login page, you can now launch the SSO process directly by clicking on a new Single SignOn link:

** TRAK-2015-3267: (tabbed) Resolved issue where extra-large text pop-ups sometimes didn't display the full text **

If you clicked Click for more in an extra-large character field and then clicked the pop-up icon to view the text in the pop-up window, we did not display the full text in the pop-up. We fixed this problem.

** TRAK-2015-3289: Removed option for HTML output types in search notifications **

HTML is an unreliable output type, so we removed it from the list of allowable attachment types when defining search notifications, after verifying that no one was using it in Production.

** TRAK 2015-3294: (full) Tile Groups now close automatically when navigating to an old-architecture object **

To avoid display issues in tile groups caused by opening old-architecture objects in full-screen mode, we now automatically close any open tile groups after warning you that we are about to do so.

** TRAK-2015-3335: Exporting search results to Excel now uses custom date formats **

If you have a custom date format defined and you export Grid search results to Excel, we now display any exported date fields in that custom date format.

** TRAK 2015-3354: You can now clear child-level autocomplete reference fields **

We added a [Clear] option for child-level autocomplete reference fields.

** TRAK-2015-3493: (tabbed) Fixed problem that sometimes made tabs initially collapsed **

We fixed an issue that could cause a tab to appear unexpectedly collapsed under rare conditions.

** TRAK-2015-3499: Improvements to the INPO Operating Experiences email **

For our Operating Experiences customers, we made the following improvements to the email that we automatically generate following an INPO OE load:

• The date in the subject line now corresponds to the date of the import file that we processed, not the date on which it was processed. This eliminates confusion in the rare case where a file is delayed in being processed or made available for processing.
• We corrected the "On this day in history..." link to point to INPO's new website.
• WANO events now link directly to the corresponding topic at wano.org.

** TRAK 2015-3618: (tabbed) Fields that dynamically change regions no longer appear to lose their content **

We added logic to prevent a boundary case that may cause newly entered field values to appear empty after the field dynamically changes screen placement.

** TRAK 2015-3652: (tabbed) Regions with no fields no longer display **

We no longer display regions with no visible fields.

** TRAK-2015-3653: We lightened some of the darker standard dashboard tile colors **

We made a little lighter some of the darker default tile colors so that text is easier to read.

** TRAK-2015-3664: Better support for large search queries **

We now do a better job of supporting queries with a large number of criteria.

** TRAK 2015-3758: The Assigned To field is now included in the XLS file when you export from grid search results **

We now include the workflow Assigned To field in the Excel spreadsheet we generate when you export from the grid search results screen.

** TRAK-2015-3766: Grid and Report saved searches now handle special date criteria for child fields **

You can now define Grid or Report saved searches that include child-level date criteria using the special keywords Yesterday, Last Week, etc.

** TRAK-2015-3780: The ::ResultsCount:: variable in notifications now handles zero results **

The ::ResultsCount:: variable in search notifications now handles the case where the search returns zero results.

** TRAK 2015-3902: (tabbed) Fixed an issue where embedded SSRS reports could cause object post-processing to not occur **

We fixed a rare issue that could cause embedded SSRS reports to block certain asynchronous processing that we perform after an object has been modified: notably, feeding the search engine or generating history records.

** TRAK 2015-3925: (tabbed) A date selected from a child date field widget is now captured when a refresh occurs **

We resolved an issue that could prevent date fields in child grids from sending updated values back to the server if those fields were set to refresh on change.

** TRAK 2015-4070: (tabbed) Resolved a problem with displaying checkboxes that are defaulted and made non-modifiable **

We now display the correct state of a checkbox when it defaults to unchecked from checked and becomes non-modifiable at the same time.

** TRAK 2015-4008: (tabbed) The [Print] menu options now sort alphabetically **

We now sort the [Print] menu options alphabetically when there are multiple print templates available for an object, with the exception of the Default print option, which still displays first.

** TRAK 2015-4072: (tabbed) Asterisk-style required field display now goes away as expected when a field becomes non-required **

If you have asterisk-style required field displays enabled, and a refresh action on an object turns a field from required to non-required, the asterisk goes away and the field prompt becomes non-bold as expected, indicating that the field is no longer required.

** TRAK 2015-4082: (tabbed) Fixed duplicate "Drop to attach files" instructions in the attachment upload region **

If you attached a file to an object and clicked save, the "Drop to attach files" instructions were sometimes duplicated. We fixed this problem.

** TRAK 2015-4312: (tabbed) Resolved issue with radio button display **

We fixed a case where radio button references did not show the correct value when they become non-modifiable on refresh.

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-2014-1621: Better error reporting during imports **

We now do a better job of bubbling up to you any errors you encounter while running data imports.

** TSR 2014-1884: The Data Import screen now supports IE11 **

We resolved some UI issues related to Internet Explorer 11.

** TRAK 2014-3135: You can now upload tab-delimited data files **

Reference Data Loader and the Data Import screen now support tab-delimited files. Use the hexadecimal equivalent of the desired ASCII code, i.e. 0x09, for the tab character.

** TRAK 2015-1912: Better protection for certain queries issued in the Query Builder window **

We made some improvements to the types of queries we allow privileged users to issue through the Query Builder window.

** TRAK 2015-1950: Enhancements to system views **

We made the following enhancements to the default system views accessible through Query Builder:

• Added who-columns (LastUpdatedBy, LastUpdateDateTime, and LastUpdatingProcess)
• New views for exposing data related to search notifications, module roles, module rules, and module rule targets
• Added new fields to the Module and Fields views

Note that you may need to click [Generate Subscriber Views] in the Preferences screen before these changes are available for your subscriber.

** TRAK 2015-2277: The Data Import screen now supports reference fields **

You can now import values into reference fields using the Data Import screen. For this to work, the reference field can only have one field marked as Display, and the value in the spreadsheet that queries for this field must resolve to a single unique reference record.

** TRAK 2015-2553: Usability improvements to the Data Import screen **

We made several usability improvements to the Data Import screen. For details, please see the corresponding help topic

** TRAK-2015-2569: Users can now specify a reporting authority under which to log in **

You can now select reporting authorities to display on the new login page that users can choose to restrict their access when they log in. This is useful if your organization has multiple sites, for example, and users only ever want to see information pertaining to a specific site during a session. You can also choose to force the selection of a reporting authority in order for users to log on.

When users select an Authority, all search results, BI reports, etc. are restricted to objects that have an authority at that level or below. See the Login Page Preferences topic for more details.

** TRAK-2015-2928: Improvements to several administrative screens **

We made a few improvements to administrative screens:

1. When the Use new login page attribute is enabled in the Preferences screen, we now hide functionality that does not apply; specifically, we hide:
   • The SSO/Windows domain user field in Maintain Persons.
   • The message color attributes, support areas, and support area persons regions in Login page preferences.
   • The Hide anonymous links and Cross references checkboxes in Preferences.
   • The Assignable, External, and Workflows fields, and the Operating Experiences region in Reporting Authorities.
2. The logon page banner in the Login page preferences screen is now assigned a unique ID so changes to it will take effect immediately, without having to work around the browser caching the old version of the banner.
3. Finally, a new Admin Audit Trail screen lets administrators see when admin-related data (such as password resets) were made, and by whom.

** TRAK 2015-3035: Dataset dates now respect custom date format setting from Preferences screen **

We now honor the custom date format from the Preferences screen in Dataset searches and BI reports.

** TRAK 2015-3800: We now present clearer errors when failures in SAML SingleSignOn occur **

When failures in processing SAML SSO assertions occur due to configuration errors or other issues, we now do a better job presenting the actual error encountered.

** TRAK 2015-4016: The Search Logs screen now lets you filter by keyword **

The Search Logs screen now lets you filter by keyword.

** TRAK 2015-4147: Ability to create metadata objects at the end of a data import run **

You can now create JSON-formatted templates that describe how we should create module objects to store information about an import at the end of a successful run. For details, please reference the relevant help topic.

** TRAK 2015-4247: Improvements to handling of forbidden passwords **

We made some improvements to the way we handle forbidden-word password policies.

** TRAK 2015-4369: The Query Builder [Refeed Search] button now ignores the object timestamp check **

When you refer objects to the search engine through the Query Builder [Refeed Search] button, we now force the object to the index even if it contains the same last-updated timestamp as the object in the database. This helps avoid situations where the database and search index become out of sync because a value was manually updated through SQL, but the LastUpdatedOn timestamp was not updated before the object was refed to the search index.

For Module Developers

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

** TRAK 2011-2831: (tabbed) More control over how search results are sorted **

By default, the search engine's relevancy ranking algorithm sorts results according to rules such as how often or how close together keywords occur in the body of an object, without taking into account information about which fields that data belongs to. You can now control the sorting by assigning a Search boost value to any header or child level fields that you would like to be preferred in search results. All fields have an implied boost value of 1, except for the Identifier, which has an implied boost value of 3. If you want to deemphasize a field you can assign a value like 0.5. To make a field more relevant you'd set a value greater than 1, e.g. 2.3.

Since boost values are part of the index, after making this change you need to refeed the index.

** TRAK-2015-1339: (tabbed) Cascading New()s are no longer allowed **

We now prevent calculations from recursively creating an indefinite number of new items. Now, if this condition occurs, the end-user receives an error explaining that a "recursive new... has fired from the calculation logic," and it will suggest that a module developer should review the rules that led to this condition.

** TRAK 2015-2563: Enhancements to Report Book printing **

The Report Book printing functionality can now handle report books that are many thousands of pages long. In addition, if you have the Require that uploaded attachments can convert to PDF attribute checked, we will store a ConvertedPDFPages number with the attachment that you can then reference in DXL (see TRAK-2015-3248 below).

** TRAK-2015-2914: (tabbed) You can now protect data returned in search results **

You can now protect data returned in search results by enabling a new attribute that hides values returned unless the user also specifies search criteria for that field:

The typical use case for this feature is if you have a reference field hierarchy with static At or Below criteria driving off an attribute of the logged-on user. For example, say you have an Observed On reference field that stores the person on whom an observation was performed. You want to let users across the enterprise see data regardless of the observee, but you want to mask the observee unless he or she is in a person's reporting hierarchy (i.e. the person is an observee's manager or higher up). In that case you would create static reference field search criteria so that logged-on persons can only restrict results to persons who are At or Below their reporting level, and you would set the Search Filter Controls attribute for the field to Display results when criteria populated. YourWay will then only display an observee's name if search criteria were specified, otherwise it will display the text [NOT DISPLAYED].

You can choose to ignore this attribute on a per-role basis through the Ignore search filter controls attribute.

** TRAK-2015-3248: (tabbed) Enhancements to DXL functions **

1. You can now retrieve a person's full name in FirstName LastName format.
2. You can retrieve the number of pages an uploaded attachment would convert to in PDF format.
3. A new PrintInfo() function returns metadata about the results of a particular template's print of an object.

For more details, see the Development help topic.

** TRAK-2015-3262: (tabbed) Resolved issue with deleting subscriber roles **

We fixed a problem that occurred when deleting a subscriber-level role.

** TRAK 2015-3353: (tabbed) Save First attribute now applied to all print menu options **

If you have a Save First rule target applied to the print button, that now applies to all print options, not just the default one.

** TRAK 2015-3993: (tabbed) Update current task looks at the current working task, not the highlighted task **

The Update current task rule target now operates on the current working task, whether or not it is assigned to you or a team you belong to.

** TRAK 2015-4074: (tabbed) Changing an object now always feeds to Solr, even if the header level doesn't change **

We now update the header-level last-update timestamp whenever data is updated at the child or task levels. Among other benefits, such as improved concurrency control, this ensures that a modified object is always re-fed to the search engine, even if data at the header level didn't change.

Other

This section describes fixes and enhancements to our backend architecture. Tickets in this section primarily affect Ideagen personnel, such as our Operations group, or environment management personnel at our on-site customers.

** TRAK-2015-3217: Added a configuration option for a backend process **

We added a configuration option that allows us to set the number of connections a backend process can hold at a time.

** TRAK-2015-3265: (tabbed) The Forgot password email's From: attribute is now the subscriber-configured email address **

The Forgot password email now has its From: address set to whatever is defined for the subscriber, instead of being hardcoded to administrator@devonway.com.

** TRAK-2015-3329: Scheduled jobs now handle restarted services **

Scheduled jobs now handle the situation where an executing process is restarted and kick off the next run of the job without waiting for a timeout to occur.