...
Column Name | Details |
|---|---|
| UUID | If specified, the UUID is used to identify the System Element. This field can be blank if the Unique ID is specified. |
| Unique ID | If UUID isn't specified then the Unique ID is used to identify the CaseSystem Element. 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 Time | Date 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. |
| Comments | This 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. |
...
- 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:
...
To improve the User experience, InfraLink now offers an Account Reactivation Upon Successful Authentication setting, configurable per each Authentication Provider. This setting will be set to one of the following valuesThis 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.
...
| Note | ||
|---|---|---|
| ||
For additional information on PowerDB integration with InfraLink, contact InfraLink SupportHelpdesk. |
| Excerpt | ||
|---|---|---|
| ||
Highlighted features include: Bulk Status Transitions via Import; Bulk Completion of Device Tasks via Import; Add Open Issue Flags to Multiple System Element Views; Filter All Cases View by List of Case Numbers; Purge Case Records; User-Friendly Account Reactivation through Reactivation Policy Options; and PowerDB Integration Service -. |