Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

With the most recent release of Infralink/IMMS (v.3.5.28), we are happy to offer the following new features and functionality functionality.

Table of Contents

System Element Configuration Templates

...

InfraLink System Elements represent the functional decomposition of the System being installed or under maintenance and are typically reflected in the System design. Each System Element has a specific function and Location and falls under a defined System Element Type. The parent-child relationship between System Elements establishes the System Hierarchy. Within a system, instances of a parent System Element and its respective child System Elements (e.g., assemblies) are often consistent across the design and numerous installation locations.

...

Gliffy Diagram
displayNameUpdates - Template Element Creation
nameUpdates - Template Element Creation
pagePin2

Notification Banners

...

InfraLink now supports instance-wide Notification Banners. These administrator-defined messages are displayed just below the top-level navigation bar, advising users of information or warnings related to the project/program or the InfraLink instance.

Gliffy Diagram
displayNameNotification Banners
nameNotification Banners
pagePin3

More than one Notification Banner may be active at any given time. InfraLink will rotate the banner display at a set interval. Banners are ordered by the creation timestamp, and displayed in descending order (i.e., the most recently created banner is displayed first).  

Note
titleInterval Setting in Minutes

The banner refresh/rotation interval is an instance-level setting (i.e., NotificationBanner.Interval_In_Minutes) within application.properties. The default interval setting is eleven (11) minutes, but this can be adjusted at the instance administrator's request.


Once Users have read the message, they can remove the notification by clicking the "X" to the right of the banner. This action is logged as the Users' acknowledgement.

...

  • Active Notification Banners are displayed below the top-level navigation bar.
  • An "X" to the far right side of the banner allows Users to remove the notification.
  • The Configure drop-down menu now includes a Notification Banners option, which opens the Notification Banners grid view.
    • The Notification Banners grid view allows administrators to view all Notification Banners and filter those records by various attributes, including notification type, status and banner display dates.
    • Clicking the New button, atop the Notification Banners grid view, opens the New Notification Banner form.
    • Selecting a record from within the Notification Banners grid view opens the corresponding Notification Banner Details panel. 
    • Notification Banner Details panel includes an Acknowledged Users section, which lists all Users who have acknowledged the Notification Banner, as well as the date and time the acknowledgement occurred.

Work Ticket Owner Permissions

...

With an expansion of Owner Permissions, like those recently released for Case records, Work Tickets now support -All and -Own Permissions. Formerly, User Roles could include "Read" and "Update" Permissions for Work Tickets. Now, Work Ticket Permissions offer:

  • Read All - This Permission mirrors the previous "Read" Permission, allowing the User to see all Work Tickets for the assigned Contract(s).
  • Read Own - This Permission allows Users to see only those Work Tickets they created or those to which they are assigned.
  • Update All - This Permission mirrors the previous "Update" Permission, allowing the User to update all Work Tickets for the assigned Contract(s).
  • Update Own - This Permission allows Users to update only those Work Tickets they created or those to which they are assigned.
Note

Own Permissions are not enabled by default.  Enabling Own Permissions on any instance requires an update to the application properties.  That is, the following setting must be added to the application.properties file, and then the application must be restarted.

Image Added


What You Will See in the User Interface:

...

 

Gliffy Diagram
nameWT_Owner_Permissions
pagePin1

External Case Number Settings Expanded 

...

External Case Numbers, represented in free form text fields, associate InfraLink Cases to record numbers from a Client/Customer system. External Case Number behavior is configured at the Contract level and now includes options such as Not Available, Optional, Optional Unique, Required, and Required Unique. Enforcing uniqueness across a Contract's External Case Number values will reduce duplication of those entries, increase efficiency across systems, and increase validation efforts to ensure that what's represented in InfraLink is then represented in the client/customer system. 

...

Gliffy Diagram
displayNameExternal Case Number Options Annoated
nameExternal Case Number Options Annoated
pagePin4


   

Excerpt
hiddentrue

Highlighted features include: System Element Configuration Templates; Instance-wide Notification Banners; Work Ticket Owner Permissions; and Expanded Settings for External Case Numbers.

-