Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Scroll Exporter macro migration

Read Complete Release Notes

Scroll export button
scopecurrent
template-idc9a14909-8f27-452d-bca0-164bee1a9265
captionDownload this Page
add-onScroll PDF Exporter

Feature released in SummitAI Platform (Alps)

What's New?

With new Scripting option available on few of the pages of the SummitAI application, the Administrators can now write their own Java Script and CSS codes to customize the fields available on these pages.

The pages, which have Scripting option available, display a SCRIPTING icon on their respective ACTIONS panel. Currently, the SCRIPTING icon is available on the following pages:

  1. NEW INCIDENT page (Incident > User > New Incident)
  2. INCIDENT DETAILS page (Incident > User > Manage Incidents > Incident List > Select Incident)
  3. NEW SERVICE REQUEST page (Request > User > New Service Request)
  4. SERVICE REQUEST DETAILS page (Request > User > Manage Service Requests > Service Request List > Select Service Request)
  5. CHANGE RECORD DETAILS page (Change > User > Change Record List > Select a Change Record)
  6. PROBLEM RECORD DETAILS page (Problem > User > Problem Record List > Select a Problem Record)
  7. CONFIGURATION ITEM DETAILS page (CMDB > User > Configuration Item List > Select a Configuration Item)
  8. THEME CONFIGURATION page (Admin > Basic > Infrastructure > Themes > Theme Configuration)

    Note
    titleNote:

    The Scripting option is only available when you are editing an existing theme on the THEME CONFIGURATION page. The Scripting option is not available when you add a new theme on the THEME CONFIGURATION page.

Configuration

To enable the SCRIPTING option in the SummitAI application (on the above mentioned pages), select the check box, Enable Scripting, under the SCRIPTING section of the ROLE TEMPLATE - OTHER CONFIGURATION page (Admin > Basic > Users > Role Template > Select a Template from the LIST section > On the ACTIONS panel, click OTHER CONFIGURATION).

Also, to enable the SCRIPTING option, add the following key in the web.Config file:

<add key="ADM:DynamicScripting_EnabledPages" value="im_logticket.aspx,im_ticketdetail.aspx,sr_detail.aspx,cmdb_editconfigurationitem.aspx,pm_editproblemticket.aspx,cm_editchangerequest.aspx,adm_themeconfiguration.aspx,enduser_dashboard.aspx,sr_logservicecatalog.aspx" />


Note
titleNote:

The SCRIPTING icon  is displayed on the ACTIONS panel of the following pages: NEW INCIDENTINCIDENT DETAILSNEW SERVICE REQUESTSERVICE REQUEST DETAILSCHANGE RECORD DETAILSPROBLEM RECORD DETAILS, and CONFIGURATION ITEM DETAILS.

The Scripting feature is Tenant-specific for the following pages: NEW INCIDENTINCIDENT DETAILSNEW SERVICE REQUESTSERVICE REQUEST DETAILSCHANGE RECORD DETAILSPROBLEM RECORD DETAILS, and CONFIGURATION ITEM DETAILS.

For THEME CONFIGURATION page, the SCRIPTING icon  is present under the Application and End User Dashboard tabs, only when an existing Theme from the THEME CONFIGURATION page is edited.

The Scripting feature for Application and End User dashboard is Theme-specific.

While using any of the above mentioned pages, on clicking the  SCRIPTING icon present on the ACTIONS panel, the users are redirected to the SCRIPTING – PAGE NAME (TENANT) page where they can write their own Java Script and CSS codes to customize the fields present on the page. For more information, see Scripting.

Known Issues

The fields that are mandatory before Scripting cannot be made non-mandatory using the scripting functionality. If you make an already mandatory field as non-mandatory, chances are that it may or may not work successfully.

  • On the SCRIPTING page, the CONTROL drop-down is not a mandatory field, and so the CONTROL drop-down is not validated, on clicking SUBMIT.
  • On the SCRIPTING page, every time the Scripting for any one of the Tenants is activated and deactivated, new versions of the selected page are created.
  • On the SCRIPTING page, each time SUBMIT is clicked, a new version is created, even when there is no script change done by the user.