Note: This article is under construction and may contain incomplete or missing information. Please report any inaccuracies by leaving a comment below or submitting a ticket.
A - D
Administrator (role) - The Administrator is a predefined Application Security Role with access to manage user security and Apps. Users belonging to this role can grant other users access to Models and Dimension members, and manage Apps. Apps can be configured with Advanced Workflow, such as adding Contributors, Approvers, and Reviewers.
System Administrator (role) - The System Administrator is a predefined System Security Role that grants access to the entire system, including each Application and its related data. Users belonging to this role have the ability to impersonate any user within the system. By default, the person installing Kepion will be added as the default System Administrator. Additional users can be granted to this role through the SYSTEM module.
ADMINISTRATOR (module) - The ADMINISTRATOR module is used to manage user security and Apps. Security can be configured for individual users, roles or groups and restricted by Models and Dimension members.
Resources: Administrator Guide
The Advanced Contributor is a predefined Application Security Role that allow users to use the Transactional Drill-Through feature.
When configuring a Dashboard App, the Workflow Type can be set as either Basic or Advanced. When set to Advanced, there are three types of users that can be added: Contributors, Reviewers, and Approvers.
See Also: Basic Workflow
App (sometimes: Dashboard App, Workflow App or Workbook App) - Refers to the combination of a Dashboard or Workbook together with its security and workflow settings. Apps are generally the 'solution' that end-users interact with. Apps are accessible through the APPS module.
APPS (module) - The APPS module displays all the available Apps that a user has access to.
App Id (appid)
A number assigned to an Application when added to Kepion through the SYSTEM module.
Resources: App URL Structure
When an APP has been saved or submitted, the saved instance is called an App Instance. An App Instance that is used in an advanced workflow is also referred to as a Submission.
Application (Application Database)
An Application is a container that groups together common elements, such as Models, Dimensions, Rules, Forms, Dashboards and Apps. From the back end, an application will be represented as a single SQL database. An application can be managed through the MODELER, ADMINISTRATOR and SYSTEM modules.
Variables are used within an Application to ease maintenance and help facilitate automation. Common usage include embedding variables within Forms, Rules and Dashboards. Variables come in different types, such as Standard Variable and Member Variable. Variables can also be self referencing, allowing for complex expressions to be achieved.
See Also: Standard Variable; Member Variable
Resources: Configure Application Variables
One of three types of Users that can be added to a App Workflow, along with Contributor and Reviewer. Approvers can modify a submission and either approve or reject it. Approvers are only available in an Advanced Workflow.
Attributes are found in Dimensions and extend the available information relating to dimension members. Attributes can be defined with various data types, such as String, Double, Boolean, Byte, Int16, Int32, Int64 and DateTime.
Authorization Id (authid)
A number assigned to each App in an Application when added through the ADMINISTRATOR module.
Resources: App URL Structure
When configuring an App, the Workflow Type can be set as either Basic or Advanced. When set to Basic, the only types of users that can be added to the Workflow are Contributors.
See Also: Advanced Workflow
One of three types of users that can be added to a Workflow, along with Reviewer and Approver. Contributors can create new Submissions, modify the data, and in an Advanced Workflow, submit their data for approval.
A Dashboard can combine multiple Forms, Filters, Rules, and other components together for end-users to interact with.
Resources: Dashboard Designer Guide
A component found within the Rule Designer editor, data rules are designed for business users to create and maintain business rules without having to write customized SQL. There are two types of Data Rules: VIEW Rules which are used to layer in new calculated records within a partition of a Model, and ACTION Rules which are used to INSERT or DELETE existing records.
Resources: Rule Designer Guide
A set of Dimension members used to scope selections, usually Filters within a Form. There are two types of Defined Sets: MEMBERS and DYNAMIC. With DYNAMIC, the Members are selected by specifying a set of conditions. With MEMBERS, the Members are selected directly from a UI.
Resources: Configure Defined Set
The process of generating the actual OLAP cubes that drive the Models in the Application. Any structural change made to the Application will require a Deployment. This ensures that the Application as configured in the MODELER is reflected in the OLAP Database.
Resources: Modeler Guide - Deployment
A SQL, MDX, or XMLA script that runs during Deployment, often used to update custom elements in an Application, or automate particular tasks. Deployment Scripts can be managed in the MODELER under Deployment > Scripts in the navigation pane.
Resources: Use Script at Deployment
Dimensions are tables used to organize and filter related data. Dimensions are one of the essential building blocks of an Application. Models are built by combining one or more Dimensions together. Kepion comes with three predefined Dimensions: Account, Time, and Scenario.
Analytical - A functionality available in Forms which allows you to 'drill' into the data within the Model to determine which Dimension Members contributed to the final displayed value. This feature is accessed by right-clicking on a value in a Form.
Transactional - A functionality available in Forms which allows you to 'drill' into the individual transactions within the SQL Database, to understand the values at the lowest-level that contributed to the final displayed value. This feature needs to be configured in the Modeler before it can be accessed by right-clicking on a value in a Form.
Drop-Down Cell - A type of input cell that can be configured in the MODELER in the DROP-DOWN tab of the Forms node. By default, Drop-Down cells are a light shade of purple. Previously named Model Combinations.
Resources: Add Drop-Down to Form
Drop-Down Menu - An additional way to configure the navigation menu in a Dashboard App.
Resources: Add Drop-Down to Dashboard Navigation
E - H
Any user that primarily accesses the Apps and Modules created through Kepion, rather than the back-end features such as the Modeler.
A component that allows users to upload attachments through a Dashboard and share files of any type with other users. File Stores are created and managed within the MODELER module.
Resources: Use File Store Attachment
Filter - One of the three parts used to define a Form, along with Rows and Columns. Filters are used to switch between different data contexts in a Form.
Data Filter - A filter applied to the columns in a Form to filter by the different data in the cells. A useful component within a Form to manage large numbers of rows of data.
One of the essential components used in Kepion. Forms can be thought of as similar to Excel Pivot Tables, but with more powerful and flexible configuration capabilities. Forms belong to a Model and are defined by the Dimensions that define the Model. Forms are created by assigning hierarchies and measures to the Rows, Columns, and Filters. Forms can used as a read-only report or be configured for data input.
Kepion supports Active Directory Groups, allowing for IT departments to manage user security outside of the system. It's often easier to manage permissions and user security by Group, as opposed to individually configuring each user. Groups are similar to Kepion Roles, with the former being defined by Active Directory (AD) and the later only within Kepion.
See Also: Role
Hierarchy - Defined within a Dimension, a hierarchy represents a set of members derived from the underlying Dimension data. A Hierarchy can be defined with different types of structures. For example, hierarchy members can be flat, have parent-child relationships, or defined across Dimension Attributes representing various levels.
Member List Hierarchy - A type of Dimension Hierarchy structure that represents a sub-set of Dimension members configured in either Flat or Hierarchy mode. Each member of this hierarchy has access to information defined by the Attributes of the Dimension. Member Lists are used when adding Dimensions to a Model by defining the scope of available members within the Model. The default Time Dimension contains the following default Member Lists: Days, Months, Quarters and Years. Note that each Member List contains a different set of Dimension Members.
Parent-Child Hierarchy - A type of Dimension Hierarchy structure in which a sub-set of Dimension Members are organized with a parent-child relationship. This hierarchy is also known as a Member List in Hierarchy mode. The default Account Dimension is an example of a Parent-Child Hierarchy.
Leveled Hierarchy - A type of Dimension Hierarchy that is created off of Dimension Attributes. A Leveled Hierarchy is always associated with a given Member List, and derives its members from a combination of the members within the Member List itself and the associated Dimension Attributes. For example, the default Time Dimension contains a Member List called Months, with a Leveled Hierarchy called Fiscal Calendar. The Fiscal Calendar is defined based on the Dimension Attributes FiscalYear, FiscalQuarter and MemberId. Note that the Time Dimension attributes are hidden in the MODELER module for ease of use.
Attribute Hierarchy - A Dimension Hierarchy based on a Dimension's Attribute. An Attribute Hierarchy can be enabled by checking the Hierarchy box in the Attributes node.
I - L
A general name to refer to the Kepion software in order to differentiate it from Kepion the company.
Linked Models are used to link multiple Models together. Models which are linked can share Measures and Dimensions. The main use of this feature is to create Validation Models which define relationships between Dimension Members.
Resources: Use Linked Models
M - P
MDX (Multidimensional Expressions) is a language for OLAP Databases, in the same way that SQL is a language for Relational Databases. MDX is used to define multi-dimensional calculations on OLAP cubes. For performance considerations, write calculations on the Relational Databases in SQL whenever possible.
A Member refers to an item within a Dimension Hierarchy. For Member-List Hierarchies, a Member will consist of properties for MemberID, MemberLabel, MemberName, Input, Annotate and any additional Dimension Attributes that are defined. For Attribute Hierarchies, a Member refers to a single data from the Dimension Attribute. It is common to refer to Members by the way they are displayed. For example, a Geography Dimension may contain Members such as United States, Canada, and Australia.
A type of Application Variable that holds a specific Dimension member. Member Variables are useful because you can add them to various locations across the Application, and then update all the values in one spot.
Resources: Use Member Variables in Form Filter
The structure in Kepion representative of the OLAP Cube generated during Deployment. More simply, Models can be thought of as a combination of Dimensions. The point where each Dimension intersects in a Model is where the data lies. Models are used for capturing and reporting on data.
The Model Designer is a predefined Application Security Role that allow users to manage the core modeling aspects of an Application, including the ability to create new Dimensions, Hierarchies, and Models. The Model Designer role is also able to manage Dashboards, Forms, Rules, and Application Variables, as well as deploy the OLAP Databases.
Modeler (role) - The person building an Application in Kepion, and/or using the MODELER Section.
See Also: Model Designer
MODELER (module)- The MODELER module is used to manage the core building aspects of the Application, where Modelers can define Dimensions, Hierarchies, Models, Forms, Dashboards, Rules, and more.
Resources: Modeler Guide
Module - A generic term for any of the following sections of Kepion: APPS, MODELER, ADMINISTRATOR, and SYSTEM.
See Also: App, Modeler, Administrator, System
Module (App) - See: App
Often used to specifically refer to the different sections of the MODELER or ADMINISTRATOR modules, accessible through the right-hand navigation pane. For example, the All Models node or Deployment node. May sometimes refer more generally to any selectable section, especially when the selection is part of a hierarchy.
Online Analytical Processing
Q - T
One of three types of users that can be added to a Workflow, along with Contributor and Approver. Reviewers can view and comment on a submission, but cannot modify the data.
The Kepion term for a group of users. Users belonging to the same Role will inherit all the permissions and security defined by the Role. Adding Groups and individual users to Roles can help with security management and automation.
See Also: Group
The following Application Security Roles are predefined for every Application: Administrator, Model Designer, and Advanced Contributor. Each comes with a specific set of permissions and security settings, configured for that role. The System Security Role includes the System Administrator.
See Also: Administrator, Model Designer, Advanced Contributor
A generic term for either the App, set of Apps, an entire Application, or a set of Applications built to fit a given scope of customer requirements.
SQL is a language for Relational Databases. A SQL Rule is a script written with raw T-SQL code to perform actions within an Application. As all the data that powers the Application is stored in a SQL Database, SQL Rules can be leveraged to build from simple to highly complex business rules.
A type of Application Variable that holds raw text, and can be injected in a multitude of different locations within an Application. Standard Variables can define a single data point, like an integer, or more complex definitions like SQL or MDX snippets.
Resources: Use Standard Variables
A saved or submitted instance of a Dashboard or Workbook App by a user. A submission is also known as an App Instance. Submissions can have various states associated with it, including saved, approved, and rejected. An App can be configured in the ADMINISTRATOR module to allow multiple submissions. Note that the data posted in one submission affects the database immediately, and will change the data in all other submissions and Apps.
A component within the Dashboard Editor used to display generic text on the Dashboard. Text Components can be further customized into buttons, action rules, and hyperlinks in the settings configuration menu.
U - X
An identity in Kepion that represents either a real person, or a machine account that can access various components of the system. Security can be granted and denied to individual users.
Similar in concept to Excel Workbook, the Workbook is defined by a set of one or more Forms.
The Workbook App is defined by a set of Forms that together creates a Workbook that business users can interact with.
See Also: Dashboard App
The process that a Workflow App's submissions and user data undergo to be changed, reviewed, and approved.
See Also: Basic Workflow, Advanced Workflow
Y - Z