Versions Compared

Key

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

...

Case Bulk Status Transitions Import File

Column Name

Details

UUIDIf specified, the UUID is used to identify the Case. This field can be blank if the Item # is specified.
Item #If UUID is not specified, then the Item # is used to identify the Case. This field can be blank if the UUID is specified.
Target Status

Required. 

This column denotes the Status to which the Case transitions. The target Status must be a valid target Status (i.e., correctly placed in the Case Workflow), and the Target Status Name should be entered and not the Transition Name. For example, the Transition Name might be "Acknowledge" but the Target Status name is "Acknowledged Case" so "Acknowledged Case" should be the entry in the CSV file.

Effective TimeThis column marks the Date and Time (formatted mm/dd/yyyy hh:mm:ss AM/PM) of the transition to that status. If left blank, the Default Effective Time from the "Import Transitions" upload form will be utilized. If both this field and the "Import Transitions" upload form Default Effective Time are blank, then the current Date and Time at the time of processing the CSV row will be used. Transitions can also be backdated if necessary. 
CommentsThis column allows Users to add a comment for the Case transition. If blank, the Default Comment from the "Import Transitions" upload form will be utilized. If both this field and the "Import Transitions" upload form Default Comment are blank, “Case Transitioned via import” will be utilized for the transition comment.


System Element Bulk Status Transitions Import File

Column Name

Details

UUIDIf specified, the UUID is used to identify the System Element. This field can be blank if the Unique ID is specified.
Unique IDIf UUID isn't specified then the Unique ID is used to identify the Case. This field can be blank if the UUID is specified.
Target Status

Required.

This column denotes the Status to which the System Element transitions. The target Status must be a valid target Status (i.e. correctly placed in the System Element Workflow), and the Target Status Name should be entered and not the Transition Name. For example, the Transition Name might be "In Service System Element" but the Target Status name is "In Service " so "In Service " should be the entry in the CSV file.

Effective TimeDate and time of the transition, in format mm/dd/yyyy hh:mm:ss AM/PM. By allowing a date and time to be specified, transitions can be backdated to when the work was performed. If blank, the Default Effective Time from the transition upload form will be utilized. If both this field and the form Default Effective Time are blank, then the current datetime at the time of processing the CSV row will be used. Transitions can also be backdated if necessary. 
CommentsThis column allows Users to add a comment for the System Element transition. If blank, the Default Comment from the "Import Transitions" upload form will be utilized. If both this field and the "Import Transitions" upload form Default Comment are blank, “Transitioned via import” will be utilized for the transition comment.


What You Will See in the User Interface:

...

Task Update and Files Bulk Import FIle

Column Name

Details

ID

Required

The Task ID can be determined by adding the “ID” column to the All Tasks grid view.

Name

Task Name. This is not used by the import process but is something that a Project Administrator can use to help prepare and validate the information.

System Element

The System Element ID is not used by the import process but is something that a Project Administrator can use to help prepare and validate the information.

Completed

The date and time a Task is completed, in the following format: mm/dd/yyyy hh:mm:ss AM/PM.

This will only be utilized, if the Task (based on the ID) is in an Open or In Progress status.

Completed By

The User who completed the Task.

The User name must match exactly to their Account in InfraLink and they must have the permission to complete the Task. This will only be utilized, if the Task (based on the ID) is in an Open or In Progress status.

File

File to attach/replace to the Task. This will be the file name (including extension) of the file in the prepared ZIP file. Files can only be uploaded to Tasks configured to have a work form.

Comments

Comment for the Task Update. If none specified, the comment from the “Update Comment” in the "Import Task Updates and Files" upload form will be utilized.


Error Checking

The below table summarizes error checking that is performed via the Import process. Reference this table to better understand inputs and what can be altered for a successful import. 

Task Status

Task Requires Work Form

Work Form in CSV

Completion Info in CSV

Result

Open

Yes

Yes

Yes

Validate and Process

Open

Yes

Yes

No

Error - Must complete Task to upload Work Form

Open

Yes

No

Yes

Error - Task completion requires a Work Form

Open

Yes

No

No

Error - No completion data or Work Form present

Open

No

Yes

Yes

Error - Task not configured for a Work Form

Open

No

Yes

No

Error - Task not configured for a Work Form

Open

No

No

Yes

Error - Validate and Process

Open

No

No

No

Error - No completion data or Work Form present

In progress

Yes

Yes

Yes

Error - Cannot attach Work Form to in progress Tasks

In progress

Yes

Yes

No

Error - Cannot attach Work Form to in progress Tasks

In progress

Yes

No

Yes

Error - Task completion requires a Work Form

In progress

Yes

No

No

Error - No completion data or Work Form present

In progress

No

Yes

Yes

Error - Task not configured for a Work Form

In progress

No

Yes

No

Error - Task not configured for a Work Form

In progress

No

No

Yes

Validate and Process

In progress

No

No

No

Error - No completion data or Work Form present

Completed

Yes

Yes

N/A

(1) If form previously loaded, update form (2) Otherwise the Task was completed in InfraLink and the form filled out in InfraLink, therefore, Error - Work Form cannot be updated

Completed

Yes

No

N/A

Silently skipped

Completed

No

Yes

N/A

Error - Task not configured for a Work Form

Completed

No

No

N/A

Silently skipped


Note
titleBulk Completion Limited to Device Tasks at Present

Functionality is currently limited to Device Tasks. Similar capabilities for PM Tasks may become available with a future release.

...

Gliffy Diagram
displayNameImport Task Updates and Files
nameImport Task Updates and Files
pagePin23


Add Open Issue Flags to Multiple System Element Views

...

 

Gliffy Diagram
macroId95cc7173-1bd7-4fb6-9838-44a03e1b01f9
nameOpen Issues Flagged in View
pagePin1
 


Filter All Cases View by List of Case Numbers

...

Gliffy Diagram
namePaste Case # from Excel
pagePin1
 


Purge Case Records

...

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 feature provides the ability to remove duplicate or erroneously created Cases. Previously, Users' only was to transition such Cases to a Canceled status. 

...