Change request

Change Request requires an IT Advisor: Change license. A change request can be created by all non-tenant users in ITA based on templates created by an Administrator (a user with permission "Planning Work Orders") in the ITA 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. Approved request can be Closed by the Administrator. After that 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. 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. Creating equipment using Change Requests Every change request in accepted state, having at least one genome selector can be used for equipment creation. It is allowed to have more than one genome selector which as a result will create more than one device. In order to create new equipment you have to have administrator permissions. In the ITA web client:  Change Management  >  Change Requests Find desired change request Make sure it is in accepted state Locate 'Create equipment' button Select one storage room from dropdown list Equipment will be created in selected storage room. ITA_change-request-create-equipment_360006638958.png Validation related to creating equipment using Change Requests In order to use Change Request for equipment creation it has to be validated What actions trigger validation? Validation is triggered by following actions: Submitting request Accepting request Creating equipment based on request What validation levels we define? Warning - will allow action to complete (eg. submit request). Yellow color in web client. Error - will not allow action to complete. Red color in web client What kind of validators we define? Barcode validator - Checks if every barcode set in genome selector is unique. This will not be validated if genome selector do not use barcode or barcode is empty. Genome type validator - not every product from custom catalog that can be selected in genome selector can be used for equipment creation. List of illegal product types: Breaker Breaker module Door Perforated tile Hacs Cacs Vertical Grille Window Wall Gap Water tank Block Person Custom property validators - used to validate mapping between form fields and custom property definitions. Form field is matched with custom property definition if it has the same label. Custom property type validator - checks if form field type and custom property type are matching. Form field type Custom property type Text String Number Integer, Decimal, String Email Email Location String Radio String Select String Custom property mandatoriness validator - checks if form field value was set when custom property definition is marked as mandatory. Custom property uniqueness validator - checks if form field value is unique among all equipment when custom property definition is marked as unique Custom property value validator - checks if form field value is correct depending on custom property type. What validator is being run on particular action? Validator Submitting request Accepting request Creating equipment Barcode Error Error Error Genome type Error Error Error Custom property - type Error Error Error Custom property - mandatory Not run Not run Warning Custom property - unique Not run Not run Warning Custom property - value Not run Not run Error

Change Request requires an IT Advisor: Change license. Change request templates are managed by Administrators (users with permission "Planning Work Orders") to prepare a Request Form in the ITA 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 Checkbox Select input (combo box) Radio button Header 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. Change request templates and equipment creation Some form fields can be now exported as Custom Property: Text input Numeric input Email input Location selector Radio button Select input (combo box) Every change request template having at least one genome selector can be used for equipment creation. During that process new device will be created based on genome selector included in template. Every form field exported as Custom property will be used to create new Custom Property and that Custom Property will be instantly assigned to the device. Custom Property 'Requestor' will always be created and assigned to every equipment. It contains name of user that requested device. Change request templates and equipment creation - validation In order to use template for equipment creation it has to be validated. Validation level Warning (W) - Warning occurrence will allow action to complete ( saving change request template ). Yellow color in web client. Error (E) - will not allow action to complete. Red color in web client Validators Label validator (E) - This validator checks if every form field defined in change request has unique label. We identify validation errors with labels therefore it is important to have every form field its own label. Custom property validators - used to validate mapping between form fields and custom property definitions. Form field is matched with custom property definition if it has the same label. Type custom property validator (E) - Validates if there is matched custom property definition. It checks if form field type and custom property type are matching. Form field type Custom property type Form field type Custom property type Text String Number Integer, Decimal, String Email Email Location String Radio String Select String

Change requests require an IT Advisor: Change license. Request changes to the data center using custom build change request forms called Change request templates. Administrators can accept requests and create equipment from them. See Data Center Change Requests for more information.