UBIK Wiki Test / Augmensys - User contributions [en]

POI editing

2018-02-19T14:27:42Z

KVB: Created page with "Users can edit the location of a POI using two ways: through the Map View, and using a Geo Property editor. == Editing POIs in the Map View == You can change the location of..."

Users can edit the location of a POI using two ways: through the Map View, and using a Geo Property editor.

== Editing POIs in the Map View ==

You can change the location of POIs in the Map View. To do so, follow these steps:

# Toggle "Edit Mode" by pressing the "Edit" button in the left sidebar.
# Tap a POI to select it.
#* Note that the POI must be editable - this means, the underlying Geo property defining the location should not be read-only. If it is, you will not be able to select this POI in Edit Mode.
# With the POI selected, the editing controls will now appear.
#* You can edit the location by manually typing in coordinates, or...
#* By pressing the "Teach" button, which will set the POI to your current location, or...
#* By tapping anywhere on the map. The POI will jump to the tapped location.

Once you are satisfied with the POI's new location, you can press "OK" to save and commit the changes. Pressing "Cancel" will revert your changes, and move the POI back to its previous location. After pressing "OK" or "Cancel" you are free to edit another POI, or to exit "Edit Mode" by toggling the "Edit" button once more.

[[media:Recording_map_view.mp4|Demo video]]

== Editing Geo Properties ==

Editing Geo Properties works very similarly to editing POIs in the Map View, with the exception that you will only see a single POI in the map view. Again, you can change the coordinates of the Geo property by using the coordinate textboxes, "Teach" function, or by tapping the map. After pressing "OK" in the Geo property editor, you will have a chance to save and commit your changes afterwards, just like with any other property type.

Note that an object does not need to be classified as POI to be able to use the geo property editor. Any geo property, even if not related to a POI classification, can be edited using this control.

[[media:Recording_geo_editor.mp4|Demo video]]

File:Recording geo editor.mp4

2018-02-19T14:27:26Z

KVB:

File:Recording map view.mp4

2018-02-19T14:17:14Z

KVB:

Charts

2018-01-23T16:21:26Z

KVB:

We have provided a default chart template that can be used anywhere.
In our standard application, a chart is visible when clicking a Chart type property in the property list. A dialog will show up, displaying the chart.
The chart can be further extended by customizing UBIKChart.xaml. However, we have made sure to support complex data structures from the chart, and to allow for most of the custom presentation data to come from the server side.

== Chart properties ==
[[File:Chart_annotations.png|thumb]]

The chart receives its data from a property containing a ChartData object. This object is packed with customizable data that the chart template binds to.
This data is received from the server. However, you may also customize the chart template to your liking to override certain values. The image on the right can help clarify some of these properties.

Here is a breakdown of all the date, and how it is represented in the UI:

==== ChartData ====
* '''Header (string):''' title of the chart
* '''PrimaryAxis ([[#ChartAxis|ChartAxis]]):''' the X-axis
* '''SecondaryAxis ([[#ChartAxis|ChartAxis]]):''' the Y-axis
* '''Series (list of [[#ChartValueSeries|ChartValueSeries]]):''' all line series visible on the chart
* '''Thresholds (list of [[#ChartThreshold|ChartThreshold]]):''' all horizontal thresholds visible on the chart

==== ChartAxis ====
* '''Header (string):''' the label of the axis
* '''Interval (double):''' the interval between gridlines on the axis
* '''DateTimeIntervalType (int):''' the interval type in case of a date axis
* '''LabelFormat (string):''' the format string to define how value labels are formatted. See [[#Label formatting|Label formatting]]
* '''Minimum (object):''' the minimum value to display on the axis
* '''Maximum (object):''' the maximum value to display on the axis

==== ChartValueSeries ====
* '''Name (string):''' the name of the series (will be shown in the legend)
* '''Color (int)''': the color of the line
* '''Items (list of [[#ChartItem|ChartItem]]):''' the list of data points on the line

==== ChartItem ====
* '''XValue (object):''' the X value of the data point
* '''YValue (object):''' the Y value of the data point

==== ChartThreshold ====
* '''Value (object):''' the value of the threshold (on the Y-axis)
* '''Color (int):''' the color of the threshold line

=== Label formatting ===
The ChartAxis object contains a property "LabelFormat" that allows you to customize how the value labels on the axes are presented. This special format string only applies to numbers and dates.
Some examples of what you could do what the format string:

{| class="wikitable"
! Input
! Format string
! Output
|-
|5.5
|"##.000"
|5.500
|-
|01/05/2017 16:00:00
|"yyyy"
|2017
|-
|01/05/2017 16:00:00
|"dd/MM/yyyy"
|01-05-2017
|-
|}

[https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-numeric-format-strings See here] for how to format numeric objects, and [https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings here] for how to format dates.

== Interactivity ==
You can zoom in on the chart by using the pinch zoom gesture on touch-screen devices, or by using the scroll wheel on your mouse. After zooming, you can pan around the chart by simply pressing and dragging.
Note that for larger data sets, the performance might suffer when zooming and panning.

Charts

2018-01-23T16:08:43Z

KVB:

Charts

2018-01-23T16:03:33Z

KVB:

We have provided a default chart template that can be used anywhere.
In our standard application, a chart is visible when clicking a Chart type property in the property list. A dialog will show up, displaying the chart.

== Chart properties ==
[[File:Chart_annotations.png|thumb]]

The chart receives its data from a property containing a ChartData object. This object is packed with customizable data that the chart template binds to.
This data is received from the server. However, you may also customize the chart template to your liking to override certain values. The image on the right can help clarify some of these properties.

Here is a breakdown of all the date, and how it is represented in the UI:

==== ChartData ====
* '''Header (string):''' title of the chart
* '''PrimaryAxis ([[#ChartAxis|ChartAxis]]):''' the X-axis
* '''SecondaryAxis ([[#ChartAxis|ChartAxis]]):''' the Y-axis
* '''Series (list of [[#ChartValueSeries|ChartValueSeries]]):''' all line series visible on the chart
* '''Thresholds (list of [[#ChartThreshold|ChartThreshold]]):''' all horizontal thresholds visible on the chart

==== ChartAxis ====
* '''Header (string):''' the label of the axis
* '''Interval (double):''' the interval between gridlines on the axis
* '''DateTimeIntervalType (int):''' the interval type in case of a date axis
* '''LabelFormat (string):''' the format string to define how value labels are formatted. See [[#Label formatting|Label formatting]]
* '''Minimum (object):''' the minimum value to display on the axis
* '''Maximum (object):''' the maximum value to display on the axis

==== ChartValueSeries ====
* '''Name (string):''' the name of the series (will be shown in the legend)
* '''Color (int)''': the color of the line
* '''Items (list of [[#ChartItem|ChartItem]]):''' the list of data points on the line

==== ChartItem ====
* '''XValue (object):''' the X value of the data point
* '''YValue (object):''' the Y value of the data point

==== ChartThreshold ====
* '''Value (object):''' the value of the threshold (on the Y-axis)
* '''Color (int):''' the color of the threshold line

=== Label formatting ===
The ChartAxis object contains a property "LabelFormat" that allows you to customize how the value labels on the axes are presented. This special format string only applies to numbers and dates.
Some examples of what you could do what the format string:

{| class="wikitable"
! Input
! Format string
! Output
|-
|5.5
|"##.000"
|5.500
|-
|01/05/2017 16:00:00
|"yyyy"
|2017
|-
|01/05/2017 16:00:00
|"dd/MM/yyyy"
|01-05-2017
|-
|}

[https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-numeric-format-strings See here] for how to format numeric objects, and [https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings here] for how to format dates.

File:Chart annotations.png

2018-01-23T16:01:47Z

KVB:

Charts

2018-01-23T15:55:46Z

KVB: /* Chart properties */

We have provided a default chart template that can be used anywhere.
In our standard application, a chart is visible when clicking a Chart type property in the property list. A dialog will show up, displaying the chart.

== Chart properties ==
The chart receives its data from a property containing a ChartData object. This object is packed with customizable data that the chart template binds to.
This data is received from the server. However, you may also customize the chart template to your liking to override certain values.

Here is a breakdown of all the date, and how it is represented in the UI:

==== ChartData ====
* '''Header (string):''' title of the chart
* '''PrimaryAxis ([[#ChartAxis|ChartAxis]]):''' the X-axis
* '''SecondaryAxis ([[#ChartAxis|ChartAxis]]):''' the Y-axis
* '''Series (list of [[#ChartValueSeries|ChartValueSeries]]):''' all line series visible on the chart
* '''Thresholds (list of [[#ChartThreshold|ChartThreshold]]):''' all horizontal thresholds visible on the chart

==== ChartAxis ====
* '''Header (string):''' the label of the axis
* '''Interval (double):''' the interval between gridlines on the axis
* '''DateTimeIntervalType (int):''' the interval type in case of a date axis
* '''LabelFormat (string):''' the format string to define how value labels are formatted. See [[#Label formatting|Label formatting]]
* '''Minimum (object):''' the minimum value to display on the axis
* '''Maximum (object):''' the maximum value to display on the axis

==== ChartValueSeries ====
* '''Name (string):''' the name of the series (will be shown in the legend)
* '''Color (int)''': the color of the line
* '''Items (list of [[#ChartItem|ChartItem]]):''' the list of data points on the line

==== ChartItem ====
* '''XValue (object):''' the X value of the data point
* '''YValue (object):''' the Y value of the data point

==== ChartThreshold ====
* '''Value (object):''' the value of the threshold (on the Y-axis)
* '''Color (int):''' the color of the threshold line

=== Label formatting ===
The ChartAxis object contains a property "LabelFormat" that allows you to customize how the value labels on the axes are presented. This special format string only applies to numbers and dates.
Some examples of what you could do what the format string:

{| class="wikitable"
! Input
! Format string
! Output
|-
|5.5
|"##.000"
|5.500
|-
|01/05/2017 16:00:00
|"yyyy"
|2017
|-
|01/05/2017 16:00:00
|"dd/MM/yyyy"
|01-05-2017
|-
|}

[https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-numeric-format-strings See here] for how to format numeric objects, and [https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings here] for how to format dates.

Charts

2018-01-23T15:42:23Z

KVB: /* Chart properties */

We have provided a default chart template that can be used anywhere.
In our standard application, a chart is visible when clicking a Chart type property in the property list. A dialog will show up, displaying the chart.

== Chart properties ==
The chart receives its data from a property containing a ChartData object. This object is packed with customizable data that the chart template binds to.
This data is received from the server. However, you may also customize the chart template to your liking to override certain values.

Here is a breakdown of all the date, and how it is represented in the UI:

==== ChartData ====
* '''Header (string):''' title of the chart
* '''PrimaryAxis ([[#ChartAxis|ChartAxis]]):''' the X-axis
* '''SecondaryAxis ([[#ChartAxis|ChartAxis]]):''' the Y-axis
* '''Series (list of [[#ChartValueSeries|ChartValueSeries]]):''' all line series visible on the chart
* '''Thresholds (list of [[#ChartThreshold|ChartThreshold]]):''' all horizontal thresholds visible on the chart

==== ChartAxis ====
* '''Header (string):''' the label of the axis
* '''Interval (double):''' the interval between gridlines on the axis
* '''DateTimeIntervalType (int):''' the interval type in case of a date axis
* '''LabelFormat (string):''' the format string to define how value labels are formatted
* '''Minimum (object):''' the minimum value to display on the axis
* '''Maximum (object):''' the maximum value to display on the axis

==== ChartValueSeries ====
* '''Name (string):''' the name of the series (will be shown in the legend)
* '''Color (int)''': the color of the line
* '''Items (list of [[#ChartItem|ChartItem]]):''' the list of data points on the line

==== ChartItem ====
* '''XValue (object):''' the X value of the data point
* '''YValue (object):''' the Y value of the data point

==== ChartThreshold ====
* '''Value (object):''' the value of the threshold (on the Y-axis)
* '''Color (int):''' the color of the threshold line

Charts

2018-01-23T15:41:23Z

KVB: Created page with "We have provided a default chart template that can be used anywhere. In our standard application, a chart is visible when clicking a Chart type property in the property list...."

We have provided a default chart template that can be used anywhere.
In our standard application, a chart is visible when clicking a Chart type property in the property list. A dialog will show up, displaying the chart.

== Chart properties ==
The chart receives its data from a property containing a ChartData object. This object is packed with customizable data that the chart template binds to.
This data is received from the server. However, you may also customize the chart template to your liking to override certain values.

Here is a breakdown of all the date, and how it is represented in the UI:

==== ChartData ====
* '''Header (string):''' title of the chart
* '''PrimaryAxis ([[#ChartAxis|ChartAxis]]):''' the X-axis
* '''SecondaryAxis ([[#ChartAxis|ChartAxis]]):''' the Y-axis
* '''Series (list of ChartValueSeries):''' all line series visible on the chart
* '''Thresholds (list of ChartThreshold):''' all horizontal thresholds visible on the chart

==== ChartAxis ====
* '''Header (string):''' the label of the axis
* '''Interval (double):''' the interval between gridlines on the axis
* '''DateTimeIntervalType (int):''' the interval type in case of a date axis
* '''LabelFormat (string):''' the format string to define how value labels are formatted
* '''Minimum (object):''' the minimum value to display on the axis
* '''Maximum (object):''' the maximum value to display on the axis

==== ChartValueSeries ====
* '''Name (string):''' the name of the series (will be shown in the legend)
* '''Color (int)''': the color of the line
* '''Items (list of ChartItem):''' the list of data points on the line

==== ChartItem ====
* '''XValue (object):''' the X value of the data point
* '''YValue (object):''' the Y value of the data point

==== ChartThreshold ====
* '''Value (object):''' the value of the threshold (on the Y-axis)
* '''Color (int):''' the color of the threshold line

UBIK WinX Client Basics

2017-11-30T14:11:13Z

KVB: /* Guid editor */

{{UBIK}} Client is the mobile application for viewing and modifying data, showing documents, starting navigation, visualizing POIs and much more.

Client applications are available for Android and WinX, however the features available on each of the platform dependent applications might differ. An overview of the available features can be found in the [[Client_Feature_Table|feature comparison table]].

== Login ==
Users need to login in order to access confidential data, this can be done in the [[Login View]].

== Profiles ==
Profiles are used to store connection information for {{UBIK}} services. It specifies the location where to find the service along with other useful informations. Profiles are stored by UBIK whenever the user created connection information and stored it in the settings. However, profiles can also be created and edited with any text editor. Possible settings to be defined are:
* InternalConnectionSettings: Connections settings how to connect to the Content and the USAM service that has been set up.
** Application: the [[APPLICATION]] to use with the service
** AuthenticationPort: Port Number of the authentication (USAM) service (default: 777)
** AuthenticationProtocol: Protocol of the authentication service (default: https)
** AuthenticationServer: the ip address of the authentication server
** AuthenticationService: the path to the authentication service
** ContentPort: Port Number of the content service (default: 777)
** ContentProtocol: Protocol of the content service (default: https)
** ContentServer: the ip address of the content server
** ContentService: the path to the content service
** Context: the [[CONTEXT]] to use with the service
** SyncMode: the used sync mode (Online [= Auto], Manual, Offline; default:Online)
* IsDefault: true, if the profile should be the default profile
* Name: the name of the profile (will also be used to identify the database)
* Project: the project name. Use this to share a single project name with more than one profile. If the project is defined, all profile with the same project will share one database.
* ShowHiddenSettings: show hidden settings (feault: false)

Example:
<source lang = "xml">
<?xml version="1.0" encoding="utf-8"?>
<Profile xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/UBIK.WinX.Settings">
<Description i:nil="true" />
<InternalConnectionSettings>
<Application>APP_DEMO</Application>
<AuthenticationPort>777</AuthenticationPort>
<AuthenticationProtocol>https</AuthenticationProtocol>
<AuthenticationServer>80.243.175.50</AuthenticationServer>
<AuthenticationService>UBIK/DBG/AUG/DEMO.250/USAM/USAM.svc</AuthenticationService>
<ContentPort>777</ContentPort>
<ContentProtocol>https</ContentProtocol>
<ContentServer>80.243.175.50</ContentServer>
<ContentService>UBIK/DBG/AUG/DEMO.250/CONTENT/UBIKContent.svc</ContentService>
<Context>CXT_DEMO</Context>
<SyncMode>Online</SyncMode>
</InternalConnectionSettings>
<IsDefault>true</IsDefault>
<Name>DEMO.250.AT</Name>
<Project>DEMO.250</Project>
<ShowHiddenSettings>false</ShowHiddenSettings>
</Profile>
</source>

== Content Browser ==
Allows to navigate through the entire data model in a hierarchical manner, as it is published by the server.

Initially, a list of objects ("root objects") is shown. Upon selecting an object, a new browser is opened for that object, showing details about it. When an object is selected in the content browser, it is called the browser's context. For such a contextual object, child objects and selected properties are shown. Also, there is a context menu providing actions related to the currently selected object.

=== Status Bar ===
[[File:UI_WinX_DbSavingIndicator.PNG|300 px|thumb|border|alt=Saving Symbol|Saving Symbol]]
{{Version/WinXSince|2.5.4}}Whenever content is being saved into the local database (for example, after a branch is downloaded from the server), there will be a blinking symbol indicating the saving activity is happening in the background.
During that time, the user is advised to not logout or close the app because the content might be lost otherwise. However, it is okay to undertake other tasks such as browsing, editing or downloading branches.

=== Child Page ===

[[File:ChildPage.PNG|400 px|thumb|border|alt=Child Page|Child Page]]

The child page shows the context of a selected object.

The global status bar shows the icon, the name and the description of the selected object. An arrow on the left side allows the user to navigate back to the parent object. On the right side the currently logged-in user is indicated. By clicking on the username one is able to navigate back to the home screen or log off.

The right side of the child page shows child objects of the current object. Each child object is represented by an icon, a name and a description.

On the left side of the child page the current object´s high priority properties are shown. By clicking on a live value property, the live value details dialog opens. By clicking on an editable [[UBIK_WinX_Client_Basics#High_priority_properties| high priority property]], an editor opens {{Version/WinXSince|2.5.4}}. If a property was edited a save button is shown in the lower left corner, allowing the user to commit the changes. If a property of a query object was edited an evaluate button is shown in the lower left corner, allowing the user to run the query with the changed propery.

=== Details Page ===

=== Context Menu ===

=== Objects ===

==== Root objects vs child objects ====

The first entry point in the ''Content Browser'' is the list of root objects.

==== Task objects ====

==== Query objects ====

==== Safety relevant objects ====

==== Commissioning objects ====

==== Locked objects ====

=== Properties ===

==== Live value properties ====

==== High priority properties ====
High priority properties are properities having a priority higher than the [[Settings#Content |priority threshold]].

==== Selective List Properties ====

==== Properties with value records {{Version/WinXSince|2.5.4}} ====
[[File:UI_WinX_PropertyWithValueRecords.png|thumb|A property with value records]]
[[File:UI_WinX_PropertyValueRecords.png|thumb|Property value records dialog]]
In addition to its value, a property might also bring along a series of value records showing "who changed the value at what time".

When such records exist, the property row shows a special symbol on the right side. After a right click (with mouse) or a long tap (with touch) on the property row, a dialog will be shown to present these records (sorted by their time, recent ones on top).

{{Clear}}

==== Editors ====

===== Geo Editor & Teach In =====

==== Guid editor ====
[[File:Guid_property_dialog.PNG|thumb|border|alt=Guid property editor dialog|Guid property editor dialog]]

To edit Guid properties (that do not have a selective list available), we have implemented a special system. Since a Guid property always just contains the Guid as a reference to another object, we can use a query to find the object we want to assign to this property.

When the Guid property has a FilterQuery datamember (which should contain the guid of a query), it will become editable through this query. Note that this FilterQuery guid will not actually be visible in the client. All this should be setup in the backend, the client has no control over this.

When clicking an editable Guid property, you will see a dialog with up to 3 extra buttons added (see image):

;View Object
:This button will be enabled when there is a valid guid assigned to the property. Clicking this button will immediately navigate to the referenced object.
;Edit Property
:If the property has a valid FilterQuery assigned to it, clicking this button will launch that query. If no FilterQuery is assigned, this button will be invisible.
;Clear Property Value
:If the property has a guid assigned, the user can press this button to reset the value back to empty.

Additionally, if a valid FilterQuery is assigned, the user will see the results of that query ''inline'', if the query delivers 200 results or fewer. The user can select an item from this horizontally scrollable list, and press "OK" to assign the UID of the selected object to the Guid property. This is useful for cases where the user does not want to jump into the full query to be able to select an object.

If the user does choose to launch the full query page (or if the query returns over 200 objects), they can click any of the displayed items in the query's child list. When clicking one of them, it will immediately be set as the reference in the original Guid property. To cancel selecting an item (and stop editing the property), simply navigate to any other page (by pressing back, using navigation bar, etc).

[[Category:WinX|UBIK WinX Client Basics]]

=== Documents ===
UBIK supports and displays document objects and a bunch of actions related to them (editing, redlining, creation, thumbnails, ...).

==== Customizing Possibilities ====

==== Editing{{Version/WinXSince|2.5.4}} ====
[[File:UI_WinX_EditDocumentButton.png|thumb|Button to edit a document]]
For [[SYSCLS_EDITABLEDOCUMENT|editable documents]], there is an {{key press|edit}} button in the bottom app bar. It allows the user to edit a document file using the default app of the OS. If a file is changed during the edit, the same {{key press|save}} button appears just like it does for content with changed properties.
{{Hint|Similar to saving, other app features also apply on edited documents. For example, reverting local changes for an edited document will throw away the changed document file and restore it to the server version.}}
[[File:UI_WinX_EditDocumentOverlayButton.png|thumb|Edit button in thumbnail overlay]]
An alternative way to start editing is to right click on a document's thumbnail, which brings up an overlay of buttons, and then select the {{key press|edit}} button. The difference here is that there is no {{key press|save}} button and any changes are automatically saved (and committed if in online mode).
{{Clear}}

==== Offline availability ====
When a user selects a branch to bring offline, files of all document objects underneath are downloaded in principle. However, they can also be selectively configured to be ignored with a [[SYSCLS_OFFLINE_AVAILABLE_DOCUMENT|classification]] on the server-side. Once a document is classified as offline available, the document file will not be removed when the storage for already synchronized document files is cleared.
{{Hint|This is not to be confused with the accessibility related to [[User_Rights|user rights]]. The logic here is "some documents '''do not have to''' be downloaded", not "some documents '''can not''' be downloaded/accessed". In other words, a user can browse to and open the document regardless of this configuration.}}

==== Clear Online Documents ====
By clearing the online documents, it is possible to free up system memory if needed. It can be triggered by pressing the button "Clear online documents" in the general settings tab. Online documents are documents already uploaded to the server. They can be downloaded anytime agian when the client is connected to the server. However, documents classified as offline available will not be affected and will always stay on the device.

== AR Features ==

=== POI View ===
Brings up the POI View|Augmented Reality view and displays Points of Interest (POI's) related to the current location of the mobile device.

=== Markerless ===

=== Map View ===
Opens the Map View and displays Points of Interest (POI's) related to the current location of the mobile device.

== Positioning ==
{{UBIK}} clients use a [[Location_Manager|Location Manager]] in order to gain knowledge about their position, so it can help the user navigate to his/her target.

The user can choose one of different positioning modes optimized for different environments.
Most of them incorporate multiple technologies for calculating positions or checking their reliability.

=== Positioning modes ===

* ''Use all'' - uses all available position sources
* ''LLA only mode'' - used for positioning using markers only
* ''Beacon Proximity mode'' - uses iBeacon proximity and LLA only

=== Technologies ===

==== GPS ====
GPS is used as a primary positioning input source for outdoor areas. Its precision depends on the environment and satellite availability. With good circumstances, the accuracy varies between 1 and 10 meters.

==== LLA markers ====
LLA markers basically are QR codes with location data encoded into them - which can be used for positioning when they are scanned.

==== Object Proximity Positioning ====
The location of nearby Geo-Objects can be used for positioning.

The position of a Geo-Object can be used manually by pushing the button {{key press|Use Location}} in the [[UBIK_WinX_Client_Basics#Context_Menu|Context Menu]].

The geo information of an object gets used automatically if exactly one single object is found through scanning. If more objects are found, their geo information doesn´t get used. Scanning includes [[UBIK Client Basics#Bar Code|Bar Code]], [[UBIK Client Basics#QR Code|QR Code]], [[UBIK Client Basics#OCR|OCR]] and [[UBIK Client Basics#RFID|RFID]]. The automatic use of Geo-Object´s location can be turned off by disabling the "EnableObjectProximityPositioning" setting.

[[Category:WinX|UBIK WinX Client Basics]]

==== Beacon-Proximity Positioning ====
The Beacon Proximity Mode detects if the user is in the proximity of a beacon. The proximity region is defined by a proximity distance which creates a sphere around the beacon. Whenever the calculated distance to a beacon is smaller than the proximity distance, the user is supposed to be at the position of the beacon. If multiple regions intersect the user is supposed to be at the position of the nearest beacon.
In order to use Beacon Proximity as a Positioning System, Bluetooth Low Energy has to be available and enabled on the mobile device. If a new environment should be equipped with iBeacon-Positioning, an expert has to mount iBeacons on known positions and calibrate the propagation factor of these beacons. Proximity beacons can be configured using [[SYSCLS_PROXIMITY_BEACON]]. {{Version/WinXSince|UWP}}

[[Category:WinX|UBIK WinX Client Basics]]

== Finding Objects ==
=== Free Text Search ===

=== ID Marker ===

=== QR Code ===

=== Bar Code ===

=== RFID Code ===
Provides a fast and convenient way for users to find objects that are identifiable through [[RFID tags|RFID tags]].

=== OCR ===

== See also ==
* [[Client_Feature_Table]]

[[Category:WinX|UBIK WinX Client Basics]]

UBIK WinX Client Basics

2017-11-30T14:10:12Z

KVB: /* Guid editor */

{{UBIK}} Client is the mobile application for viewing and modifying data, showing documents, starting navigation, visualizing POIs and much more.

Client applications are available for Android and WinX, however the features available on each of the platform dependent applications might differ. An overview of the available features can be found in the [[Client_Feature_Table|feature comparison table]].

== Login ==
Users need to login in order to access confidential data, this can be done in the [[Login View]].

== Profiles ==
Profiles are used to store connection information for {{UBIK}} services. It specifies the location where to find the service along with other useful informations. Profiles are stored by UBIK whenever the user created connection information and stored it in the settings. However, profiles can also be created and edited with any text editor. Possible settings to be defined are:
* InternalConnectionSettings: Connections settings how to connect to the Content and the USAM service that has been set up.
** Application: the [[APPLICATION]] to use with the service
** AuthenticationPort: Port Number of the authentication (USAM) service (default: 777)
** AuthenticationProtocol: Protocol of the authentication service (default: https)
** AuthenticationServer: the ip address of the authentication server
** AuthenticationService: the path to the authentication service
** ContentPort: Port Number of the content service (default: 777)
** ContentProtocol: Protocol of the content service (default: https)
** ContentServer: the ip address of the content server
** ContentService: the path to the content service
** Context: the [[CONTEXT]] to use with the service
** SyncMode: the used sync mode (Online [= Auto], Manual, Offline; default:Online)
* IsDefault: true, if the profile should be the default profile
* Name: the name of the profile (will also be used to identify the database)
* Project: the project name. Use this to share a single project name with more than one profile. If the project is defined, all profile with the same project will share one database.
* ShowHiddenSettings: show hidden settings (feault: false)

Example:
<source lang = "xml">
<?xml version="1.0" encoding="utf-8"?>
<Profile xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/UBIK.WinX.Settings">
<Description i:nil="true" />
<InternalConnectionSettings>
<Application>APP_DEMO</Application>
<AuthenticationPort>777</AuthenticationPort>
<AuthenticationProtocol>https</AuthenticationProtocol>
<AuthenticationServer>80.243.175.50</AuthenticationServer>
<AuthenticationService>UBIK/DBG/AUG/DEMO.250/USAM/USAM.svc</AuthenticationService>
<ContentPort>777</ContentPort>
<ContentProtocol>https</ContentProtocol>
<ContentServer>80.243.175.50</ContentServer>
<ContentService>UBIK/DBG/AUG/DEMO.250/CONTENT/UBIKContent.svc</ContentService>
<Context>CXT_DEMO</Context>
<SyncMode>Online</SyncMode>
</InternalConnectionSettings>
<IsDefault>true</IsDefault>
<Name>DEMO.250.AT</Name>
<Project>DEMO.250</Project>
<ShowHiddenSettings>false</ShowHiddenSettings>
</Profile>
</source>

== Content Browser ==
Allows to navigate through the entire data model in a hierarchical manner, as it is published by the server.

Initially, a list of objects ("root objects") is shown. Upon selecting an object, a new browser is opened for that object, showing details about it. When an object is selected in the content browser, it is called the browser's context. For such a contextual object, child objects and selected properties are shown. Also, there is a context menu providing actions related to the currently selected object.

=== Status Bar ===
[[File:UI_WinX_DbSavingIndicator.PNG|300 px|thumb|border|alt=Saving Symbol|Saving Symbol]]
{{Version/WinXSince|2.5.4}}Whenever content is being saved into the local database (for example, after a branch is downloaded from the server), there will be a blinking symbol indicating the saving activity is happening in the background.
During that time, the user is advised to not logout or close the app because the content might be lost otherwise. However, it is okay to undertake other tasks such as browsing, editing or downloading branches.

=== Child Page ===

[[File:ChildPage.PNG|400 px|thumb|border|alt=Child Page|Child Page]]

The child page shows the context of a selected object.

The global status bar shows the icon, the name and the description of the selected object. An arrow on the left side allows the user to navigate back to the parent object. On the right side the currently logged-in user is indicated. By clicking on the username one is able to navigate back to the home screen or log off.

The right side of the child page shows child objects of the current object. Each child object is represented by an icon, a name and a description.

On the left side of the child page the current object´s high priority properties are shown. By clicking on a live value property, the live value details dialog opens. By clicking on an editable [[UBIK_WinX_Client_Basics#High_priority_properties| high priority property]], an editor opens {{Version/WinXSince|2.5.4}}. If a property was edited a save button is shown in the lower left corner, allowing the user to commit the changes. If a property of a query object was edited an evaluate button is shown in the lower left corner, allowing the user to run the query with the changed propery.

=== Details Page ===

=== Context Menu ===

=== Objects ===

==== Root objects vs child objects ====

The first entry point in the ''Content Browser'' is the list of root objects.

==== Task objects ====

==== Query objects ====

==== Safety relevant objects ====

==== Commissioning objects ====

==== Locked objects ====

=== Properties ===

==== Live value properties ====

==== High priority properties ====
High priority properties are properities having a priority higher than the [[Settings#Content |priority threshold]].

==== Selective List Properties ====

==== Properties with value records {{Version/WinXSince|2.5.4}} ====
[[File:UI_WinX_PropertyWithValueRecords.png|thumb|A property with value records]]
[[File:UI_WinX_PropertyValueRecords.png|thumb|Property value records dialog]]
In addition to its value, a property might also bring along a series of value records showing "who changed the value at what time".

When such records exist, the property row shows a special symbol on the right side. After a right click (with mouse) or a long tap (with touch) on the property row, a dialog will be shown to present these records (sorted by their time, recent ones on top).

{{Clear}}

==== Editors ====

===== Geo Editor & Teach In =====

==== Guid editor ====
[[File:Guid_property_dialog.PNG|thumb|border|alt=Guid property editor dialog|Guid property editor dialog]]

To edit Guid properties (that do not have a selective list available), we have implemented a special system. Since a Guid property always just contains the Guid as a reference to another object, we can use a query to find the object we want to assign to this property.

When the Guid property has a FilterQuery datamember (which should contain the guid of a query), it will become editable through this query. Note that this FilterQuery guid will not actually be visible in the client. All this should be setup in the backend, the client has no control over this.

When clicking an editable Guid property, you will see a dialog with up to 3 extra buttons added (see image):

;View Object
:This button will be enabled when there is a valid guid assigned to the property. Clicking this button will immediately navigate to the referenced object.
;Edit Property
:If the property has a valid FilterQuery assigned to it, clicking this button will launch that query. If no FilterQuery is assigned, this button will be invisible.
;Clear Property Value
:If the property has a guid assigned, the user can press this button to reset the value back to empty.

Additionally, if a valid FilterQuery is assigned, the user will see the results of that query ''inline'', if the query delivers 200 results or fewer. The user can select an item from this horizontally scrollable list, and press "OK" to assign the UID of the selected object to the Guid property. This is useful for cases where the user does not want to jump into the full query to be able to select an object.

Once the user has launched the query, they can click any of the displayed items. When clicking one of them, it will immediately be set as the reference in the original Guid property. To cancel selecting an item (and stop editing the property), simply navigate to any other page (by pressing back, using navigation bar, etc).

[[Category:WinX|UBIK WinX Client Basics]]

=== Documents ===
UBIK supports and displays document objects and a bunch of actions related to them (editing, redlining, creation, thumbnails, ...).

==== Customizing Possibilities ====

==== Editing{{Version/WinXSince|2.5.4}} ====
[[File:UI_WinX_EditDocumentButton.png|thumb|Button to edit a document]]
For [[SYSCLS_EDITABLEDOCUMENT|editable documents]], there is an {{key press|edit}} button in the bottom app bar. It allows the user to edit a document file using the default app of the OS. If a file is changed during the edit, the same {{key press|save}} button appears just like it does for content with changed properties.
{{Hint|Similar to saving, other app features also apply on edited documents. For example, reverting local changes for an edited document will throw away the changed document file and restore it to the server version.}}
[[File:UI_WinX_EditDocumentOverlayButton.png|thumb|Edit button in thumbnail overlay]]
An alternative way to start editing is to right click on a document's thumbnail, which brings up an overlay of buttons, and then select the {{key press|edit}} button. The difference here is that there is no {{key press|save}} button and any changes are automatically saved (and committed if in online mode).
{{Clear}}

==== Offline availability ====
When a user selects a branch to bring offline, files of all document objects underneath are downloaded in principle. However, they can also be selectively configured to be ignored with a [[SYSCLS_OFFLINE_AVAILABLE_DOCUMENT|classification]] on the server-side. Once a document is classified as offline available, the document file will not be removed when the storage for already synchronized document files is cleared.
{{Hint|This is not to be confused with the accessibility related to [[User_Rights|user rights]]. The logic here is "some documents '''do not have to''' be downloaded", not "some documents '''can not''' be downloaded/accessed". In other words, a user can browse to and open the document regardless of this configuration.}}

==== Clear Online Documents ====
By clearing the online documents, it is possible to free up system memory if needed. It can be triggered by pressing the button "Clear online documents" in the general settings tab. Online documents are documents already uploaded to the server. They can be downloaded anytime agian when the client is connected to the server. However, documents classified as offline available will not be affected and will always stay on the device.

== AR Features ==

=== POI View ===
Brings up the POI View|Augmented Reality view and displays Points of Interest (POI's) related to the current location of the mobile device.

=== Markerless ===

=== Map View ===
Opens the Map View and displays Points of Interest (POI's) related to the current location of the mobile device.

== Positioning ==
{{UBIK}} clients use a [[Location_Manager|Location Manager]] in order to gain knowledge about their position, so it can help the user navigate to his/her target.

The user can choose one of different positioning modes optimized for different environments.
Most of them incorporate multiple technologies for calculating positions or checking their reliability.

=== Positioning modes ===

* ''Use all'' - uses all available position sources
* ''LLA only mode'' - used for positioning using markers only
* ''Beacon Proximity mode'' - uses iBeacon proximity and LLA only

=== Technologies ===

==== GPS ====
GPS is used as a primary positioning input source for outdoor areas. Its precision depends on the environment and satellite availability. With good circumstances, the accuracy varies between 1 and 10 meters.

==== LLA markers ====
LLA markers basically are QR codes with location data encoded into them - which can be used for positioning when they are scanned.

==== Object Proximity Positioning ====
The location of nearby Geo-Objects can be used for positioning.

The position of a Geo-Object can be used manually by pushing the button {{key press|Use Location}} in the [[UBIK_WinX_Client_Basics#Context_Menu|Context Menu]].

The geo information of an object gets used automatically if exactly one single object is found through scanning. If more objects are found, their geo information doesn´t get used. Scanning includes [[UBIK Client Basics#Bar Code|Bar Code]], [[UBIK Client Basics#QR Code|QR Code]], [[UBIK Client Basics#OCR|OCR]] and [[UBIK Client Basics#RFID|RFID]]. The automatic use of Geo-Object´s location can be turned off by disabling the "EnableObjectProximityPositioning" setting.

[[Category:WinX|UBIK WinX Client Basics]]

==== Beacon-Proximity Positioning ====
The Beacon Proximity Mode detects if the user is in the proximity of a beacon. The proximity region is defined by a proximity distance which creates a sphere around the beacon. Whenever the calculated distance to a beacon is smaller than the proximity distance, the user is supposed to be at the position of the beacon. If multiple regions intersect the user is supposed to be at the position of the nearest beacon.
In order to use Beacon Proximity as a Positioning System, Bluetooth Low Energy has to be available and enabled on the mobile device. If a new environment should be equipped with iBeacon-Positioning, an expert has to mount iBeacons on known positions and calibrate the propagation factor of these beacons. Proximity beacons can be configured using [[SYSCLS_PROXIMITY_BEACON]]. {{Version/WinXSince|UWP}}

[[Category:WinX|UBIK WinX Client Basics]]

== Finding Objects ==
=== Free Text Search ===

=== ID Marker ===

=== QR Code ===

=== Bar Code ===

=== RFID Code ===
Provides a fast and convenient way for users to find objects that are identifiable through [[RFID tags|RFID tags]].

=== OCR ===

== See also ==
* [[Client_Feature_Table]]

[[Category:WinX|UBIK WinX Client Basics]]

File:Guid property dialog.PNG

2017-11-30T14:06:00Z

KVB: KVB uploaded a new version of File:Guid property dialog.PNG

Reporting

2017-11-22T15:53:15Z

KVB: /* Editing the stylesheet */

Our Reporting feature allows users to create reports from queries, which will be saved to a file on disk, and displayed using a web browser.
Reports will contain information about the child objects of the query that the user is currently viewing. All offline available children, as well as all their properties and their children will recursively be captured and written to the report file. Reports can be used for printing, documentation, or logging purposes.
Users may also configure custom styling for the reports.

== Creating a report ==
Please see '''[[media:UBIK_WinX_Reporting.mp4|this video]]''' to see how to create and open report files.
If you cannot view the video, follow these instructions:

# Navigate to any query object.
# Click the "Create Report" button in the left-hand pane.
# The application picker will immediately be shown. Pick the application you wish to open the XML file with.
#* Due to a security feature of Chrome, the report will not be properly styled. Please use another browser.
#* You may also open the report using a regular text editor. Note that the report will not be styled in that case.
# Reports will be stored under '''LocalState/Reports'''. You may open them again from this folder at any time, or discard them.

== Styling reports ==
The user can completely customize the look and layout of reports in any way they please. We have provided a default stylesheet that can be overwritten or edited. The stylesheet uses the XSLT language, which converts XML data into HTML, which is interpreted by web browsers. XSLT should be uses mostly for creating templates or "containers" for XML elements, while additional (external) CSS files can be used to handle (visual) styling. This is also the approach we used for the default stylesheet.

=== Editing the stylesheet ===
Our default stylesheet will be located under '''LocalState/Reports/Stylesheet'''. If the stylesheet file or folders do not exist yet, our default stylesheet will be copied to this location upon app startup. The file will never be overwritten again by the default stylesheet, so it is safe to customize the contents of this file to your liking. To revert your changes quickly, you can simply delete the file again, and it will be regenerated once a new report is created, or the app is restarted.

To edit the stylesheet, simply open it with your favorite code editor or notepad. We suggest that you familiarize yourself with the XSLT (as well as HTML) syntax and functions before trying to make changes to this file. You can find an introductory tutorial to XSLT '''[https://www.w3schools.com/xml/xsl_intro.asp here]'''. Additionally, we have included comments inside the default stylesheet to clarify some of the code. Using XSLT, you can create templates for each individual XML element. To style these templates, you may use external CSS files (or inline CSS styles in HTML). For convenience, we have included an external CSS stylesheet within this XSLT file.

To view the changes you have made to the stylesheet, simply reload the report in your browser, or create a new one.

[[Category:WinX|Reporting]]

Reporting

2017-11-22T15:14:01Z

KVB:

Our Reporting feature allows users to create reports from queries, which will be saved to a file on disk, and displayed using a web browser.
Reports will contain information about the child objects of the query that the user is currently viewing. All offline available children, as well as all their properties and their children will recursively be captured and written to the report file. Reports can be used for printing, documentation, or logging purposes.
Users may also configure custom styling for the reports.

== Creating a report ==
Please see '''[[media:UBIK_WinX_Reporting.mp4|this video]]''' to see how to create and open report files.
If you cannot view the video, follow these instructions:

# Navigate to any query object.
# Click the "Create Report" button in the left-hand pane.
# The application picker will immediately be shown. Pick the application you wish to open the XML file with.
#* Due to a security feature of Chrome, the report will not be properly styled. Please use another browser.
#* You may also open the report using a regular text editor. Note that the report will not be styled in that case.
# Reports will be stored under '''LocalState/Reports'''. You may open them again from this folder at any time, or discard them.

== Styling reports ==
The user can completely customize the look and layout of reports in any way they please. We have provided a default stylesheet that can be overwritten or edited. The stylesheet uses the XSLT language, which converts XML data into HTML, which is interpreted by web browsers. XSLT should be uses mostly for creating templates or "containers" for XML elements, while additional (external) CSS files can be used to handle (visual) styling. This is also the approach we used for the default stylesheet.

=== Editing the stylesheet ===
Our default stylesheet will be located under '''LocalState/Reports/Stylesheet'''. If the stylesheet file or folders do not exist yet, our default stylesheet will be copied to this location upon app startup. The file will never be overwritten again by the default stylesheet, so it is safe to customize the contents of this file to your liking. To revert your changes quickly, you can simply delete the file again, and it will be regenerated once a new report is created, or the app is restarted.

To edit the stylesheet, simply open it with your favorite code editor or notepad. We suggest that you familiarize yourself with the XSLT (as well as HTML) syntax and functions before trying to make changes to this file. You can find an introductory tutorial to XSLT [https://www.w3schools.com/xml/xsl_intro.asp here]. Additionally, we have included comments inside the default stylesheet to clarify some of the code. Using XSLT, you can create templates for each individual XML element. To style these templates, you may use external CSS files (or inline CSS styles in HTML). For convenience, we have included an external CSS stylesheet within this XSLT file.

To view the changes you have made to the stylesheet, simply reload the report in your browser, or create a new one.

[[Category:WinX|Reporting]]

Reporting

2017-11-22T15:10:04Z

KVB: /* Creating a report */

Our Reporting feature allows users to create reports from queries, which will be saved to a file on disk, and displayed using a web browser.
Reports will contain information about the child objects of the query that the user is currently viewing. All offline available children, as well as all their properties and their children will recursively be captured and written to the report file. Reports can be used for printing, documentation, or logging purposes.
Users may also configure custom styling for the reports.

== Creating a report ==
Please see '''[[media:UBIK_WinX_Reporting.mp4|this video]]''' to see how to create and open report files.
If you cannot view the video, follow these instructions:

# Navigate to any query object.
# Click the "Create Report" button in the left-hand pane.
# The application picker will immediately be shown. Pick the application you wish to open the XML file with.
#* Due to a security feature of Chrome, the report will not be properly styled. Please use another browser.
#* You may also open the report using a regular text editor. Note that the report will not be styled in that case.
# Reports will be stored under '''LocalState/Reports'''. You may open them again from this folder at any time, or discard them.

== Styling reports ==
The user can completely customize the look and layout of reports in any way they please. We have provided a default stylesheet that can be overwritten or edited. The stylesheet uses the XSLT language, which converts XML data into HTML, which is interpreted by web browsers. XSLT should be uses mostly for creating templates or "containers" for XML elements, while additional (external) CSS files can be used to handle (visual) styling. This is also the approach we used for the default stylesheet.

=== Editing the stylesheet ===
Our default stylesheet will be located under '''LocalState/Reports/Stylesheet'''. If the stylesheet file or folders do not exist yet, our default stylesheet will be copied to this location upon app startup. The file will never be overwritten again by the default stylesheet, so it is safe to customize the contents of this file to your liking. To revert your changes quickly, you can simply delete the file again, and it will be regenerated once a new report is created, or the app is restarted.

To edit the stylesheet, simply open it with your favorite code editor or notepad. We suggest that you familiarize yourself with the XSLT (as well as HTML) syntax and functions before trying to make changes to this file. You can find an introductory tutorial to XSLT [https://www.w3schools.com/xml/xsl_intro.asp here]. Additionally, we have included comments inside the default stylesheet to clarify some of the code. Using XSLT, you can create templates for each individual XML element. To style these templates, you may use external CSS files (or inline CSS styles in HTML). For convenience, we have included an external CSS stylesheet within this XSLT file.

To view the changes you have made to the stylesheet, simply reload the report in your browser, or create a new one.

Reporting

2017-11-22T15:09:22Z

KVB: /* Editing the stylesheet */

Our Reporting feature allows users to create reports from queries, which will be saved to a file on disk, and displayed using a web browser.
Reports will contain information about the child objects of the query that the user is currently viewing. All offline available children, as well as all their properties and their children will recursively be captured and written to the report file. Reports can be used for printing, documentation, or logging purposes.
Users may also configure custom styling for the reports.

== Creating a report ==
Please see [[media:UBIK_WinX_Reporting.mp4|this video]] to see how to create and open report files.
If you cannot view the video, follow these instructions:

# Navigate to any query object.
# Click the "Create Report" button in the left-hand pane.
# The application picker will immediately be shown. Pick the application you wish to open the XML file with.
#* Due to a security feature of Chrome, the report will not be properly styled. Please use another browser.
#* You may also open the report using a regular text editor. Note that the report will not be styled in that case.
# Reports will be stored under '''LocalState/Reports'''. You may open them again from this folder at any time, or discard them.

== Styling reports ==
The user can completely customize the look and layout of reports in any way they please. We have provided a default stylesheet that can be overwritten or edited. The stylesheet uses the XSLT language, which converts XML data into HTML, which is interpreted by web browsers. XSLT should be uses mostly for creating templates or "containers" for XML elements, while additional (external) CSS files can be used to handle (visual) styling. This is also the approach we used for the default stylesheet.

=== Editing the stylesheet ===
Our default stylesheet will be located under '''LocalState/Reports/Stylesheet'''. If the stylesheet file or folders do not exist yet, our default stylesheet will be copied to this location upon app startup. The file will never be overwritten again by the default stylesheet, so it is safe to customize the contents of this file to your liking. To revert your changes quickly, you can simply delete the file again, and it will be regenerated once a new report is created, or the app is restarted.

To edit the stylesheet, simply open it with your favorite code editor or notepad. We suggest that you familiarize yourself with the XSLT (as well as HTML) syntax and functions before trying to make changes to this file. You can find an introductory tutorial to XSLT [https://www.w3schools.com/xml/xsl_intro.asp here]. Additionally, we have included comments inside the default stylesheet to clarify some of the code. Using XSLT, you can create templates for each individual XML element. To style these templates, you may use external CSS files (or inline CSS styles in HTML). For convenience, we have included an external CSS stylesheet within this XSLT file.

To view the changes you have made to the stylesheet, simply reload the report in your browser, or create a new one.

Reporting

2017-11-22T15:06:49Z

KVB: /* Editing the stylesheet */

Our Reporting feature allows users to create reports from queries, which will be saved to a file on disk, and displayed using a web browser.
Reports will contain information about the child objects of the query that the user is currently viewing. All offline available children, as well as all their properties and their children will recursively be captured and written to the report file. Reports can be used for printing, documentation, or logging purposes.
Users may also configure custom styling for the reports.

== Creating a report ==
Please see [[media:UBIK_WinX_Reporting.mp4|this video]] to see how to create and open report files.
If you cannot view the video, follow these instructions:

# Navigate to any query object.
# Click the "Create Report" button in the left-hand pane.
# The application picker will immediately be shown. Pick the application you wish to open the XML file with.
#* Due to a security feature of Chrome, the report will not be properly styled. Please use another browser.
#* You may also open the report using a regular text editor. Note that the report will not be styled in that case.
# Reports will be stored under '''LocalState/Reports'''. You may open them again from this folder at any time, or discard them.

== Styling reports ==
The user can completely customize the look and layout of reports in any way they please. We have provided a default stylesheet that can be overwritten or edited. The stylesheet uses the XSLT language, which converts XML data into HTML, which is interpreted by web browsers. XSLT should be uses mostly for creating templates or "containers" for XML elements, while additional (external) CSS files can be used to handle (visual) styling. This is also the approach we used for the default stylesheet.

=== Editing the stylesheet ===
Our default stylesheet will be located under '''LocalState/Reports/Stylesheet'''. If the stylesheet file or folders do not exist yet, our default stylesheet will be copied to this location upon app startup. The file will never be overwritten again by the default stylesheet, so it is safe to customize the contents of this file to your liking. To revert your changes quickly, you can simply delete the file again, and it will be regenerated once a new report is created, or the app is restarted.

To edit the stylesheet, simply open it with your favorite code editor or notepad. We suggest that you familiarize yourself with the XSLT (as well as HTML) syntax and functions before trying to make changes to this file. You can find an introductory tutorial to XSLT [https://www.w3schools.com/xml/xsl_intro.asp here]. Using XSLT, you can create templates for each individual XML element. To style these templates, you may use external CSS files (or inline CSS styles in HTML). For convenience, we have included an external CSS stylesheet within this XSLT file.

File:UBIK WinX Reporting.mp4

2017-11-22T14:56:28Z

KVB:

Reporting

2017-11-22T14:51:47Z

KVB:

Our Reporting feature allows users to create reports from queries, which will be saved to a file on disk, and displayed using a web browser.
Reports will contain information about the child objects of the query that the user is currently viewing. All offline available children, as well as all their properties and their children will recursively be captured and written to the report file. Reports can be used for printing, documentation, or logging purposes.
Users may also configure custom styling for the reports.

== Creating a report ==
Please see [[media:UBIK_WinX_Reporting.mp4|this video]] to see how to create and open report files.
If you cannot view the video, follow these instructions:

# Navigate to any query object.
# Click the "Create Report" button in the left-hand pane.
# The application picker will immediately be shown. Pick the application you wish to open the XML file with.
#* Due to a security feature of Chrome, the report will not be properly styled. Please use another browser.
#* You may also open the report using a regular text editor. Note that the report will not be styled in that case.
# Reports will be stored under '''LocalState/Reports'''. You may open them again from this folder at any time, or discard them.

== Styling reports ==
The user can completely customize the look and layout of reports in any way they please. We have provided a default stylesheet that can be overwritten or edited. The stylesheet uses the XSLT language, which converts XML data into HTML, which is interpreted by web browsers. XSLT should be uses mostly for creating templates or "containers" for XML elements, while additional (external) CSS files can be used to handle (visual) styling. This is also the approach we used for the default stylesheet.

=== Editing the stylesheet ===
Our default stylesheet will be located under '''LocalState/Reports/Stylesheet'''. If the stylesheet file or folders do not exist yet, our default stylesheet will be copied to this location upon app startup. The file will never be overwritten again by the default stylesheet, so it is safe to customize the contents of this file to your liking. To revert your changes quickly, you can simply delete the file again, and it will be regenerated once a new report is created, or the app is restarted.

To edit the stylesheet, simply open it with your favorite code editor or notepad. We suggest that you familiarize yourself with the XSLT (as well as HTML) syntax and functions before trying to make changes to this file. You can find an introductory tutorial to XSLT [https://www.w3schools.com/xml/xsl_intro.asp here].

Reporting

2017-11-22T14:35:39Z

KVB:

Our Reporting feature allows users to create reports from queries, which will be saved to a file on disk, and displayed using a web browser.
Reports will contain information about the child objects of the query that the user is currently viewing. All offline available children, as well as all their properties and their children will recursively be captured and written to the report file. Reports can be used for printing, documentation, or logging purposes.
Users may also configure custom styling for the reports.

== Creating a report ==
Please see this video to see how to create and open report files.
If you cannot view the video, follow these instructions:

# Navigate to any query object.
# Click the "Create Report" button in the left-hand pane.
# The application picker will immediately be shown. Pick the application you wish to open the XML file with.
#* Due to a security feature of Chrome, the report will not be properly styled. Please use another browser.
#* You may also open the report using a regular text editor. Note that the report will not be styled in that case.
# Reports will be stored under '''LocalState/Reports'''. You may open them again from this folder at any time, or discard them.

== Styling reports ==
The user can completely customize the look and layout of reports in any way they please. We have provided a default stylesheet that can be overwritten or edited. The stylesheet uses the XSLT language, which converts XML data into HTML, which is interpreted by web browsers. XSLT should be uses mostly for creating templates or "containers" for XML elements, while additional (external) CSS files can be used to handle (visual) styling. This is also the approach we used for the default stylesheet.

=== Editing the stylesheet ===
Our default stylesheet will be located under '''LocalState/Reports/Stylesheet'''. If the stylesheet file or folders do not exist yet, our default stylesheet will be copied to this location upon app startup. The file will never be overwritten again by the default stylesheet, so it is safe to customize the contents of this file to your liking. To revert your changes quickly, you can simply delete the file again, and it will be regenerated once a new report is created, or the app is restarted.

To edit the stylesheet, simply open it with your favorite code editor or notepad. We suggest that you familiarize yourself with the XSLT (as well as HTML) syntax and functions before trying to make changes to this file. You can find an introductory tutorial to XSLT [https://www.w3schools.com/xml/xsl_intro.asp here].

Reporting

2017-11-22T13:49:44Z

KVB: Created page with "Our Reporting feature allows users to create reports from queries, which will be saved to a file on disk, and displayed using a web browser. Reports will contain information a..."

UBIK WinX Client Basics

2017-11-13T10:36:23Z

KVB: /* Editors */

{{UBIK}} Client is the mobile application for viewing and modifying data, showing documents, starting navigation, visualizing POIs and much more.

Client applications are available for Android and WinX, however the features available on each of the platform dependent applications might differ. An overview of the available features can be found in the [[Client_Feature_Table|feature comparison table]].

== Login ==
Users need to login in order to access confidential data, this can be done in the [[Login View]].

== Profiles ==
Profiles are used to store connection information for {{UBIK}} services. It specifies the location where to find the service along with other useful informations. Profiles are stored by UBIK whenever the user created connection information and stored it in the settings. However, profiles can also be created and edited with any text editor. Possible settings to be defined are:
* InternalConnectionSettings: Connections settings how to connect to the Content and the USAM service that has been set up.
** Application: the [[APPLICATION]] to use with the service
** AuthenticationPort: Port Number of the authentication (USAM) service (default: 777)
** AuthenticationProtocol: Protocol of the authentication service (default: https)
** AuthenticationServer: the ip address of the authentication server
** AuthenticationService: the path to the authentication service
** ContentPort: Port Number of the content service (default: 777)
** ContentProtocol: Protocol of the content service (default: https)
** ContentServer: the ip address of the content server
** ContentService: the path to the content service
** Context: the [[CONTEXT]] to use with the service
** SyncMode: the used sync mode (Online [= Auto], Manual, Offline; default:Online)
* IsDefault: true, if the profile should be the default profile
* Name: the name of the profile (will also be used to identify the database)
* Project: the project name. Use this to share a single project name with more than one profile. If the project is defined, all profile with the same project will share one database.
* ShowHiddenSettings: show hidden settings (feault: false)

Example:
<source lang = "xml">
<?xml version="1.0" encoding="utf-8"?>
<Profile xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/UBIK.WinX.Settings">
<Description i:nil="true" />
<InternalConnectionSettings>
<Application>APP_DEMO</Application>
<AuthenticationPort>777</AuthenticationPort>
<AuthenticationProtocol>https</AuthenticationProtocol>
<AuthenticationServer>80.243.175.50</AuthenticationServer>
<AuthenticationService>UBIK/DBG/AUG/DEMO.250/USAM/USAM.svc</AuthenticationService>
<ContentPort>777</ContentPort>
<ContentProtocol>https</ContentProtocol>
<ContentServer>80.243.175.50</ContentServer>
<ContentService>UBIK/DBG/AUG/DEMO.250/CONTENT/UBIKContent.svc</ContentService>
<Context>CXT_DEMO</Context>
<SyncMode>Online</SyncMode>
</InternalConnectionSettings>
<IsDefault>true</IsDefault>
<Name>DEMO.250.AT</Name>
<Project>DEMO.250</Project>
<ShowHiddenSettings>false</ShowHiddenSettings>
</Profile>
</source>

== Content Browser ==
Allows to navigate through the entire data model in a hierarchical manner, as it is published by the server.

Initially, a list of objects ("root objects") is shown. Upon selecting an object, a new browser is opened for that object, showing details about it. When an object is selected in the content browser, it is called the browser's context. For such a contextual object, child objects and selected properties are shown. Also, there is a context menu providing actions related to the currently selected object.

=== Status Bar ===
[[File:UI_WinX_DbSavingIndicator.PNG|300 px|thumb|border|alt=Saving Symbol|Saving Symbol]]
{{Version/WinXSince|2.5.4}}Whenever content is being saved into the local database (for example, after a branch is downloaded from the server), there will be a blinking symbol indicating the saving activity is happening in the background.
During that time, the user is advised to not logout or close the app because the content might be lost otherwise. However, it is okay to undertake other tasks such as browsing, editing or downloading branches.

=== Child Page ===

[[File:ChildPage.PNG|400 px|thumb|border|alt=Child Page|Child Page]]

The child page shows the context of a selected object.

The global status bar shows the icon, the name and the description of the selected object. An arrow on the left side allows the user to navigate back to the parent object. On the right side the currently logged-in user is indicated. By clicking on the username one is able to navigate back to the home screen or log off.

The right side of the child page shows child objects of the current object. Each child object is represented by an icon, a name and a description.

On the left side of the child page the current object´s high priority properties are shown. By clicking on a live value property, the live value details dialog opens. By clicking on an editable [[UBIK_WinX_Client_Basics#High_priority_properties| high priority property]], an editor opens {{Version/WinXSince|2.5.4}}. If a property was edited a save button is shown in the lower left corner, allowing the user to commit the changes. If a property of a query object was edited an evaluate button is shown in the lower left corner, allowing the user to run the query with the changed propery.

=== Details Page ===

=== Context Menu ===

=== Objects ===

==== Root objects vs child objects ====

The first entry point in the ''Content Browser'' is the list of root objects.

==== Task objects ====

==== Query objects ====

==== Safety relevant objects ====

==== Commissioning objects ====

==== Locked objects ====

=== Properties ===

==== Live value properties ====

==== High priority properties ====
High priority properties are properities having a priority higher than the [[Settings#Content |priority threshold]].

==== Selective List Properties ====

==== Properties with value records {{Version/WinXSince|2.5.4}} ====
[[File:UI_WinX_PropertyWithValueRecords.png|thumb|A property with value records]]
[[File:UI_WinX_PropertyValueRecords.png|thumb|Property value records dialog]]
In addition to its value, a property might also bring along a series of value records showing "who changed the value at what time".

When such records exist, the property row shows a special symbol on the right side. After a right click (with mouse) or a long tap (with touch) on the property row, a dialog will be shown to present these records (sorted by their time, recent ones on top).

{{Clear}}

==== Editors ====

===== Geo Editor & Teach In =====

==== Guid editor ====
[[File:Guid_property_dialog.PNG|thumb|border|alt=Guid property editor dialog|Guid property editor dialog]]

To edit Guid properties (that do not have a selective list available), we have implemented a special system. Since a Guid property always just contains the Guid as a reference to another object, we can use a query to find the object we want to assign to this property.

When the Guid property has a FilterQuery datamember (which should contain the guid of a query), it will become editable through this query. Note that this FilterQuery guid will not actually be visible in the client. All this should be setup in the backend, the client has no control over this.

When clicking an editable Guid property, you will see a dialog with the 3 following buttons added (see image):

;View Object
:This button will be enabled when there is a valid guid assigned to the property. Clicking this button will immediately navigate to the referenced object.
;Edit Property
:If the property has a valid FilterQuery assigned to it, clicking this button will launch that query.
;Clear Property Value
:If the property has a guid assigned, the user can press this button to reset the value back to empty.

Once the user has launched the query, they can click any of the displayed items. When clicking one of them, it will immediately be set as the reference in the original Guid property. To cancel selecting an item (and stop editing the property), simply navigate to any other page (by pressing back, using navigation bar, etc).

[[Category:WinX|UBIK WinX Client Basics]]

=== Documents ===
UBIK supports and displays document objects and a bunch of actions related to them (editing, redlining, creation, thumbnails, ...).

==== Customizing Possibilities ====

==== Editing{{Version/WinXSince|2.5.4}} ====
[[File:UI_WinX_EditDocumentButton.png|thumb|Button to edit a document]]
For [[SYSCLS_EDITABLEDOCUMENT|editable documents]], there is an {{key press|edit}} button in the bottom app bar. It allows the user to edit a document file using the default app of the OS. If a file is changed during the edit, the same {{key press|save}} button appears just like it does for content with changed properties.
{{Hint|Similar to saving, other app features also apply on edited documents. For example, reverting local changes for an edited document will throw away the changed document file and restore it to the server version.}}
[[File:UI_WinX_EditDocumentOverlayButton.png|thumb|Edit button in thumbnail overlay]]
An alternative way to start editing is to right click on a document's thumbnail, which brings up an overlay of buttons, and then select the {{key press|edit}} button. The difference here is that there is no {{key press|save}} button and any changes are automatically saved (and committed if in online mode).
{{Clear}}

==== Offline availability ====
When a user selects a branch to bring offline, files of all document objects underneath are downloaded in principle. However, they can also be selectively configured to be ignored with a [[SYSCLS_OFFLINE_AVAILABLE_DOCUMENT|classification]] on the server-side. Once a document is classified as offline available, the document file will not be removed when the storage for already synchronized document files is cleared.
{{Hint|This is not to be confused with the accessibility related to [[User_Rights|user rights]]. The logic here is "some documents '''do not have to''' be downloaded", not "some documents '''can not''' be downloaded/accessed". In other words, a user can browse to and open the document regardless of this configuration.}}

==== Clear Online Documents ====
By clearing the online documents, it is possible to free up system memory if needed. It can be triggered by pressing the button "Clear online documents" in the general settings tab. Online documents are documents already uploaded to the server. They can be downloaded anytime agian when the client is connected to the server. However, documents classified as offline available will not be affected and will always stay on the device.

== AR Features ==

=== POI View ===
Brings up the POI View|Augmented Reality view and displays Points of Interest (POI's) related to the current location of the mobile device.

=== Markerless ===

=== Map View ===
Opens the Map View and displays Points of Interest (POI's) related to the current location of the mobile device.

== Positioning ==
{{UBIK}} clients use a [[Location_Manager|Location Manager]] in order to gain knowledge about their position, so it can help the user navigate to his/her target.

The user can choose one of different positioning modes optimized for different environments.
Most of them incorporate multiple technologies for calculating positions or checking their reliability.

=== Positioning modes ===

* ''Use all'' - uses all available position sources
* ''LLA only mode'' - used for positioning using markers only
* ''Beacon Proximity mode'' - uses iBeacon proximity and LLA only

=== Technologies ===

==== GPS ====
GPS is used as a primary positioning input source for outdoor areas. Its precision depends on the environment and satellite availability. With good circumstances, the accuracy varies between 1 and 10 meters.

==== LLA markers ====
LLA markers basically are QR codes with location data encoded into them - which can be used for positioning when they are scanned.

==== Object Proximity Positioning ====
The location of nearby Geo-Objects can be used for positioning.

The position of a Geo-Object can be used manually by pushing the button {{key press|Use Location}} in the [[UBIK_WinX_Client_Basics#Context_Menu|Context Menu]].

The geo information of an object gets used automatically if exactly one single object is found through scanning. If more objects are found, their geo information doesn´t get used. Scanning includes [[UBIK Client Basics#Bar Code|Bar Code]], [[UBIK Client Basics#QR Code|QR Code]], [[UBIK Client Basics#OCR|OCR]] and [[UBIK Client Basics#RFID|RFID]]. The automatic use of Geo-Object´s location can be turned off by disabling the "EnableObjectProximityPositioning" setting.

[[Category:WinX|UBIK WinX Client Basics]]

==== Beacon-Proximity Positioning ====
The Beacon Proximity Mode detects if the user is in the proximity of a beacon. The proximity region is defined by a proximity distance which creates a sphere around the beacon. Whenever the calculated distance to a beacon is smaller than the proximity distance, the user is supposed to be at the position of the beacon. If multiple regions intersect the user is supposed to be at the position of the nearest beacon.
In order to use Beacon Proximity as a Positioning System, Bluetooth Low Energy has to be available and enabled on the mobile device. If a new environment should be equipped with iBeacon-Positioning, an expert has to mount iBeacons on known positions and calibrate the propagation factor of these beacons. Proximity beacons can be configured using [[SYSCLS_PROXIMITY_BEACON]]. {{Version/WinXSince|UWP}}

[[Category:WinX|UBIK WinX Client Basics]]

== Finding Objects ==
=== Free Text Search ===

=== ID Marker ===

=== QR Code ===

=== Bar Code ===

=== RFID Code ===
Provides a fast and convenient way for users to find objects that are identifiable through [[RFID tags|RFID tags]].

=== OCR ===

== See also ==
* [[Client_Feature_Table]]

[[Category:WinX|UBIK WinX Client Basics]]

File:Guid property dialog.PNG

2017-11-13T10:34:39Z

KVB:

Login View

2017-10-24T12:11:11Z

KVB: /* Accessing login view */

For confidentiality reason, users are required to login before they have access to most of the {{UBIK}} features.

== Accessing login view ==
[[File:UI_WinX_Login_View.png|120px|thumb|alt=Login View|Login View]]
The login view is displayed after starting the app. It is possible to access the login view from every where in the app by pressing the login icon in the top right corner and selecting "log out".

At the top of the screen, the name of the most recently used profile (if any) will be displayed. When pressing "Login" without selecting a different profile first, this profile will automatically be used.

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Profile selection ==
[[File:Profile_browser.png|x200px|thumb|alt=Profile Browser (collapsed)|Profile Browser (collapsed)]] [[File:Profile_browser_expanded.png|x200px|thumb|alt=Profile Browser (expanded)|Profile Browser (expanded)]]
The name of the currently selected profile is displayed on the top of the view. By default, the last used profile will be selected here.
It is possible to change the profile by pressing the Profile Button. The profile selection flyout will pop up, from which the user can select any profile (see the figure on the right).

To add custom profiles, you must add them under the app's RoamingState folder. You can also categorize your profiles using subfolders within this directory.
You will see 2 different tabs when opening the profile selection view, with the third hidden by default.

=== Favorites ===
The "Favorites" tab shows profiles that the user has marked as favorites. To mark a profile as favorite, simply click the the star icon next to a profile's name. You will see it immediately appearing in the favorites list (sorted alphabetically). You can of course undo this action by simply pressing the star icon again to unmark the profile as favorite.

=== Recent ===
The "Recent" tab shows all available profiles, ordered by most recently used (at the top), to least recently used, excluding favorited profiles (which appear in the "Favorites" tab). When you click a profile anywhere in the selection view, it will be timestamped, and added to the top of the "Recent" tab.

=== Browser ===
To view the "Browser" tab, the user can click the expansion button on the right side to toggle the tab open or closed.
The "Browser" tab shows all available profiles (including favorites), but displays them exactly as your file browser would, including subfolders. The user can navigate through subfolders simply by clicking them.

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Login Dialog ==
[[File:UI_WinX_Login_Dialog.png|thumb|alt=Login Dialog|Login Dialog]]
The login dialog is opened by pressing the Login button. The dialog also opens automatically after selecting a profile.
The first time the user uses a single profile to connect to a service, he is asked whether the system should remeber login and password (for the user and profile). If the user selects yes, the login dialog will not appear again and the credentials are used immediately the next time he connects by using the profile. If the user selects no, he has to enter his credentials every time.

=== Offline Login ===
Every successfull online login is stored. The stored credentials are used for supporting offline logins.
{{Hint|You can access a local database without online connection (offline) when the credentials where used once to connect successfully to the online service.}}

=== Clear Cache ===
The clear cache feature (settings) deletes all the remembered credentilas (login and password) from the system.
{{Attention|Offline logins are not possible after clearing the cache until the user connected once at the online service.}}

== Team login {{Version/WinXSince|2.6.1}}==
[[File:UI_WinX_Team_Login_Button.png|thumb|alt=Team Login Button|Team Login Button]]
[[File:UI_WinX_Team_Login_Dialog.png|thumb|alt=Team Login Dialog|Team Login Dialog]]
Team login allows a group of users to login with a single device and perform tasks together as a team.
=== Team login button ===
{{Attention|This button is not available by default in the app, certain custom templates are needed for this. An example template can be downloaded {{FileLink|xaml_262_20170310_Team_Login_Button.zip|here}}.}}
=== Team login dialog ===
The team login dialog has the following parts:
# Profile selector to change profiles;
#Team member list (each member has a remove button at the right side);
# {{key press|+}} button to add members;
# {{key press|Login}} button;
# {{key press|Close}} button.
The same [[Login_View#Login_Dialog|login dialog]] shows up once the {{key press|+}} button is pressed and the members should enter their credentials one by one. Once all the members are successfully added, press the {{key press|Login}} button to login as a team.
{{Hint|All members in a team should login to the same service, namely using the same profile. Therefore, the profile selector will be disabled as long as the member list is not empty.}}

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

Login View

2017-10-24T12:09:39Z

KVB: /* Profile selection */

For confidentiality reason, users are required to login before they have access to most of the {{UBIK}} features.

== Accessing login view ==
[[File:UI_WinX_Login_View.png|100px|thumb|alt=Login View|Login View]]
The login view is displayed after starting the app. It is possible to access the login view from every where in the app by pressing the login icon in the top right corner and selecting "log out".

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Profile selection ==
[[File:Profile_browser.png|x200px|thumb|alt=Profile Browser (collapsed)|Profile Browser (collapsed)]] [[File:Profile_browser_expanded.png|x200px|thumb|alt=Profile Browser (expanded)|Profile Browser (expanded)]]
The name of the currently selected profile is displayed on the top of the view. By default, the last used profile will be selected here.
It is possible to change the profile by pressing the Profile Button. The profile selection flyout will pop up, from which the user can select any profile (see the figure on the right).

To add custom profiles, you must add them under the app's RoamingState folder. You can also categorize your profiles using subfolders within this directory.
You will see 2 different tabs when opening the profile selection view, with the third hidden by default.

=== Favorites ===
The "Favorites" tab shows profiles that the user has marked as favorites. To mark a profile as favorite, simply click the the star icon next to a profile's name. You will see it immediately appearing in the favorites list (sorted alphabetically). You can of course undo this action by simply pressing the star icon again to unmark the profile as favorite.

=== Recent ===
The "Recent" tab shows all available profiles, ordered by most recently used (at the top), to least recently used, excluding favorited profiles (which appear in the "Favorites" tab). When you click a profile anywhere in the selection view, it will be timestamped, and added to the top of the "Recent" tab.

=== Browser ===
To view the "Browser" tab, the user can click the expansion button on the right side to toggle the tab open or closed.
The "Browser" tab shows all available profiles (including favorites), but displays them exactly as your file browser would, including subfolders. The user can navigate through subfolders simply by clicking them.

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Login Dialog ==
[[File:UI_WinX_Login_Dialog.png|thumb|alt=Login Dialog|Login Dialog]]
The login dialog is opened by pressing the Login button. The dialog also opens automatically after selecting a profile.
The first time the user uses a single profile to connect to a service, he is asked whether the system should remeber login and password (for the user and profile). If the user selects yes, the login dialog will not appear again and the credentials are used immediately the next time he connects by using the profile. If the user selects no, he has to enter his credentials every time.

=== Offline Login ===
Every successfull online login is stored. The stored credentials are used for supporting offline logins.
{{Hint|You can access a local database without online connection (offline) when the credentials where used once to connect successfully to the online service.}}

=== Clear Cache ===
The clear cache feature (settings) deletes all the remembered credentilas (login and password) from the system.
{{Attention|Offline logins are not possible after clearing the cache until the user connected once at the online service.}}

== Team login {{Version/WinXSince|2.6.1}}==
[[File:UI_WinX_Team_Login_Button.png|thumb|alt=Team Login Button|Team Login Button]]
[[File:UI_WinX_Team_Login_Dialog.png|thumb|alt=Team Login Dialog|Team Login Dialog]]
Team login allows a group of users to login with a single device and perform tasks together as a team.
=== Team login button ===
{{Attention|This button is not available by default in the app, certain custom templates are needed for this. An example template can be downloaded {{FileLink|xaml_262_20170310_Team_Login_Button.zip|here}}.}}
=== Team login dialog ===
The team login dialog has the following parts:
# Profile selector to change profiles;
#Team member list (each member has a remove button at the right side);
# {{key press|+}} button to add members;
# {{key press|Login}} button;
# {{key press|Close}} button.
The same [[Login_View#Login_Dialog|login dialog]] shows up once the {{key press|+}} button is pressed and the members should enter their credentials one by one. Once all the members are successfully added, press the {{key press|Login}} button to login as a team.
{{Hint|All members in a team should login to the same service, namely using the same profile. Therefore, the profile selector will be disabled as long as the member list is not empty.}}

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

Login View

2017-10-24T12:08:30Z

KVB: /* Profile selection */

For confidentiality reason, users are required to login before they have access to most of the {{UBIK}} features.

== Accessing login view ==
[[File:UI_WinX_Login_View.png|100px|thumb|alt=Login View|Login View]]
The login view is displayed after starting the app. It is possible to access the login view from every where in the app by pressing the login icon in the top right corner and selecting "log out".

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Profile selection ==
[[File:Profile_browser.png|x200px|thumb|alt=Profile Browser (collapsed)|Profile Browser (collapsed)]] [[File:Profile_browser_expanded.png|x200px|thumb|alt=Profile Browser (expanded)|Profile Browser (expanded)]]
The name of the currently selected profile is displayed on the top of the view. By default, the last used profile will be selected here.
It is possible to change the profile by pressing the Profile Button. The profile selection flyout will pop up, from which the user can select any profile (see the figure on the right).

To add custom profiles, you must add them under the app's RoamingState folder. You can also categorize your profiles using subfolders within this directory.
You will see 3 different tabs when opening the profile selection view.

=== Favorites ===
The "Favorites" tab shows profiles that the user has marked as favorites. To mark a profile as favorite, simply click the the star icon next to a profile's name. You will see it immediately appearing in the favorites list (sorted alphabetically). You can of course undo this action by simply pressing the star icon again to unmark the profile as favorite.

=== Recent ===
The "Recent" tab shows all available profiles, ordered by most recently used (at the top), to least recently used, excluding favorited profiles (which appear in the "Favorites" tab). When you click a profile anywhere in the selection view, it will be timestamped, and added to the top of the "Recent" tab.

=== Browser ===
To view the "Browser" tab, the user can click the expansion button on the right side to toggle the tab open or closed.
The "Browser" tab shows all available profiles (including favorites), but displays them exactly as your file browser would, including subfolders. The user can navigate through subfolders simply by clicking them.

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Login Dialog ==
[[File:UI_WinX_Login_Dialog.png|thumb|alt=Login Dialog|Login Dialog]]
The login dialog is opened by pressing the Login button. The dialog also opens automatically after selecting a profile.
The first time the user uses a single profile to connect to a service, he is asked whether the system should remeber login and password (for the user and profile). If the user selects yes, the login dialog will not appear again and the credentials are used immediately the next time he connects by using the profile. If the user selects no, he has to enter his credentials every time.

=== Offline Login ===
Every successfull online login is stored. The stored credentials are used for supporting offline logins.
{{Hint|You can access a local database without online connection (offline) when the credentials where used once to connect successfully to the online service.}}

=== Clear Cache ===
The clear cache feature (settings) deletes all the remembered credentilas (login and password) from the system.
{{Attention|Offline logins are not possible after clearing the cache until the user connected once at the online service.}}

== Team login {{Version/WinXSince|2.6.1}}==
[[File:UI_WinX_Team_Login_Button.png|thumb|alt=Team Login Button|Team Login Button]]
[[File:UI_WinX_Team_Login_Dialog.png|thumb|alt=Team Login Dialog|Team Login Dialog]]
Team login allows a group of users to login with a single device and perform tasks together as a team.
=== Team login button ===
{{Attention|This button is not available by default in the app, certain custom templates are needed for this. An example template can be downloaded {{FileLink|xaml_262_20170310_Team_Login_Button.zip|here}}.}}
=== Team login dialog ===
The team login dialog has the following parts:
# Profile selector to change profiles;
#Team member list (each member has a remove button at the right side);
# {{key press|+}} button to add members;
# {{key press|Login}} button;
# {{key press|Close}} button.
The same [[Login_View#Login_Dialog|login dialog]] shows up once the {{key press|+}} button is pressed and the members should enter their credentials one by one. Once all the members are successfully added, press the {{key press|Login}} button to login as a team.
{{Hint|All members in a team should login to the same service, namely using the same profile. Therefore, the profile selector will be disabled as long as the member list is not empty.}}

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

Login View

2017-10-24T12:08:08Z

KVB: /* Accessing login view */

For confidentiality reason, users are required to login before they have access to most of the {{UBIK}} features.

== Accessing login view ==
[[File:UI_WinX_Login_View.png|100px|thumb|alt=Login View|Login View]]
The login view is displayed after starting the app. It is possible to access the login view from every where in the app by pressing the login icon in the top right corner and selecting "log out".

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Profile selection ==
[[File:Profile_browser.png|x250px|thumb|alt=Profile Browser (collapsed)|Profile Browser (collapsed)]] [[File:Profile_browser_expanded.png|x250px|thumb|alt=Profile Browser (expanded)|Profile Browser (expanded)]]
The name of the currently selected profile is displayed on the top of the view. By default, the last used profile will be selected here.
It is possible to change the profile by pressing the Profile Button. The profile selection flyout will pop up, from which the user can select any profile (see the figure on the right).

To add custom profiles, you must add them under the app's RoamingState folder. You can also categorize your profiles using subfolders within this directory.
You will see 3 different tabs when opening the profile selection view.

=== Favorites ===
The "Favorites" tab shows profiles that the user has marked as favorites. To mark a profile as favorite, simply click the the star icon next to a profile's name. You will see it immediately appearing in the favorites list (sorted alphabetically). You can of course undo this action by simply pressing the star icon again to unmark the profile as favorite.

=== Recent ===
The "Recent" tab shows all available profiles, ordered by most recently used (at the top), to least recently used, excluding favorited profiles (which appear in the "Favorites" tab). When you click a profile anywhere in the selection view, it will be timestamped, and added to the top of the "Recent" tab.

=== Browser ===
To view the "Browser" tab, the user can click the expansion button on the right side to toggle the tab open or closed.
The "Browser" tab shows all available profiles (including favorites), but displays them exactly as your file browser would, including subfolders. The user can navigate through subfolders simply by clicking them.

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Login Dialog ==
[[File:UI_WinX_Login_Dialog.png|thumb|alt=Login Dialog|Login Dialog]]
The login dialog is opened by pressing the Login button. The dialog also opens automatically after selecting a profile.
The first time the user uses a single profile to connect to a service, he is asked whether the system should remeber login and password (for the user and profile). If the user selects yes, the login dialog will not appear again and the credentials are used immediately the next time he connects by using the profile. If the user selects no, he has to enter his credentials every time.

=== Offline Login ===
Every successfull online login is stored. The stored credentials are used for supporting offline logins.
{{Hint|You can access a local database without online connection (offline) when the credentials where used once to connect successfully to the online service.}}

=== Clear Cache ===
The clear cache feature (settings) deletes all the remembered credentilas (login and password) from the system.
{{Attention|Offline logins are not possible after clearing the cache until the user connected once at the online service.}}

== Team login {{Version/WinXSince|2.6.1}}==
[[File:UI_WinX_Team_Login_Button.png|thumb|alt=Team Login Button|Team Login Button]]
[[File:UI_WinX_Team_Login_Dialog.png|thumb|alt=Team Login Dialog|Team Login Dialog]]
Team login allows a group of users to login with a single device and perform tasks together as a team.
=== Team login button ===
{{Attention|This button is not available by default in the app, certain custom templates are needed for this. An example template can be downloaded {{FileLink|xaml_262_20170310_Team_Login_Button.zip|here}}.}}
=== Team login dialog ===
The team login dialog has the following parts:
# Profile selector to change profiles;
#Team member list (each member has a remove button at the right side);
# {{key press|+}} button to add members;
# {{key press|Login}} button;
# {{key press|Close}} button.
The same [[Login_View#Login_Dialog|login dialog]] shows up once the {{key press|+}} button is pressed and the members should enter their credentials one by one. Once all the members are successfully added, press the {{key press|Login}} button to login as a team.
{{Hint|All members in a team should login to the same service, namely using the same profile. Therefore, the profile selector will be disabled as long as the member list is not empty.}}

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

Login View

2017-10-24T12:07:26Z

KVB: /* Accessing login view */

For confidentiality reason, users are required to login before they have access to most of the {{UBIK}} features.

== Accessing login view ==
[[File:UI_WinX_Login_View.png|left|thumb|alt=Login View|Login View]]
The login view is displayed after starting the app. It is possible to access the login view from every where in the app by pressing the login icon in the top right corner and selecting "log out".

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Profile selection ==
[[File:Profile_browser.png|x250px|thumb|alt=Profile Browser (collapsed)|Profile Browser (collapsed)]] [[File:Profile_browser_expanded.png|x250px|thumb|alt=Profile Browser (expanded)|Profile Browser (expanded)]]
The name of the currently selected profile is displayed on the top of the view. By default, the last used profile will be selected here.
It is possible to change the profile by pressing the Profile Button. The profile selection flyout will pop up, from which the user can select any profile (see the figure on the right).

To add custom profiles, you must add them under the app's RoamingState folder. You can also categorize your profiles using subfolders within this directory.
You will see 3 different tabs when opening the profile selection view.

=== Favorites ===
The "Favorites" tab shows profiles that the user has marked as favorites. To mark a profile as favorite, simply click the the star icon next to a profile's name. You will see it immediately appearing in the favorites list (sorted alphabetically). You can of course undo this action by simply pressing the star icon again to unmark the profile as favorite.

=== Recent ===
The "Recent" tab shows all available profiles, ordered by most recently used (at the top), to least recently used, excluding favorited profiles (which appear in the "Favorites" tab). When you click a profile anywhere in the selection view, it will be timestamped, and added to the top of the "Recent" tab.

=== Browser ===
To view the "Browser" tab, the user can click the expansion button on the right side to toggle the tab open or closed.
The "Browser" tab shows all available profiles (including favorites), but displays them exactly as your file browser would, including subfolders. The user can navigate through subfolders simply by clicking them.

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Login Dialog ==
[[File:UI_WinX_Login_Dialog.png|thumb|alt=Login Dialog|Login Dialog]]
The login dialog is opened by pressing the Login button. The dialog also opens automatically after selecting a profile.
The first time the user uses a single profile to connect to a service, he is asked whether the system should remeber login and password (for the user and profile). If the user selects yes, the login dialog will not appear again and the credentials are used immediately the next time he connects by using the profile. If the user selects no, he has to enter his credentials every time.

=== Offline Login ===
Every successfull online login is stored. The stored credentials are used for supporting offline logins.
{{Hint|You can access a local database without online connection (offline) when the credentials where used once to connect successfully to the online service.}}

=== Clear Cache ===
The clear cache feature (settings) deletes all the remembered credentilas (login and password) from the system.
{{Attention|Offline logins are not possible after clearing the cache until the user connected once at the online service.}}

== Team login {{Version/WinXSince|2.6.1}}==
[[File:UI_WinX_Team_Login_Button.png|thumb|alt=Team Login Button|Team Login Button]]
[[File:UI_WinX_Team_Login_Dialog.png|thumb|alt=Team Login Dialog|Team Login Dialog]]
Team login allows a group of users to login with a single device and perform tasks together as a team.
=== Team login button ===
{{Attention|This button is not available by default in the app, certain custom templates are needed for this. An example template can be downloaded {{FileLink|xaml_262_20170310_Team_Login_Button.zip|here}}.}}
=== Team login dialog ===
The team login dialog has the following parts:
# Profile selector to change profiles;
#Team member list (each member has a remove button at the right side);
# {{key press|+}} button to add members;
# {{key press|Login}} button;
# {{key press|Close}} button.
The same [[Login_View#Login_Dialog|login dialog]] shows up once the {{key press|+}} button is pressed and the members should enter their credentials one by one. Once all the members are successfully added, press the {{key press|Login}} button to login as a team.
{{Hint|All members in a team should login to the same service, namely using the same profile. Therefore, the profile selector will be disabled as long as the member list is not empty.}}

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

Login View

2017-10-24T12:02:03Z

KVB: /* Profile selection */

For confidentiality reason, users are required to login before they have access to most of the {{UBIK}} features.

== Accessing login view ==
[[File:UI_WinX_Login_View.png|thumb|alt=Login View|Login View]]
The login view is displayed after starting the app. It is possible to access the login view from every where in the app by pressing the login icon in the top right corner and selecting "log out".

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Profile selection ==
[[File:Profile_browser.png|x250px|thumb|alt=Profile Browser (collapsed)|Profile Browser (collapsed)]] [[File:Profile_browser_expanded.png|x250px|thumb|alt=Profile Browser (expanded)|Profile Browser (expanded)]]
The name of the currently selected profile is displayed on the top of the view. By default, the last used profile will be selected here.
It is possible to change the profile by pressing the Profile Button. The profile selection flyout will pop up, from which the user can select any profile (see the figure on the right).

To add custom profiles, you must add them under the app's RoamingState folder. You can also categorize your profiles using subfolders within this directory.
You will see 3 different tabs when opening the profile selection view.

=== Favorites ===
The "Favorites" tab shows profiles that the user has marked as favorites. To mark a profile as favorite, simply click the the star icon next to a profile's name. You will see it immediately appearing in the favorites list (sorted alphabetically). You can of course undo this action by simply pressing the star icon again to unmark the profile as favorite.

=== Recent ===
The "Recent" tab shows all available profiles, ordered by most recently used (at the top), to least recently used, excluding favorited profiles (which appear in the "Favorites" tab). When you click a profile anywhere in the selection view, it will be timestamped, and added to the top of the "Recent" tab.

=== Browser ===
To view the "Browser" tab, the user can click the expansion button on the right side to toggle the tab open or closed.
The "Browser" tab shows all available profiles (including favorites), but displays them exactly as your file browser would, including subfolders. The user can navigate through subfolders simply by clicking them.

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Login Dialog ==
[[File:UI_WinX_Login_Dialog.png|thumb|alt=Login Dialog|Login Dialog]]
The login dialog is opened by pressing the Login button. The dialog also opens automatically after selecting a profile.
The first time the user uses a single profile to connect to a service, he is asked whether the system should remeber login and password (for the user and profile). If the user selects yes, the login dialog will not appear again and the credentials are used immediately the next time he connects by using the profile. If the user selects no, he has to enter his credentials every time.

=== Offline Login ===
Every successfull online login is stored. The stored credentials are used for supporting offline logins.
{{Hint|You can access a local database without online connection (offline) when the credentials where used once to connect successfully to the online service.}}

=== Clear Cache ===
The clear cache feature (settings) deletes all the remembered credentilas (login and password) from the system.
{{Attention|Offline logins are not possible after clearing the cache until the user connected once at the online service.}}

== Team login {{Version/WinXSince|2.6.1}}==
[[File:UI_WinX_Team_Login_Button.png|thumb|alt=Team Login Button|Team Login Button]]
[[File:UI_WinX_Team_Login_Dialog.png|thumb|alt=Team Login Dialog|Team Login Dialog]]
Team login allows a group of users to login with a single device and perform tasks together as a team.
=== Team login button ===
{{Attention|This button is not available by default in the app, certain custom templates are needed for this. An example template can be downloaded {{FileLink|xaml_262_20170310_Team_Login_Button.zip|here}}.}}
=== Team login dialog ===
The team login dialog has the following parts:
# Profile selector to change profiles;
#Team member list (each member has a remove button at the right side);
# {{key press|+}} button to add members;
# {{key press|Login}} button;
# {{key press|Close}} button.
The same [[Login_View#Login_Dialog|login dialog]] shows up once the {{key press|+}} button is pressed and the members should enter their credentials one by one. Once all the members are successfully added, press the {{key press|Login}} button to login as a team.
{{Hint|All members in a team should login to the same service, namely using the same profile. Therefore, the profile selector will be disabled as long as the member list is not empty.}}

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

File:Profile browser expanded.png

2017-10-24T11:55:18Z

KVB:

Login View

2017-10-24T11:52:20Z

KVB: /* Profile selection */

For confidentiality reason, users are required to login before they have access to most of the {{UBIK}} features.

== Accessing login view ==
[[File:UI_WinX_Login_View.png|thumb|alt=Login View|Login View]]
The login view is displayed after starting the app. It is possible to access the login view from every where in the app by pressing the login icon in the top right corner and selecting "log out".

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Profile selection ==
[[File:Profile_browser.png|thumb|alt=Profile Browser (collapsed)|Profile Browser (collapsed)]]
The name of the currently selected profile is displayed on the top of the view. By default, the last used profile will be selected here.
It is possible to change the profile by pressing the Profile Button. The profile selection flyout will pop up, from which the user can select any profile (see the figure on the right).

To add custom profiles, you must add them under the app's RoamingState folder. You can also categorize your profiles using subfolders within this directory.
You will see 3 different tabs when opening the profile selection view.

=== Recent ===
The "Recent" tab shows all available profiles, ordered by most recently used (at the top), to least recently used. When you click a profile anywhere in the selection view, it will be timestamped, and added to the top of the "Recent" tab.

=== Favorites ===
The "Favorites" tab shows profiles that the user has marked as favorites. To mark a profile as favorite, simply click the the star icon next to the profile's name. You will see it immediately appearing in the favorites list (sorted alphabetically). You can of course undo this action by simply pressing the star icon again to unmark the profile as favorite.

=== Browser ===
The "Browser" tab shows all available profiles, but displays them exactly as your file browser would, including subfolders. The user can navigate through subfolders simply by clicking them.

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Login Dialog ==
[[File:UI_WinX_Login_Dialog.png|thumb|alt=Login Dialog|Login Dialog]]
The login dialog is opened by pressing the Login button. The dialog also opens automatically after selecting a profile.
The first time the user uses a single profile to connect to a service, he is asked whether the system should remeber login and password (for the user and profile). If the user selects yes, the login dialog will not appear again and the credentials are used immediately the next time he connects by using the profile. If the user selects no, he has to enter his credentials every time.

=== Offline Login ===
Every successfull online login is stored. The stored credentials are used for supporting offline logins.
{{Hint|You can access a local database without online connection (offline) when the credentials where used once to connect successfully to the online service.}}

=== Clear Cache ===
The clear cache feature (settings) deletes all the remembered credentilas (login and password) from the system.
{{Attention|Offline logins are not possible after clearing the cache until the user connected once at the online service.}}

== Team login {{Version/WinXSince|2.6.1}}==
[[File:UI_WinX_Team_Login_Button.png|thumb|alt=Team Login Button|Team Login Button]]
[[File:UI_WinX_Team_Login_Dialog.png|thumb|alt=Team Login Dialog|Team Login Dialog]]
Team login allows a group of users to login with a single device and perform tasks together as a team.
=== Team login button ===
{{Attention|This button is not available by default in the app, certain custom templates are needed for this. An example template can be downloaded {{FileLink|xaml_262_20170310_Team_Login_Button.zip|here}}.}}
=== Team login dialog ===
The team login dialog has the following parts:
# Profile selector to change profiles;
#Team member list (each member has a remove button at the right side);
# {{key press|+}} button to add members;
# {{key press|Login}} button;
# {{key press|Close}} button.
The same [[Login_View#Login_Dialog|login dialog]] shows up once the {{key press|+}} button is pressed and the members should enter their credentials one by one. Once all the members are successfully added, press the {{key press|Login}} button to login as a team.
{{Hint|All members in a team should login to the same service, namely using the same profile. Therefore, the profile selector will be disabled as long as the member list is not empty.}}

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

File:Profile browser.png

2017-10-24T11:51:31Z

KVB: KVB uploaded a new version of File:Profile browser.png

Login View

2017-10-23T14:30:12Z

KVB: /* Favorites */

For confidentiality reason, users are required to login before they have access to most of the {{UBIK}} features.

== Accessing login view ==
[[File:UI_WinX_Login_View.png|thumb|alt=Login View|Login View]]
The login view is displayed after starting the app. It is possible to access the login view from every where in the app by pressing the login icon in the top right corner and selecting "log out".

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Profile selection ==
[[File:Profile_browser.png|thumb|alt=Profile Browser|Profile Browser]]
The name of the currently selected profile is displayed on the top of the view. By default, the last used profile will be selected here.
It is possible to change the profile by pressing the Profile Button. The profile selection flyout will pop up, from which the user can select any profile (see the figure on the right).

To add custom profiles, you must add them under the app's RoamingState folder. You can also categorize your profiles using subfolders within this directory.
You will see 3 different tabs when opening the profile selection view.

=== Recent ===
The "Recent" tab shows all available profiles, ordered by most recently used (at the top), to least recently used. When you click a profile anywhere in the selection view, it will be timestamped, and added to the top of the "Recent" tab.

=== Favorites ===
The "Favorites" tab shows profiles that the user has marked as favorites. To mark a profile as favorite, simply click the the star icon next to the profile's name. You will see it immediately appearing in the favorites list (sorted alphabetically). You can of course undo this action by simply pressing the star icon again to unmark the profile as favorite.

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

=== Browser ===
The "Browser" tab shows all available profiles, but displays them exactly as your file browser would, including subfolders. The user can navigate through subfolders simply by clicking them.

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Login Dialog ==
[[File:UI_WinX_Login_Dialog.png|thumb|alt=Login Dialog|Login Dialog]]
The login dialog is opened by pressing the Login button. The dialog also opens automatically after selecting a profile.
The first time the user uses a single profile to connect to a service, he is asked whether the system should remeber login and password (for the user and profile). If the user selects yes, the login dialog will not appear again and the credentials are used immediately the next time he connects by using the profile. If the user selects no, he has to enter his credentials every time.

=== Offline Login ===
Every successfull online login is stored. The stored credentials are used for supporting offline logins.
{{Hint|You can access a local database without online connection (offline) when the credentials where used once to connect successfully to the online service.}}

=== Clear Cache ===
The clear cache feature (settings) deletes all the remembered credentilas (login and password) from the system.
{{Attention|Offline logins are not possible after clearing the cache until the user connected once at the online service.}}

== Team login {{Version/WinXSince|2.6.1}}==
[[File:UI_WinX_Team_Login_Button.png|thumb|alt=Team Login Button|Team Login Button]]
[[File:UI_WinX_Team_Login_Dialog.png|thumb|alt=Team Login Dialog|Team Login Dialog]]
Team login allows a group of users to login with a single device and perform tasks together as a team.
=== Team login button ===
{{Attention|This button is not available by default in the app, certain custom templates are needed for this. An example template can be downloaded {{FileLink|xaml_262_20170310_Team_Login_Button.zip|here}}.}}
=== Team login dialog ===
The team login dialog has the following parts:
# Profile selector to change profiles;
#Team member list (each member has a remove button at the right side);
# {{key press|+}} button to add members;
# {{key press|Login}} button;
# {{key press|Close}} button.
The same [[Login_View#Login_Dialog|login dialog]] shows up once the {{key press|+}} button is pressed and the members should enter their credentials one by one. Once all the members are successfully added, press the {{key press|Login}} button to login as a team.
{{Hint|All members in a team should login to the same service, namely using the same profile. Therefore, the profile selector will be disabled as long as the member list is not empty.}}

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

Login View

2017-10-23T14:22:35Z

KVB: /* Profile selection */

For confidentiality reason, users are required to login before they have access to most of the {{UBIK}} features.

== Accessing login view ==
[[File:UI_WinX_Login_View.png|thumb|alt=Login View|Login View]]
The login view is displayed after starting the app. It is possible to access the login view from every where in the app by pressing the login icon in the top right corner and selecting "log out".

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Profile selection ==
[[File:Profile_browser.png|thumb|alt=Profile Browser|Profile Browser]]
The name of the currently selected profile is displayed on the top of the view. By default, the last used profile will be selected here.
It is possible to change the profile by pressing the Profile Button. The profile selection flyout will pop up, from which the user can select any profile (see the figure on the right).

To add custom profiles, you must add them under the app's RoamingState folder. You can also categorize your profiles using subfolders within this directory.
You will see 3 different tabs when opening the profile selection view.

=== Recent ===
The "Recent" tab shows all available profiles, ordered by most recently used (at the top), to least recently used. When you click a profile anywhere in the selection view, it will be timestamped, and added to the top of the "Recent" tab.

=== Favorites ===
The "Favorites" tab shows profiles that the user has marked as favorites. To mark a profile as favorite, simply click the the star icon next to the profile's name. You will see it immediately appearing in the favorites list (sorted alphabetically).

=== Browser ===
The "Browser" tab shows all available profiles, but displays them exactly as your file browser would, including subfolders. The user can navigate through subfolders simply by clicking them.

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Login Dialog ==
[[File:UI_WinX_Login_Dialog.png|thumb|alt=Login Dialog|Login Dialog]]
The login dialog is opened by pressing the Login button. The dialog also opens automatically after selecting a profile.
The first time the user uses a single profile to connect to a service, he is asked whether the system should remeber login and password (for the user and profile). If the user selects yes, the login dialog will not appear again and the credentials are used immediately the next time he connects by using the profile. If the user selects no, he has to enter his credentials every time.

=== Offline Login ===
Every successfull online login is stored. The stored credentials are used for supporting offline logins.
{{Hint|You can access a local database without online connection (offline) when the credentials where used once to connect successfully to the online service.}}

=== Clear Cache ===
The clear cache feature (settings) deletes all the remembered credentilas (login and password) from the system.
{{Attention|Offline logins are not possible after clearing the cache until the user connected once at the online service.}}

== Team login {{Version/WinXSince|2.6.1}}==
[[File:UI_WinX_Team_Login_Button.png|thumb|alt=Team Login Button|Team Login Button]]
[[File:UI_WinX_Team_Login_Dialog.png|thumb|alt=Team Login Dialog|Team Login Dialog]]
Team login allows a group of users to login with a single device and perform tasks together as a team.
=== Team login button ===
{{Attention|This button is not available by default in the app, certain custom templates are needed for this. An example template can be downloaded {{FileLink|xaml_262_20170310_Team_Login_Button.zip|here}}.}}
=== Team login dialog ===
The team login dialog has the following parts:
# Profile selector to change profiles;
#Team member list (each member has a remove button at the right side);
# {{key press|+}} button to add members;
# {{key press|Login}} button;
# {{key press|Close}} button.
The same [[Login_View#Login_Dialog|login dialog]] shows up once the {{key press|+}} button is pressed and the members should enter their credentials one by one. Once all the members are successfully added, press the {{key press|Login}} button to login as a team.
{{Hint|All members in a team should login to the same service, namely using the same profile. Therefore, the profile selector will be disabled as long as the member list is not empty.}}

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

Login View

2017-10-23T13:19:16Z

KVB: /* Accessing login view */

Login View

2017-10-23T13:18:49Z

KVB:

Login View

2017-10-23T13:14:53Z

KVB: Undo revision 20419 by KVB (talk)

For confidentiality reason, users are required to login before they have access to most of the {{UBIK}} features.

== Accessing login view ==
[[File:Profile_browser.png.png|thumb|alt=Profile Browser|Profile Browser]]
The login view is displayed after starting the app. It is possible to access the login view from every where in the app by pressing the login icon in the top right corner and selecting "log out".

== Profile selection ==
The name of the currently selected profile is displayed on the top of the view.
It is possible to change the profile by pressing the Profile Button. A list of all available logins is presented to the user and he may select one of them. The default profile is marked with a star.

== Login Dialog ==
[[File:UI_WinX_Login_Dialog.png|thumb|alt=Login Dialog|Login Dialog]]
The login dialog is opened by pressing the Login button. The dialog also opens automatically after selecting a profile.
The first time the user uses a single profile to connect to a service, he is asked whether the system should remeber login and password (for the user and profile). If the user selects yes, the login dialog will not appear again and the credentials are used immediately the next time he connects by using the profile. If the user selects no, he has to enter his credentials every time.

=== Offline Login ===
Every successfull online login is stored. The stored credentials are used for supporting offline logins.
{{Hint|You can access a local database without online connection (offline) when the credentials where used once to connect successfully to the online service.}}

=== Clear Cache ===
The clear cache feature (settings) deletes all the remembered credentilas (login and password) from the system.
{{Attention|Offline logins are not possible after clearing the cache until the user connected once at the online service.}}

== Team login {{Version/WinXSince|2.6.1}}==
[[File:UI_WinX_Team_Login_Button.png|thumb|alt=Team Login Button|Team Login Button]]
[[File:UI_WinX_Team_Login_Dialog.png|thumb|alt=Team Login Dialog|Team Login Dialog]]
Team login allows a group of users to login with a single device and perform tasks together as a team.
=== Team login button ===
{{Attention|This button is not available by default in the app, certain custom templates are needed for this. An example template can be downloaded {{FileLink|xaml_262_20170310_Team_Login_Button.zip|here}}.}}
=== Team login dialog ===
The team login dialog has the following parts:
# Profile selector to change profiles;
#Team member list (each member has a remove button at the right side);
# {{key press|+}} button to add members;
# {{key press|Login}} button;
# {{key press|Close}} button.
The same [[Login_View#Login_Dialog|login dialog]] shows up once the {{key press|+}} button is pressed and the members should enter their credentials one by one. Once all the members are successfully added, press the {{key press|Login}} button to login as a team.
{{Hint|All members in a team should login to the same service, namely using the same profile. Therefore, the profile selector will be disabled as long as the member list is not empty.}}

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

Login View

2017-10-23T13:12:22Z

KVB: /* Accessing login view */

For confidentiality reason, users are required to login before they have access to most of the {{UBIK}} features.

== Accessing login view ==
[[File:Profile_browser.png|thumb|alt=Profile Browser|Profile Browser]]
The login view is displayed after starting the app. It is possible to access the login view from every where in the app by pressing the login icon in the top right corner and selecting "log out".

[[Category:Pages with broken file links|Login View]]
[[Category:WinX|Login View]]

== Profile selection ==
The name of the currently selected profile is displayed on the top of the view.
It is possible to change the profile by pressing the Profile Button. A list of all available logins is presented to the user and he may select one of them. The default profile is marked with a star.

== Login Dialog ==
[[File:UI_WinX_Login_Dialog.png|thumb|alt=Login Dialog|Login Dialog]]
The login dialog is opened by pressing the Login button. The dialog also opens automatically after selecting a profile.
The first time the user uses a single profile to connect to a service, he is asked whether the system should remeber login and password (for the user and profile). If the user selects yes, the login dialog will not appear again and the credentials are used immediately the next time he connects by using the profile. If the user selects no, he has to enter his credentials every time.

=== Offline Login ===
Every successfull online login is stored. The stored credentials are used for supporting offline logins.
{{Hint|You can access a local database without online connection (offline) when the credentials where used once to connect successfully to the online service.}}

=== Clear Cache ===
The clear cache feature (settings) deletes all the remembered credentilas (login and password) from the system.
{{Attention|Offline logins are not possible after clearing the cache until the user connected once at the online service.}}

== Team login {{Version/WinXSince|2.6.1}}==
[[File:UI_WinX_Team_Login_Button.png|thumb|alt=Team Login Button|Team Login Button]]
[[File:UI_WinX_Team_Login_Dialog.png|thumb|alt=Team Login Dialog|Team Login Dialog]]
Team login allows a group of users to login with a single device and perform tasks together as a team.
=== Team login button ===
{{Attention|This button is not available by default in the app, certain custom templates are needed for this. An example template can be downloaded {{FileLink|xaml_262_20170310_Team_Login_Button.zip|here}}.}}
=== Team login dialog ===
The team login dialog has the following parts:
# Profile selector to change profiles;
#Team member list (each member has a remove button at the right side);
# {{key press|+}} button to add members;
# {{key press|Login}} button;
# {{key press|Close}} button.
The same [[Login_View#Login_Dialog|login dialog]] shows up once the {{key press|+}} button is pressed and the members should enter their credentials one by one. Once all the members are successfully added, press the {{key press|Login}} button to login as a team.
{{Hint|All members in a team should login to the same service, namely using the same profile. Therefore, the profile selector will be disabled as long as the member list is not empty.}}

[[Category:WinX|Login View]]

Login View

2017-10-23T13:11:58Z

KVB: /* Accessing login view */

For confidentiality reason, users are required to login before they have access to most of the {{UBIK}} features.

== Accessing login view ==
[[File:Profile_browser.png.png|thumb|alt=Profile Browser|Profile Browser]]
The login view is displayed after starting the app. It is possible to access the login view from every where in the app by pressing the login icon in the top right corner and selecting "log out".

[[Category:WinX|Login View]]

== Profile selection ==
The name of the currently selected profile is displayed on the top of the view.
It is possible to change the profile by pressing the Profile Button. A list of all available logins is presented to the user and he may select one of them. The default profile is marked with a star.

== Login Dialog ==
[[File:UI_WinX_Login_Dialog.png|thumb|alt=Login Dialog|Login Dialog]]
The login dialog is opened by pressing the Login button. The dialog also opens automatically after selecting a profile.
The first time the user uses a single profile to connect to a service, he is asked whether the system should remeber login and password (for the user and profile). If the user selects yes, the login dialog will not appear again and the credentials are used immediately the next time he connects by using the profile. If the user selects no, he has to enter his credentials every time.

=== Offline Login ===
Every successfull online login is stored. The stored credentials are used for supporting offline logins.
{{Hint|You can access a local database without online connection (offline) when the credentials where used once to connect successfully to the online service.}}

=== Clear Cache ===
The clear cache feature (settings) deletes all the remembered credentilas (login and password) from the system.
{{Attention|Offline logins are not possible after clearing the cache until the user connected once at the online service.}}

== Team login {{Version/WinXSince|2.6.1}}==
[[File:UI_WinX_Team_Login_Button.png|thumb|alt=Team Login Button|Team Login Button]]
[[File:UI_WinX_Team_Login_Dialog.png|thumb|alt=Team Login Dialog|Team Login Dialog]]
Team login allows a group of users to login with a single device and perform tasks together as a team.
=== Team login button ===
{{Attention|This button is not available by default in the app, certain custom templates are needed for this. An example template can be downloaded {{FileLink|xaml_262_20170310_Team_Login_Button.zip|here}}.}}
=== Team login dialog ===
The team login dialog has the following parts:
# Profile selector to change profiles;
#Team member list (each member has a remove button at the right side);
# {{key press|+}} button to add members;
# {{key press|Login}} button;
# {{key press|Close}} button.
The same [[Login_View#Login_Dialog|login dialog]] shows up once the {{key press|+}} button is pressed and the members should enter their credentials one by one. Once all the members are successfully added, press the {{key press|Login}} button to login as a team.
{{Hint|All members in a team should login to the same service, namely using the same profile. Therefore, the profile selector will be disabled as long as the member list is not empty.}}

[[Category:WinX|Login View]]

File:Profile browser.png

2017-10-23T13:08:46Z

KVB: