Tagged with version_2.9 - Visokio Forums

New: Connectors-iGeolise Travel Time (2.9+)

richard — Tue, 28 Jan 2014 11:29:53 -0500

In Omniscope 2.9 (b820+) we have added an iGeolise Travel Time connector. This connector is available as an operation in DataManager and contains three services:

Time Maps

Create isochrone shapes showing the area around an origin which can be reached in a given time period and using a specified mode of transport.
Routing

Retrieve directions for your journeys. Configurable options include the start or arrival date/time and a mode of transport,
Rank Points

Upload a collection of origin and destination points along with a mode of transport and maximum journey time. Travel Time will return only the destinations which can be reached in the given time period along with the distance and time taken to reach the location.

The DataManager block contains a link to iGeolise Travel Time's sign up page where you can create an account.

Please let us know if you encounter any problems or have any questions.

Performance: DataManager Aggregation block operation (2.9-Plus)

mraburgess — Wed, 07 Oct 2015 16:34:17 -0400

I have a DM aggregation block running on 14 million records x 38 fields. On 1 field doing unique values (has 5 million unique values) I am running various sums, 6 first non-empty values, 1 unique value count, 1 min & 1 max

It has been running for 2 days now yet is only using 6GB of my 64GB RAM (windows 10 pro, Xeon 8 core processor, Omniscope version 2.9 build 1765 (rc) [plus] x64)

Is there anything i can do to make aggregate use the available RAM more intelligently - i have other files use far more of the RAM, but always have this issue with aggregation.

thanks

Printing: PDF Export from Linux OS without a GUI

donald — Fri, 27 Jun 2014 11:51:04 -0400

There are some additional library dependencies which are required to enable printing and PDF download from mobile Server installations when running on Linux OS without a GUI. You might experience printing Mobile reports with "black images".
Please follow these instructions to workaround this issue.

MAIN SOLUTION (should work across different Linux distributions; tested on CentOS and Ubuntu 14.04): Use XVFB

You need to install these additional packages on your headless Linux machine: xvfb, libxss1
On Ubuntu Server 14.04 you also need dbus-x11 libnss3 libgconf2-4 libfontconfig libpangocairo-1.0-0 libXcomposite1 libasound2 libxtst6 libcupsmime1 libgtk2.0-0

sudo apt-get install xvfb libxss1 ...

Then you just need to start Omniscope Server through this command:

xvfb-run -a --server-args='-screen 0, 1024x768x24' ./omniscope-server-headless.sh

If this command fails, run xvfb-run with "-e /dev/stdout" option to see the error messages in the console.
e.g. in case of Font error you may need to install these additional packages:
sudo apt-get install -y xfonts-100dpi xfonts-75dpi xfonts-scalable xfonts-cyrillic

If you are running the Omniscope Server through Upstart background service, in the visokio-omniscope server installation directory modify the _launch.sh file (last line) from:
"$JAVA_CMD" $JAVA_VM_PARS $ADD_VM_PARS -cp "$JAVA_CP" "$@"
to
xvfb-run --server-args='-screen 0, 1024x768x24' "$JAVA_CMD" $JAVA_VM_PARS $ADD_VM_PARS -cp "$JAVA_CP" "$@"

Then start the service as usual as per instructions http://www.visokio.com/kb/linux-installs
N.B. xvfb-run seems not compatible with privbind. So if you are using privbind to bind to reserved port (e.g. 80) you need to use an alternative solution: e.g. setting up Linux IPTABLES to redirect port 80 to Omniscope port 8080 see here for reference https://www.frozentux.net/iptables-tutorial/iptables-tutorial.html#REDIRECTTARGET

Setting up R for Omniscope 2.9

glen — Mon, 01 Jun 2015 09:30:43 -0400

Omniscope integrates with open source analytics libraries written in the R language, making R-based analytics more accessible and productive since data scientists and business users can work together, each doing what each does best.

Installing R is a simple process, but is required for use within Omniscope. This Forum post details how the user does this by completing the following simple steps.

Select the link below which corresponds to your current operating system to install R. The process is similar to installing a normal piece of software. It is particularly important to note where R has been installed (the R binary path) if the default location is not used.

http://cran.r-project.org/bin/windows/base/

http://cran.r-project.org/bin/linux/

http://cran.r-project.org/bin/macosx/

Each of these links also has helpers for installing R in each of the operating systems.
Now the R binary path needs to be configured in Omniscope. This is done by selecting:

Data > R statistics > R settings…

This will open the following window:

The default location for R is already entered into the R binary file path. If you have installed R to a different location then this will need to be entered manually. Once this step has been completed click “Check now” to ensure that Omniscope is able to use R’s functionality. This will open the following dialog box:

If this is displayed then you are ready to use R functionality inside Omniscope.

Web Server: HTTPS and URL Redirection

antonio — Fri, 06 Dec 2013 10:42:51 -0500

Omniscope Mobile Web Server allows you to configure both HTTPS and URL redirection.

These two different redirection rules are applied in the following order:

URL Redirection: redirects incoming client requests to a different host/context
This technique allows you to make a web address/context available under more than one URL address.
It can be used for URL shortening, to prevent broken links, to allow multiple domain names to refer to a single Omniscope Mobile. (more info here)

Host redirection
For instance, the following configuration allows to redirect the client, that was navigating to "alpha.omniscope.me", to the different "https://omniscope.me" host.

e.g. it redirects from "http://alpha.omniscope.me/folder/file.iok" to "https://omniscope.me/folder/file.iok"

Context redirection
Another example is to redirect requests to a particular context (e.g. link to a particular IOK file)
Say that your server is serving at "http://server.domain" and you want to redirect "http://server.domain/dashboard" to the full link "http://server.domain/MyDefinitelyBeautifulDashboard.iok". The following configuration allow you to do so.

e.g. it redirects from "http://server.domain/dashboard" to "http://server.domain/MyDefinitelyBeautifulDashboard.iok"

Host and context redirection
This example combines host and context redirection.
Say that you server is serving at "http://alpha.omniscope.me" and you want to redirect the "/demo" context to a different host "https://demoserver/" and different context "/MyBeautifulDashboard.iok". Then use the following configuration

It will redirect from "http://alpha.omniscope.me/demo" to "https://demoserver/MyBeautifulDashboard.iok".

To redirect all incoming requests to a particular context regardless your server host/virtualhost name, then leave the VirtualHosts field empty.

N.B. by specifying the Redirect from field you define which context has to be redirected.
If you leave it blank then the URL redirection will be applied on all the incoming requests. In this case it is better if you perform redirection to a different host by specifying a full URL in the Redirect to field (e.g. "https://differentHost/pathTo/file.iok")
Be aware that misconfiguration may create redirect loop error.
Redirect HTTP to HTTPS: redirects all incoming HTTP requests to HTTPS.
If the HTTPS protocol is enabled, this option will configure your server to serve the content only through the HTTPS secured channel.

Versions: March 2015 minor updates to 2.9 Plus

steve — Sun, 29 Mar 2015 05:04:27 -0400

We've introduced a few new minor features and fixes to 2.9 Plus, initially available in a hotfix build for testing:

http://www.visokio.com/download/plus?branch=special&feature=Plus/Hotfix_March2015MiscFixes

Tab selection when printing and creating PDFs (Omniscope Mobile)

In the print/PDF dialog in Omniscope Mobile (from the 3-dots application menu), you can now select which tabs to print, with shortcuts to select All or Current. Note that it is much faster to print/PDF only a single tab.

BOM support for UTF data files such as CSV

This was added to provide fast data export from Omniscope Mobile (via cloud icon ) while supporting Excel integration and international characters/accents.

Native XLSX file export is several times slower than CSV, which for files of many 100,000s of records becomes quite a hindrance. However without BOM support, CSV export cannot support international characters in a way that is compatible with Excel (UTF-8 files without BOM open in Excel as ASCII and show international characters garbled).

The BOM (byte order mark) is an optional sequence of 2 or 3 characters which are never found in normal text and which, if present, signal that the rest of the file is in a UTF character encoding (supporting an enormous range of characters, accents and symbols from most countries and regions).

When exporting to text-based files such as CSV, if you choose UTF-8 or UTF-16 encoding, Omniscope now writes the BOM to the start of the file. On double-clicking a CSV with Excel installed, Excel will detect this and open it displaying international characters correctly. Note that Omniscope Mobile always uses UTF-8 encoding (irrespective of the server's operating system defaults) when exporting view data using the cloud icon ().

Similarly, when importing from text-based files such as CSV, Omniscope now detects the BOM which is optionally present at the start of UTF-8 and UTF-16 encoded text. If found, Omniscope now forces UTF encoding and overrides whatever encoding was configured, then skips the BOM and reads the file correctly. This makes the safe assumption that the BOM sequence is a reliable indicator of encoding.

We've also added an app-wide setting allowing you to disable these two UTF-8 BOM changes (import and export effects), should there be unexpected problems with 3rd party CSV producers/consumers:
Settings > Advanced > Data sources > Support UTF BOM (byte order marks)"

Support for "Show no records watermark" option (Omniscope Mobile)

If you have disabled the "No records" or "Empty" watermark text (using Settings > Advanced tab settings > Show no records watermark), Omniscope Mobile now honours this setting.

Excessive rounding in Bar/line value labels (Omniscope Mobile)

The optional value labels at the top of bars, showing the numeric measure values, were often formatted with excessive truncation/rounding/abbreviation. This would lead to a series of bars with (e.g.) "9" showing, despite it being clearly visible that they were different heights and actually somewhere between 8.5 to 9.5.

This has now been fixed, and the configured accuracy of the measure field will be used providing there is enough space above the bar.

This bug was most apparent with "flipped" (bars going sideways) Bar views. However, after this fix, if you have configured "Thin bars" there may still be not enough room to show sufficient accuracy; you should change your bar widths using Bar view toolbar > Layout > Medium bars to resolve.

Export: Re-branding data exports from browser views

richard — Fri, 28 Feb 2014 08:06:48 -0500

Omniscope Mobile's export view functionality has been extended to support branded exports using an existing XLSX file as a template (b936+).

Attached is an example using the 'Bond Prices' demo file and a basic XLSX file as a template. Any exports generated from this IOK file will now be output as an XLSX using the same styling etc.

To use this example, unzip 'mobile.zip' and place it within your 'mobile' directory of the Omniscope Mobile Server deployment. (Note: You will need to enable exports for this to work - see links below).

Go to this post for instructions on how to enable exporting.
Go to this post for instructions on how to configure branding.

Setting up branded exports

To configure your own branded exports:

Move your XLSX file into the 'branding.internal/mobile/app' folder related to the relevant IOK.
Copy the 'export_view.xml' file to the same location.
Edit the contents of the XML file using the instructions below.
Run your IOK file using Omniscope Mobile Server and click the export button on any view.

Configuring the XML

templateFile
Points to your XLSX file which must be inside the same 'branding.internal/mobile/app' folder.

worksheet
Name of the worksheet which will contain your export.

column/row
Column/row position where the data export will start.

includeHeaders
Whether or not to include a header row of field names.

Versions: Funnel charts and Radar View in web browser versions 2.9+?

alexandervolk — Wed, 28 Jan 2015 04:37:36 -0500

Hello,

Currently, a Bar/Line View set up as a Funnel chart doesn't display correctly in web browser version. Same goes for the Radar View as a whole.

Are these generally not supported in HTML5 browser version or are there plans to make them available soon?

Thanks
Alex

Branding: Re-branding HTML5 web browser versions

antonio — Wed, 06 Nov 2013 13:07:21 -0500

Introduction

Starting from 2.9 b795 we have extended the re-branding options to include Omniscope view versions deployed to browsers as HTML5/JS

In order to able to brand Omniscope you need:
1) Ensure getStatic="true”:

To do this, it is recommended you modify the folder.xml file and change the anonymous user permissions to allow all users to benefit from the UI customisation:

...
   
      
   
...

2) Have a “branding.internal\mobile” folder (see attached example folder) in the directory you want to customise under the Mobile sharing folder. Alternative, have a “branding” folder in the Omniscope installation directory.

The branding has been split into three different areas, “Admin, Server and App” where resources for each of these areas is stored inside of “branding.internal” folder.

The description below refers to the main "Mobile sharing folder" as the root folder.

Admin web server

You can customise various resources and htmls files relating to the Admin server, by placing a “branding.internal\mobile\admin” folder in the root folder.

You can then override or replace the existing files with your own custom logo or add text to the appropriate html files.

Note, placing the folder in sub-directory won't work - branding can only be done from the root folder.

Mobile web server

You can customise various resources and htmls files relating to the Mobile web server, by placing a “branding.internal\mobile\server” folder in the root mobile sharing root folder, or even in a sub-folder within mobile sharing folder to show different branding on a per-customer basis.

For example, if you have three different clients, then you can place “branding.internal\server” folder in each of the client’s directory and configure them to have their own logo etc.

App

Just like Mobile web server you can override on a per-folder basis the app-splash and favicon shown for the IOK file is loading. In order to customise app specific resources, you need create “branding.internal\mobile\app” folder in the appropriate directory containing the file.

Omniscope (Desktop/Mobile sharing)

Omniscope will look for branding\app folder in the installation branding folder (branding folder of Omniscope application itself) for the resources.

Further information

Omniscope Mobile looks for branding resources in a hierarchical way and falling back to installation branding folder.

For example, to find the favicon to load when loading the IOK file in Mobile web server. Omniscope Mobile will search for favicon.ico file in the following order:

Looks for branding.internal\app in the folder that contains the IOK that it is loading.
If found, uses that, otherwise, goes into parent folder and does the same as 1. It does this all the way up to the mobile sharing folder. Note, if the folder that Omniscope is using to display the resource is protected, then the user will be prompted to enter authentication details.
If it can’t find it the resource in the mobile sharing folder, it will check installed branding folder (branding folder “branding” installed in the Omniscope installation directory). No authentication is required to access resources from installed branding.
If it can’t find the file, it will check if the file is bundled with Omniscope, otherwise throws a File not found error.

Versions: Web Publishing in version 2.9?

dpawley — Tue, 06 Jan 2015 10:43:33 -0500

I don't suppose the Web-Publishing aspect of Omniscope is fully functional on the latest update? I am asking as sometimes we would like to share some of our reports with users that don't have access to Omniscope and this idea is great - just doesn't work?

Any advice would be great

Versions: 'Omniscope Web Server' part of Scheduler not visible?

stavro — Fri, 12 Dec 2014 07:41:34 -0500

Hi everyone,

I noticed on the site that Omniscope Scheduler 2.9 has an option called 'Omniscope Web Server'. We are running version 2.9, but we can't see it on our Scheduler. What is the problem?

I am using the version: 2.9-beta b1342

Integration: Central list of Parameters in a file?

bfromson1 — Thu, 20 Nov 2014 10:43:17 -0500

Is it possible to have a list of parameters in a file which can be read by an Omniscope instance and the parameters then used.

Specific application is to have a list of server names in one place, then individual reports can use this list to open database connections. If server is ever changed then only one change in one file would be required.

Styling & Branding tips: Setting up styles and presets 2.9+

daniel — Thu, 16 Oct 2014 09:24:18 -0400

A useful way for making your reports and visualisations to be consistent and shareable taking advantage of the new layout features in 2.9.

Attached are two examples of .ILF styling files which are files you simply click and run in Omniscope to add these styling sets to your own installation and menus. These will automatically prompt you to save them into your style list where you can apply them onto any tab.

I have also included a XML file for presets, you have to import this file into your preset menu (see images 1 & 2) and make sure to apply to application wide setting so that it is saved to your Omniscope installation. Once installed the new presets will appear within the menu (image 3).

As an FYI and plug, I am a freelance Omniscope consultant who would like to offer my services.
So please contact me if you have any opportunities, seek training or short term/part-time work that needs doing.

FMI check out some examples on my blog, LinkedIn or pm

uk.linkedin.com/in/dancklam/
http://spatiametrics.wordpress.com/omniscope-data-visualisations/

Installation: Public-facing Omniscope (Mobile) Server setup

steve — Fri, 08 Aug 2014 05:05:32 -0400

The Omniscope installer includes two apps:

Omniscope - a native desktop app that opens and explores IOK files (the free Viewer). When activated, enables analysing and editing your own data, configuring and authoring IOKs, and also DataManager for importing, transforming and exporting data.
Omniscope Server - a native desktop app or background server process comprising the Scheduler (for automating IOK updates and publishing) and Mobile Server, a production grade http server for a web-based Omniscope Viewer.

Providing you have a Server Edition license you can host a public Omniscope server like ours: https://omniscope.me
Note that Server Edition licenses are sold by number of concurrent web users supported, an individual user being a browser instance on either a desktop or mobile device.

Hardware needed

To experiment, or for smaller files, a reasonable desktop or laptop will do. We support Windows, Mac and common server-class Linux distributions. You can simply run the Server app from your start menu shortcut, after activating.

For a production-grade system, you'd want it always-on, with a UPS, hardware redundancy, etc., probably hosted in a datacenter or IaaS cloud like Amazon EC2.

Install configuration

You'd also ideally want to install Omniscope to run as a service, i.e. in the background on startup, without a user desktop session logged in.

Once you have the Server app open, you'll see the links to the default sharing folder and serving web address in the Omniscope Server window. Drop some IOKs in the sharing folder and start browsing locally.

To make it publicly available:

Configure security options as needed
Enable port forwarding on your external network firewall
Buy a domain name
Configure the domain to point to your firewall's external IP address
If using user logins, you should also buy an SSL certificate and configure HTTPS only access.

You now have a public server available at http://www.your-domain-name.com/

For more details see http://forums.visokio.com/discussion/2610/announcing-omniscope-2.9-beta/p1

Forum: Finding Updates and Details of What's New?

dpawley — Fri, 27 Jun 2014 07:35:26 -0400

Hi all

I am new to all this discussion pages and thought I would try a few. When Omniscope is updated and you are prompted to download the file from the website, is it me or is there no details of what has been updated?

I would be good to have a similar to an Apple App Update that just briefly explains what is new so you can try it out.

If this is detailed then can someone point me in the right direction?

Cheers, Danny

Export: Download PDF/Print from browser versions (2.9+)

antonio — Fri, 27 Jun 2014 13:29:47 -0400

We are happy to introduce a new feature allowing Omniscope Mobile users (those viewing tabs in their device's own browsers) to download or print the hosted IOK file exactly as seen in their device's (including tablet devices) own browser.

From the app top-right "3 dots" menu, by selecting

Download as PDF, the server will generate and send to client a PDF file containing all the IOK file tabs captured as high quality images page by page.
Print..., the server will generate a printable HTML report, made of all IOK file tabs high-quality images, that will automatically prompt the end-user native browser print dialog.

Users can select which aspect-ratio to use to generate the PDF or the printable HTML report
When prompted,

Ticking Use current browser size will generate a report that follows exactly the same app proportions (e.g. views, filters) as seen by the user in their browser.
Unticking the option will produce a A4 friendly landscape format report, in which the app proportion will be adapted to the A4 ratio.

For instance, iPad users may want to download a PDF that looks exactly the way they are experiencing Server-hosted Omniscope IOK files from inside their iPad browsers by using the Use current browser size option and the result will be something similar to the attached PDF.

N.B. If you run Omniscope Server on Linux server OS and you print a report you may encounter errors / visual glitches, so please follow this troubleshooting post

Mobile: Client-side auto-refresh (2.9+)

mustafa — Mon, 09 Jun 2014 10:03:33 -0400

In the latest version of Omniscope 2.9 we have made improvements to what happens when the server IOK file is updated while a client is browsing it. These changes make it easier for you to collaborate or create a continuously updating dashboard.

Depending on the kind of change, the client may be able to continue interacting, or be forced to reload (refresh the browser). Changes that force a reload include adding/deleting records/fields. Changes that don't force a reload include adding/removing views/tabs.

How to configure

This behaviour is configured per-file, from the Desktop app. Open the IOK file in Desktop, then click on
Settings > Web sharing>Edit client settings

You will then be prompted with different settings you can persist in the IOK regarding Mobile. Click Edit alongside Client-side auto-refresh.

You'll see this dialog, currently showing the defaults:

Section: Check for changes to server copy of file...

This section defines when the file on the server is checked to see if it has changed.

Only when interacting with the file
The check will happen only when the user is actively interacting with the file e.g. when switching tabs or adjusting filters.
In the background
The check will happen periodically, in the background, while the client has the page open.

Note: this option may increase server load because the file would remain in server memory. For large files on shared servers this would prevent inactive apps from being unloaded from server memory, ultimately reducing performance in extreme cases.

Section: When a change is detected...

This section defines what happens when the client detects the file on the server has changed.

Show button
If ticked, a lighting flash icon will appear on the main toolbar of the client (if the toolbar is showing). Clicking it will reload the application.
Show prompt
If ticked, a prompt will be shown explaining what has happened. Depending on the change, the user could choose to continue working on the session.
Reload automatically
If ticked, the client will automatically reload immediately to show the new changes, but only if the user has not made any client-side changes of their own such as filtering, selection or view menus.

You should tick this option for a live-updating dashboard.

Network View: Now available in browser versions

chris — Thu, 29 May 2014 12:48:14 -0400

In the latest version of Omniscope 2.9 (b1284) we have added the Network View to Omniscope mobile options.

The Network view supports a subset of the functionality of the desktop equivalent, more specifically:

Both grouped and relational network types are supported.
Node size, shape and colour.
Line width and arrows.
Label font and background.
The "Circle" and "Best fit" layouts.

We are planning to migrate other functionality, such as line labels and additional layout types, in the near future. We will update on this forum post once these features have been implemented.

The screenshot below is a relational network showing the voting between countries at the Eurovision song contest 2014. Here we are filtering so that links are only shown where 8 or more points are being awarded. Popular countries, such as Austria and The Netherlands (who came 1st and 2nd respectively) are positioned nearer the center of the network.

The screenshot below shows a grouped network where an employee database is split by sex, location and age range. The size and colours of the nodes indicate the number of records, so for example we can see a large proportion of males are based in London (98 Males out of 646 total).

The Mobile Network view supports tiling and paning. Both of these features are not available in the desktop Network view. The screenshot below shows the Eurovision data described above paned by the number of points awarded, from 1 point to 12 points:

If you encounter any problems using the network view please let us know. In addition, if you have any comments or ideas for improving the Network view we would be keen to hear from you.

Display: Localisation/field formatting for browser versions (2.9+)

Peter — Fri, 23 May 2014 09:48:49 -0400

Localisation and field formatting is now available throughout the mobile application. Date and number values are formatted throughout the app based on the set up data locale.

Fields with dates and numbers are formatted according to the field settings and timezone in the IOK file.
Abbreviations are now more accurate throughout the application.

Security: Mobile Web Server Authentication using AD & LDAP+SSO

Veaceslav — Fri, 23 May 2014 06:49:45 -0400

Mobile Web Server Authentication

Mobile Server authentication has been redesigned to include LDAP/Active Directory (AD) authentication and Single-Sign-On (SPNEGO) mechanism while preserving the List Of Users (Omniscope Users) existing mechanism.

A realm defines a protection space. Realms allow the protected resources on the server to be partitioned into a set of protection spaces, each with its own authentication and authorization settings.

By default, all protected resources on the server are configured in the config.xml file. This is the (Home) realm. Specific folders may be manually configured to have their own set of permissions and authentication groups. For more information about folder permissions read this post.

Server permissions may be configured for anonymous users and for authentication groups.

A group may have a list of authentication mechanisms and server permissions.

For instance, the server may be configured to have a group named 'Data Analysts' with permissions to:
- List directory
- View in mobile
- Export view data
and authenticate users through LDAP Query and List Of Users.

Authentication mechanisms

List Of Users

List Of Users mechanism let's you define custom Omniscope users that are stored and managed by the Omniscope Mobile server. No third party servers/services are involved. Users are manually added/edited/removed by an administrator of the server.

A user name and a password has to be added for each individual user. Read this post for more information about List Of Users mechanism configuration.

LDAP Query

LDAP Query authentication mechanism let's you configure Omniscope Mobile server to query an LDAP server to validate user credentials.

Users are stored and managed by an LDAP/AD server
Omniscope Mobile server is configured to query the LDAP/AD server

To learn how to configure Omniscope server to use LDAP Query read this post.

SPNEGO (Single-Sign-On) Mechanism

SPNEGO (Single-Sign-On) mechanism allows users to authenticate automatically with their LDAP/AD account without asking them for credentials. Having a proper setup, authorized users never type their credentials in any dialog or form. Unauthorized users, however, are either prompted for credentials or are denied server access.

Users are stored and managed by an LDAP/AD server
LDAP/AD user password is never sent to Omniscope server
Omniscope Mobile server is configured to ask the LDAP/AD server to validate user tokens

How does SPNEGO work ?

The browser negotiates with the LDAP/AD server and gets a temporary ticket which is further used to generate temporary unique tokens that are included in every client/browser request sent to Omniscope Mobile server. The tokens contain no information about client user name, password, or any other sensitive data, they are simple strings that can be verified only by the LDAP/AD server. Whenever Omniscope Mobile receives requests having SPNEGO tokens, Omniscope Mobile asks the LDAP/AD for token validation and if the token is valid, LDAP/AD provides only the user name associated with that token. Omniscope server checks whether this user is authorized to be served the requested resource and proceeds accordingly.

To learn how to configure Omniscope server to use SPNEGO mechanism read this post.

Authentication Groups

A group may have multiple authentication mechanisms. Each mechanism will be used during authentication until the user authenticates successfully. If no group authorizes the action that has been requested by the user, the access will be denied.

You may want to temporarily disable groups instead of deleting them and then adding them back later when needed. Disabled groups are disregarded during authentication.

Installation: Updating to Omniscope 2.9

Valentina — Mon, 28 Apr 2014 12:00:27 -0400

Hi all,

If I want to download Omniscope 2.9, do I have to delete the previous version first or it does not matter.

Filtering: Date filter endpoint input in 2.9?

OO83 — Thu, 20 Feb 2014 06:15:38 -0500

Hi,

The date filters in version 2.9 look to be only adjustable by scrolling.

Is it possible to allow start/end dates to be typed in order to manipulate/adjust date filters, please?

Thanks

Idea: Text Processing - Eliminate/substitute unwanted characters within strings?

davedunckley — Tue, 29 Oct 2013 07:06:58 -0400

Hi,

Just wondering if there is a way of replacing everything within brackets in a string of text.

I have a field that has a name, then a former name within parentheses. I would like to be able to remove the ( ) and also everything within.

Example:

Smith (jones)

Should become:
Smith

as should:
(jones) Smith

Thanks in advance
Dave

New: Chromium browser engine bundled (2.9+)

antonio — Tue, 15 Apr 2014 09:20:07 -0400

From version 2.9 b1149+ Omniscope will bundle the Chromium browser engine, a stable, modern and standards-compliant open-source browser engine which is behind the Google Chrome browser.

This major change will bring important benefits:

Users will not need a browser installed on their machine to use Web view, Content view, and Omniscope Mobile interface.
Application stability will improve as Omniscope will no longer suffer from issues caused by the old version of the installed browser (e.g. IE6).
Omniscope user experience will be boosted and improved in terms of look-and-feel, regardless the machine specifications.

Please feel free to test it and send us your feedback.

Sources: Google Drive spreadsheet connection error - version 2.9?

nuriozlu — Tue, 08 Apr 2014 04:16:57 -0400

i am having an unknown host error while trying to connect my google drive spreadsheets
for your information

Connectors: Facebook Atlas paid search report (2.9+)

chris — Wed, 26 Mar 2014 12:33:07 -0400

Hi,

In tonight's Omniscope 2.9 release (b1053) we have added the ability to select the report type in the Facebook Atlas connector. You now can choose from "Web media report" and "Paid search report".

The "Web media report" is the default report that was supported in older versions of Omniscope.

The "Paid search report" is a new report that mirrors the paid search report in the web interface.

Please let us know if you have any questions about this, or if you have any ideas for improving the Atlas connector.

Chris

New: Bookmarks - Import/export link (2.9+)

chris — Wed, 15 Jan 2014 13:15:59 -0500

In Omniscope 2.9 we have added the ability to Import, export and link to DataManager bookmarks. These options are available in the "Bookmarks" tab in the data-panel.

Import bookmarks. This option allows you to import all the bookmarks saved in a bookmarks XML file. This file can be located on your own computer, on a network location or somewhere in the cloud. Any bookmarks that you import will be embedded in your local bookmark file, so any edits you make will be made locally and will not edit the bookmarks XML file.
Link to bookmarks.This option allows you to link to a bookmark XML file. You can link to a file on your own computer, a file on a network or a file somewhere in the cloud. Linked bookmarks cannot be edited, and are updated every time you open DataManager. You can trigger a manual refresh by selecting the linked bookmark and clicking the "Refresh" button in the bookmarks toolbar. If the linked bookmarks file is deleted they will no longer appear in your bookmarks the next time the list is updated. Linking to bookmarks allows you or your company to create a central bookmarks file that can be managed by an administrator and linked-to by multiple Omniscope users. If, for example, a database password changes, only a single update is required to propagate that change to all users.
Export all bookmarks/Export folder. These options allow you to export all your bookmarks or a selected folder to a bookmarks XML file. After exporting, other Omniscope users can either import or link to the bookmarks. You can choose to export bookmarks to your local computer, a network location or somewhere on the cloud. Any passwords defined in any of the sources or outputs that you export will be encrypted.

Please let us know if you have any questions or ideas for improving this feature.

New: Mobile Tag & Tile Views for browser versions (2.9+)

chris — Mon, 16 Dec 2013 09:42:02 -0500

We have added two new views to Omniscope Mobile: Tag and Tile (2.9b719+).

Tag view

The Mobile tag view replicates the look and feel of the Omniscope desktop equivalent.

The following options are currently supported:

Style options including number of tags, tag size range, tag font, tag orientation and tag margin.
Single field selection.
Size/colour/fade.
Colour keys.

The following options are still outstanding. We are planning to implement this functionality in the next few months:

Row/column layout.
The ability to select more than one field.
Tiling/Paning.

Tile view

The Mobile tile view supports most of the options available in Omniscope desktop, including:

The ability to show images as well as regular tiles. Image options including Grid/Mosaic layout, title, title colour.
Multiple group levels. Omniscope Desktop supports only 2 levels, however we have built the mobile tag view to support any number.
Size/Sort/Colour/Value.

The following options have not been implemented. We are planning to implement this functionality in the next month:

Image zooming.
Image effects (shadow/glow).
Image mouse-over.
Image surrounding colour.

Please let us know if you have any questions or have any ideas for ways we can improve these views.

Export: View data from browser versions

richard — Wed, 04 Dec 2013 12:40:26 -0500

Mobile Web Server now supports exporting the data behind each view in CSV format. This is available from build 691 and is disabled by default. We will be updating our alpha site in the next week or so which will include this functionality.

To enable this functionality for all files, launch Omniscope Server and navigate to Mobile Web Server > Config > Default folder configuration > Edit > Anonymous permission > Edit. On the permissions dialogue box (shown below) turn on Export view data.

All views will now display a button for exporting their underlying dataset. The output dataset will respect any aggregation settings configured in the view.