This new functionality enables users to request changes to the data center through custom build change request forms called Change Request Templates.
Change Request requires Data Center Operation: Change License
Change request templates
Change request templates are managed by Administrators (users with permission "Planning Work Orders") to prepare a Request Form in the DCO web client using the Change Management > Change Request Templates option. The Request Form is then filled in by users to request changes in the data center.
Each template has a Name, Activation state, and Form field to specify information about the change. Templates are flexible; multiple templates can be defined in the system. For example, you can create a template for adding equipment, another for moving items, and another for creating users or custom properties.
Administrators can create, edit, delete, activate, or deactivate a template. Only active templates can be used to create change requests.
Form fields that can be used in the template (and then in the change requests):
- Text input
- Numeric input
- Date input
- Multi-line text field
- Email input
- Select input (combo box)
- Radio button
- Genome selector
- Location selector
- Blank space - separator
The Genome selector allows you to specify the equipment model from the Custom Catalogue. This is useful for creating a template for adding equipment. You can specify the kinds of equipment (PDU, UPS, Server) and/or mounting types to select in the field.
Three value fields are available for publishing properties from a work order task to an asset: Barcode, Serial number, and Name.
You can use the Location selector to select the existing Location, Floor Plan, or Room from the data set.
You can define basic validation on each field to prevent users from submitting a change request with incorrect or missing information. For example, each field can be made optional or required; text fields can have a minimum or maximum length. When you edit the template form, you can enter values into the fields to see how they work. These values are not persisted.
The Administrator can define the form layout for four different screen sizes to make the form adjustable to the user's screen size when they are creating or editing a change request.
Creation, deletion, and editing change request templates are logged by the Audit log and can be verified in the desktop client by running the report.
A change request can be created by all non-tenant users in DCO based on templates created by an Administrator (a user with permission "Planning Work Orders") in the DCO web client: Change Management > Change Requests.
A typical scenario:
- A user creates a change request, and fills in the form. The change request can be saved as Draft.
- A Draft or a newly created request can be Submitted if all fields are filled in according to the validation specified in the form.
- The Submitted request is read-only and waits for an Administrator to act. The request can be Unsubmitted by the author if some corrections need to be done, which puts it back into Draft.
- The Administrator can do one of three operations on a Submitted change request:
- Approve: The Administrator has accepted and processed the request, for example, by creating a work order for executing the change.
- Reject: Indicates the change is impossible to complete.
- Require more information: The request status is changed to Need update. The author can modify the form data and resubmit the request.
- Closed: The final step, used when the request has been executed. The request can then be deleted by the author or the Administrator.
Requests in Draft state are only visible to the author; they are not visible to other users.
Requests in other states are visible only to the author and Administrators.
If the author of a request is removed from the system, requests in Draft and Needs Update states are deleted. Requests in Submitted, Rejected, and Approved states survive so administrators can act on them.
Requests in Approved state
If a request contains one Genome, the Admin can Copy Genome Properties to populate properties from the Genome in the request to an asset in an open work order. The values that are copied are: Barcode, Serial number, and Name. There is validation on the barcode to keep it unique in the model.
Note: The work order must be created in the DCO desktop client.
You can comment on requests in states other than Draft to allow further communication between the author and the administrator.
When a request changes state, or a comment is posted, a notification email is sent to interested parties:
- If the change or comment is made by the author of the request, email is sent to all administrators.
- If the change or comment is made by an administrator, email is sent to the author of the request.
Email is sent in the user’s preferred language.
Note: You must configure mail settings with the Mail configuration REST web service.
Creating, deleting and changing the request state is logged in the Audit log. You can run a report in the desktop client to view the audit log.
Barcode lock feature
When you import data via ETL, you can configure the option to lock the bar code, serial number, and name fields to avoid data changing from a synchronisation.
Improvements to reports
The U-space report was updated to include full-depth U-space. Free front, rear, and full depth U-space is now included in the report.
The Forecast report now includes the power capacity for planned changes in a room based on work orders.
Server management options moved from Webmin to the web client
The management of backup and restore have been moved to the new Backup and Restore page in the web client. See the updated backup and restore documentation here Backup and Restore.
Server log files can now be downloaded from the Download Server Log files page in the web client.
ETL and Power Monitoring Expert integrations can now be configured from the web client. See the updated documentation here ETL configuration.
- ITO log files have been removed from DCO.
- The ITO server must now be backed up separately.
- The ZipSlip vulnerability (CVE-2018-7806) has been fixed. CVSS score: 6.6, CVSS vector: AV:A/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H. The issue affects all previous versions.
- ZipSlip vulnerability allows authenticated users to upload malicious file which could contain path traversal file names, this could potentially allow for the arbitrary upload of files contained with the zip onto the server file system outside of the intended directory. See more on the Data Center Operation Software Vulnerability Fixes page.