This document provides an overview of Panorama's support organization and processes. It outlines how to contact support via phone, email or web form, and what information is needed when reporting an incident, such as screenshots and system details. It describes how incidents are classified, tracked and prioritized according to urgency level. The document reviews diagnostic methods for different incident types, including testing functionality on different machines and in other applications. It provides examples of common resolution steps and tools used to diagnose and fix issues. The overall goal is to guide customers on effectively working with the support team to resolve incidents.
2. Objectives
By the end of this lesson you will be able to:
List the methods of contacting support
Gather information required for identifying the source
of the incident
Access troubleshooting tools
Perform basic diagnosis
3. Agenda
Support Organization and SLA
Contacting Support
Gathering Information
Incident Classification
Diagnostics
Resolution
7. Resolving Incidents
What is an Incident? Something doesn’t work as expected, just
an inquiry about how something should
work.
How do I report one?
We answer phone calls and emails and
web submitted cases, We are available
almost 24/7 hours
How do you track
incidents?
We use Microsoft Dynamics CRM, to
manage the incoming requests.
8. Panorama Support SLA
Incident Type Definition/Impact
Response
Time
Urgent calls Production down Up to 2
Medium severity
Affects important work but not
production failure
Up to 4 hours
Standard
doesn’t have immediate effect on
business
Up to 24 hours
Full SLA:
http://bit.ly/qauNmD
14. Contacting Support – via Support Site
http://tech.panorama.com/index.php/supportr
equest
Open your case right from here, for the
quickest service.
15. General Recommendation
Recommended communication language: English
Case number
Will be assigned in first call
Used for tracking for the lifetime of the case
18. Functionality Related Questions
The questions we usually ask:
Expected behavior
How does it work in different circumstances?
When did the problem initially start or when have you
noticed it?
Last actions before the problem appeared?
19. Environmental Related Information
Flash version
Internet Explorer version
Is Panorama web site in Trusted sites
Where does the problem appear:
Server
Single client
More then one client
Necto
Server
Web
Necto
Clients
21. Basic Categorization
Malfunction: “It doesn’t work”
• Obvious malfunction or unexpected behavior
Feature Request :”I want it to do…”
• Adding functionality that is currently not in the
product
Question:“How to”
• Information request
22. Incident Categories• One or more applications did not load (connectivity)
• Unexpected error or behaviorMalfunction (functionality)
• Chart or grid are not represented correctly
• Scaling or numbers are drawn incorrectlyUI (Visual)
• User doesn’t see the data that should be displayed
• Security doesn’t apply on selected groupSecurity
• Calculation shows unexpected results
• Data is incorrect or not logical compared to other systemsData
• The performance of selected application is poor in any step (application
loading, view opening, operation etc.Performance
• Installation or upgrade process ends unexpectedlyInstallation/Upgrade
• When using the SDK functions, methods or parameters, malfunction is
observedSDK
• Any other issueMisc
26. Malfunction – Common To-Do
Check different scenarios:
Different server or client machine
Different IE browser/Flash
Relevant log files and tools:
Event viewer
Panorama flash logs UI (Visual)
Security
Data
Performance
Installation/Upgrade
SDK
Misc
Malfunction
27. UI – the Questions
Questions:
Does it happen on all client machines or
several?
Does it happen on Necto Desktop?
Test:
2-3 clients with different configuration
(IE, Flash browser)
Required information:
Screenshot
Expected behavior
Exact client information
Malfunction
Security
Data
Performance
Installation/Upgrade
SDK
Misc
UI (Visual)
29. UI -Common to-do’s
Erase IE browser temporary files and cookies. The
cookies often store such information such as:
Client Flash version
Fonts/colors used previously
Pane Layouts positioning
Malfunction
Security
Data
Performance
Installation/Upgrade
SDK
Misc
UI (Visual)
30. Security – Review of Security Types
Content
Security
Data (OLAP )
Security
Roles
• Which portions of the
data will be available
• Defined in terms of
Dimensions and
Members
Users
• Which
workboards will
be available
UI (Visual)
Malfunction
Data
Performance
Installation/Upgrade
SDK
Misc
Security
31. Security Issues - Diagnoses
Validation steps:
User Impersonation using:
SQL Management Studio
Necto Run As…
Role
Definitions
Import /
Sync Roles
IIS
Definition
Browser
Definition
End user
Definition
UI (Visual)
Malfunction
Data
Performance
Installation/Upgrade
SDK
Misc
Security
32. Security
Data
What is a data Error?
Wrong data value
Incorrect calculations
Totals not being summed up correctly
Any other issue that causes false data
UI (Visual)
Malfunction
Performance
Installation/Upgrade
SDK
Misc
Data
33. Data - Diagnosis
Test in the SQL Management Studio
and MDX Studio
Test in different application: Excel
Pivot Tables
Simplify view / create a new view
Review resolve order
Test advanced settings
Locate error location: server, client or
both
Security
UI (Visual)
Malfunction
Performance
Installation/Upgrade
SDK
Misc
Data
34. Data – Diagnostic Tools
TraceQueries - capture MDX into a log file
Send the cube
Without data or with demo data
Attach relevant view
Security
UI (Visual)
Malfunction
Performance
Installation/Upgrade
SDK
Misc
Data
35. Data
Performance
Find the bottleneck
Security
UI (Visual)
Malfunction
Installation/Upgrade
SDK
Misc
Performance
36. Data
Performance
Measure in seconds / minutes
Activate or Deactivate cache and measure again
Test different applications
Example: Excel Pivot Table
Review the view structure:
Large dimensions used in axis
Nesting
Security
UI (Visual)
Malfunction
Installation/Upgrade
SDK
Misc
Performance
37. Performance
Installation / Upgrade
Access permissions
Network access restrictions (firewalls,
blocked port numbers)
Validate installation prerequisites
Check installation log
Migration of data from NovaView if
relevant.
Data
Security
UI (Visual)
Malfunction
SDK
Misc
Installation/Upgrade
38. SDK
Create an HTML file based on SDK sample.
Create an HTML component or JavaScript in a Necto
WorkBoard.
Performance
Data
Security
UI (Visual)
Malfunction
Installation/Upgrade
Misc
SDK
40. New Feature Request / Hot Fix
Gather
information
Understand
reason
Product
Manager
review
Approval /
Reject
Prioritization Implementation
41. Summary
Search Knowledge base and Forum before calling
Help us improve: indicate and provide missing
knowledge
Provide detailed incident information, screenshots
and relevant logs
We are here to help you with incidents and to
provide knowledge
We are happy to share this information with you in order to provide better service for your and our customers.
Questions we usually ask regarding the environment in which you run:
What version of Flash are you using?
What version of Internet Explorer are you using?
Panorama web site in Trusted sites
Screenshot of the issue before/after
Does the problem appear on the Server and Clients or the server or clients only?
Necto software is strongly bounded with many other applications. First we eliminate those bounds.
For location of panorama logs see: http://tech.panorama.com/index.php/kb/62-frequently-asked-questions/456-panorama-logs
An Event viewer:
http://www.bleepingcomputer.com/forums/topic40108.html
Does it happen on all client machines or several? Does it happen on Necto Desktop?
Test 2-3 clients with different configuration (IE, Flash browser)
What information required:
Screenshot
Expected way of work
Exact client information
Necto Security includes 2 layer, as security error can originate from either type of security:
Content Security rules, define allowed workboard for certain users or a role the user belongs to. Content Security allows workboards to be segmented according to functional areas or organizational hierarchy. For example, certain workboards containing high-level strategic indicators might be visible only to Executives.
Data Security relates to which portions of the data will be available for different audiences. Its implementation addresses questions such as Who has access to Sales Performance for all products?, Can we restrict access to forecasted sales?, and others. The definitions of such Data Access Rules are made in terms of which Dimensions and Members must be hidden or shown, and are defined in the OLAP Cube (we refer to this method as OLAP Security).
Both security methods are applied per user or per role that the user belongs to.
Using TraceQueries registry key will create a MDX tracing at the folder c:\Program Files\Common Files\Panorama\log
Explanation about TraceQueries: http://tech.panorama.com/index.php/kb/73-panorama-necto-2011/574-use-tracequeries-mechanism-to-debug-performance-issues-and-errors
The installation log is created in: C:\Panorama Necto Installation
Handling a feature request includes the following steps:
Gather information about the requested feature
Understand the reason and rational behind the request
The product manager will review the request
The product manager will either approve or reject the new feature request
If approved, a development priority will be assigned to the feature. Should it be added immediately in a service pack, or should it be implemented in the next version of the product?