Difference Between Istanbul and Jakarta Release

5/3/2018 Difference between Istanbul and Jakarta release - IT Service Management - ServiceNow Community
 Question
Difference between Istanbul and Jakarta release

S by suprakash
created 10mo ago (edited 8mo ago) in IT Service Management
I want to know all the modi cation/deletion/addition in Jakarta release in comparison with Istanbul.
If any one can provide me any details other than release document or an link where the the differences are mentioned , it will be greatly helpful for
me..
Thank you
 Upvote (0) 12877 Views
 Accepted Solution See this answer in context
V vamsisaladi • 10mo ago
I have done some go through and con gured some updates in istanbul vs jakarta each application wise separated. feel
fee to browse through or go to speci c module you are looking for.
(mark answered if you nd this helpful so others can also look into it)
https://community.servicenow.com/community?id=community_question&sys_id=439ff22ddb58dbc01dcaf3231f961936 1/47
Business Management :
1. 1. Release Management:
Istanbul — No Update
Jakarta — New Features
The label for the DSL (Definitive Software Library) table is changed to DML (Definitive Media Library). But the table name
remained same — dsl and number generated for the dsl table is appended with DML instead of DSL
Now DML references to the rm_release table using the fields: Pending releaseandGenerated by release
1. 2. Time Card:
Istanbul — New Features
Time Sheet — It's a group of all time cards.
Time Card can added like
Manually by users by creating time cards for their assignments.

By copying from previous week time sheets.
By auto generate action that finds all active project task assignments for the user and generates time cards for them.
By scheduling a recurring job that finds all active project task assignments for the user and generates time cards for them.
Time Card Approval:
a. o Time card approvers can approve all the time cards in a timesheet
b. o Project managers can approve time cards related to their projects alone.
Remaining Effort: - This field can be configured to show remaining effort for a project task.
Project managers can configure if time cards should be generated for the project or for individual tasks.
Project managers can view the exception reports for the team members who have not submitted their time cards
for the current or the previous week.
Time card admins can configure the maximum number of hours per day or per week that can be in a timesheet.
For those who have Performance Analytics Premium license, two new dashboards (project manager dashboard and
user manager dashboard) have been introduced for time cards in Jakarta (Performance Analytics — Content Pack -
Project Portfolio Suite Dashboards)
Time sheet policies
By default, the Default time sheet policy is available with the system.
And part of this framework the following properties are removed and replaced by Time sheet policies
a. o com.snc.time_card.start_day
b. o com.snc.time_card.time_worked
c. o com.snc.time_card.autocreate
d. o com.snc.time_card.update.resource
e. o com.snc.time_sheet.max_hours_per_day
f. o com.snc.time_sheet.max_hours_per_week
g. o com.snc.time_card.update.effort
Worker portal
Project time category
Time card approver role
Functional changes
The field Generate time cards for top task only on Project form is deprecated. The level at which the time cards for a project
can be created is determined by the eld Allow time card reporting on
The time card property Update the task's 'Actual effort' based on the hours entered in the time card is replaced by the
field Update actual effort from time card in Preferences tab on the project form.
The property Default hourly rate used when processing time cards if we can't get a rate from labor rate
cards(com.snc.time_card.default_rate) is no longer accessible from time card properties. The property can be set from System
Properties.
IT Operations Management
1. 1. Event management
Launch a web application — From an alert that matches the conditions set in an alert rule.
Operational Metrics — It is enabled by a new plugin ITOM Metric Management (com.snc.sa.metric). It has prediction
function which projects expected metric values by learning from historical metric data.
Custom maintenance definition — It allows to define maintenance rules to mark CIs in maintenance status, where these
CIs are excluded from impact calculation.
Configue event collection from Zabbix - A default Zabbix
Correlated alert groups — It is displayed in dashboard alert panel. For that you have to drill down in an alert, in the Event
Management dashboard.
Monitor incoming alerts - Alerts that are members of correlated alert groups are indicated in the Alerts Console.
Personalized dashboard - Create a personalized dashboard query using Dashboard views.
Integration of Dependency Views map with Metrics Explorer view - In a Dependency Views map, you can switch to
metrics mode to display the Metrics Explorer with operational metrics data for CIs on the map. All map CIs are accessible in
the right-hand side pane, from where you can drill into metrics data.
CMDB alert groups - Service Analytics now also correlates alerts for CIs without historical data, based on the CI's
relationships in the CMDB.
Functional changes
Avoid impact to event processing during a platform upgrade: Event Management jobs that started running before the
upgrade commenced continue to run during the platform upgrade.
Identifier attributes: You can now change the default set of attributes that Service Analytics alert aggregation uses to form
patterns for alert aggregation.
Service Analytics correlated alert groups are now referred to as automated alert groups and are displayed along with the
other alert groups in the Event Management dashboard and the alert console.
Service Analytics root cause analysis (RCA) now also applies to alerts associated with manual services.
Operational Intelligence — This contains Operational Metrics and learns from historical metric data, builds standard
statistical models to detect statistical outliers and anomalies and raise anomaly alerts.
Collect event messages from cloud endpoints — Configure custom push connectors to connect to external event
sources. You can select to send events either through the MID Server or the instance.
Event rule designer — Create event rules to generate alerts for tracking and remediation. With this designer you can
a. o Transform information in events to populate specified alert field values and compose alert fields from
various values.
b. o Configure threshold rules that create or close alerts only when the incoming matching events exceed the
specified threshold.
c. o Bind alerts to CIs using CI identifiers.
Can configure a connector instance to collect events using the NagiosXIHP Operations Manager i (OMi) connector.
Quick response — To an alert by applying remediation or launching an application
WebService URL event collection — Configure the MID WebService Event Collector Context extension to enable the URL
method to push event messages from an external source to the MID Server. You can collect custom payloads in JSON,
XML, or plain text format. We have some pre built MID WebService Event Collector extensions in the base instance.
a. o AWS events transform script
b. o Azure events transform script

c. o Event collection from BMC TrueSight
Predictive alerts — Used to predict a sequence of future alerts for automated alert groups. You can use this information to
take preventive measures. (enable by setting the property "sa_analytics.pred.cl_enabled" to true)
Monitored services — View all services that are supported by Event Management, such as, alert groups, discovered
services, manual services, and technical services.
Promotion of anomaly alert — Users can create alert promotion rules, to create a regular Event Management alert that is
based on an anomaly alert.
a. o Event Management > Operational Metrics > Anomaly Alerts.
b. o Right-click an alert in the Alert Anomalies list and select Promote Anomaly Alert.
With this you can add a blacklist item to prevent the creation of a new Event Management alert that would otherwise
be created by an alert promotion rule. Right-click an anomaly alert and select Blacklist CI.
Functional changes
Navigation changes - Connectors and listeners are found under these menu options:
Event Connectors (Pull)
Connector Definitions
Connector Instances
Event Listener (Push)
Listener Transform Scripts

MID WebService Event Listener
MID SNMP Traps Listener
Automated alert groups - RCA can be applied to automated alert groups to identify root cause alert. This helps direct
resources to the root cause of a problem. To enable this set property "Enable Alert Correlation RCA".
CMDB alert groups - In addition to using hosting and containment relationships to form CMDB alert groups, there is now
also support for user defined suggested relationships.
Manual alert groups - The Service Analytics Alert Aggregation Learner learns the patterns of the alerts in manual alert
groups. This knowledge is then used with incoming alert streams. Service Analytics automatically forms automatic alert
groups according to the patterns in the manual alert groups.
Provide feedback about the usefulness of an alert group, you must use the feedback field on the alert form.
2. MID Server
MID Server pause - The MID Server can be temporarily paused to prevent it from polling the ECC Queue for work and from
sending Discovery results back to the instance.
MID Server upgrade - The MID Server is put into Upgrading status while an upgrade is being performed. If upgrade fails the
MID Server is put into Upgrade Failed status.
We also have validating and validating failed status new in Istanbul
MID Server version and user compatibility - MID Server list view and the MID Server form provide indicators to show you if
the version of the MID Server is compatible with the instance and also if MID Server user is configured correctly.
Privileged commands —
The dzdo privileged command is supported.
You can add new privileged commands to the Privileged Command [privileged_command] table and configure the
MID Server to use them in a predefined order.
You can create a special configuration for the pbrun privileged command that allows it to run as a profile.
Guided setup — A system that helps you download a MID Server and configure it to work with your instance, using a
series of easy-to-follow panels. (ITOM Guided Setup - > MID Server)
Credentials debug - A new section of the ECC queue payload is available to help troubleshoot issues with credentials:
<credentials_debug>.
Functional changes
MID Server selection criteria: In addition to IP ranges and capabilities, MID Servers can specify an additional selection criterion:
supported applications.(like orchestration , service analytics)
Role and settings validation - The system uses real-time validation of MID Server role assignments to prevent incompatible
settings. New business rules block unsupported MID Server role configurations and issue appropriate warnings.
Pre-upgrade testing - When a MID Server detects that it needs to upgrade, it automatically performs a series of short tests
that evaluate available disk space, access to the download site, and permissions required to execute certain file operations
on the MID Server host. If all these tests pass, the MID Server upgrade proceeds automatically. If any test fails, the upgrade
cannot proceed, and the instance publishes error messages to the MID Server Issue [ecc_agent_issue] table.
MID Server IP range auto-assignment - An instance can automatically assign MID Servers to IP ranges that represent
subnets in your network. The MID Servers must be running and valid and must have access to the subnets to which they
are assigned.
optional MID Server guided setup — Tasks added are
a. o A setup task to allow you to create SNMP and SNMPv3 credentials.
b. o A setup task to allow you to select available MID Servers for auto-assignment(IP-ranges) to discovered subnets.
Managing active issues - MID Server Issue [ecc_agent_issue] table displays active MID Server issues and publishes error
messages that pinpoint the most likely cause of the issue.
Post-cloning credential issues: Automatic processes detect and notify you of possible MID Server user credential
issues after instance cloning.
Resource threshold alerts: The MID Server reports its CPU and JVM memory usage back to the instance at a
prescribed interval, and the instance evaluates that usage against con gurable thresholds. If either threshold is
breached, the instance can log an issue. A new registered event allows users to create email noti cations or custom
scripts when CPU and memory thresholds are breached. Resource threshold alerting is disabled by default, but each
type can be enabled by setting system properties.
Pre-upgrade testing issues: When a MID Server detects that it needs to upgrade, it automatically performs a series of
short tests to determine if it is capable of upgrading. If any test fails, the instance publishes error messages in the
MID Server Issue [ecc_agent_issue] table, allowing an administrator to resolve issues prior to the actual upgrade.
User connectivity issues: Error messages published to the MID Server Issue [ecc_agent_issue] table can provide
insight into authentication and authorization failures involving MID Server users and help identify network
connectivity problems that prevent a MID Server from establishing a TCP/IP connection.
Disabling the Asynchronous Message Bus (AMB) Client - A MID Server connection parameter allows you to disable the
AMB client when it is not suitable for your environment.
Functional changes
Business rules for MID Server resource threshold alerting were renamed and now also evaluate CPU and memory usage.
Update mean on MID Server Status — Renamed to Update cpu mean on MID Server Status with added functionality.
Before it used to calculate avg value of 24hour CPU usage, when CPU data inserted in ECC Agent Scalar Metric
[ecc_agent_scalar_metric] table. Now when a record is inserted in the ECC Agent Scalar Metric [ecc_agent_scalar_metric]
table, this business rule triggers a script include that evaluates threshold settings to determine if the MID Server has breached
its configured CPU resource thresholds.
Update MID Server Status table — Renamed to Update max memory on MID Server Status with added functionality.
Before it used to calculate avg value of 24hour memory usage, when CPU data inserted in ECC Agent Scalar Metric
[ecc_agent_memory_metric] table. Now when a record is inserted in the ECC Agent Memory Metrics
[ecc_agent_memory_metric] table, this business rule triggers a script include that evaluates threshold settings to determine if
the MID Server has breached its configured memory resource thresholds.
IT Service Management
1. 1. Change Management
CAB Workbench — Change Advisory Board enables a CAB manager to schedule, plan, and manage CAB meetings.
(Activating the CAB workbench activates the Service Portal plugin)
a. o Create CAB definition: CAB Manager can define CAB based on which CAB meetings and their agendas are
created.
The other functions of CAB manager can add as part of CAB definition are :
Set CAB meeting schedule

Create series of CAB meetings
Set CAB meeting agenda
Specify discussion time for each agenda item
Set CAB meeting board
Set CAB meeting delegates
Notify CAB attendees
a. o Create individual CAB meetings: The CAB manager can create individual CAB meetings outside of a CAB definition.
b. o Ensure change requests are CAB approved: Normal and emergency change requests can now be marked for CAB
approval via the CAB required check box on the Change Request form.
c. o Set CAB meeting delegate: Change requesters can now specify a delegate to attend the CAB meeting on their behalf
via the CAB delegate field on the Change Request form.
d. o View CAB calendar: The change manager and change requester can view the CAB calendar and drill down into the
specifics of CAB meetings.
e. o Approve or reject change requests: CAB managers can approve or reject change requests during the CAB meeting,
which are then processed through the appropriate workflow.
f. o Record and view CAB meeting notes: The CAB manager can record meeting notes, which can be viewed later by CAB
members and change requesters.
Configuration item (CI) healthCI health dashboard can now be accessed from a health icon available next to the
Configuration item field on the Change Request form.
Change Management property - It controls at which level logging should be displayed.
(com.snc.change_management.cab.log) It is activated with CAB Workbench.
Change Management Best Practice Plugin — It updates change form and some functionalities
a. o Added the Outages related list to the Change Request form.
b. o Sends notifications to the requester when a change is approved and scheduled, when work has begun, and when
work has been completed.
c. o Sends notifications to the requester when a change request is put on hold or removed from on hold.
d. o Displays a report showing the list of planned outages, so that decisions about scheduling change requests can be
made accordingly.
e. o Reorganized the Change form to better reflect the needs of a change manager or requester.
f. o Added the Task SLA related list and rearranged related lists.
g. o Updated the fields in the Change Request popup view to show the most relevant information.
h. o Added approval history to the change request activity log.
i. o Added the Requested by field to the Change Request list view.
j. o Added Planned start date, Planned end date, and Type fields to the Change Task form.
k. o Rearranged the fields on the Change Task form to contain the fields that provide most value for your users.
l. o Updated the mandatory and restricted Change Request properties for standard Change templates.
m. o Added that the change task type Implementation must fall within the planned start/end dates of the related change
request.
n. o Made Work notes mandatory when a change request is canceled.
o. o Added new state values: Pending, New, Work in Progress, Closed, and Canceled to the Change Task form.
p. o Displays all configuration items directly affected by a change on the Affected CI's related list.
q. o Provides a warning that the planned end date is prior to planned start date now occurs on the Change Request
and Change Task forms.
Note: Customers who upgrade from a previous release must request the plugin, because activating it could break existing
customizations.( com.snc.best-practice.change.jakarta)
Standard change properties - A two-step verification process has been introduced in requesting a standard change from
service catalog. The process redirects the requester from a standard change template to a change request that can be
viewed prior to submission. The two-step process is enabled in standard change properties.
Standard change proposals can now include change tasks. When approved, the resulting standard change templates generate
change tasks.
CAB workbench —
a. o In the CAB Definition and CAB Meeting form, the Order button is removed and the Add Sort button was added
for agenda management.
b. o The CAB Date field is now updated to the most recent CAB meeting date that the change request is associated
with.
c. o The Allotted Time field has been added to the Agenda item list and displays the allotted time for that item. This
allows the CAB manager to override the default amount of time per agenda item.
d. o The meeting start time and meeting end time fields are now mandatory.
e. o The form widget has been enhanced to allow more lines of content to be displayed in the planning form section.
Functional changes
Impacted CI's/Services: allows any class of CI to be specified in the Impacted CI's/Services related list. Previously,
it only allowed business services to be included.
CI's Affected by Task: creates a relationship between all CI's specified in the Affected CI's related list on the Change
Request form and the Affected by Task related list on the Configuration Item record.
CI's Impacted by Task: creates a relationship between all CI's specified in the Impacted CI's/Services related list on
the Change Request form and the Impacted by Task related list on the Configuration Item record.
1. 2. Incident Management
Incident Management Best Practice Plugin — It updates change form and some functionalities
a. o Makes the Work notes field mandatory when there is a change in the incident priority, so that incident
managers can more easily track what caused a change in priority.
b. o Added the Request related list, so that you can more easily track a request opened from an incident.
c. o Clears the Assigned to field when the assignment group is changed.
d. o Added the Parent Incident field to the related forms section, so that your users can see which incidents
have parent records.
e. o Changed the field labels Closed code and Closed Notes to Resolution code and Resolution notes.
f. o Updated the On Hold choice list to include Awaiting Caller, Awaiting Change, Awaiting Problem, and
Awaiting Vendor. If Awaiting Caller is selected, it is mandatory to enter additional comments.
customizations.( com.snc.best-practice.incident.jakarta)
1. 3. Problem Management
Problem Management Best Practice Plugin — It updates change form and some functionalities
a. o Makes the Work notes field mandatory when there is a change in the problem priority, so that problem
managers can more easily track what caused a change in priority.
b. o Added the Major Problem check box and the Review Outcome field to facilitate the management and
documentation of major problem reviews.
c. o Added the report Incident Trend by Configuration Item, so problem managers can view incident trends by
service or configuration item (CI) over time to determine potential problems.
d. o Updated the Problem form layout, adding the fields Business service, Impact, Urgency, Closed, and
Closed by and changed the layout of the form to make it more user-friendly.
e. o Makes the Priority field read-only. This field is set based on the impact and urgency of the problem.
f. o Hides the Known error field on the Problem form and the Known error flag is set to true when the
problem is set to the state Known Error.
g. o Updated the UI action Close Incident to Resolve Incident enabling problem owners to resolve and
communicate updates to child incidents when a resolution has been identified. Your users can review and confirm the
resolution.
customizations.(com.snc.best-practice.problem.jakarta)
1. 4. Service Catalog
New Variables — Email and URL types are new variable types available.
Customizable variable display -
Service Catalog > Catalog Variables > Variable Default Size (On global level)
For Individual form level changes the width option is available on Type Specifications Tab.
Wish list - You can save partially configured catalog items to your wish list, and finish if off later. (not supported for Order
Guides and Wizards.)
Record producers reporting - Create reports that map the record producers to the base records generated by them.
(Service Catalog > Request Reports > Created by Record Producers)
Required check box: You can mark a check box variable as mandatory by selecting the Required Checked check box.
Help text : If you select the Show help option for a variable, you can use the Instructions field to enter HTML help text.
Selecting the Always Expanded field opens the help text when the form loads always displaying the help text.
Service Catalog currently does not support List v3.
Debug UI Customization — this is a new submodule introduced under the Catalog Administration module, enables
catalog administrators to perform a health check of Service Catalog pages, enabling catalog administrators to pinpoint the
issue and self-heal.
It can be enabled or disable under Catalog Administration module.
Variable Watcher —tab is available for Service Catalog variables. A catalog administrator can monitor individual variables
for changesâ€¯inâ€¯their state and value due toâ€¯Catalog Client Scripts, Catalog UI Policies, and Catalog Data Lookups.
Variable Action Loggeror a full analysis of all the client-side actions affecting the state and values of every variable on a
catalog form.
Applies on Target Record — check box available in the Catalog UI Policies and Catalog Client Scripts submodules. It
provides full feature support for variable editors on records created via record producers (only for task-extended tables).
Catalog UI Policies, Catalog Client Scripts, Catalog Data Lookups, Reference Qualifiers, and dependent reference fields are
supported on the default variable editor used for records created via record producers.
New Variables
IP Address: To capture the IPv4 and IPv6 data for a catalog item. Under the Validation Scripts submodule, a validation
script type associated with this variable is available.
Duration:
Changes on Existing variables
Apart from the Macro, Macro with label, and UI page variable types, Service Portal supports all types of variables.
Note: Convert the UI Macro variable to portal widget and associate with the same widget.
Service Portal supports two-column layouts only for the top-level containers.
You can specify example text as a hint for a variable before you enter a value.
Variable set extension —When you apply Catalog UI policy Actions and GlideForm APIs (setReadOnly, setMandatory
setDisplay) on a variable set, the actions are applied on every variable within the variable set. You can make variables read-
only and mandatory, or change the display of variables by performing these actions on the corresponding variable set. The
same feature is available for containers as well.
Catalog UI Policy condition builder - Variables associated with a variable set have the variable set name associated with
them in the Catalog UI Policy condition builder as well as in the Catalog UI Policy Actions list.
Automated Test Framework for Service Catalog - Catalog administrators can write automated tests to validate their
catalog items because Service Catalog is supported in the Automated Test Framework (ATF).
Record producer redirection settings — control the behavior of record producer after its generation in the UI.
All fields except the variable fields have been removed from the Catalog UI Policy condition builder to avoid any confusion
when creating Catalog UI policies.
The Description field has been removed from the Question tab on the Variable form.
Functional changes
When Copy UI Action, all the associated variables, Catalog UI Policies, Catalog Client Scripts, and Catalog Data
Lookups are copied along with the catalog item. product model associated with the catalog item is not copied unless specified.
1. 5. SLA
New Roles — sla_admin and sla_manager

SLA Time Line —
a. o Filter: To filter off the data that the timeline displays.

b. o Task SLA Details: A section to displays information on stages, task updates, and out-of-schedule for SLA timeline.
c. o Stepped zoom: To provide several zoom in or out levels to control SLA timeline zoom resolution.
d. o Toggle button: To show/hide task updates that did not cause an SLA stage.
e. o Ability to debug or verify: To check if a task is mapped appropriately with a defined SLA using the SLA timeline.
f. o Ability to select business elapsed time or business time left: The selection is saved into user preferences for
display in the SLA timeline.
g. o Reference picker: To preview the task selection to be introduced in the SLA timeline.
h. o Refresh button: To refresh the SLA timeline with the latest values of the task SLA.
i. o Carousel navigation: To take you through all the task stages easily.
j. o Ability to select a different time zone from the SLA timeline has been added.
k. o Ability to calculate the breach date and time of the SLA from the Due Date field of the task to which the SLA is
attached to.
Service Level Agreement Best Practice Plugin — It updates change form and some functionalities
a. o The SLA notification and escalation workflow sends notifications when a task reaches a certain percentage
of its allotted SLA duration.
b. o The Service Level Target field has been added for filtering, searching, and reporting on different service
level target types.
Note: Customers who upgrade from a previous release must request the plugin, because activating it could break
existing customizations.(com.snc.best-practice.sla.jakarta)
Reporting and Dashboards
1. 1. Reporting
Istanbul — No Features added
Classic Reports list layout (Reports > View / Run) is removed. Previously, it was possible to enable this version of the
Reports list layout by setting the system property glide.ui.report.new_home to false. This property setting no longer has an
effect and only the redesigned Reports list layout is available.
Custom chart creation is removed.
Functional changes
a. o View and run reports in the mobile app.

b. o PDF functionality improved —Fields printer friendly form, Using set number of datapoints to prevent JVM running out of
memory and performance issues.
c. o UTC date value field was changed from Date to DateTime, to prevent a one-day shift in Calendar reports.
d. o Pivot report and multilevel pivot report titles display.
e. o Drill down from several report types to a list with a drilldown view displays the specified drilldown view.
f. o Unauthorized users receive the correct error message when they try to delete or modify a report.
g. o The Highlight based on option in calendar reports is now persistent.
Import External Data - reports based on data maintained outside of your instance.
Content on Service Portal - display on Service Portal using Service Portal widgets.
Report Designer - Configure a report, preview it, iterate and adjust it, and then share the report using the integrated Share
panel.
Accessibility — standardized Report Home, Report Designer, and reporting content (e.g., widgets on dashboards) as per
Web Content Accessibility Guidelines Level A.
Highcharts 5 —
Interactive analysis - Launch a detailed analysis of your data from any list.
Functional changes
a. o The Custom Charts plugin is removed.

b. o The Chart Color field retains its value when the groupby or stackby field values are changed and when
switching between chart types in Report Designer.
c. o Multiple datasets are available to all users. Previously Performance Analytics Premium was required.
d. o When using Insert and Stay, color rules are not copied to the new report.
e. o Multilevel pivot report improvements:
f. o Options added for displaying row and column lines.
g. o Added automatic collapsing and expanding of rows.
h. o Enhancement fixes for columns headers.
i. o Enhancements to PDF export and scheduled export.
j. o Improved word wrapping.
k. o Color coding added to single score reports.
l. o Changed the configuration of the report_security plugin to default on upgrades. Users who upgrade no longer
have to contact security to install this plugin.
m. o Improved the loading of the table list.
n. o Fixed warning messages in the zboot console log.
o. o Improved default color list for multiple datasets.
p. o Enabled dot walking on the Aggregation field for Average and Sum aggregation.
q. o List functions now available on the Report list
r. o The [report_view] table is no longer populated with new entries. The Report Stats list enables you to view how
often each of your reports is run and how long it takes for the reports to run. For more information, see Report statistics.
1. 2. Dashboards
Responsive canvas dashboards are introduced if not enabled set property glide.cms.enable.responsive_grid_layout to true. If
property doesn't exist you can create one. (like in helinki).
All users can create or view dashboards - When responsive canvas is enabled, users with any role can create and share
dashboards. Users without a role can view dashboards that are shared with them.
New dashboard permissions and sharing - When responsive canvas is enabled, dashboards use more flexible and
granular dashboard-specific permissions, which separate view and edit rights.
On responsive dashboards, tabs can no longer be linked between dashboards. Tabs that were linked between multiple
dashboards in previous releases remain linked after upgrade.
On responsive dashboards, you can no longer specify a home tab on a dashboard. The leftmost dashboard tab is always
the home tab.
Responsive dashboard tabs cannot be published as a homepage. Instead, create a single-tabbed dashboard and share it
with other users.
Functional changes
a. o All dashboards have an Owner field.

b. o Only users with access to the Slow Performance Graphs widget can add this widget to dashboards.
c. o Many changes to Interactive Filters.
d. o Content packs for Application Portfolio Management, Discovery, Human Resources Service Management Scoped, and
Incident Spotlight.
Once Responsive canvas/Dashboard is enabled :
New dashboards use responsive canvas and existing dashboards are converted to responsive canvas.
Users receive an email notification when a dashboard is shared with them.
Use the Restrict to roles field to specify roles required to access the dashboard.
Dashboard quick layouts were moved to the Configuration pane.
Many dashboard actions have been moved to the context menu.
Add a tab from the Configuration pane or context menu.
Breakdowns and breakdown element appear under the dashboard header.
Responsive Canvas dashboards are enabled(introduced in Istanbul)
Create a dashboard version of a homepage - create responsive dashboards from existing homepages, providing better
accessibility, improved sharing, and easier widget layout.
Cascading interactive filters - Dashboard administrators can create hierarchical interactive filters. Selecting a filter value
at a higher level automatically filters the choices available for lower-level filters in the hierarchy.
Software asset management -
Solution library - Easily install and update dashboards and visualizations for Performance Analytics content packs.
 Helpful (22)
15 Replies ( Latest reply 2mo ago by vamsisaladi ) Show All Replies
V vaibhavbhatnagar • 10mo ago
Hello,
See if this is helpful Features and changes by product
 Helpful (1)
gauravchoudhury Forum Level 2 • 10mo ago
Hi Suprakash,
If you are looking for something very speci c, then I would suggest you refer to the release notes for both Istanbul & Jakarta.
1. Istanbul Release Notes (Click Here)

2. Jakarta Release Notes (Click Here)
Also, you can refer to some Jakarta Highlights in this thread.
 Helpful (2)
Shiva Thomas • 10mo ago
Hi Suprakash,
If you're looking for a one page quick overview of the differences, you can read my blog article: Jakarta Sneak Peak
Also, this slide may be useful to you.
 Helpful (4)  Show Replies
Rajashekhar Mushke Forum Level 1 • 10mo ago
Hi Dutta,
Please Refer Below articles,
Upgrading from previous families
If your instance is more than one family behind, you can upgrade directly from your current release to your target
release. For example, if your instance is on Geneva, you can upgrade from Geneva directly to Istanbul.
ServiceNow fully supports the current and two previous family releases, as well as any interim hot fixes and patch
releases. For more information about release terminology and availability phases, see the ServiceNow Release Cycle
[KB0547244] article in the HI Knowledge Base.
V vamsisaladi • 10mo ago 

I have done some go through and con gured some updates in istanbul vs jakarta each application wise separated. feel fee to browse
through or go to speci c module you are looking for.
(mark answered if you nd this helpful so others can also look into it)
Business Management :
1. 1. Release Management:
The label for the DSL (Definitive Software Library) table is changed to DML (Definitive Media Library). But the table name
remained same — dsl and number generated for the dsl table is appended with DML instead of DSL
Now DML references to the rm_release table using the fields: Pending releaseandGenerated by release
1. 2. Time Card:
Time Sheet — It's a group of all time cards.
Time Card can added like
Manually by users by creating time cards for their assignments.

By copying from previous week time sheets.
By auto generate action that finds all active project task assignments for the user and generates time cards for them.
By scheduling a recurring job that finds all active project task assignments for the user and generates time cards for them.
Time Card Approval:
a. o Time card approvers can approve all the time cards in a timesheet
b. o Project managers can approve time cards related to their projects alone.
Remaining Effort: - This field can be configured to show remaining effort for a project task.
Project managers can configure if time cards should be generated for the project or for individual tasks.
Project managers can view the exception reports for the team members who have not submitted their time cards for the
current or the previous week.
Time card admins can configure the maximum number of hours per day or per week that can be in a timesheet.
For those who have Performance Analytics Premium license, two new dashboards (project manager dashboard and user
manager dashboard) have been introduced for time cards in Jakarta (Performance Analytics — Content Pack - Project Portfolio
Suite Dashboards)
Time sheet policies
By default, the Default time sheet policy is available with the system.
And part of this framework the following properties are removed and replaced by Time sheet policies
a. o com.snc.time_card.start_day
b. o com.snc.time_card.time_worked
c. o com.snc.time_card.autocreate
d. o com.snc.time_card.update.resource
e. o com.snc.time_sheet.max_hours_per_day
f. o com.snc.time_sheet.max_hours_per_week
g. o com.snc.time_card.update.effort
Worker portal
Project time category
Time card approver role
Functional changes
The field Generate time cards for top task only on Project form is deprecated. The level at which the time cards for a project can
be created is determined by the eld Allow time card reporting on
The time card property Update the task's 'Actual effort' based on the hours entered in the time card is replaced by the field
Update actual effort from time card in Preferences tab on the project form.
The property Default hourly rate used when processing time cards if we can't get a rate from labor rate
cards(com.snc.time_card.default_rate) is no longer accessible from time card properties. The property can be set from System
Properties.
IT Operations Management
1. 1. Event management
Launch a web application — From an alert that matches the conditions set in an alert rule.
Operational Metrics — It is enabled by a new plugin ITOM Metric Management (com.snc.sa.metric). It has prediction function
which projects expected metric values by learning from historical metric data.
Custom maintenance definition — It allows to define maintenance rules to mark CIs in maintenance status, where these CIs are
excluded from impact calculation.
Configue event collection from Zabbix - A default Zabbix
Correlated alert groups — It is displayed in dashboard alert panel. For that you have to drill down in an alert, in the Event
Management dashboard.
Monitor incoming alerts - Alerts that are members of correlated alert groups are indicated in the Alerts Console.
Personalized dashboard - Create a personalized dashboard query using Dashboard views.
Integration of Dependency Views map with Metrics Explorer view - In a Dependency Views map, you can switch to metrics
mode to display the Metrics Explorer with operational metrics data for CIs on the map. All map CIs are accessible in the right-hand
side pane, from where you can drill into metrics data.
CMDB alert groups - Service Analytics now also correlates alerts for CIs without historical data, based on the CI's relationships in
the CMDB.
Functional changes
Avoid impact to event processing during a platform upgrade: Event Management jobs that started running before the upgrade
commenced continue to run during the platform upgrade.
Identifier attributes: You can now change the default set of attributes that Service Analytics alert aggregation uses to form
patterns for alert aggregation.
Service Analytics correlated alert groups are now referred to as automated alert groups and are displayed along with the other
alert groups in the Event Management dashboard and the alert console.
Service Analytics root cause analysis (RCA) now also applies to alerts associated with manual services.
Operational Intelligence — This contains Operational Metrics and learns from historical metric data, builds standard statistical
models to detect statistical outliers and anomalies and raise anomaly alerts.
Collect event messages from cloud endpoints — Configure custom push connectors to connect to external event sources. You
can select to send events either through the MID Server or the instance.
Event rule designer — Create event rules to generate alerts for tracking and remediation. With this designer you can
a. o Transform information in events to populate specified alert field values and compose alert fields from various
values.
b. o Configure threshold rules that create or close alerts only when the incoming matching events exceed the
specified threshold.
c. o Bind alerts to CIs using CI identifiers.
Can configure a connector instance to collect events using the NagiosXIHP Operations Manager i (OMi) connector.
Quick response — To an alert by applying remediation or launching an application
WebService URL event collection — Configure the MID WebService Event Collector Context extension to enable the URL
method to push event messages from an external source to the MID Server. You can collect custom payloads in JSON, XML, or
plain text format. We have some pre built MID WebService Event Collector extensions in the base instance.
a. o AWS events transform script
b. o Azure events transform script
c. o Event collection from BMC TrueSight
Predictive alerts — Used to predict a sequence of future alerts for automated alert groups. You can use this information to take
preventive measures. (enable by setting the property "sa_analytics.pred.cl_enabled" to true)
Monitored services — View all services that are supported by Event Management, such as, alert groups, discovered services,
manual services, and technical services.
Promotion of anomaly alert — Users can create alert promotion rules, to create a regular Event Management alert that is based
on an anomaly alert.
a. o Event Management > Operational Metrics > Anomaly Alerts.
b. o Right-click an alert in the Alert Anomalies list and select Promote Anomaly Alert.
With this you can add a blacklist item to prevent the creation of a new Event Management alert that would otherwise be
created by an alert promotion rule. Right-click an anomaly alert and select Blacklist CI.
Functional changes
Navigation changes - Connectors and listeners are found under these menu options:
Event Connectors (Pull)
Connector Definitions
Connector Instances
Event Listener (Push)
Listener Transform Scripts

MID WebService Event Listener
MID SNMP Traps Listener
Automated alert groups - RCA can be applied to automated alert groups to identify root cause alert. This helps direct resources
to the root cause of a problem. To enable this set property "Enable Alert Correlation RCA".
CMDB alert groups - In addition to using hosting and containment relationships to form CMDB alert groups, there is now also
support for user defined suggested relationships.
Manual alert groups - The Service Analytics Alert Aggregation Learner learns the patterns of the alerts in manual alert groups.
This knowledge is then used with incoming alert streams. Service Analytics automatically forms automatic alert groups according
to the patterns in the manual alert groups.
Provide feedback about the usefulness of an alert group, you must use the feedback field on the alert form.
2. MID Server
MID Server pause - The MID Server can be temporarily paused to prevent it from polling the ECC Queue for work and from
sending Discovery results back to the instance.
MID Server upgrade - The MID Server is put into Upgrading status while an upgrade is being performed. If upgrade fails the MID
Server is put into Upgrade Failed status.
We also have validating and validating failed status new in Istanbul
MID Server version and user compatibility - MID Server list view and the MID Server form provide indicators to show you if the
version of the MID Server is compatible with the instance and also if MID Server user is configured correctly.
Privileged commands —
The dzdo privileged command is supported.
You can add new privileged commands to the Privileged Command [privileged_command] table and configure the MID
Server to use them in a predefined order.
You can create a special configuration for the pbrun privileged command that allows it to run as a profile.
Guided setup — A system that helps you download a MID Server and configure it to work with your instance, using a series of
easy-to-follow panels. (ITOM Guided Setup - > MID Server)
Credentials debug - A new section of the ECC queue payload is available to help troubleshoot issues with credentials:
<credentials_debug>.
Functional changes
MID Server selection criteria: In addition to IP ranges and capabilities, MID Servers can specify an additional selection criterion:
supported applications.(like orchestration , service analytics)
Role and settings validation - The system uses real-time validation of MID Server role assignments to prevent incompatible
settings. New business rules block unsupported MID Server role configurations and issue appropriate warnings.
Pre-upgrade testing - When a MID Server detects that it needs to upgrade, it automatically performs a series of short tests that
evaluate available disk space, access to the download site, and permissions required to execute certain file operations on the MID
Server host. If all these tests pass, the MID Server upgrade proceeds automatically. If any test fails, the upgrade cannot proceed,
and the instance publishes error messages to the MID Server Issue [ecc_agent_issue] table.
MID Server IP range auto-assignment - An instance can automatically assign MID Servers to IP ranges that represent subnets in
your network. The MID Servers must be running and valid and must have access to the subnets to which they are assigned.
optional MID Server guided setup — Tasks added are
a. o A setup task to allow you to create SNMP and SNMPv3 credentials.
b. o A setup task to allow you to select available MID Servers for auto-assignment(IP-ranges) to discovered subnets.
Managing active issues - MID Server Issue [ecc_agent_issue] table displays active MID Server issues and publishes error
messages that pinpoint the most likely cause of the issue.
Post-cloning credential issues: Automatic processes detect and notify you of possible MID Server user credential issues
after instance cloning.
Resource threshold alerts: The MID Server reports its CPU and JVM memory usage back to the instance at a prescribed
interval, and the instance evaluates that usage against con gurable thresholds. If either threshold is breached, the instance
can log an issue. A new registered event allows users to create email noti cations or custom scripts when CPU and
memory thresholds are breached. Resource threshold alerting is disabled by default, but each type can be enabled by
setting system properties.
Pre-upgrade testing issues: When a MID Server detects that it needs to upgrade, it automatically performs a series of short
tests to determine if it is capable of upgrading. If any test fails, the instance publishes error messages in the MID Server
Issue [ecc_agent_issue] table, allowing an administrator to resolve issues prior to the actual upgrade.
User connectivity issues: Error messages published to the MID Server Issue [ecc_agent_issue] table can provide insight into
authentication and authorization failures involving MID Server users and help identify network connectivity problems that
prevent a MID Server from establishing a TCP/IP connection.
Disabling the Asynchronous Message Bus (AMB) Client - A MID Server connection parameter allows you to disable the AMB client
when it is not suitable for your environment.
Functional changes
Business rules for MID Server resource threshold alerting were renamed and now also evaluate CPU and memory usage.
Update mean on MID Server Status — Renamed to Update cpu mean on MID Server Status with added functionality. Before it
used to calculate avg value of 24hour CPU usage, when CPU data inserted in ECC Agent Scalar Metric [ecc_agent_scalar_metric]
table. Now when a record is inserted in the ECC Agent Scalar Metric [ecc_agent_scalar_metric] table, this business rule triggers a
script include that evaluates threshold settings to determine if the MID Server has breached its configured CPU resource thresholds.
Update MID Server Status table — Renamed to Update max memory on MID Server Status with added functionality. Before it
used to calculate avg value of 24hour memory usage, when CPU data inserted in ECC Agent Scalar Metric
[ecc_agent_memory_metric] table. Now when a record is inserted in the ECC Agent Memory Metrics [ecc_agent_memory_metric]
table, this business rule triggers a script include that evaluates threshold settings to determine if the MID Server has breached its
configured memory resource thresholds.
IT Service Management
1. 1. Change Management
CAB Workbench — Change Advisory Board enables a CAB manager to schedule, plan, and manage CAB meetings. (Activating
the CAB workbench activates the Service Portal plugin)
a. o Create CAB definition: CAB Manager can define CAB based on which CAB meetings and their agendas are created.
The other functions of CAB manager can add as part of CAB definition are :
Set CAB meeting schedule

Create series of CAB meetings
Set CAB meeting agenda
Specify discussion time for each agenda item
Set CAB meeting board
Set CAB meeting delegates
Notify CAB attendees
a. o Create individual CAB meetings: The CAB manager can create individual CAB meetings outside of a CAB definition.
b. o Ensure change requests are CAB approved: Normal and emergency change requests can now be marked for CAB approval
via the CAB required check box on the Change Request form.
c. o Set CAB meeting delegate: Change requesters can now specify a delegate to attend the CAB meeting on their behalf via the
CAB delegate field on the Change Request form.
d. o View CAB calendar: The change manager and change requester can view the CAB calendar and drill down into the specifics
of CAB meetings.
e. o Approve or reject change requests: CAB managers can approve or reject change requests during the CAB meeting, which
are then processed through the appropriate workflow.
f. o Record and view CAB meeting notes: The CAB manager can record meeting notes, which can be viewed later by CAB
members and change requesters.
Configuration item (CI) healthCI health dashboard can now be accessed from a health icon available next to the Configuration
item field on the Change Request form.
Change Management property - It controls at which level logging should be displayed. (com.snc.change_management.cab.log)
It is activated with CAB Workbench.
Change Management Best Practice Plugin — It updates change form and some functionalities
a. o Added the Outages related list to the Change Request form.
b. o Sends notifications to the requester when a change is approved and scheduled, when work has begun, and when work
has been completed.
c. o Sends notifications to the requester when a change request is put on hold or removed from on hold.
d. o Displays a report showing the list of planned outages, so that decisions about scheduling change requests can be made
accordingly.
e. o Reorganized the Change form to better reflect the needs of a change manager or requester.
f. o Added the Task SLA related list and rearranged related lists.
g. o Updated the fields in the Change Request popup view to show the most relevant information.
h. o Added approval history to the change request activity log.
i. o Added the Requested by field to the Change Request list view.
j. o Added Planned start date, Planned end date, and Type fields to the Change Task form.
k. o Rearranged the fields on the Change Task form to contain the fields that provide most value for your users.
l. o Updated the mandatory and restricted Change Request properties for standard Change templates.
m. o Added that the change task type Implementation must fall within the planned start/end dates of the related change
request.
n. o Made Work notes mandatory when a change request is canceled.
o. o Added new state values: Pending, New, Work in Progress, Closed, and Canceled to the Change Task form.
p. o Displays all configuration items directly affected by a change on the Affected CI's related list.
q. o Provides a warning that the planned end date is prior to planned start date now occurs on the Change Request and
Change Task forms.
customizations.( com.snc.best-practice.change.jakarta)
Standard change properties - A two-step verification process has been introduced in requesting a standard change from service
catalog. The process redirects the requester from a standard change template to a change request that can be viewed prior to
submission. The two-step process is enabled in standard change properties.
Standard change proposals can now include change tasks. When approved, the resulting standard change templates generate change
tasks.
CAB workbench —
a. o In the CAB Definition and CAB Meeting form, the Order button is removed and the Add Sort button was added for
agenda management.
b. o The CAB Date field is now updated to the most recent CAB meeting date that the change request is associated with.
c. o The Allotted Time field has been added to the Agenda item list and displays the allotted time for that item. This allows
the CAB manager to override the default amount of time per agenda item.
d. o The meeting start time and meeting end time fields are now mandatory.
e. o The form widget has been enhanced to allow more lines of content to be displayed in the planning form section.
Functional changes
Impacted CI's/Services: allows any class of CI to be specified in the Impacted CI's/Services related list. Previously, it only
allowed business services to be included.
CI's Affected by Task: creates a relationship between all CI's specified in the Affected CI's related list on the Change Request
form and the Affected by Task related list on the Configuration Item record.
CI's Impacted by Task: creates a relationship between all CI's specified in the Impacted CI's/Services related list on the
Change Request form and the Impacted by Task related list on the Configuration Item record.
1. 2. Incident Management
Incident Management Best Practice Plugin — It updates change form and some functionalities
a. o Makes the Work notes field mandatory when there is a change in the incident priority, so that incident managers
can more easily track what caused a change in priority.
b. o Added the Request related list, so that you can more easily track a request opened from an incident.
c. o Clears the Assigned to field when the assignment group is changed.
d. o Added the Parent Incident field to the related forms section, so that your users can see which incidents have
parent records.
e. o Changed the field labels Closed code and Closed Notes to Resolution code and Resolution notes.
f. o Updated the On Hold choice list to include Awaiting Caller, Awaiting Change, Awaiting Problem, and Awaiting
Vendor. If Awaiting Caller is selected, it is mandatory to enter additional comments.
customizations.( com.snc.best-practice.incident.jakarta)
1. 3. Problem Management
Problem Management Best Practice Plugin — It updates change form and some functionalities
a. o Makes the Work notes field mandatory when there is a change in the problem priority, so that problem managers
can more easily track what caused a change in priority.
b. o Added the Major Problem check box and the Review Outcome field to facilitate the management and
documentation of major problem reviews.
c. o Added the report Incident Trend by Configuration Item, so problem managers can view incident trends by service
or configuration item (CI) over time to determine potential problems.
d. o Updated the Problem form layout, adding the fields Business service, Impact, Urgency, Closed, and Closed by
and changed the layout of the form to make it more user-friendly.
e. o Makes the Priority field read-only. This field is set based on the impact and urgency of the problem.
f. o Hides the Known error field on the Problem form and the Known error flag is set to true when the problem is
set to the state Known Error.
g. o Updated the UI action Close Incident to Resolve Incident enabling problem owners to resolve and
communicate updates to child incidents when a resolution has been identified. Your users can review and confirm the
resolution.
customizations.(com.snc.best-practice.problem.jakarta)
1. 4. Service Catalog
New Variables — Email and URL types are new variable types available.
Customizable variable display -
Service Catalog > Catalog Variables > Variable Default Size (On global level)
For Individual form level changes the width option is available on Type Specifications Tab.
Wish list - You can save partially configured catalog items to your wish list, and finish if off later. (not supported for Order Guides
and Wizards.)
Record producers reporting - Create reports that map the record producers to the base records generated by them. (Service
Catalog > Request Reports > Created by Record Producers)
Required check box: You can mark a check box variable as mandatory by selecting the Required Checked check box.
Help text : If you select the Show help option for a variable, you can use the Instructions field to enter HTML help text. Selecting
the Always Expanded field opens the help text when the form loads always displaying the help text.
Service Catalog currently does not support List v3.
Debug UI Customization — this is a new submodule introduced under the Catalog Administration module, enables catalog
administrators to perform a health check of Service Catalog pages, enabling catalog administrators to pinpoint the issue and self-
heal.
Variable Watcher —tab is available for Service Catalog variables. A catalog administrator can monitor individual variables for
changesâ€¯inâ€¯their state and value due toâ€¯Catalog Client Scripts, Catalog UI Policies, and Catalog Data Lookups.
Variable Action Loggeror a full analysis of all the client-side actions affecting the state and values of every variable on a catalog
form.
Applies on Target Record — check box available in the Catalog UI Policies and Catalog Client Scripts submodules. It
provides full feature support for variable editors on records created via record producers (only for task-extended tables).
Catalog UI Policies, Catalog Client Scripts, Catalog Data Lookups, Reference Qualifiers, and dependent reference fields are
supported on the default variable editor used for records created via record producers.
New Variables
IP Address: To capture the IPv4 and IPv6 data for a catalog item. Under the Validation Scripts submodule, a validation script type
associated with this variable is available.
Duration:
Changes on Existing variables
Apart from the Macro, Macro with label, and UI page variable types, Service Portal supports all types of variables.
Note: Convert the UI Macro variable to portal widget and associate with the same widget.
Service Portal supports two-column layouts only for the top-level containers.
You can specify example text as a hint for a variable before you enter a value.
Variable set extension —When you apply Catalog UI policy Actions and GlideForm APIs (setReadOnly, setMandatory
setDisplay) on a variable set, the actions are applied on every variable within the variable set. You can make variables read-only
and mandatory, or change the display of variables by performing these actions on the corresponding variable set. The same
feature is available for containers as well.
Catalog UI Policy condition builder - Variables associated with a variable set have the variable set name associated with them
in the Catalog UI Policy condition builder as well as in the Catalog UI Policy Actions list.
Automated Test Framework for Service Catalog - Catalog administrators can write automated tests to validate their catalog
items because Service Catalog is supported in the Automated Test Framework (ATF).
Record producer redirection settings — control the behavior of record producer after its generation in the UI.
All fields except the variable fields have been removed from the Catalog UI Policy condition builder to avoid any confusion when
creating Catalog UI policies.
The Description field has been removed from the Question tab on the Variable form.
Functional changes
When Copy UI Action, all the associated variables, Catalog UI Policies, Catalog Client Scripts, and Catalog Data Lookups
are copied along with the catalog item. product model associated with the catalog item is not copied unless specified.
1. 5. SLA
New Roles — sla_admin and sla_manager

SLA Time Line —
a. o Filter: To filter off the data that the timeline displays.
b. o Task SLA Details: A section to displays information on stages, task updates, and out-of-schedule for SLA timeline.
c. o Stepped zoom: To provide several zoom in or out levels to control SLA timeline zoom resolution.
d. o Toggle button: To show/hide task updates that did not cause an SLA stage.
e. o Ability to debug or verify: To check if a task is mapped appropriately with a defined SLA using the SLA timeline.
f. o Ability to select business elapsed time or business time left: The selection is saved into user preferences for display in
the SLA timeline.
g. o Reference picker: To preview the task selection to be introduced in the SLA timeline.
h. o Refresh button: To refresh the SLA timeline with the latest values of the task SLA.
i. o Carousel navigation: To take you through all the task stages easily.
j. o Ability to select a different time zone from the SLA timeline has been added.
k. o Ability to calculate the breach date and time of the SLA from the Due Date field of the task to which the SLA is attached
to.
Service Level Agreement Best Practice Plugin — It updates change form and some functionalities
a. o The SLA notification and escalation workflow sends notifications when a task reaches a certain percentage of its
allotted SLA duration.
b. o The Service Level Target field has been added for filtering, searching, and reporting on different service level
target types.
customizations.(com.snc.best-practice.sla.jakarta)
Reporting and Dashboards
1. 1. Reporting
Istanbul — No Features added
Classic Reports list layout (Reports > View / Run) is removed. Previously, it was possible to enable this version of the Reports list
layout by setting the system property glide.ui.report.new_home to false. This property setting no longer has an effect and only the
redesigned Reports list layout is available.
Custom chart creation is removed.
Functional changes
a. o View and run reports in the mobile app.

b. o PDF functionality improved —Fields printer friendly form, Using set number of datapoints to prevent JVM running out of memory
and performance issues.
c. o UTC date value field was changed from Date to DateTime, to prevent a one-day shift in Calendar reports.
d. o Pivot report and multilevel pivot report titles display.
e. o Drill down from several report types to a list with a drilldown view displays the specified drilldown view.
f. o Unauthorized users receive the correct error message when they try to delete or modify a report.
g. o The Highlight based on option in calendar reports is now persistent.
Import External Data - reports based on data maintained outside of your instance.
Content on Service Portal - display on Service Portal using Service Portal widgets.
Report Designer - Configure a report, preview it, iterate and adjust it, and then share the report using the integrated Share panel.
Accessibility — standardized Report Home, Report Designer, and reporting content (e.g., widgets on dashboards) as per Web
Content Accessibility Guidelines Level A.
Highcharts 5 —
Interactive analysis - Launch a detailed analysis of your data from any list.
Functional changes
a. o The Custom Charts plugin is removed.

b. o The Chart Color field retains its value when the groupby or stackby field values are changed and when switching
between chart types in Report Designer.
c. o Multiple datasets are available to all users. Previously Performance Analytics Premium was required.
d. o When using Insert and Stay, color rules are not copied to the new report.
e. o Multilevel pivot report improvements:
f. o Options added for displaying row and column lines.
g. o Added automatic collapsing and expanding of rows.
h. o Enhancement fixes for columns headers.
i. o Enhancements to PDF export and scheduled export.
j. o Improved word wrapping.
k. o Color coding added to single score reports.
l. o Changed the configuration of the report_security plugin to default on upgrades. Users who upgrade no longer have to
contact security to install this plugin.
m. o Improved the loading of the table list.
n. o Fixed warning messages in the zboot console log.
o. o Improved default color list for multiple datasets.
p. o Enabled dot walking on the Aggregation field for Average and Sum aggregation.
q. o List functions now available on the Report list
r. o The [report_view] table is no longer populated with new entries. The Report Stats list enables you to view how often
each of your reports is run and how long it takes for the reports to run. For more information, see Report statistics.
1. 2. Dashboards
Responsive canvas dashboards are introduced if not enabled set property glide.cms.enable.responsive_grid_layout to true. If property
doesn't exist you can create one. (like in helinki).
All users can create or view dashboards - When responsive canvas is enabled, users with any role can create and share
dashboards. Users without a role can view dashboards that are shared with them.
New dashboard permissions and sharing - When responsive canvas is enabled, dashboards use more flexible and granular
dashboard-specific permissions, which separate view and edit rights.
On responsive dashboards, tabs can no longer be linked between dashboards. Tabs that were linked between multiple
dashboards in previous releases remain linked after upgrade.
On responsive dashboards, you can no longer specify a home tab on a dashboard. The leftmost dashboard tab is always the
home tab.
Responsive dashboard tabs cannot be published as a homepage. Instead, create a single-tabbed dashboard and share it with
other users.
Functional changes
a. o All dashboards have an Owner field.

b. o Only users with access to the Slow Performance Graphs widget can add this widget to dashboards.
c. o Many changes to Interactive Filters.
d. o Content packs for Application Portfolio Management, Discovery, Human Resources Service Management Scoped, and Incident
Spotlight.
Once Responsive canvas/Dashboard is enabled :
New dashboards use responsive canvas and existing dashboards are converted to responsive canvas.
Users receive an email notification when a dashboard is shared with them.
Use the Restrict to roles field to specify roles required to access the dashboard.
Dashboard quick layouts were moved to the Configuration pane.
Many dashboard actions have been moved to the context menu.
Add a tab from the Configuration pane or context menu.
Breakdowns and breakdown element appear under the dashboard header.
Responsive Canvas dashboards are enabled(introduced in Istanbul)
Create a dashboard version of a homepage - create responsive dashboards from existing homepages, providing better
accessibility, improved sharing, and easier widget layout.
Cascading interactive filters - Dashboard administrators can create hierarchical interactive filters. Selecting a filter value at a
higher level automatically filters the choices available for lower-level filters in the hierarchy.
Software asset management -
Solution library - Easily install and update dashboards and visualizations for Performance Analytics content packs.
Attend Knowledge18 Pre-Conference Training!
Learn New Skills and Connect with Experts!
BROWSE SESSIONS
Contact Us     
Help
Terms of Use
Privacy Policy
Trademark and Branding
© 2018 ServiceNow. All rights reserved.

Difference Between Istanbul and Jakarta Release - IT Service Management - ServiceNow Community

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Difference Between Istanbul and Jakarta Release - IT Service Management - ServiceNow Community

Enviado por

Direitos autorais:

Formatos disponíveis

5/3/2018 Difference between Istanbul and Jakarta release - IT Service Management - ServiceNow Community

 Upvote (0) 12877 Views

 Accepted Solution See this answer in context

V vamsisaladi • 10mo ago

Jakarta — New Features

Istanbul — New Features

Time Sheet — It's a group of all time cards.

Time Card can added like

Manually by users by creating time cards for their assignments.

Time Card Approval:

Jakarta — New Features

Time sheet policies

Project time category

Time card approver role

Istanbul — New Features

Jakarta — New Features

b. o Azure events transform script

Event Connectors (Pull)

Event Listener (Push)

Listener Transform Scripts

Jakarta — New Features

Set CAB meeting schedule

Jakarta — New Features

Jakarta — New Features

Jakarta — New Features

Istanbul — New Features

Jakarta — New Features

Jakarta — New Features

New Roles — sla_admin and sla_manager

a. o Filter: To filter off the data that the timeline displays.

Reporting and Dashboards

Istanbul — No Features added

a. o View and run reports in the mobile app.

Jakarta — New Features

a. o The Custom Charts plugin is removed.

Istanbul — New Features

a. o All dashboards have an Owner field.

Once Responsive canvas/Dashboard is enabled :

Jakarta — New Features

Responsive Canvas dashboards are enabled(introduced in Istanbul)

15 Replies ( Latest reply 2mo ago by vamsisaladi ) Show All Replies

V vaibhavbhatnagar • 10mo ago

See if this is helpful Features and changes by product

gauravchoudhury Forum Level 2 • 10mo ago

1. Istanbul Release Notes (Click Here)

Also, you can refer to some Jakarta Highlights in this thread.

Shiva Thomas • 10mo ago

Also, this slide may be useful to you.

 Helpful (4)  Show Replies

Rajashekhar Mushke Forum Level 1 • 10mo ago

Please Refer Below articles,

Upgrading from previous families

 Helpful (1)  Show Replies

V vamsisaladi • 10mo ago 

Jakarta — New Features

Istanbul — New Features

Time Sheet — It's a group of all time cards.

Time Card can added like

Manually by users by creating time cards for their assignments.

Time Card Approval:

Jakarta — New Features

Time sheet policies

Project time category