Customize Service Manager User Interface

Last modified on 2022/08/01 17:33
Contents

Different platform accounts

Definition

Each Service Manager platform contains one to three different accounts:

  • Account 40000 (optional): Demo environment which contains a test case database with fake but consistent data on users, equipment, catalogs, projects, etc. This database is used to perform tests, conduct training and run demos using the standard configuration and to check the behavior of wizards and processes.
  • Account 50004: Production environment which contains actual data used on a daily basis by users.
  • Account 50005 (optional): Test environment which contains a sandbox database whith a copy of the production data. This database is used to run tests without affecting the production database or logged-in users.
EndDefinition

         ev itsm Accounts.png

Each of the accounts contains three CSS stylesheets. Open url.png See the description.

StyleSheetsDefinition
  • optimized.css stylesheet: Used to view the entire CSS stylesheet in a structured way.
  • optimized.min.css stylesheet: Contains the same data as the "optimized.css" stylesheet but in a more compact format. This ensures that it will be read faster by Service Manager for optimal performance when displaying pages.
  • customer_optimized.css stylesheet: A stylesheet that can be customized by customers who want to modify the Service Manager graphic interface, i.e. colors and text in the login page, menus, Home page, etc.

Caution

  • You cannot undo the copying of the sandbox database to the production database. You must first ensure that the entire configuration of the sandbox database has been correctly copied to the production database, otherwise it will be lost.
  • Any modification that has not been validated in the test account may have a significant impact on Service Manager, especially for integrations, workflows, business rules and alerts that perform batch updates.

Best Practice

  • Before implementing processes and configurations in the production database, you must validate them in the sandbox database.
  • You should copy the production database to the sandbox database on a regular basis so that the sandbox database contains up-to-date production data.
  • The three platform accounts are affected each time a new Service Manager version is installed. If you want to test the new functionalities of a version before using them in the production environment, you should install a second platform. To do so, please contact your EasyVista consultant.
             ev itsm Two platforms.png

Definition of a style guide for each account

Each Service Manager account can have its own style guide using a CSS stylesheet.

  • Data is found in the "easyvista/www/Styles" folder. Note: You must have one folder for each environment or for each style guide.
  • Data on the graphic interface is stored in the A_STYLE table in the EVO_ADMIN schema.
    • RELATIVE_PATH field: Name of the folder containing the CSS stylesheet and other graphic resources for the interface belonging to an account. This value refers to a folder stored in the "easyvista/www/Styles" folder.
    • STYLE_ID field: This is automatically generated when an additional row is created.
  • A_COMPANY table: To modify the style guide of an Service Manager account, copy and paste the STYLE_ID value found in the A_STYLE table.

Example

Use of two different style guides

  • A_STYLE table:
    • Default style guide, points to the "easyvista/www/Styles/Easyvista_Prod" folder.
    • Sandbox style guide, points to the "easyvista/www/Styles/Easyvista_SandBox" folder.
             Customize_EZV_A_STYLE_STYLE_ID.png
  • A_COMPANY table:
    • The production database (account 50004) and test database (account 40000) use the default style guide.
    • The sandbox database (account 50005) uses the sandbox style guide.
             Customize_EZV_A_COMPANY_STYLE_ID.png

Procedures

         Fundamentals - Connexion page.png

How to force a default account on the login page

1. Copy index_prod.html and index_sandbox.html pages from easyvista/www/login_saas folder to easyvista/www folder.

2. Open http(s)://<EasyVista platform name>/index_prod.html and http(s)://<EasyVista platform name>/index_sandbox.html.
 You access the production database and sandbox database login pages. Note: The Account field is hidden.

3. Modify the httpd.conf file to force an account by default. Note: The file is located in the conf folder where Apache was installed.

4. Restart Apache services to integrate the modifications.

example  Configuration of the DirectoryIndex section in the httpd.conf file

  • Replace:
<IfModule dir_module>
   DirectoryIndex index.html index.php
</IfModule>
  • By:
<IfModule dir_module>
   DirectoryIndex index_prod.html
</IfModule>

How to modify the logo on the login page

Note: Images are stored by default in the easyvista/www/login folder.
 

Modification of the standard logo in http(s)://<EasyVista platform name>/index.php

1. Go to the easyvista/www/login folder.

2. Replace the image called logo_ezv.png by your own logo.
 

Customization of the logo based on the account

1. Modify row 16 in the login_prod.html and login_sandbox.html pages.

,logo:'<img src="/Styles/CLIENT_1/login/logo_prod.png" border="0">'

example  

  • In the production database, display logo_prod.png ==> index_prod.html page
,logo:'<img src="/login/logo_prod.png" border="0">'
  •  In the sandbox database, display logo_sandbox.png ==> index_sandbox.html page
,logo:'<img src="/login/logo_sandbox.png" border="0">'

How to modify graphic elements

Each account has its own stylesheet. You can therefore modify the graphic elements for each graphic interface.

      Open url.png  See the the graphic elements you can modify using the CSS stylesheet

Tags:
Powered by XWiki © EasyVista 2022