Worklists
Summary
This small enhancement adds the flags column to the Activity worklist, making it consistent with other worklists.
Configuration Instructions
No System Administrator actions are necessary to enable this feature.
Summary
When many columns are hidden from a worklist view, it was previously difficult to find the desired column to add to the view because the options were not presented in a logical order. This enhancement to Worklists updates the existing worklist Column Chooser to add support for filtering of the columns that are available to add to a worklist. Available columns will also be listed in alphabetical order.
Column names will now be alphabetized and a search box at the top of the list can be utilized to find the desired column.
Columns displayed in the column chooser may now be filtered
Configuration Instructions
No System Administrator actions are necessary to enable this feature.
Summary
This enhancement updates all materialized worklists to limit the amount of data cached when using a dated worklist.
Currently, dated worklists will locally cache every date visited by the user. When a user visits many dates without changing their sort or filters, their memory and disk caches will grow over time, reducing performance.
With this change, RIS now keeps track of each day visited (or re-visited). When a worklist is refreshed, old values are removed from the cache. A new WLMaxDaysToCache RIS System Configuration value controls how many days are retained in the cache.
Note that when the Confirmation worklist loads a date range, the date range will always override the WLMaxDaysToCache value.
Configuration Instructions
No System Administrator actions are necessary to enable this feature; however, optional configuration is available:
RIS Client
Changes to RIS System Configuration Settings
The following related settings were added or updated:
|
Setting |
Default |
Purpose |
|
WLMaxDaysToCache |
Value=Days as Integer, Default=[7] |
Number of days on a dated worklist that will remain cached on the client. Added in v2018.5.6 #27951 |
Summary
This enhancement to Worklists extends the new more flexible and efficient "materialized" worklist functionality enhancements to all RIS worklists, including supporting the existing "group by" functionality on the Image Request worklist.
Previously, many RIS worklists were updated to a new materialized worklist pattern.
With this change, all remaining worklists are now updated.
This includes the ability of the Image Request worklist to "group" items:
All previous functionality of the Image Request WL is maintained.
Configuration Instructions
Service Team assistance is required to enable this feature.
· Worklists may now be configured to materialized mode.
Related Redmine Items
· Feature #27966 (Backport of 20942) - Implement remaining WL to use the materialized WL pattern
· Feature #27967 (Backport of 22367) - Enable GroupBy feature for the Image Request materialized worklist
Summary
This enhancement to Worklists introduces the ability to disable any worklists not being used by an organization to avoid the unnecessary overhead required to process and store the associated data.
Currently, a worklist such as the Billing Exception WL is populated even if it is not used by a customer. This can mean that millions of rows of data are processed and stored when they are not needed.
With this change, a new WorklistDisabled RIS Lookup Table Editor has been created:
When a worklist is added to this lookup table, that worklist will no longer:
· have worklist rules evaluated.
· have worklist items added.
Existing items from these worklists will be marked as inactive and be removed as part of the "Daily Maintenance" job.
|
|
Changes to the WorklistDisabled lookup table requires all RIS Services to be restarted. |
Configuration Instructions
System Administrators must complete the following actions to enable this feature:
RIS Client
Changes to RIS Access String Settings
Grant Config.LookupEditor.WorklistDisabled permissions as necessary.
The following related settings were added or updated:
|
Setting |
Default |
Purpose |
|
Config.LookupEditor.WorklistDisabled |
Value=[None|Full], Default=[None] |
Controls access to the "WorklistDisabled" lookup table editor. Added in v2018.5.6 #27969 |
Changes to other RIS Access Tables
· Add selected worklists to the WorklistDisabled RIS Lookup Table.
Services
· If the WorklistDisabled lookup table has been modified, all RIS Services must be restarted.
Summary
This enhancement to Worklists updates all materialized worklists to utilize client-side custom formatting for person names.
Currently names of people are formatted by the database. For example, the user id "millst" is formatted as “Mills, Tim, KBE” by the database. This step adds load to the database and limits the ability to enable custom formatting of the name (e.g. a request that the name be formatted as “Mr. Tim Mills, KBE”).
With this change, the RIS UI will apply desired custom formatting via formatting specified in a new PersonNameInWLFormat RIS System Configuration value.
Configuration Instructions
System Administrators must complete the following actions to enable this feature:
RIS Client
Changes to RIS System Configuration Settings
Configure PersonNameInWLFormat and PersonNameInWLCacheTimeToLiveMinutes for your organization.
The following related settings were added or updated:
|
Setting |
Default |
Purpose |
|
PersonNameInWLCacheTimeToLiveMinutes |
Value=Minutes as Integer [Min=5], Default=[1440] |
Number of minutes to refresh the server-side cache for person_keys to descriptions. Added in v2018.5.6 #27971 |
|
PersonNameInWLFormat |
Value=String [May include any field on the l_person table, plus user_id], Default=[{last_name}, {first_name}{ middle_name}{, name_suffix_code}{ (user_id)}] |
The string format for displaying person names in materialized worklists. Added in v2018.5.6 #27971 |
Related Redmine Items
· Feature #27970 (Backport of #20940) - Client-side formatting of worklist person name values
· Feature #27971 (Backport of #23199) - UI Expanded Materialized WL Columns
Summary
This enhancement to the RIS Database adds support for running RIS with a database configured to use SQL Server Availability Groups (SQL Server 2016 or newer).
SQL Server Availability Groups (AG) allow for multiple SQL Server instances to work together in a group, where a database on one server is designated as primary and all copies of that database on other SQL Server instances are secondary read-only. This is referred to as the MS SQL Server High Availability Disaster Recovery (HADR) solution. The "Always On" aspect requires that the primary server could fail over to a secondary server without data loss.
Configuration Instructions
Service Team assistance is required to enable this feature.
