Sitrion ONE - Key Components


Download the detailed Product Description here.

Sitrion ONE is the award-winning employee app to reach and engage all your employees. Your employees get all actionable tasks, notifications and communications from multiple sources into one intelligent productivity stream. Additionally your employees are able to initiate processes, look up documents or share important messages quickly. Sitrion ONE is the only solution which combines enterprise security (SOC2 compliant) and standardized integrations with a user-centric, consumerized experience.

Sitrion ONE consists of a native Client App (an app for iOS, Android and Windows Phone ), micro-apps which provide specific functionality within it, a multi-tenant Cloud, an on-premises Hub, software to interact with backend systems, and a development environment, the AppBuilder. Please go to the Security Guide for further technical details.

At the mobile device, ONE is a single native Client App.  The first time a user launches the Client App, it requests an email address. The address is used to associate the user with a company in the ONE Cloud.  The user is requested to enter network credentials which are stored in a database in the hub (on the customer’s premises) or authenticates against Microsoft ADFS.  From this point forward, the network credentials are never passed and never stored in the Cloud or the Client App – only the user identity and a security token are used.

Sitrion ONE contains specific functionality for use cases around displaying information updates and approval tasks.  “Cards ” are designed specifically for these use cases.  Cards are presented in a “Productivity Stream” in the ONE Client App.

Each Card displays either a piece of information or an approval task.  The general layout of the cards are templatized so that they have consistency, but the data and controls can vary from case to case. To ensure that cards display extremely quickly, the data for them is proactively gathered and stored in the ONE Cloud.  So, for example, the data from a blog post in SharePoint is moved into the Cloud so that as soon as a user opens the ONE Client App it can be immediately downloaded to the phone.

The ONE native Client App has a rendering engine built into it.  When the ONE Client App contacts the ONE Cloud, new or updated Micro-Apps are delivered to the client.  At the client, the micro-app is really just XML that provides instructions which the rendering engine uses to implement the interface and behaviors for that Micro-App (e.g.  if the Micro-App is used for searching, the XML contains information about the search field, search button, how to format the search results, etc).  This definition is cached on the client, so it can function quickly without needing to download a lot of data. 

The screen to the left shows an example of the Sitrion ONE native Client App with an expert search Micro-App currently in use.

Collectors” are the software pieces of Sitrion ONE that perform the process of gathering card data and moving it to the Sitrion ONE cloud.  Interactions with backend systems (either looking up data or adding data such as entering a time off request) is performed through software called “Connectors”.  These two kinds of software can be combined.  A Collector could retrieve all of the vacation requests that need approval by a certain manager.  When the manager taps the approve button on the card, the Connector code is used to update the backend system. For further details and a list of all integrated systems please go to the Integration Guide.

The ONE Cloud performs several other very important functions.  It stores lists of users grouped into roles for each company.  This allows assigning of Micro-Apps to roles so that, for example, everyone in Sales gets a CRM search Micro-App.  The ONE Cloud also forms a secure tunnel into the customer premises.  This allows the Micro-Apps to communicate with backend systems securely without the need to add some other hardware or software.  The ONE Cloud is also where any specific code associated with a Micro-App will run (for example, the actual code that sends an update to a time tracking system when a user fills out a time tracking entry in the ONE Client App).  The ONE Cloud also delivers push notifications to the clients. 

The ONE Cloud provides other administrative capabilities beyond mapping micro-apps to roles accessible via the Administration.  It collects usage data and provides reporting for company administrators as well as monitoring the connection to the Hub.  It provides controls for theming of the ONE Client App.  It also allows a way to set configuration data used by the clients. For further details please go to the Administration Guide.

The Hub is a service that opens the secure tunnel to the cloud, stores the credentials for on-premises access, and proxies requests as necessary.  The Hub is a very lightweight part of the system. For further details please go the to "Installing the Hub".

The last major element of the the platform is the development environment "AppBuilder".  The AppBuilder is an extension for Microsoft Visual Studio that allows Micro-Apps to be defined.  This can be a “no coding” process where the tool generates the code, or developers can build specific functionality.  The AppBuilder contains the ability to connect to backend systems and map the data from them into specific parts of a Micro-App.  It also contains functionality for designing the experience in a Micro-app (deciding what kinds of UI elements are used and where they are positioned for example).  When a Micro-App is defined, a developer can publish it to staging or production from the AppBuilder. For further details please go to the Development Guide.

Glossary - Main Components


Please see the Glossary to get an overview about all main components of Sitrion ONE.

Share this page
X
Tell your colleagues and friends about Sitrion. Choose a social channel below to share this page.