inorigo® Application Builder is a module used to build Applications to view and interact with information. Applications can vary widely in usage, complexity and in their layout. An inorigo Application can easily display parts of the information model built in inorigo Model Builder. Typically Knowledge Sets are used to create reusable knowledge blocks that can be used in multiple Applications throughout the inorigo instance. Applications are not restricted to data from inorigos database, but can display and merge multiple external data sources together.

Components

inorigo Application Builder make use of Components to display information and visualizations of data. Filter Components list data for users to select and view, and, Result Components visualise or clarify data by rendering Charts, Maps, Graphs, Matrices.

Panels

A panel is the area in which content can be added to an Application. Design your Application by adding additional panels to split content over tabs or parts of the screen.

Windows

Inorigo Launcher is used to Launch the Model Builder and Application Builder Modules. Upon first use, download and install the inorigo Launcher. User Menu  > Help > Download Launcher

Once the Launcher has been installed, access Application Builder through the workbench. Inorigo Launcher will automatically download and install the necessary Java files to your computer.

Troubleshooting

– Nothing happens when I click the Model/Application Builder icon in Workbench

Ensure that your browser and operating system permits inorigo Launcher to start from your browser.

Other Operating Systems

Java Webstart is used for all other operating systems.

When opening Application Builder the Applications panel appears with all available (accessible by User) Applications. Access this menu again through File > Open  [CTRL + O]

Filter the list with the Search Field and toggle Bookmarked / All Applications

Its possible to open mulitple Applications from the same instance simultaneously. First open a new Application Builder window through Modules > Application Builder and then bring up the Applications panel [CTRL + O] to open a second application.

Filter Components are commonly built by creating a linked tree structure where a Filter Component is added to the Application through a link from another Filter Component. In Filter Components that are linked, selecting a unit in one Filter Component will result in a selection of the units in another Filter Component that have a connection to the selected unit in the information model. This allows users to view the relationship between units, to trigger result components through selections etc and should be understood as the core functionality for interacting with information in Applications.

In the image below the Filter Component containing Employment (p1) has been linked from the Filter Component containing Persons (p0). When selecting the unit Amy Higgins, the unit Amy Higgins @ inpraxius AB (100 Percent /Year) also becomes selected. When a unit is selected by the user it becomes Explicitly Selected which is illustrated by the Blue and Bold font. All connected units in linked filter components will then become black and bold, they are Implicitly Selected. Other components does not normally differentiate over explicit and implicit selections unless  certain expressions are used. The shift in color is mainly to help the user remember the clicked unit.

Selections can be narrowed down by adding to an explicit selection from implicit selections. In the image below, all units in the right component have connections to the unit Inpraxius AB in the middle component. Once the unit in the middle component is also explicitly selected, only units in other linked filter components that have connections to both selected units will be implicitly selected.

Selections in Structured Filter Components (tree structures)

When clicking on a node in a selection box the behavior of how to determine the selections deserves an explanation. The examples below is based on a selection box where you want to see the Composition-strucutre, i.e. objects that have Contains– and / or Consist of-relations to one another.

Action	Description	Result
	A selection box where no selections have been made.
Click on the top node Car.	Car and all its descendants have been explicitly selected.
Toggle selection by pressing the CTRL-key (on the keyboard) and clicking on the node Block.	The node Block should be de-selected, but the rest of the selected nodes should remain in the same state.
Change selection by clicking on the node Rim.	The node Rim is selected and the rest of the selected nodes are deselected.
Add to selection by pressing the CTRL-key and clicking on Tyre.	The unit Tyre is added to the selection so that both Rim and Tyreare selected.
Toggle selection by pressing the CTRL-key and pressing the mouse key on Rim and drag it down to Tyre.	Both Rim and Tyre are deselected, and the rest of the nodes becomes selectable, i.e. it returns to original state.
Press the ALT-key and click on Engine.	Only Engine is selected.
Add Car to the selection by clicking on it while holding down the CTRL- and the ALT-key.	The node Car is added to the selection.

The Application Navigator is available in a hidden panel to the right in the workspace. Reveal it by pressing the leftmost button Application Navigator in the image above. The navigator panel may be pinned to the workarea. Clicking a component in the Application Navigator selects the component.

The Application Navigator consists of two tabs, Panels & Components and Filter Structure.

Multiple components/panels can be selected from the View navigator with CTRL + Click. Use this functionality to delete or copy several components simultaneously.

Panels & Components displays all panels and the Filter Components that they contain in the application. Press New Panel to add a panel to the application.

Panels containing components are represented with a folder icon and empty panels are represented with the inorigo logo.

Move components between panels by right-clicking and selecting move to, or delete components by pressing Delete…

Filter Structure only displays structure of Filter Components and allows you to hide/reveal connected components by pressing the plus or minus symbols.

Right-clicking a component allows you to delete it or move it to another panel. Notice that parent components can’t be deleted since that would break a link between other Filter Components.

The area in which all components are places consist of at least one Panel This is the area where the application is built. Components will maintain the scale and position given on a panel when an application is running. Applications aren’t responsive to resolutions so it’s important to plan for standard resolutions when positioning components onto a panel.

By default a panel named Main is added to all new Applications.

Like components a panel can be hidden, named and set to display background images and colors.

New panels are added to the Application from the Application Navigator menu.

By default they are placed floating on top of the other panel. Applications with floating panels are prohibited from being saved, since they cannot run properly in browsers. Always dock the panels into your desired configuration by drag-and-dropping them into position.

By docking panels as full-screen, they will appear as tabs in the Application, where the user may toggle between tabs.

By docking a Panel to either side of another panel, the Application is will be split to display both panels.

These configurations can be combined in many ways, as long as all panels are docked.

View Navigator is efficient for viewing and editing multiple components simultaneously.

Component layering management
Components can be layered on top of one another. To manage layering, the following functions can be found by right-clicking on the component header, or in the View Navigator

• Bring to Front =Target component is placed at top front
• Bring Forward = Target component moves 1 step forward from its position in the layers
• Send to Back = Target component is placed at the very back
• Send Backward = Target component moves 1 step backward from its position in the layers.

Copy and Paste Components
All types of components can be copied and pasted. Right-click on a components header or the View Navigator and choose Copy/Paste.

Multiple components can be copied and pasted simultaneously from the View Navigator. If the copied components are located within the same panel, their positioning will be honored. If not, they are listed left to right.

A copied component holds all the settings and links as the original component. A filter component that has been linked from another filter component will thus stay within the same tree structure when copied.

Subset Copy

Subset copy can be used to clone a filter component, whilst creating a link between them. This is useful when the first filter component in a structure is to be copied, and a link should be established between it and the original.

Application Builder has three types of components, Filter, Result and Layout components. A Filter Component holds either information units from inorigo or other data sources defined by search queries. Users of the Applications interact with Filter Components by selecting units that they contain. A selection in turn can trigger connected Result Components, connected units in other Filter Components and more.

Each Filter Component is given a p number for referencing. The first box gets the identifier p0, the second box p1 and so on. The identifiers may be used to refer to a Filter Component in expressions.

Create a Filter Component

Right-click any empty area in a Panel to reveal the Components menu and choose the Data type that you intend for the Filter Component to contain. Use the Search Panel to define the content of the Filter Component.

Example – Create a Filter Component that contains Persons

1. Reveal Menu and choose Association

2. A search Panel appears, select Definition to find the Association Definition Person

3.A new search Panel appears, Search for Person, select the Association Definition and press OK.

4. Press Search to Preview the result of the search filter and press Search Query  to create the Filter Component

Linking Filter Components

To link a Filter Component from another filter component, either right-click any unit in the original filter component, or find the Link to Component menu in the filter component settings panel. When creating a link you have five options;

Example – Link Filter Component containing Persons to Employment and link Employment to Organisation

1. Choose more connections from Persons

2. Find the desired reference Employment. Either drag and drop the or press add connection. A Search Panel appears with a preset filter, Definition = Employment. You may add criteria or press Search Query to create the Filter Component.

3. In the same manner, right-click any unit in the new filter component with Employments and choose more connections.

4. Select the connection to Employer and drag it to the Panel, press search query. These three Filter Components are now linked and the units are connected as displayed in the image below

Head Settings

Edit Content Reveals the search panel that determines the content of the Filter Component. At any point the search criteria can be edited to change the content of a filter component.

Filter components that have been created through a link from other  Filter components have the option to toggle Show connected items only  on and off. By disabling show connected items all units that fits the search criteria (define it under Edit Content) will be displayed. If Show connected items only is enabled, only those units that match the search criteria and have connections to the units in the filter component that the current filter component is linked from will be displayed.

The image below displays and example of the functionality. The Search criteria for email address is all email addresses. The Filter Component is linked from Organisation. If Show connected items only is enabled, only email addresses connected to organisation will be displayed.

A filter component may show either a flat list, or a structured tree of selection. In a basic and predefined configuration it is possible to structure the selection by either classification (the relation Classifies/Is a kind of) or by composition (the relations Consist of/Is a part of and Contains/Included in). Choosing any of the structured tree alternatives will cause the application to loop through all items in the list to find its parent (according to the proper relation(s)). As the top parent is found, all selection is structured down the tree. The application will not loop downwards from the original items though, but stops at the level to which the original box items belong.
The advanced configuration allows many more relation types and options.

The Recursive Structure Filter component

The outcome in a Structure Filter component is dependant of the initial content in the Filter component, and the different kind of relations that exist to this content.

A Structure Filter component is created between objects of same type, e.g. it is not possible to mix Generic Units and Specific Units within the same Filter component.

A Structure Filter component can be configured as one of following; Classification, Composition or Recursive.

Legacy Structures can manually be re-configured as Recursive

Only Recursive Structure allows to display Bundle (on web)

Only one Connection is allowed per Filter component

Configuration panel

The controls for Structure Filter component is found in the upper section of configuration panel, while details are configurable in the lower section.

A good piece of advice is to consider the different options to build a structure that enhances readability and decreases unnecessary complexity. Let’s look at an example;

The top Filter component displays a plain Is a Part of relation, while the lower Filter component displays the Is a Part of relation with Reversed Tree option.

A reversed Classifies (or any relation looking at children) will tend to display parent nodes more than once, which may not be desirable, while a reversed “Is a Kind of” (or any relation looking at parent nodes) will only display parents once. The settings depends on what kind of information resides in the Filter component and what output is expected.

Input panels are used to create, edit and delete units through an Application.

Video Tutorial on creating input Panels for filter components

Layout

Use the rightmost arrows to determine the order in which the nested entry panels appear in the Application. The nested unit placed on top in the list will appear leftmost in the entry panel.

Size Control

Specify the height and the width of the Attribute Value window. Split Position defines where the nested entry fields start counting from the top of the entry panel.

Delete entries to reset to the default values (Default values are given in italic, customized values are normal)

With the introduction of Size Control, manual entry panels re-sizes are no longer remembered when a panel is closed and reopened.

Tooltip

Make use of the attribute property Tooltip to display a tooltip to in the input panel. Tooltip is available as property for all attribute classes.

Each Filter Component (not including the advanced) have editing settings that control the set of actions allowed on that filter component on the web. The editing actions allow a user to open units and have access to the unit attribute values.

Create

User with Normal or Sysadmin rights gains the right to Create new objects in the Filter Component. This option also enables the right to Copy an object in an Application.

Subclass

User with Normal or Sysadmin have the right to Subclass objects in the Filter Component.

Read

User with access rights in have the right to right click and choose open, to view objects in the Filter Component.

Update

User with Normal or Sysadmin have the right to Update objects in the Filter Component.

Delete

User with Normal or Sysadmin rights in have the right to Delete objects in the Filter Component.

Copy

User with Normal or Sysadmin rights in have the right to Copy objects in the Filter Component. If the object being copied also has relation(s) to Nested Unit(s), these will also be copied.

Bookmark

User with access rights in have the right to Bookmark objects in the Filter Component. This feature is only available in the inorigo® Workbench.

It is possible to configure the unit attributes and their values by pressing the edit button located to the left of the Filter Name. The plus button adds a new nested entry panel.

This opens up the Edit panel.

Note that there might be a fifth box in the top section of the window; underneath “Definition”, a box with “Is a kind of” will appear if the units may have super-classes.

The bottom section of the window shows the unit definition, super-class (if applicable) and all attributes.

Instead of showing multiple filter components having to edit each one separately, it is possible to nest other units into the other Unit Attribute Panel. The filter component unit is referred to as the nesting unit and the other ones nested units. To be able to nest a unit it has to reference the nesting unit with a relation or with an attribute.

Nested units will be displayed in the same input panel to avoid confusion from end users. For nested units that have one attribute, an entry field is added and will appear just as an attribute for the nesting unit See Phone Number or Email in image below. Nested units with more than one attribute will appear as a Card that can be collapsed and expanded to provide a better overview in the panel. See Employment in image below.

To nest a unit press the Add button below the unit attribute edit button.

This opens up the Add (nested unit) panel.

Nesting with references

There are two ways to complete this task; one is Quick Setup and the other is a manual setup. Use quick setup to nest a unit with an attribute reference and manual setup to nest a unit with a relation reference.

Quick Setup

Use the connections panel to identify a desired reference to nest into the input panel. You may choose to include abstract or disabled attributes from the panel. The indentation in the panel reveals the classification structure for the referents.

Below is an example of a nested unit chosen through quick setup.

The most important and required are:

• Title, default is given
• Definition is required when dealing with Associations and Specific Units, a default definition is selected for you
• Point out the Nesting Unit in the Automation column in the lower section, a default is given
• You should decide the multiplicity for the Nested Unit, the default value is 1.

Press OK button to finish the configuration, there is no more required setup to finish the configuration. Find the description of each field below:

It is possible to nest many units. The example below illustrates a possible model in inorigo® Model Builder:

Nesting many units could look like the image below:

Nesting with relations

When using a manual setup choose one of the relation types in the combo box Type:

First of all, set the relation Type, e.g. Generic- or Specific Unit Relation:

The most important and required are:

• Title
• Point out the Nesting Unit in the Automation column in the lower section, it is defaulted to point at attribute objectOneID
• relationSpecifierID; select the relation from a list of values in the Automation column
• objectTwoID; If you want to limit the Valueset from the one specified in the model, pick a Valueset – Filter Component – to select values from.
• You should decide the multiplicity for the Nested Unit, the default value is 1.

Press OK button to finish the configuration, there is no more required setup to finish the configuration. Find the description of each field below:

By specifying a valueset – for objectTwoID in this example – it is possible to filter objects that have the same type of relation but have different parent objects.
This applies to all Generic domain relations except AsInstanceRel since that relation has a Rule attribute to control this behaviour.

Consider the following example of Model Builder structure where Generic Unit Thing x is included in two separate items with different parent objects (Generic Type):

Building an Application to show the relations between objects to eventually be able to create objects on the web could start like this:

We want to separate the objects in p2 box since we want to manage them separately. By setting a definition (parent object) to filter the content of filter box p2 and adding another filter box to show the items of the other parent object (Designs and Models):

Now it is possible to control the contents of the Nested Units when specifying them in Editing panel. First of all we need to find out which object belongs to objectOneIDby opening the object being used as Nesting Unit (1) and then open Edit Relation panel (2):

Now we know that Generic Units in p1 filter box is objectTwoID. Add a new Nested Unit for p1 filter box:

The valueset defined for Nested objects (Designs) will make sure a filter is applied to only show items with parent object Designs on web.

The other Nested Unit for Models is created similarly, just using the valueset from p3 filter box. Final result with two Nested Units:

By pressing the pen symbol on any attribute we can configure how it its behavior in the input panel through this Automation panel

Quick Setup

Lists predefined configurations that can be used.

• Fixed Value = Sets the combination Mode=Suggested, Settings=Immutable
• Default Value = Sets the combination Mode=Suggested, Settings=Editable & Resettable

Mode

Mode controls the automation behavior.

• Off = The value will never be set automatically.
• Suggested = The value will be set by the system only once (when panel is opened) or by reset.
• Automatic= The value will be set continuously by the system as the user edits any other value within the input panel

Settings

Immutable

An immutable value cannot be changed once it’s been saved to the database, no matter if it’s  a person or an automatic expression that attempts to edit the value.

• True = The value can be changed only when the Unit is new (not yet created).
• False = The value can always be changed.

Editable

Editable refers to manual user editability from the panel only.

• True = The user is allowed to manually edit the value.
• False = The user is not allowed to manually edit the value.

Resettable

• True = A reset button is displayed allowing the user to (re)calculate the value.
• False: No reset button is displayed.

Volatile

A an attribute must be set as volatile (previously known as Calcualted) in Model Builder for the option to be enabled. The actual values are never saved, but continuously executed every time they need to be displayed. Note that these values have negative impacts on performance.

• True = The value is not saved to DB.
• False=The value is saved to DB.

Value

Sets the type used to create the automation / suggestion.

• None = nothing is used, the value will either be NULL or manually entered by the user.
• Reference = Used if the attribute is the nesting unit.
• Explicit = Set one value, like a string of text or a specific inorigo unit.
• Method = Call on method to generate the value
• Expression = Format an expression to generate the value

Mutually exclusive settings

• Mode=Automatic can not be combined with Editable=True.
• Source=Reference can not be combined with Editable=True.
• Mode=Suggested can not be combined with Volatile=True.

How an automation or suggestion is triggered

The configuration is given to an attribute attribute for the specific input panel only. Other input panels or places to edit the same attribute in inorigo will not share the given automation configuration.

Mode = Suggested: The suggestion is triggered when the input panel is opened to create. Once an attribute value has been set and saved to the database a value will never be suggested again. This applies even if the value = NULL

Mode = Automatic: the automation is executed whenever a user sets or make any changes to any other attribute value within the input panel. This will continue to occur every time the input panel is opened and any change is made.

Referring to other values within the nested panel via Expressions

When writing expressions for input panels, it’s possible to refer to any other attribute in the panel. This example demonstrates how.

I want to generate automated email for an attribute in Email.

To do so I must

• Get the first and last name from within the nesting unit person.
• Get the employing organisation from the nested unit Employment.

Refer to attributes within a unit

{Attribute Name}

example:

{Person}

Refer to the nesting unit from a nested unit.

The nesting unit can be referred to in a standard way, either by referring to {Person} or the units ID.

$get({Person},”First Name”)

I’d then like to add a dot and the last name afterwards.

$get({Person},”First Name”) + “.” + $get({Person},”Last Name”)

Refer to another nested unit from a nested unit

To refer to another nested unit, we must traverse through the nesting unit in the expression. In this expression we get the attribute organisation, from the nested unit Employment, that is nested to person.

$get($get({Person},”Employment”),”Organisation”)

Organisation is an association unit and if I’d like to find a specific attribute from within organisation, I’ll simply add another statement to point to the specific attribute, in this instance the attribute Name.

$get($get($get({Person},”Employment”),”Organization”),”Name”)

I can then add the whole expression together, and write out an “@” and “.com” to complete the email address.

$get({Person},”First Name”) + “.” + $get({Person},”Last Name”) + “@” +

$get($get($get({Person},”Employment”),”Employer”),”Name”)

+ “.com”

Remember that utilizing ID’s rather than names is a more stable way of writing expressions.

You can easily add the ID, rather than the name by CTRL + clicking a variable in the expression editors menu.

Input Panels be referred to via expressions, and can thus be added as calculated columns or buttons in an Application,

How to add a button that refers to an input panel to a Matrix calculated column

• Create a Filter Component and configure your input panel.
• Create a Matrix Component and populate it with data from the Filter Component {pX}
• Add a Calculated Column (HTML) with the following expression
• “<button onclick=\”getApplicationRuntime().postEntityAction(‘Create‘,’AsInstance’,'” + $GET(@Y_Object,”ID”) + “‘,’p0’)\”>CREATE</button>”
  • Create can be replaced with Read, Update, Delete, Bookmark for desired usecase.
  • CREATE can be replaced with desired naming on button.

How to add a button with customized styling

• Create a variable style
• “<style>.button {background-color: #4CAF50;border: none;color: white;padding: 1px 2px;text-align: center;font-size: 11px;cursor: pointer;}.button:hover {background-color: #008CBA;color: white;}</style>”
  • Update the HTML with your desired styling
• utilize the following expression for the Matrix Calculated Column (HTML)
• “<head>” + {style} + “</head><body><button class=\”button\” onclick=\”getApplicationRuntime().postEntityAction(‘Create‘,’AsInstance’,'” + $GET(@Y_Object,”ID”) + “‘,’p0’)\”>CREATE</button></body>”
  • Style is the name of your variable

Group: As the amount of data in a box may be very large, it is possible to move selected- and selectable units to the top of the box. This effectively removes the problem of having to scroll to find selected units in a long list. Check the Group option to group the selection. Default setting is On.

No selection shows all rows: Any resulting component will display a result as if all objects were selected in a Filter component. Default setting is Off.

Show structure controls: Enables the user to manage the outlook of a tree structure. Default setting is On.

Show filter field: Enables the user to apply a filter to reduce the amount of objects in the Filter box list. Default setting is On.

Sort: This setting defines the sort order in Filter Component on the web. Possible values are Ascending (default) and Descending.

Background

Color specifies a background color, background colors will always fill the component. Overlapping components will be partly covered when using background color.

Image can be added as background as well, Select an already added image from inorigo or add one to a unit. Press the magnifier  and choose computer to upload a new image. Press Delete  to remove the background.

A background image can be scaled in the five ways displayed below.

Web Layout Options

1. Enables the title bar. It must be visible to display a title bar Tooltip, the Search Button or the Menu.
2. Enables the footer bar. It must be visible to display the Edit Buttons or the Counter.
3. Enables the search field permanently under the title bar. Search Button can be used as a more compact alternative.
4. Enables the counter of Selected / Total items in component.
5. Enables the edit buttons permanently in the footer. Menu can be used as a more compact alternative.
6. Enables the search button. The search button toggles a search field under the title bar.
7. Enables the menu. Users reveal the menu by clicking the hamburger icon in the top-right corner. Available functions in the menu varies over components, editing settings and user rights.
8. Replaces component box with a searchable drop down menu.

There are many advantages in using Knowledge Sets as foundation for applications. To name a few, you are able to

• Write queries that determines the content of Filter Components in ways that the Search Panel cannot do, such as adding OR statements.
• Leave out Filter Components that contains references between content for improved performance structure in Application Builder
• Reuse Knowledge Sets in multiple Applications to build your Applications faster and to centralize data governance.

Basing an Application of a Knowledge Set

Updating a Knowledge Set in Application Builder

It is possible to display tabular data in Application Builder, either from a source in the form of an Excel-sheet or a tab-separated text-file. The source has to be stored as a “Resource” in inorigo®.

You also have the possibility to retrieve the data by an SQL-statement or a URL pointing to tabular data, i.e. an Excel-sheet or tab-separated text-file.

Video tutorial on Calculated Filter Components

A Calculated Filter Component is generated from the content of another filter component via an expression. They provide formatting capabilities for tailored, with no required changes to the business model.

To create a Calculated Filter Component, go through the link to component menu from any filter component and select Calculated Filter Component…

The default expression, @item

creates a subset copy of the filter component.

To update content in a Calculated Filter Component, edit the expression under Content in the Settings Menu.

Usage Example

There are endless applicable user cases for Calculated Filter Components, these are a few examples. The functions documentation available from the workbench and the expression editor provides documentation on available functions.

The $CASE function can be used to create conditions from the objects in the original filter component:

$case(@p1 > @p2, “Greater”, @p1 = @p2, “Equals”, “Else”, “Less”)

In this example CASE is used to link all objects with a value larger than 15 to High Priority, all values greater than 15 (but smaller than 15) to Low Priority, and all other values to No Priority.

$CASE(@item>15, “High Priority”,@item>12, “Low Priority”, “ELSE”, “No Priority”)

Additional cases can be added to the expression.

Notice that the same result can be achieved by creating and linking objects in the Model Builder, Calculated Filter Components are useful for application-specific solutions that are not intended to be kept in the model.

A result component bases its input on selections made in filter boxes. The selected values becomes available to the result components via expressions. Every filter component is assigned a variable name, e.g. p0, p1 etc. In the result component you are able to access the selected data by using the appropriate variable name, e.g. $sum(@p0). The expressions gets the input (p0) which is a list of selected objects and aggregates the values of the attribute Amount. The result is subsequently available to the component.

In addition to using expressions, you also have the opportunity to use methods for more advanced calculations. In some components you may select a method directly, however, a method can also be invoked from an expression, e.g. $call(“My Process Unit Definition/My Method”, @p0, @p1). Please note that you can supply any number of input parameters to the method and the method should return a result that can be vizualised by the component.

A method refers to a change method, defined in the Methods tab of a change. Find the predefined method in the drop down or search for it using the lookup button. Defining a method is a skill of its own and requires education and a very good understanding of the information structure in inorigo® Model Builder.

An expression is a simple form of method. It doesn’t contain any advanced functions (like looping), but is more powerful than methods to use for simple calculations, such as summarizing attribute values.

Defining an expression is also a skill of its own. It requires some training, but no formal education. A simple example will illustrate the nature of expressions:

Expressions can also hold HTML code, for use in Calculation Boxes or Text Area Components.

Putting this HTML code:

“black hot drink

white cold drink ”

into an Expression field for a Calculation box would result in:

When you want to display a list with URL links in a calculation box

Step-by-step guide

Prepequisites for the example : You have created a filter box named: p1 , The Attribute name= “Internal Link”

When you want to display a list with URL links in a matrix

Step-by-step guide

Prepequisites for the example : You have created a matrix with one or more column/-s  containing HTML link/-s

When you want to embed a redirect button in an Application.

Embed a static HTML page

The chart components in Application Builder give the user a way to graphically view and examine the data stored in inorigo®. The different chart components are Bar Chart, Bubble Chart, Line Chart, Pie Chart and Meter which all work in a similar manner.

Bar Chart Settings

Setting	Description
X-Axis Title	The title of the x-axis. Possible to disable from tooltip by un-ticking the check box.
Y-Axis Title	The title of the y-axis. Possible to disable from tooltip by un-ticking the check box.
Tooltip	Enable or disable the display of axis tooltip
Aggregation	This option is applied on charts that has a 2nd or 3rd dimension.  Bar chart is an example of a two-dimensional chart, where the handling of multiple values will be applied on the y-axis. Bubble chart has three dimensions, why the handling of multiple values will be applied on the bubble size (if both x- and y-values are same). User needs to determine whether the values should be summarized or averaged.
Sorting	Value Description X Ascending Will list the values on X-axis ascending X Descending Will list the values on X-axis descending Y Ascending Will list the values on Y-axis ascending Y Descending Will list the values on Y-axis descending Z Ascending Will list the values on Z-axis ascending (only Bubble chart) Z Descending Will list the values on Z-axis descending (only Bubble chart)
Color	Single: Specifies a single color, used throughout the serie.Generated: The system will generate one color per x-axis value. Unit Attribute: Specifies, with an expression, the unit attribute from which to fetch the color. Observe that the if the color is either generated or fetched from a unit attribute, the color of the legend (shown in run mode) will be white, since it can not show a variety of colours.
Legend Entry	Specifies the text to to be displayed for chart legend in run mode.
Legend?	Enable or disable the display of Legend. Applies on web.
X-Axis Values	Specifies, with an expression, where the values on the x-axis comes from.
Y-Axis Values	Specifies, with an expression, where the values on the y-axis comes from. The y-axis can handle numerical values as well as numerical strings, i.e. strings that only contain numerical values.

 

Extra Tooltip values

Web charts have extended possibilities to show tooltip information. It is possible to add any information based on expressions illustrated in picture below:

Setting	Description
Name	The presentation name for tooltip
Expression	The expression that collects the value
	Add tooltip button
	Remove tooltip button
	Edit tooltip button

 

Multiple series

	Deletes serie
	Adds serie

Setting	Description
Grid	Determines if a grid will show behind the chart.
Outline	Determines if the chart elements will show outlines.
Surface	Flat: Specifies if the chart is shown flat on the background.Raised: Specifies if the chart is shown raised from the background. 3D: Specifies if the chart is shown in 3D.
Multiple bars layout	If the chart has more than one serie, this setting specifies weather the bars should beGroup: placed adjacent to each other. Stack: placed on top of each other.
Min Bar Width	The combination of chart width and the setting below will increase readability of chart as a minimum value of Bar width will be applied. This is very useful when chart size need to be minimized due to space limitations in the Application. When Bars size reach the value specified in settings, the size of Bar will no longer decrease, instead a horizontal scroll bar will compensate for this. Value Description Min Bar Width Set the minimum width of each bar to display on web
Fixed axes	Ticking this check box will enable fixed axes
Min Y Value	Set a fixed minimum Y-value for Y-axis
Max Y Value	Set a fixed maximum Y-value for Y-axis

Setting	Description
Rollover	Determines if the chart elements react to mouse hoovering.
Selection shows outline	Determines if the chart elements shows an outline when selected.

Bar Charts shares the same, Common Layout Settings as most other components. Notice that although available in the application builder, the web layout options revolving around selections such as ‘Edit buttons Visible’ is not applicable since the Bar Chart does not contain any inorigo units to edit.

A Bubble Chart is a chart with bubbles whose size constitute a third dimension (where the x- and y-axis constitute the first two). In the image below, the bubble size represents the area of the country.

Adding Bubble Charts

Add a Bubble Chart by pressing the plus icon ( ) and navigate to the chart menu under the result components. A new Bubble chart component will be added for the user to define.

The Graphs section defines all the information connected to a graph. It allows the user to change the colour and the title of the graph. The fields marked x, y and Bubble size are expression fields that defines the values to be plotted. The expression fields accept expressions that evaluates to lists. The values in the x-, y and bubble size-list will be matched in the same order as they occur in the list. The x and y position of each bubble is locked in it’s position by the values of the axis, just as in a regular chart, but the bubbles have no axis which determines how big a bubble should be, for this purpose there is an algorithm which traverses the values of each bubble and then decides how big the bubbles should be. The size value of the bubbles are proportional to the area of the bubbles, this means that if the size value of two bubbles differ with a factor of two, then the area of the bubbles will also do so.

The Delete icon is used to delete a series and the plus icon () is used to add a new series to the graph.

Getting started

A bubble chart is a way of plotting 3 dimensions of data in a 2 dimensional chart. Just like any other chart it takes two values to determine the position of each point, these are the x and y-values. In a bubble chart it is also possible to determine the size of each point, this is what we call the third dimension.

Below is a screenshot of a bubble chart where different countries are used as data source. The x-axis denotes the population of each country, the y-axis denotes the area of each country and the bubble size reflects the ratio between these i.e population density (population /area). Just as in the other charts, it is possible to add multiple charts in the same Application. In this example all blue bubbles are European countries and the red bubbles are African countries.

As some bubble points might get big and overlap each other it sometimes can be useful to use the zoom function in order to get a more detailed view over the interesting bubbles. This is done by using the scroll heel on the mouse. The picture below illustrates a more detailed view over some of the bubbles in the lower left corner obtained by using the scroll wheel on the mouse.

The data used to produce the chart in this example is obtained from the geography domain. This example uses two charts in the same chart component, one blue and one green and each get it’s values from it’s own filter component. Unfortunately the geography domain in inorigo doesn’t contain area information, the area information in this example was fetched from Wikipedia and is presented below. The area and population density information was manually added as attributes to the countries in inorigo.

And corresponding was done for the African countries.

The picture below shows the whole Application, including the Bubble charts property panel which also shows the expressions used in this specific example.

The example above shows how to use bubble charts with both the x- and y-axis numeric, but it would of course also be possible to let the x and y-expression evaluate to a list of labels and have categories as x and y-axis.

Bubble Chart Settings

Setting	Description
X-Axis Title	The title of the x-axis. Possible to disable from tooltip by un-ticking the check box.
Y-Axis Title	The title of the y-axis. Possible to disable from tooltip by un-ticking the check box.
Aggregation	This option is applied on charts that has a 2nd or 3rd dimension.  Bar chart is an example of a two-dimensional chart, where the handling of multiple values will be applied on the y-axis. Bubble chart has three dimensions, why the handling of multiple values will be applied on the bubble size (if both x- and y-values are same). User needs to determine whether the values should be summarized or averaged.
Sorting	Value Description X Ascending Will list the values on X-axis ascending X Descending Will list the values on X-axis descending Y Ascending Will list the values on Y-axis ascending Y Descending Will list the values on Y-axis descending Z Ascending Will list the values on Z-axis ascending (only Bubble chart) Z Descending Will list the values on Z-axis descending (only Bubble chart)
Color	Single: Specifies a single color, used throughout the serie.Generated: The system will generate one color per x-axis value. Unit Attribute: Specifies, with an expression, the unit attribute from which to fetch the color. Observe that the if the color is either generated or fetched from a unit attribute, the color of the legend (shown in run mode) will be white, since it can not show a variety of colours.
Legend Entry	Specifies the text to to be displayed for chart legend in run mode.
Legend?	Enable or disable the display of Legend. Applies on web.
X-Axis Values	Specifies, with an expression, where the values on the x-axis comes from.
Y-Axis Values	Specifies, with an expression, where the values on the y-axis comes from. The y-axis can handle numerical values as well as numerical strings, i.e. strings that only contain numerical values.
Bubble Size	Specifies, with an expression, where the values for the bubble size comes from.

Handle Multiple series

Additional Series can be added by pressing the symbol to the left under Extra tooltip values.

	Deletes serie
	Adds serie

 

Extra Tooltip values

Web charts have extended possibilities to show tooltip information. It is possible to add any information based on expressions illustrated in picture below

Setting	Description
Name	The presentation name for tooltip
Expression	The expression that collects the value
	Add tooltip button
	Remove tooltip button
	Edit tooltip button

Setting	Description
Grid	Determines if a grid will show behind the chart.
Fixed axis	Ticking this check box will enable fixed axes
Min Y Value	Set a fixed minimum Y-value for Y-axis
Max Y Value	Set a fixed maximum Y-value for Y-axis

 

Bubble Charts shares the same, Common Layout Settings as most other components. Notice that although available in the application builder, the web layout options revolving around selections such as ‘Edit buttons Visible’ is not applicable since inorigo units cant be edited in the Bubble Chart.

Add a Line Chart by pressing the plus icon ( ) and navigate to the chart menu under the result components. A new Line chart component will be added for the user to define.

The Graphs section defines all the information connected to a graph. It allows the user to change the colour and the title of the graph. The fields marked x and y are expression fields that defines the values to be plotted. The expression fields accept expressions that evaluates to lists. The values in the x- and y-list will be matched in the same order as they occur in the list.

The Delete icon is used to delete a series and the plus icon () is used to add a new series to the graph.

Line Chart Settings

Setting	Description
X-Axis Title	The title of the x-axis. Possible to disable from tooltip by un-ticking the check box.
Y-Axis Title	The title of the y-axis. Possible to disable from tooltip by un-ticking the check box.
Aggregation	This option is applied on charts that has a 2nd or 3rd dimension.  Bar chart is an example of a two-dimensional chart, where the handling of multiple values will be applied on the y-axis. Bubble chart has three dimensions, why the handling of multiple values will be applied on the bubble size (if both x- and y-values are same). User needs to determine whether the values should be summarized or averaged.
Sorting	Value Description X Ascending Will list the values on X-axis ascending X Descending Will list the values on X-axis descending Y Ascending Will list the values on Y-axis ascending Y Descending Will list the values on Y-axis descending Z Ascending Will list the values on Z-axis ascending (only Bubble chart) Z Descending Will list the values on Z-axis descending (only Bubble chart)
Color	Specifies a color, used throughout the serie.
Legend Entry	Specifies the text to to be displayed for chart legend in run mode.
Legend?	Enable or disable the display of Legend. Applies on web.
X-Axis Values	Specifies, with an expression, where the values on the x-axis comes from.
Y-Axis Values	Specifies, with an expression, where the values on the y-axis comes from. The y-axis can handle numerical values as well as numerical strings, i.e. strings that only contain numerical values.
Show Trend	Determines if a trend line, used to enhance entry and exit value movements, will show.

Handle Multiple series

	Deletes serie
	Adds serie

 

Extra Tooltip values

Web charts have extended possibilities to show tooltip information. It is possible to add any information based on expressions illustrated in picture below:

Setting	Description
Name	The presentation name for tooltip
Expression	The expression that collects the value
	Add tooltip button
	Remove tooltip button
	Edit tooltip button

 

Display Settings

Setting	Description
Grid	Determines if a grid will show behind the chart.
Fixed axis	Ticking this check box will enable fixed axes
Min Y Value	Set a fixed minimum Y-value for Y-axis
Max Y Value	Set a fixed maximum Y-value for Y-axis

Line Charts shares the same, Common Layout Settings as most other components. Notice that although available in the application builder, the web layout options revolving around selections such as ‘Edit buttons Visible’ is not applicable since inorigo units cant be edited in the Line Chart.

A Meter is a chart that displays information on a user defined scale with user defined colors.

Adding Meters

Add a Meter by pressing the plus icon () and navigate to the chart menu under the result components. A new Meter component will be added for the user to define.

The meter component has ha needle that will move accordingly to what value the expression in the source field evaluates to. In the example above the user has defined a minimum value of 0 and a maximum value of 3000. The expression is evaluated and the needle moves to the position accordingly.

The meter settings allows you to modify its behavior.

A Pie Chart is a circular chart divided into sectors, illustrating proportion.

Adding Pie Charts

Add a Pie Chart by pressing the plus icon ( ) and navigate to the chart menu under the result components. A new Pie chart component will be added for the user to define.

The default settings, which cannot be changed, define how the Pie react when the user interacts with them. Rollover will highlight the segment the mouse moves over and Exploded Segments will make the selected piece explode from the rest of the pie chart when selected.

Pie Chart Settings

Setting	Description
X-Axis Title	The title of the x-axis. Possible to disable from tooltip by un-ticking the check box.
Y-Axis Title	The title of the y-axis. Possible to disable from tooltip by un-ticking the check box.
Aggregation	This option is applied on charts that has a 2nd or 3rd dimension.  Bar chart is an example of a two-dimensional chart, where the handling of multiple values will be applied on the y-axis. Bubble chart has three dimensions, why the handling of multiple values will be applied on the bubble size (if both x- and y-values are same). User needs to determine whether the values should be summarized or averaged.
Sorting	Value Description X Ascending Will list the values on X-axis ascending X Descending Will list the values on X-axis descending Y Ascending Will list the values on Y-axis ascending Y Descending Will list the values on Y-axis descending Z Ascending Will list the values on Z-axis ascending (only Bubble chart) Z Descending Will list the values on Z-axis descending (only Bubble chart)
Color	Single: Specifies a single color, used throughout the serie. Generated: The system will generate one color per x-axis value. Unit Attribute: Specifies, with an expression, the unit attribute from which to fetch the color. Observe that the if the color is either generated or fetched from a unit attribute, the color of the legend (shown in run mode) will be white, since it can not show a variety of colours.
Legend Entry	Specifies the text to to be displayed for chart legend in run mode.
Legend?	Enable or disable the display of Legend. Applies on web.
Sector Names	Specifies, with an expression, where the name of the sectors come from.
Sector Values	Specifies, with an expression, where the values (the size of the sectors) come from. Limitation in Application Builder Pie chart will only display integer value.

 

Extra Tooltip values

Web charts have extended possibilities to show tooltip information. It is possible to add any information based on expressions illustrated in picture below:

Setting	Description
Name	The presentation name for tooltip
Expression	The expression that collects the value
	Add tooltip button
	Remove tooltip button
	Edit tooltip button

Write the following expression to get an extra tooltip showing percent on a Pie Chart: $loop($get(@p0,”Population”),[(100 * $ROUND($COALESCE(@record,0) / $sum(@p0,”Population”) ,2 )) + ” %” ])

 

Setting	Description
Percentage	Together with the selected Label, show size of each slice in percent of the overall chart.
Labels	Line labels: labels are connected to their sector with a line.  Simple labels: labels are shown within a light yellow frame.  Legend labels: Legend labels are shown beneath the chart on web
Fixed axis	Ticking this check box will enable fixed axes
Min Y Value	Set a fixed minimum Y-value for Y-axis
Max Y Value	Set a fixed maximum Y-value for Y-axis

 

Pie Charts shares the same, Common Layout Settings as most other components. Notice that although available in the application builder, the web layout options revolving around selections such as ‘Edit buttons Visible’ is not applicable since inorigo units cant be edited in the Pie Chart.

How to summarize values into one chart series

Components “Permanent Employment” and “Probationary Employment” both contain a Scope with the weekly hours of work for a Person. Persons can either have a permanent, a probationary, both or no employment. The following how-to explains how to display a summary of a persons scope and to filter out persons with null values for both.

The Dataset “DS” holds a calculated component with a summary of the p3 and p4 with the scope values.

Cell refers to the included components in their given order starting from cell.0

The variable DS1 applies a filternull function to the the calculated column sumScope from the dataset.

Since sumScope summarizes the content from Permanent Scope and Probationary Scope, both of them must be null for Sumscope to also be null, meaning that only Persons that lacks a value for both of the two employments will be filtered out.

Use a standard get function to get the data from the variable in the chart. p0 holds Persons and will display thus display the presentation on the X axis, and sumScope will plot the values for Y.

When multiple units are explicitly and implicitly selected in two or more filter components we cannot determine what units that connects to which. The knowledge graph provides that capability.

Tree structures are generated to display the relation between all selected units that has been included in the Knowledge Graph. These tree structures are automatically generated to fit the Knowledge Graph component and can be interacted with in several ways by the end users. Read more about interacting with Knowledge Graphs in applications here

A knowledge graph is based on a series of Filter Components, either added to the Application from a  Knowledge Set or through Search Queries in Application Builder. By generating a table from the content in the included filter components it creates a visualization of the connection between inorigo units.

Tick the boxes for the Filter Components that you want to include in the Knowledge Graph. Notice that it is in the order that you tick the components that they will be displayed in the Graph (left to right). The order is displayed under the boxes.

To set a new order, simply untick all boxes and tick them in the desired order.

Notice that when a given order lacks a connecting unit between two units a blank square is included to display the missing link. In the example below Charles Brooks is not connected to an initiative and Floyd Parsons does not have an employment.

Given order is Person –> Initiative –> Employment

Given order is Person –>Employment –> Initiative

With the same data but a different order, the blank connection is now displayed between Floyd Parsons and Initiatives.

The Matrix component in Application Builder is the same as the matrix component described in Working with inorigo® Model Builder.

In Application Builder there are two options that is worth mentioning; Link and Html

Link

The Link option will interpret the contents as a web link, thus a click on it will open the web browser.

Html

The Html option is more powerful as it will interpret html tags.

Sorting of such a column in a Matrix is evaluated in the following order;

sort property
a tag
span tag
div tag

The sort property require some special attention since this is a feature implemented in code to support special sort.

Example (expanded the example above); “” + $get(@Y_Object, “Name”) + “”

The example shows that rows will be presented with a name (Name) but sorted on the string (String) value. Removing the sort option will sort rows on name (Name).

Matrix Settings

Choose if the content should be fetched through a Method or an expression. Press the  to open the Expression Editor

Matrix Sort Order

Set a sort order in Application Builder and save the Application. The application is loaded with the given default sort order.

Pre-loaded Filter Matrix

Functionality that enables the user to convert a lazy loading temporary Matrix to a pre-loaded Filter Matrix when opened on the web. The Matrix rows will be selectable as any filter component is.

This is only applicable when the matrix is populated by an expression that consist of a single filter component reference (e.g. @p12).

An extra settings area has been added to the Application Builder Settings Panel for Matrix component, called “Web Behaviour”.
First radio button indicates normal behaviour on the web.
Second radio button indicates new behaviour.
“Group” Check box controls grouping of items as in normal filter components.

Another great feature indicated by the name is that objects in the matrix now are selectable.

 Only Applies to the Application Builder. Displays a filter field below the header.

Layout Settings

Matrix Components shares the same, Common Layout Settings as most other components.

In addition to these Common Layout Settings, the Matrix Component have the option to display Icons and Row Headers

Row Headers and Icons visible in Matrix

All grids can also be sorted in the Application on multiple columns by clicking on the column headers, and reset through the menu command reset sorting.

Notice that when units are imported to the matrix through a Dataset, the dataset needs to be updated in order for the matrix column headers to reload. This is done by making changes to and then saving the Dataset.

Clickable tooltips in cells allow matrices to display additional content to users. Tooltips can be html formatted to clarify texts, add clickable links and more.

To add a Cell tooltip, rightclick the desired column and choose add cell tooltip

Edit Cell Tooltip

Type an expression that calls on the desired content in the tooltip.

Examples of use

Display another column in the matrix as a tooltip.

$get(@Y_Object, “Column Name”)

Display a clickable link where the name of the object in the given cell is added to the url.

“<html><body><A TARGET=’_BLANK’ HREF = ‘” + “www.myurl.com/” + $GET(@Y_Object, “Column Name”) + “‘>” +  $GET(@Y_Object, “name”) + “</A></body></html>”

Clickable tooltips in cells allow matrices can be used to display additional content to users. Tooltips can be html formatted to clarify texts, add clickable links, images and more.

To add a Cell tooltip, rightclick the desired column and choose add cell tooltip

Edit Cell Tooltip

Type an expression that calls on the desired content in the tooltip.

Examples of use

1. Display another column in the matrix as a tooltip.

$get(@Y_Object, “Column Name”)

2. Display a clickable link where the name of the object in the given cell is added to the url.

“<html><body><A TARGET=’_BLANK’ HREF = ‘” + “www.myurl.com/” + $GET(@Y_Object, “Column Name”) + “‘>” +  $GET(@Y_Object, “name”) + “</A></body></html>”

Video tutorial on the Resource Viewer component

The Resource Viewer-component is intended to display images and / or other type of Resources.

The list in the resource viewer is populated with an expression and in this example it retrieves the Resource-value from the source attribute Attachment.

$get(@p0, "Attachment")

You may also select if you want the image to be scaled to fit or be displayed in real size. You can also set if you want to display the name of the resource and to show only the image section of the component or only the list section. If you for instance only have documents, it is unnecessary to display the document icon again.

The picture below depicts when you’ve selected to display the list of attachments and their names and hide the image pane.

The picture below depicts when you’ve selected to only show the image pane and to hide the list.

The world map allows the user to add a world map to an Application. The world map have the capability to highlight areas (e.g. countries) or points (e.g. cities). The map in version 4.6.0 is new and is backwards compatible with the pre-configured Country layer. The conversion from the old map will try to identify the source data type and adapt the expression accordingly;

• String
  Match Field = “Country” och Match Value = null
  
• GeGeopArea
  Match Field = “ISO” och Match Value = $GET(@item,”Alpha-2 ISO 3166″)
  
• Other
  Match Field = “Country” och Match Value = $TOSTRING(@item)
  

There are most certainly cases where the conversion will not work, thus requiring manual adjustments.

Map features:

• multiple layers where visibility can be turned on and off on web
• four layer types; Coordinates, Address, Filtered ArcGIS Layer and Fixed ArcGIS Layer
• three template layers; World countries, World major cities and Swedish municipalities, from which the World countries layer is used for backwards compatibility with Inorigo® version prior to 4.6.0
• Map gallery with 10 different map types
• layer url support username and password to allow external protected layers to be added

The choice of Layer Type depends on whether the data is dependent on a selection or whether it should be a fixed layer, and here follows two sections with a brief description of the different types of layers and the first section describes the template layers;

Template Layers

All three template layers are of type Filtered ArcGIS Layer. This means that the plotting on map is depending on a selection made in a filter component and the calculation that follows.

World countries

The most basic example is a filter component with Countries in p0 and a Map Result component. After save, the preconfigured setup will work straight away on web.

World major cities

The most basic example is a filter component with Countries in p0, linked to a location for (City) in p1 and a Map Result component. After a few minor adjustments (Source = p1, Match Value expression = $GET(@item,”name”) and a Fill color), the preconfigured setup will work straight away on web.

Swedish municipalities

The most basic example is a filter component with Countries in p0 (filter Sweden), linked to Is location for (UNECO Location) in p1 and a Map Result component. After a few minor adjustments (Source = p1, Match field =KNNAMN, Match Value expression = $GET(@item,”name”) and a Fill color), the preconfigured setup will work straight away on web.

Layer Types

Coordinates

Use this layer type when Inorigo® object have a relation to (e.g.) an attribute that holds the coordinate that can be plotted on the map. This layer type  comes with a predefined basic configuration.

Supported geographic coordinate system (GCS) are DD (decimal degrees) and DMS (degrees, minutes, seconds).

Example:

It is possible to configure Center Coordinates in either of two ways for (e.g.) Malmö in Sweden:

In the advanced panel of Map, these should be separated with a space or comma;

Address

Use this layer type when Inorigo® object have a relation to (e.g.) an attribute that holds the address that can be plotted on the map. This layer type comes with a predefined basic configuration.  This layer requires internet connection since a request for coordinates is sent to ArcGIS Feature Server. Here is an example what it could look like when being slightly modified;

Example with an Association Definition that contains two attributes – City and Address – that are concatenated into an expression for plotting on map

Filtered ArcGIS Layer

When the output on Map is based on a selection in a Filter Component, e.g. when the filter component holds cities or countries that match ArcGIS field(s). The template Layer World countries is based on this layer type. This layer requires internet connection since a request for coordinates is sent to ArcGis Feature Server.

Fixed ArcGIS Layer

This is a layer type that have a fixed set of data, not depending on a selection made in a filter component, e.g. major cities in the world that would be plotted on map undependant of any selection.

This layer requires internet connection since a request for coordinates and data is sent to ArcGIS Feature Server.

World Map Content Settings – Basic Settings

World Map Content Settings – Advanced Settings

Heat Thresholds

This panel allows user to add any number of thresholds, any combinations of colors, numbers and grouping is possible as seen in the examples below:

The threshols are created using following steps:

1. Add thresholds using  
2. Set the maximum value on the last threshold and optionally set the minimum value on first threshold
3. Set the darkest color on the last threshold and optionally set the lightest color on first threshold. Optionally also set any transparency on color – if an area is to be plotted on map, the transparency will make it possible to see through the selected area on the map
4. Select all thresholds and automatically generate an evenly distributed threshold value series using  
5. Select all thresholds and automatically generate an evenly distributed threshold color series using  

Example with a single series of thresholds and color saturation with a slight transparency

Example where a kind of grouping of colors have been applied on three different ranges of thresholds 

There are some special keyboard commands that come useful when creating thresholds:

World Maps shares the same, Common Layout Settings as most other components. Notice that although available in the application builder, the web layout options revolving around selections such as ‘Edit buttons Visible’ is not applicable since inorigo units cant be edited from the the World Map.

Display settings lets you choose between embedding the webpage in a window, adding it as a link, or as a button. If link or button is selected, you may format the colour and size of the text in the link/on the button.

If the content of the web page component is an inorigo application, you may toggle the visibility of the title and toolbar with Title Visible and Toolbar Visible

Selections over multiple applications

Utilize the webpage component and an URL parameter to make a selection in one application trigger a selection in another. Useful for embedded Applications or a flow stretching over multiple Applications.

The webpage can be set to display as Embedded, Button or Link.

Utilizing Embedded will now display the application Slave within the Application Master and selections in one will trigger selections in the other.

Utilizing Button will create a button that opens the Slave application in a new tab with the current selection.

Display a webpage from an URL provided in an attribute.

$atIndex($GET(@pX,”Attribute Name”),0)

Only one selected unit can be displayed.

The Aggregation Component supports DataSets, multi column filter components (advanced), entity Filter components and Expression Variables. Before an Aggregation table is added to the Application, it is strongly recommended to make the necessary adjustments in the source component; like changes in column class or header names. If changes must be made in Aggregation source component, it is adviced to redo the Aggregation table.

There is an indicator in Aggregation table on web that suggest a remake of the table is necessary:

The “Power” setting can be used to scale displayed values both up and down, for Grams to Kilos set it to -3 and for Kilos to Grams set it to +3. Use the Precision setting to improve readability.

Application Builder will display a raw values table only.

Aggregation Content Settings

Setting	Description
Type	SelectorNode (Filter component) or Dataset
Source	The source data for aggregation. Available types are SelectorNode (Filter component), Dataset and Variable.
Groups	Number of Group columns
Aggregations	Number of Aggregation columns
	Configure the Group and Aggregation settings

Aggregation Configuration Settings

Layout Settings

Aggregation Components shares the same, Common Layout Settings as most other components.

In addition to these Common Layout Settings, the Aggregation Component have the option to display Icons and Row Headers

Row Headers and Icons visible in a Matrix (appears in the same way in aggregation components)

All grids can also be sorted in the Application on multiple columns by clicking on the column headers, and reset through the menu command reset sorting.

Notice that when units are imported to the matrix through a Dataset, the dataset needs to be updated in order for the matrix column headers to reload. This is done by making changes to and then saving the Dataset.

The setup for Aggregation on such a component can be accomplished using several methods;

select the filter component and use Add component

select the filter component and use Links in Filter Component Settings

both of the above methods will automatically pre-select the filter component in Aggregation Edit mode:

The last method, right-clicking any empty area in the Application;

will force you to select the data source in the drop-down list when entering Edit mode of Aggregation:

Once the Source have been selected, the configuration panel will be filled with available columns for Group and Aggregation. Each row in the configuration panel represents the attributes for the objects listed in Filter component:

By default, all columns are available for grouping, and columns selected for grouping cannot be used for aggregation(s) and vice versa. All columns, that are of integer or double can be used for aggregations.

Each cell in the Group or Aggregation configuration need to be double-clicked to be available for further configuration.

The advanced filter component is based on Resource Content (xls, txt), SQL or URL.

The setup for Aggregation on such a component can be accomplished using several methods;

select the filter component and use Add component

select the filter component and use Links in Filter Component Settings

both of the above methods will automatically pre-select the filter component in Aggregation Edit mode:

The last method, right-clicking any empty area in Application;

will force you to select the data source in the drop-down list when entering Edit mode of Aggregation:

Once the Source have been selected, the configuration panel will be filled with available columns for Group and Aggregation. Each row in the configuration panel represents the result from SQL, xls chart columns or text file headers:

By default, all columns are available for grouping, and columns selected for grouping cannot be used for aggregation(s) and vice versa. All columns, that are of integer or double can be used for aggregations.

Dynamic Column Names

This check box allows the Aggregation table column headers to reflect the result from origin SQL statement. This means that if the source SQL column names change, the column names in the Aggregation table will also change (on web).
Note that when this setting is enabled, it will override manual changes made for column names in Source filter component and Aggregation table.

Each cell in the Group or Aggregation configuration need to be double-clicked to be available for configuration.

The Dataset, if created for an Application,  is based on a selection of Filter components added to an Application.

The setup for Aggregation on such a component is accomplished with the following alternatives;

use Add component

The other method, right-clicking any empty area in an Application;

will force you to, first of all, select the Mode, i.e. switch the default FIlter Component to Dataset:

and then the data source, i.e. select the appropriate available dataset to use for aggregation:

Once the Source have been selected, the configuration panel will be filled with available columns for Group and Aggregation. Each row in the configuration panel represents the selected Filter components in Dataset; pX:

By default, all columns are available for grouping, and columns selected for grouping cannot be used for aggregation(s) and vice versa. All columns, that are numbers of integer or double can be used for aggregations.

Each cell in the Group or Aggregation configuration need to be double-clicked to be available for detailed configuration.

Any expression variable can be used as source for Aggregation table. The available expressions is found in the Application Builder design tool – Application Settings, tab Expression Variables.

The setup of Aggregation will be based on the Application here:

Continents in p0 and Countries in p1 with their own (separate) set of attributes. Two attributes from p1 have been added in separate filter components p2 and p3.

Create a Dataset (“DS”) including all filter components and an expression variable; Var1 = $AGGREGATE(@DS, “SUM”, “p3”, $PACK(“p0”, “p1”, “p2”))

The setup for Aggregation on such a component is accomplished with the following steps;

use Add component

The other method, right-clicking any empty area in the Application;

will force you to, first of all, select the Mode, i.e. switch the default FIlter Component to Variable:

and then the data source, i.e. select the appropriate available Variable to use for aggregation:

Please be aware that Variables exist only when input have been selected for the calculations, i.e. when no selection exist the Variable does not exist, and this is indicated when selecting the Variable in settings panel;

Perform a selection in any filter component used by the variable and the Aggregation settings panel will be fully configurable.

Once the Source have been selected, the configuration panel will be filled with available columns for Group and Aggregation. Each row in the configuration panel represents the data included in the expression:

By default, all columns are available for grouping, and columns selected for grouping cannot be used for aggregation(s) and vice versa. All columns, that are numbers of integer or double can be used for aggregations.

Each cell in the Group or Aggregation configuration need to be double-clicked to be available for detailed configuration.

Note that this chapter only applies to inorigo® version 4.4.0, where the improved version of Aggregation is introduced. In future versions, the old Aggregations will not be supported, thus the Aggregations need to be re-designed if they are not converted in 4.4.0.

It might look like the conversion is not required since the web Application in version 4.4.0 support both the old and new Aggregation, it is converted in the fly. The support for the old Aggregation will however be removed in future versions, so it is important to perform the conversion in the Application design tool; inorigo® Application Builder

The conversion is simple and straight forward, just follow the steps as described below.

1. Open the Application that contains the Aggregation in inorigo® Application Builder and press the Edit button. You will be asked whether or not to perform the conversion, just click YES.
2. You will be prompted that the conversion was successful, just click OK.
3. The final step before conversion is complete is to Save the Application. After the save there is no going back.
4. Verify the Aggregation outlook and data 

    

The Application with Aggregation(s) will now be fully compatible with future versions of inorigo®.

The components Text Area and Image are components with static content which can be used to enrich the Application with explanatory texts and or images.

Video tutorial on the Image Component

Images are always static in the application and does not respond to selections or other user interactions. Use for example the image component to add the company logo to a Application.

Settings

The image component shares the same, Common Layout Settings as most other components. Notice that although available in the application builder, the web layout options revolving around selections such as Search Field Visible, or Edit buttons Visible is not applicable since the image component does not contain any inorigo units.

Video tutorial on the Text Area component

Use the Design Mirror to view your application design work live in a browser (Hotkey: CTRL + SHIFT + D).

Open a design mirror from Application Builder, either with or without data.  Without data displays components size and positioning and is useful for heavy applications.

As soon any changes are made in Application Builder the application window running in the browser will be updated, there is no need to save in Application Builder for the changes to apply. (Notice however that changes still need to be saved before exiting Application Builder to be applied)

Note on Performance

Design mirror with data has been tested with up to 15 filter components populated with 1000 units each without indications of noteworthy performance issues (2-5 seconds of respond time). When the numbers increase to filter components populated with 5000 or more units increased latencies should however be expected. Measurements estimate 10-15 seconds latency for Applications with a few filter components containing 5000 units each.

Collaborative work over the Design Mirror

The URL generated to run the Design Mirror can be shared among all users with access to the Application for live collaboration over the internet. Open the generated URL on any machine to run the Design Mirror view from it.

Notice that a port number in the URL may need to be changed depending on the machines network.

The design mirror URL is generated from a runtime ID of the Application Builder modules current session.  Every time Application Builder is opened in a new window, a new session starts with a new Runtime ID. This means that a new Design Mirror link will be generated each time Application Builder is opened and that you will need to redistribute a Design Mirror URL when a new collaborative session starts.

This behavior is added to ensure control over distributed Design Mirror URLs. By closing your Application Builder window and opening a new, you are able to terminate the live feed through a shared Design Mirror URL. The new window results in a new runtime ID where changes to the Application will can no longer be received from any outdated Design Mirror URL.

Application settings, by default found at the left side in inorigo® Application Builder edit mode, allows user to manage expressions and to collect data in complex data structures.

There is the Application settings

The Application settings holds four different tabs according to table below:

A Dataset is a kind of table that optionally can be created from the contents of an Application.

Features of a Dataset:

• The Dataset is defined per Application
• Consist of all Filter Components linked together in Application design
• Possible to reference such a Dataset wherever an expression applies
• Datasets include all linked Filter Components, i.e. all tabs and even those that are not visible
• Would decrease the need of a method to collect far fetched data in a complex structure
• Dataset is also supported by Advanced Filter Components; Resource Content (xls, txt), SQL and URL

Lets start with a simple Application with a few linked Filter Components.

The Application consist of the standard Geographical elements (p0 – p2), linked together with Persons (p6) and office locations (p4) via associations (p3 and p5).

Three buttons in the lower part of the Application Settings; Add, Delete and Edit.

Simply press the Add button to Create a new Dataset and you will be presented with the Add dialogue:

The tree structure is automatically built from the linked structure of Filter Components in Application. Be aware of that it is not possible to break the chain of each branch in structure, i.e. if p6 must be used, then all except p2 square boxes need to be ticked.

Please note that, even though Filter Components p3 and p5 are set as invisible, they are still available for use in Dataset.

Enter a proper name and select the Filter Components to include by clicking in each of the square boxes. This Dataset is possible to use in any expression, referencing it wherever an expression would apply; @Dataset.

The lower section of the Dataset editor enables additional calculations (columns) to be performed on the original columns in Dataset. The calculations will be included as new columns in dataset.

Part from the listed variables in the table above, any expression functions can also be used.

Below is an example where a calculated column is added:

This column can be referenced by a Calculation box with this expression: $GET($Distinct(@Dataset, “Average population”), “Average population”)

Let us use the new Dataset to create a Bar chart that displays the country Population (p2) where Person (p6) has office.

The Bar chart is referencing the Dataset to get the Person and Population. It is also possible to use the id’s of the Filter Components (p6 and p2) in expressions, i.e. $get(@Dataset,”p2″) for Population:

The best way to validate the Dataset would be to create a Matrix and set the Expression for Matrix to reference the Dataset: @Dataset_name

Result after pressing the calculate button:

The final result for the Chart and Calculation box could look like:

Please note that Calculated columns from Dataset is only visible on web.

This section describes how you can utilize the advanced filters and the aggregation table component. First of all you need to have access to “tabular” data, i.e. data that is structured as a table. Application Builder supports 3 different types; an Excel-sheet, a tab-delimited file or an SQL-statement returning a result set. It is required that each value is separated by a tab-character and each record by a linefeed if it is a text-file. You can use a URL to access data in the form of an Excel- or text-file. You could imagine that another system is publishing data which Application Builder in turn can incorporate into its visualization capabilities.

Add an advanced filter box by pressing the plus icon ( ) and navigate to the Filter Components / Advanced and select the Resource content-option. In this particular example the source data is a tab-separated text file (text file). The table below shows a couple of records of data.

You could also use an Excel-sheet to feed the component with the necessary data – excel file

The source is stored in a text-file available as a Resource in inorigo®. You will be prompted to select a resource and the dialog will look similar to the one below.

When you have selected the resource a new component will appear in the Application, see below.

All of the data available from the designated source, i.e. text, Excel SQL or URL, should now be visible in the bottom table. There are also a few more controls, for instance the Treat first row as header, which will interpret the first record in the text- or Excel-file as a header. If the data is retrieved with an SQL-statement, the names of column will be used.

The next step is to add some of the columns as filters. The columns are available in the Links-drop down list.

In our example we are interested in filtering on Category and Product. We also would like to get some aggregations based on those selections. So we select Category, Product and Aggregation table. The aggregation table is actually a Result component which is based on the selections made in the filter boxes. The Application Builder can look something like the screenshot below.

The two leftmost components, are the filter boxes which limits the result in the Aggregation table. The aggregation table lets you select what columns you want to group the results on. You can select the checkbox for what type the column should be. Either a Group column or an Aggregation column – it cannot be both.

By default a smaller set of all the calculated values are displayed in the table. However, you have the possibility to select what columns should be available in Runtime-mode. Use the Edit button in Aggregation Content settings to configure what columns to be available on web and also to format the output.

The “Format all columns” or “Format column” (the one you clicked on) allows you to specify number of decimal places (Precision), in what unit of measure (Power) the value should be displayed, visible or not, sorting and the Title.

The Group columns shows the available grouping columns, i.e. in runtime mode you can group on any number of available grouping columns.

The Aggregation columns menu item lists all available aggregation columns and you have the following calculated values to choose from.

The image below shows when you have chosen to only group on “Category” whereas the next image displays the result on grouping on “Product” as well.

Retrieve aggregated data with an expression

You can retrieve the data from the aggregation table by expressions, see examples below. The “group” columns contains Category and Product and the aggregation columns contains Sales and Picks (for simplicity’s sake). It is not recommended to get the values directly from the Aggregation table since that does not work on the web, but rather use the source instead. It is assumed source is p0.

The bar chart below displays sum of sales grouped on Category.

If you have transactional or tabular data that you wish to display in Application Builder, you also would like to connect it or convert it into inorigo® objects. The example data used in Advanced filter and aggregation table has been extended to also include a country code. The data is now also in an Excel spreadsheet to demonstrate that you can specify the type of the column in the Excel sheet and that it will be preserved into the Application. This is an example of the data excel file.

In our example we are interested in converting the Category– and Country-data into inorigo® entities. First of all you need to add the Category-data into inorigo®. In this example we’ve created a Generic Unit called Category which in turn has 8 instances.

The next step is to import the data into inorigo®. Create a new Application in Application Builder and select the Resource content-option.

Create or select the Resource-object which contains the data; press Cancel when you are prompted with the Add all columns?-dialog.

The new feature Edit Columns will bring up a dialog where you can specify the types and conversion for each column.

The Expression Editor will simplify the readability of expressions as it checks for inconsistencies and helps you with some guidance and basic validations to create the expression.

Variables – Verso View will give the list of available default variables, user defined variables and dataset(s) as input to new Expression Variables in view;

Example that shows the available items defined in view

While configuring the World Map, additional options are available – the fields that was fetched from the Layer URL;

Example showing the available fields from Layer to be used in an expression

and also the items that are referenced by the Source setting for World Map;

Example that shows the available items to be used in an expression, in this case a filter box that list Countries from the Geographical Area domain.

The status bar at the bottom of Expression Editor will provide a possible cause of error in expression. The expression will also be marked with red color as seen in the examples below;

Example 1, missing parenthesis

Example 2, wrong symbol in front of expression function

Example 3, no error, and as one can see the parenthesis is being paired for better readability

A user creating an Application also delegates the rights to the Application. The rights window is accessed from the button Rights from within an Application.

Put the Application in Edit mode with the Edit button.

Click the Rights button that is now active

A window is now opened

To add a user, press the plus button. The standard inorigo® Model Builder search panel is displayed to enable searching for users. Select one or several users in the search result and press the Ok button.

To remove one or many users from the rights window, select them and press the minus button.

The rights specified for an Application is only valid for that Application. To set up default rights, valid for all Applications and all users, is done by an Ortelius consultant (see separate manual). A default right may for example specify that all users have the right to read, but not to update, delete or manage rights for any of the inorigo® Application.

The rights set on a specific Application always override the default rights.

Introduction

The Velocity Service can be used for serving static or dynamic content stored as resources in inorigo®.

Since the service is based on the open source technology provided by the Apache Velocity Project we have chosen to honor that by naming the service accordingly.

This service enables the inorigo® server to act as a very dynamic web server where users can store their content in the inorigo® Database.

The most common type of content is probably HTML, but the Velocity Service is designed to handle any type of text based content such as XML.

In order to make the content dynamic it must contain Velocity markers and macros, thus acting as a template for the actual result.  All about the wonderful things you can do with Velocity can be found here.

Replace /ui in inorigo® Portal address with /documents/javadoc/index.html?com/inorigo/velocity/VelocityFunctionality.html to access the Velocity programming documentation.

Inorigo® Power built into your data

Using the inorigo® Execution API and/or Application Runtime data, you, as a designer, have access to almost all functionality built into the inorigo® platform.

This enables you to create very dynamic and advanced output without having to request special functionality to be developed outside the inorigo® platform.

Velocity Service Address

The Velocity Service is accessed at the …/velocity address.

Examples:

https://myserver.company.com/velocity?RESOURCE_ID=53AB2EC6-63C3-4E82-B653-F026234EDE62

• RESOURCE_ID
  Identifies the template resource by ID.
• RESOURCE_NAME
  Identifies the template resource by Name.
• VERSO_RUNTIME_ID
  Enables the Velocity Service to be integrated with an Application being viewed. (Used only when addressed from within an Application.)

Variables available for dynamic templates

A Simple Velocity Example

Save this code snippet in a html file and upload it to inorigo®

Model Builder setup

Create a Generic Unit and name it Person, and add an attribute Birth Date of class Date.

Example: the result could look like this when a Specific Unit is created with definition Person

Also add the source file as a Resource in Model Builder:

Goto the Change Log tab and copy the Id, it will be used later, e.g. C5B2870F-A085-2D85-8F76-A53300F1141B

Application Builder setup

Create a new Application, e.g. “Velocity example”, and add a Filter Component (p0) listing all Specific Units with the definition Person. Optionally enable options for Authorization on web, i.e. Create (Person), Read, Update etc.

In Application Settings, add an Expression Variable, e.g.:

The expression:

“<iframe style=’width:100%; height:96%; margin:0; padding:0;border: none;’ src=’velocity/C5B2870F-A085-2D85-8F76-A53300F1141B?VERSO_RUNTIME_ID=”+@VERSO_RUNTIME_ID+”&CLICK=”+@CLICK+”‘></iframe>”

Replace the Id in expression with the Id of the resource created before.

Now, add a Calculation box referencing the Expression Variable, @Velocity in this example.

Velocity is a great way to create placeholders for dynamic information.

Application Builder General

Navigator/Search Panel

Expression Editor