...

...

• Once added to a grid view, the Open Issues comun column can be dragged and dropped to any position within the grid.
• When included within a grid view, the Open Issues column will display a number, which indicates the count of Open Issues for that System Element or for the associated System Element if it is displayed for a Task record.

...

New functionality allows Users to now purge Case records, as well as any associated Work Tickets, via the All Cases, Work Packages, and Issue Monitor views.  This This feature provides the ability to remove duplicate or erroneously created Cases. Previously, Users' only way to address such Cases was to transition such Cases them to a Canceled status. 

Purging a Case record(s) is an administrative function, which involves a two-step confirmation and is dependent on the following:

...

User-Friendly Account Reactivation through Reactivation Policy Options

...

As a security measure, InfraLink User Accounts are automatically deactivated after a period of inactivity. The length of that inactivity period is defined by the instance administrator, but most instances utilize the default setting of 35 days. User Accounts may also be manually disabled by an administrator for a variety of reasons, such as a User no longer supporting a project.

Historically, to regain access to an instance, the User had to contact the instance administrator or Helpdesk to request account reactivation. With Users working a variety of shifts across a number of time zones, this process could sometimes experience delay.

Reactivation Policy per Authentication Provider

To improve the User experience, InfraLink now offers two new features supporting the the timely reactivation of User Accounts:

1. For User Accounts Automatically Deactivated due to inactivity, InfraLink will automatically reactivate the account upon the User's successful authentication. 
2. For User Accounts Administratively Disabled, a User's attempted login will trigger an email to instance administrators, advising of the reactivation request. With this scenario, an administrator must log in to the instance and manually approve or deny the request.

an Account Reactivation Upon Successful Authentication setting, configurable per Authentication Provider. This setting offers two options:

• Reactivate - Upon successful authentication, InfraLink will automatically reactivate an Inactive account. 
• Request Reactivation (default) - Upon successful authentication, InfraLink transitions the Account to the Reactivation Request status and notifies administrators of the same.

To effectively apply the reactivation policies, InfraLink now differentiates To effectively apply the account reactivation policy, InfraLink will differentiate between Automatically Deactivated and Administratively Disabled accounts. Specifically,  the User Account status will be set to "Inactive" after the instance-defined period of inactivity

...

, and the User account status will be set to "Disabled" when the account is manually disabled by an administrator.

...

Reactivate policy Impacts:

• For User Accounts Automatically Deactivated due to inactivity, InfraLink will automatically reactivate the account upon the User's successful authentication. 
• For User Accounts Administratively Disabled, a User's attempted login will trigger an email to instance administrators, advising of the reactivation request. With this scenario, an administrator must log in to the instance and manually approve or deny the request.

Request Reactivation Policy Impacts:

• For User Accounts Automatically Deactivated, a User's attempted login will trigger an email to instance administrators, advising of the reactivation request. With this scenario, an administrator must log in to the instance and manually approve or deny the request.
• For User Accounts Administratively Disabled, a User's attempted login will trigger an email to instance administrators, advising of the reactivation request. With this scenario, an administrator must log in to the instance and manually approve or deny the request.

What You Will See in the User Interface:

•     The Accounts grid view displays two new "User Status" filter options:
  
  • Disabled: Displays accounts that have been Administratively Disabled (not related to accounts that were auto-deactivated due to inactivity).
  • Reactivation Request: Displays accounts that were disabled that have attempted to log back in.
• The "Change Status" widget at the top of the Accounts grid view now presents the option to "Disable" an account alongside "Terminate" and "Activate" actions.

PowerDB Integration Service 

...

When a User attempts to log in to an Administratively Disabled account, InfraLink will email the following message to instance administrators, "This is an automated message to inform you that the MCDEAN user account of _Insert Name_ has requested reactivation and requires review." For administrators' convenience, the email will also include a link to the instance account.

What You Will See in the User Interface:

•     The Accounts grid view displays two new "User Status" filter options:
  
  • Disabled: Displays accounts that have been Administratively Disabled (not related to accounts that were auto-deactivated due to inactivity).
  • Reactivation Request: Displays accounts that were disabled that have attempted to log back in.
• The "Change Status" widget at the top of the Accounts grid view now presents the option to "Disable" an account alongside "Terminate" and "Activate" actions.

PowerDB Integration Service 

PowerDB, an equipment testing platform, is designed to manage electrical power Assets including their test results, ongoing inspections, and reliability analysis through test instrument interfaces and entity specific data forms. To streamline the planning and execution of testing activities and to improve data integrity throughout an installation and/or maintenance life cycle, InfraLink now offers integration with PowerDB.

...