1. The Palantir Platform… …Changes in 2.3

2. Administrative Features
Highlights in 2.3
This document outlines major changes/additions to the Palantir Platform in 2.3.
The document is not comprehensive as there have been literally 100’s of usability enhancements as part of the 2.3 release as is the case with every release.
Major Highlights:
User Features
Administrative Features
The New Dashboard
The New Dynamic Ontology Manager
Integrated into PGWeb
The New Flows Helper
A stand-alone application
The New Object and Graph History
Built-in testing framework
The Configuration Server User Interface
The Map-Layers Helper
Ontology Aliases in all Type- to-Search Menus
Custom Import using Detector/Transformer framework
Source preview during sourcing
Kite Integration into all imports
Paged Results during Tagging Search
Clustered Dispatch Servers
…and much, much more…

3. User Features

4. The New Dashboard
In 2.3, the Dashboard is no longer its own application but is actually a tab in the Browser.
The new Dashboard runs off a highly scalable ‘feeds’ framework rather than the persistent search model of previous versions.
Feeds give fine-grained results according to the user defined criteria showing the changes to an object, the documents that match a query or the changes to a filter result.

5. The New Dashboard (continued)
Investigations are now also treated like a feed so they can be easily identified and returned to for further study.

6. The New Dashboard – PalantirWeb
The user Dashboard is also available via PalantirWeb so users can monitor their feeds easily from anywhere.

7. The New Flows Helper
Flows is now its own helper with administrative ability to define new flows for custom analyses that can be used by all users.

8. New Graph History
In Versions of Palantir prior to 2.3, the graph history and data history linked so that moving backwards in graph history also undid data changes. We found that users preferred using the graph to navigate their investigation.
In 2.3, moving through the graph history simply re-arranges the graph. This is much faster than the previous graph history model.
To retain the data history, all objects now have rich object histories that can be accessed via the browser.

9. New Object History
Because data history was uncoupled from graph history, each object now has a rich data history that can be rolled-back or changed by users.
The object history can be searched using simple keyword searches. This allows for quick exploration of the object providing a rich audit trail of all changes to this object.

10. New Object History – PalantirWeb
The New Object History is also available directly in PalantirWeb so that users can review everything about the objects they are looking at.

11. A major addition to the Map Application is the addition of map layers.
Map layers can be defined using drag-and-drop of shapefiles and kmz. Once defined, layers can be styled, stacked, used to define search areas or exported for other uses.

12. Aliases used in all type-to-search menus
In order to make the Ontology more discoverable, aliases are included in type-to-search menus. An unlimited number of aliases can be defined in the ontology for any ontology type.

13. Source Preview during Manual Sourcing
When sourcing data to a data source, the sourcing panel now gives a preview of the selected document so the user can make sure they are using the correct one.
For a structured sources the user sees metadata about the data source in question.

14. Paged Results during Tagging Search
If many results match a possible tag, the search results will be paged to allow a better chance of de-duplication at the moment of tag creation.

15. Data importer shows links on the graph in addition to objects
Other User Highlights
Data importer shows links on the graph in addition to objects
Elbows can be created by simply clicking and dragging a link
A zoom-to-area function has been added to the map
During object resolution on the graph, choose the final title and object type
Timeline colors now persist across sessions/applications
ToolTip on link-by properties to show the property types being used
Histogram fonts can be increased
And more…

16. Administrative Features

17. The New Dynamic Ontology Manager
One of the major changes form an administrative point of view in 2.3 is the new Ontology Model.
The Dynamic Ontology Manager is now a stand-alone application and the ontology is now a single file rather than a set of files and folders.
The Ontology can be opened from a file or imported from a database. All changes to the ontology are instantly recorded in the ontology file.
When the ontology is completed, it can be exported back to the Database.

18. Ontology Testing Framework
In 2.3, it is now possible to test all elements of a property using a built in testing framework.
Elements can be tested individually or all at once using a ‘Test All’ interface.

19. Configuration Server UI
In 2.3, a web GUI has been added for the configuration server making installation, upgrade and management of a Palantir instance much simpler for the administrator.

20. Custom Import – Detector/Transformer Framework
In 2.3, a framework has been constructed which will genuinely allow the import of any type of data.
The framework has two components:
Detector: the Detector senses the nature of the import according to a set of rules. These could be as simple as just looking at the file extension or as complex as actually opening the file and parsing it.
Transformer: the Transformer tells the Data Importer how to interpret a file of this nature so that it can be made into Palantir Objects.
Now, when any user drops a valid data source onto the data importer, the detector will sense it and will be imported correctly.

21. Kite Integration into All Imports
Kite is an extensible transform language that is used for importing many types of data sources.
In 2.3, Kite was made the default data transformer for all imports, thus simplifying the data import process greatly.
As a result of Kite being used in this way, it is also possible to extract an automatically generated Kite Configuration file during a standard Palantir import.

22. In 2.3 we have added support for clustered Dispatch Servers.
This serves two main purposes:
Supports greater user concurrency
Supports fail-over if one of the dispatch servers goes down
Dispatch Server
Dispatch Server
Dispatch Server

23. Improved Palantir Enterprise Manager UI
The Palantir Enterprise Manager (PEM) has received a new UI for greater usability.

24. Improved UI for Palantir Monitoring Server
The Monitoring Server is used to check on system health and can be configured to deliver alerts if specific events occur. The UI for the monitoring server is available in PEM.

25. Other Administrative Improvements
Property Base types are listed in the Property Menu for the Dynamic Ontology Manager
Plugins can be exported in their original form from the Dynamic Ontology Manager
Investigative Permission Configuration can be chosen at the time of Investigation Creation
Configuration Server uses the Configuration Web UI for performing upgrades to itself
Feeds search framework operates with Raptor sources
Helpers can now act as resyncable points of import
Security changes can be performed without forcing user logout
And more…