...
Planned Dates for System Element Life Cycle Statuses
...
System Element records now support User-defined target dates for each status within that System Element's Life Cycle. That is, a User can define the date on which the System Element should transition to a particular status (i.e., the Planned Date).
Beyond providing progress visibility at the System Element Details, configuring these performance targets now informs InfraLink's deployment capabilities. With the latter, task-based workflows group related Tasks into a Work Package Case that is tied to a System Element Life Cycle Status. For example, all Tasks associated with the installation of a device (i.e., transitioning that device to the Installed status in InfraLink) are included within a Work Package. That Work Package Case should, of course, have a due date. Now, when the Work Package Generator runs nightly, Work Package due dates are automatically calculated based on the Planned Dates configured for the corresponding System Elements.
To define Planned Dates for System Element Life Cycle Statuses, a User must have System Element → Update Permissions. These target dates can be configured from the System Element Details panel or imported via the Device/Equipment List grid view.
| Note | ||
|---|---|---|
| ||
InfraLink restricts Users from changing a Work Package Case due date via the UI once the application has determined that Case's due date based on the configured Planned Dates. |
What You Will See in the User Interface:
- Planning Section in System Element Details Panel - A System Element Details panel is displayed when the System Element is selected from an applicable grid view (e.g., Device/Equipment List). This details panel now includes a Planning section. Here, a grid lists all statuses within that System Element's Life Cycle. To the right of those statuses, are two columns, Planned Date and Actual Date.
- Clicking the status line, just below the Planned Date header, opens a calendar widget for Planned Date selection.
- The Actual Date column tracks the actual date of transition to that status. This column also serves as a stop-light chart at the System Element level. On-time transitions are shown in green, and past-due transitions are shown in red.)
- Planned Date Data Columns, along with the corresponding filters, can now be added to both the Device/Equipment List and Work Packages grid views.
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
Task-Based Case Status Transitions to align with Task Status Transitions
...
Task-based Cases (i.e., Cases auto-generated from Work Packages) largely depend on the progress of the associated Tasks. Traditionally, as the associated Tasks progressed through their workflow, the Case remained static unless it was manually transitioned by the User. To improve the User experience and maintain data integrity, Instance Administrators can now configure Case Status transitions to auto-progress based on two Case Status Business Logic settings, one existing and one new. The existing Business Logic setting is Require all tasks...Completed, and the new Business Logic setting is Tasks in Progress - Automatically transition to this status when task progress starts.
- If a Case Status has Tasks in progress - Automatically transition to this status when task progress starts Business Logic setting checked, InfraLink will attempt to transition the Case to that Status when at least one Task is in an In Progress- or Completed-type status. That is, if the first of a group of Tasks transitions to an In Progress or Completed status and the current status of a Case does not have the Tasks in progress - Automatically transition to this status when task progress starts Business Logic setting checked, then InfraLink will attempt to transition the Case to the next status with that Business Logic setting enabled.
- If a Case Status has Business Logic setting Require all Tasks....Completed checked, InfraLink will attempt to transition a Case to that status when all associated Tasks have been completed for that Case. That is, if all Tasks are completed and the current status of a Case does not have the Require all tasks...completed Business Logic setting checked, InfraLink will attempt to transition the Case to the next status with that Business Logic setting enabled.
For both Business Logic settings, an automatic process will occur nightly and attempt to transition Cases as described above.
| Note | ||
|---|---|---|
| ||
For Task-based Cases, the status transitions can now be controlled via Case Business Logic settings. Thus, a User will have the ability to auto-transition a Case to a new status based on Task progress, even if that User does not have Case Update Permissions. |
...
| Warning | ||
|---|---|---|
| ||
If a Case Status has required Custom Fields that are not completed, the attempt to auto-transition the Status will not succeed. |
What You Will See in the User Interface:
- Business Logic settings for Case statuses will display a new option: Tasks in progress - Automatically transition to this status when task progress starts. This setting states that if at least one Task has been transitioned to an In Progress- or Completed-type status, InfraLink will attempt to auto-transition the Case to the associated Status.
| Gliffy Diagram | ||||||||
|---|---|---|---|---|---|---|---|---|
|
New Fields for PM Case and Work Package Details Panels: Actual Start, Actual Finish, Task Completion
...
Preventative Maintenance Cases and Task-based (i.e., Work Package) Cases will now display three additional fields within the Case Details Panel: Actual Start, Actual Finish, and Task Completion. The three fields reflect the dates and times Tasks reach Completed-type statuses (e.g., Completed, Unable to Perform), as well as the percentage of Tasks completed at the current time.
- Actual Start - The date/time the first Task in the Case reaches a Completed-type status.
- Actual Finish - The date/time all Tasks in the Case reached a Completed-type status.
- Task Completion - The percentage of Tasks that have reached a Completed-type status.
- All fields appropriately reset if a triggering Task(s) is reset (i.e., moved out of a Completed-type status).
- Displayed percentages are approximate.
What You Will See in the User Interface:
- The Actual Start, Actual Finish and Task Completion fields are now displayed within the Case Details panel for Preventative Maintenance and Task-based (i.e., Work Package) Cases.
| Note | ||
|---|---|---|
| ||
The Planned Start Date, which is set when creating a Preventative Maintenance Group, is also now displayed with in the Case Details panel. The Planned Start field was already available via grid views, but display within the Case Details panel enhances visibility. |
- The Actual Start, Actual Finish and Task Completion fields are also now available as data columns within the following three grid views:
- Status by Group
- All Cases
- Work Packages
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
Classification Policy Markings to Default for any Exports/Printouts
...
To enhance data security in InfraLink, the application will now add a FOUO, CUI, Confidential, or other Classification Policy marking to all InfraLink exports and printouts.
What You Will See in the User Interface:
- For any exports not completed via an Export Template, InfraLink will add a classification header and footer according to the Classification Policy for that Instance.
- An export warning will be affixed to any Export template advising Users that the information they are attempting to download is subject to the Instance's Classification Policy.
- All images uploaded to InfraLink will be water-marked according to the Classification Policy enabled for that Instance.
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
...