https://wiki.augmensys.com/api.php?action=feedcontributions&feedformat=atom&user=LDOUBIK Wiki / Augmensys - User contributions [en]2026-10-08T01:36:13ZUser contributionsMediaWiki 1.24.2https://wiki.augmensys.com/index.php?title=HowTo:Set_Up_CUI_Rest_API&diff=30595HowTo:Set Up CUI Rest API2026-09-21T11:25:17Z<p>LDO: </p>
<hr />
<div>==Overview==<br />
<br />
The COMOS®-UBIK® Interface (CUI) is a standard data exchange function between the {{COMOS}} and {{UBIK}} systems. It provides bidirectional communication based on the COMOS Web REST API and the UBIK CUI Plugin (UBIK.Interface.CUI.dll).<br />
<br><br />
<br />
For {{COMOS}}, make sure that you have a working installation of {{COMOS}} and COMOS Web with access to its {{COMOS}} database. You also need the license called "COMOS_Mobile_Worker_Server".<br />
<br><br />
<br />
On the UBIK side, start by installing {{UBIK}}, the UBIK database, its Web Services, and the Enterprise Server(s).<br />
<br><br />
<br />
* [[HowTo:Install_UBIK_Studio]]<br />
* [[HowTo:Install_UBIK_Database]]<br />
* [[HowTo:Install_UBIK_Web_Service]]<br />
* [[Configure_Enterprise_Service_for_CUI]]<br />
<br><br />
<br />
After that, you have two possible ways to proceed:<br />
* Create a {{UBIK}} MetaClass structure manually <br />
* Import it from {{COMOS}}.<br />
<br><br />
If you want to export data from {{COMOS}}, the first step is to review, update, or create the required templates as described in the PDF document available for download below:<br />
<br><br />
<br />
[[:File:Admin_Comos_UBIK_Interface_2025_10_EN.pdf]]<br />
<br><br />
<br />
Once the template structure in COMOS includes all MetaClasses and properties required on the UBIK side, export these {{COMOS}} templates as meta information for {{UBIK}}.<br />
<br><br />
<br />
In the standard COMOS iDB, there is a module section called M67 for COMOS Mobile Worker (UBIK). For a standard MRO use case, predefined templates are available.<br />
<br><br />
<br />
These templates are connected to COMOS CDevices that use Functional Classification C270 (iDB). For cDB installations, Classification C2 is available.<br />
<br><br />
<br />
Before proceeding, make sure that the project settings for the CUI interface exist and are active. You can find them in the COMOS Project Settings.<br />
<br><br />
<br />
Also, make sure that the "Active" checkbox for the COMOS Mobile Worker Interface is selected.<br />
<br><br />
<br />
First, ensure that the interface is set to "Active" in the project settings of SO1 (or your selected working layer).<br />
<br><br />
<br />
[[File:Project_activation.png|400px]]<br />
<br><br />
<br />
Next, open the ComosBaseObject in SO1. It can be found in the iDB databases at "@30|M67|A50|A20|A10". Please ensure that the file path for the XML file exists.<br />
<br><br />
<br />
[[File:Export_from_Comos.png|400px]]<br />
<br><br />
<br />
To import the data into a {{UBIK}} database, use {{UBIK}} Smart Studio.<br />
<br><br />
<br />
* [[Smart_Modelling]]<br />
* [[Setting_Up_UBIK_for_CUI]]<br />
<br></div>LDOhttps://wiki.augmensys.com/index.php?title=Setting_Up_UBIK_for_CUI&diff=30594Setting Up UBIK for CUI2026-09-21T10:47:57Z<p>LDO: </p>
<hr />
<div>Setting up a UBIK Database for CUI Data Exchange<br />
{{Template:HowTo/Begin}}<br />
= Instructions =<br />
To set up an interface between COMOS and a UBIK database, you need the COMOS®-UBIK® Interface (CUI) plugin, which generates the following configuration MetaClasses during installation:<br><br />
• (COMOS_PROJECT) Comos Project<br />
• (COMOS_LOGIN) Comos Login<br />
• (INTERFACE_ADMIN_COMOS) Interface Admin Comos<br />
• (SYSREL_PROJECT_LANGUAGE) Comos Project &lt;-&gt; Language<br />
<br><br />
<br><br />
<br />
= Comos Project =<br />
The recommended approach is to navigate to the MetaClass COMOS_PROJECT and derive a new MetaClass.<br />
The reason for this is to create a MetaClass that is separated from the System MetaClass, which may be modified during a UBIK update.<br />
<br><br />
<br />
To find the MetaClass in {{UBIK}} when the View is set to "See All", go to ⇒ SYSROOT ⇒ SYSTEMOBJECT ⇒ COMOS_PROJECT<br />
<br><br />
<br />
When the View is set to "Content", you can find it under Namespaces; go to ⇒ {} Comos ⇒ {} Comos.Interface ⇒ COMOS_PROJECT<br />
<br><br />
<br />
[[File:ComosProject_ContentView.png|400px]]<br />
<br><br />
<br />
After assigning a name and description to the new MetaClass, click Save. You can then create your configuration by opening the MetaClass in the Bulk Editor and creating a new instance.<br />
<br><br />
<br />
You may choose any name and description, but it is recommended to use values that also exist in {{COMOS}}.<br />
<br><br />
<br />
The Database ID should match the value configured in {{COMOS}} under the project settings for Mobile Solutions.<br />
The Enterprise Server should be the one from {{UBIK}}, configured in the same way as the Notification Endpoint.<br />
<br><br />
<br />
DATABASE_ID is the COMOS Database ID, PROJECT_ID is the COMOS Project SystemUID, and WORKING_OVERLAY_ID is the COMOS Working Overlay SystemUID from {{COMOS}}.<br />
<br><br />
<br />
DATABASE_ID and PROJECT_ID are mandatory. If you want to connect to a specific Working Overlay in COMOS, the WORKING_OVERLAY_ID is also required.<br />
<br><br />
<br />
The Registration Folder is required only if you want to use XML files for objects that are not classified in {{COMOS}}.<br />
<br><br />
<br />
[[File:New_comos_project.png|400px]]<br />
<br><br />
<br><br />
<br />
= Comos Login =<br />
Similar to COMOS_PROJECT, navigate to the MetaClass COMOS_LOGIN and derive a new MetaClass.<br />
The reason for this is to create a MetaClass that is separated from the System MetaClass, which may be modified during a UBIK update.<br />
<br><br />
<br />
To find the MetaClass in {{UBIK}} when the View is set to "See All", go to ⇒ SYSROOT ⇒ SYSTEMOBJECT ⇒ SERVICE_LOGIN ⇒ BASICAUTH_SERVICE_LOGIN ⇒ COMOS_LOGIN<br />
<br><br />
<br />
When the View is set to "Content", you can find it under Namespaces; go to ⇒ {} Comos ⇒ {} Comos.Interface ⇒ COMOS_LOGIN<br />
<br><br />
<br />
[[File:ComosLogin_ContentView.png|400px]]<br />
<br><br />
<br />
After assigning a name and description to the new MetaClass, click Save. You can then create your configuration by opening the MetaClass in the Bulk Editor and creating a new instance.<br />
<br><br />
<br />
You may choose any name and description, but it is recommended to use values that also exist in {{COMOS}}.<br />
<br><br />
<br />
You must link an instance of COMOS_PROJECT or one of its derived classes. Link the instance that you previously created in your derived COMOS_PROJECT MetaClass.<br />
<br><br />
<br />
The checkbox "RESTAPI_PRE_AUTHENTICATE" determines whether {{UBIK}} authenticates before sending data. Enable it according to your system security requirements.<br />
<br><br />
<br />
In the Service URL field, enter the ComosWebstartPage URL. Also provide the username and password used for COMOS login (typically a domain user account).<br />
<br><br />
<br />
[[File:New_Login.png|400px]]<br />
<br><br />
<br />
= Interface Admin Comos =<br />
Similar to the previous steps, navigate to the MetaClass INTERFACE_ADMIN_COMOS and derive a new MetaClass.<br />
The reason for this is to create a MetaClass that is separated from the System MetaClass, which may be modified during a {{UBIK}} update.<br />
<br><br />
<br />
To find the MetaClass in {{UBIK}} when the View is set to "See All", go to ⇒ SYSROOT ⇒ INTERFACE_ADMIN_ROOT ⇒ INTERFACE_ADMIN_COMOS<br />
<br><br />
<br />
When the View is set to "Content", you can find it under Namespaces; go to ⇒ {} Comos ⇒ {} Comos.Interface ⇒ {} Comos.Interface.Administration ⇒ INTERFACE_ADMIN_COMOS<br />
<br><br />
<br />
[[File:IA_COMOS_ContentView.png|400px]]<br />
<br><br />
<br />
After assigning a name and description to the new MetaClass, do not forget to link the Login object and then save it.<br />
<br><br />
<br />
[[File:IA_CMW_LINK.png|400px]]<br />
<br><br />
<br />
To configure the proxies that should be imported and exported, open the new Interface Admin object in the Relation Editor.<br />
<br><br />
<br />
Then drag and drop all relevant proxies onto the Interface Admin MetaClass.<br />
<br><br />
<br />
[[File:IA_RELATIONS.png|800px]]<br />
<br><br />
<br><br />
<br />
= Relation between Comos Project and Language =<br />
Unlike the previous examples, the RelationalClass SYSREL_PROJECT_LANGUAGE remains a System MetaClass and should not be derived.<br />
<br><br />
<br />
To find the MetaClass in {{UBIK}} when the View is set to "See All", go to ⇒ RELATIONDATA ⇒ SYSREL_PROJECT_LANGUAGE<br />
<br><br />
<br />
When the View is set to "Content", you can find it under Namespaces; go to ⇒ {} Comos ⇒ {} Comos.Interface ⇒ SYSREL_PROJECT_LANGUAGE<br />
<br><br />
<br />
[[File:Lang_REL_ContentView.png|400px]]<br />
<br><br />
<br />
Please open the class in the Bulk Editor.<br />
<br><br />
<br />
[[File:REL_OVERVIEW.png|1200px]]<br />
<br><br />
<br />
To create a new instance, assign a COMOS_PROJECT instance to LEFTUID and a Language object to RIGHTUID.<br />
<br><br />
<br />
Add the Microsoft LCID number for the language. Also configure the COMOS language settings to specify whether the language is the current project language and the user's default language.<br />
<br><br />
<br />
The language objects in {{UBIK}} can be found as follows:<br />
<br><br />
<br />
When the View is set to "See All", go to ⇒ SYSROOT ⇒ SYSTEM ⇒ LANGUAGE<br />
<br><br />
<br />
When the View is set to "Content", go to ⇒ {} System ⇒ {} System.Main ⇒ {} System.Main.Language ⇒ LANGUAGE ⇒ {} System<br />
<br><br />
{{Template:HowTo/End}}<br />
<br />
==See also==<br />
* [[HowTo:Add_Languages_to_UBIK]]<br />
* [https://cldr.unicode.org/ Unicode CLDR Project]<br />
* [https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/70feba9f-294e-491e-b6eb-56532684c37f Microsoft LCID]</div>LDOhttps://wiki.augmensys.com/index.php?title=Setting_Up_UBIK_for_CUI&diff=30593Setting Up UBIK for CUI2026-09-21T10:43:39Z<p>LDO: </p>
<hr />
<div>Setting up a UBIK Database for CUI Data Exchange<br />
{{Template:HowTo/Begin}}<br />
= Instructions =<br />
To set up an interface between COMOS and a UBIK database, you need the COMOS®-UBIK® Interface (CUI) plugin and the automatically created configuration MetaClasses:<br />
<br><br />
• (COMOS_PROJECT) Comos Project<br />
• (COMOS_LOGIN) Comos Login<br />
• (INTERFACE_ADMIN_COMOS) Interface Admin Comos<br />
• (SYSREL_PROJECT_LANGUAGE) Comos Project &lt;-&gt; Language<br />
<br><br />
<br><br />
<br />
= Comos Project =<br />
The recommended approach is to navigate to the MetaClass COMOS_PROJECT and derive a new MetaClass.<br />
The reason for this is to create a MetaClass that is separated from the System MetaClass, which may be modified during a UBIK update.<br />
<br><br />
<br />
To find the MetaClass in {{UBIK}} when the View is set to "See All", go to ⇒ SYSROOT ⇒ SYSTEMOBJECT ⇒ COMOS_PROJECT<br />
<br><br />
<br />
When the View is set to "Content", you can find it under Namespaces; go to ⇒ {} Comos ⇒ {} Comos.Interface ⇒ COMOS_PROJECT<br />
<br><br />
<br />
[[File:ComosProject_ContentView.png|400px]]<br />
<br><br />
<br />
After assigning a name and description to the new MetaClass, click Save. You can then create your configuration by opening the MetaClass in the Bulk Editor and creating a new instance.<br />
<br><br />
<br />
You may choose any name and description, but it is recommended to use values that also exist in {{COMOS}}.<br />
<br><br />
<br />
The Database ID should match the value configured in {{COMOS}} under the project settings for Mobile Solutions.<br />
The Enterprise Server should be the one from {{UBIK}}, configured in the same way as the Notification Endpoint.<br />
<br><br />
<br />
DATABASE_ID is the COMOS Database ID, PROJECT_ID is the COMOS Project SystemUID, and WORKING_OVERLAY_ID is the COMOS Working Overlay SystemUID from {{COMOS}}.<br />
<br><br />
<br />
DATABASE_ID and PROJECT_ID are mandatory. If you want to connect to a specific Working Overlay in COMOS, the WORKING_OVERLAY_ID is also required.<br />
<br><br />
<br />
The Registration Folder is required only if you want to use XML files for objects that are not classified in {{COMOS}}.<br />
<br><br />
<br />
[[File:New_comos_project.png|400px]]<br />
<br><br />
<br><br />
<br />
= Comos Login =<br />
Similar to COMOS_PROJECT, navigate to the MetaClass COMOS_LOGIN and derive a new MetaClass.<br />
The reason for this is to create a MetaClass that is separated from the System MetaClass, which may be modified during a UBIK update.<br />
<br><br />
<br />
To find the MetaClass in {{UBIK}} when the View is set to "See All", go to ⇒ SYSROOT ⇒ SYSTEMOBJECT ⇒ SERVICE_LOGIN ⇒ BASICAUTH_SERVICE_LOGIN ⇒ COMOS_LOGIN<br />
<br><br />
<br />
When the View is set to "Content", you can find it under Namespaces; go to ⇒ {} Comos ⇒ {} Comos.Interface ⇒ COMOS_LOGIN<br />
<br><br />
<br />
[[File:ComosLogin_ContentView.png|400px]]<br />
<br><br />
<br />
After assigning a name and description to the new MetaClass, click Save. You can then create your configuration by opening the MetaClass in the Bulk Editor and creating a new instance.<br />
<br><br />
<br />
You may choose any name and description, but it is recommended to use values that also exist in {{COMOS}}.<br />
<br><br />
<br />
You must link an instance of COMOS_PROJECT or one of its derived classes. Link the instance that you previously created in your derived COMOS_PROJECT MetaClass.<br />
<br><br />
<br />
The checkbox "RESTAPI_PRE_AUTHENTICATE" determines whether {{UBIK}} authenticates before sending data. Enable it according to your system security requirements.<br />
<br><br />
<br />
In the Service URL field, enter the ComosWebstartPage URL. Also provide the username and password used for COMOS login (typically a domain user account).<br />
<br><br />
<br />
[[File:New_Login.png|400px]]<br />
<br><br />
<br />
= Interface Admin Comos =<br />
Similar to the previous steps, navigate to the MetaClass INTERFACE_ADMIN_COMOS and derive a new MetaClass.<br />
The reason for this is to create a MetaClass that is separated from the System MetaClass, which may be modified during a {{UBIK}} update.<br />
<br><br />
<br />
To find the MetaClass in {{UBIK}} when the View is set to "See All", go to ⇒ SYSROOT ⇒ INTERFACE_ADMIN_ROOT ⇒ INTERFACE_ADMIN_COMOS<br />
<br><br />
<br />
When the View is set to "Content", you can find it under Namespaces; go to ⇒ {} Comos ⇒ {} Comos.Interface ⇒ {} Comos.Interface.Administration ⇒ INTERFACE_ADMIN_COMOS<br />
<br><br />
<br />
[[File:IA_COMOS_ContentView.png|400px]]<br />
<br><br />
<br />
After assigning a name and description to the new MetaClass, do not forget to link the Login object and then save it.<br />
<br><br />
<br />
[[File:IA_CMW_LINK.png|400px]]<br />
<br><br />
<br />
To configure the proxies that should be imported and exported, open the new Interface Admin object in the Relation Editor.<br />
<br><br />
<br />
Then drag and drop all relevant proxies onto the Interface Admin MetaClass.<br />
<br><br />
<br />
[[File:IA_RELATIONS.png|800px]]<br />
<br><br />
<br><br />
<br />
= Relation between Comos Project and Language =<br />
Unlike the previous examples, the RelationalClass SYSREL_PROJECT_LANGUAGE remains a System MetaClass and should not be derived.<br />
<br><br />
<br />
To find the MetaClass in {{UBIK}} when the View is set to "See All", go to ⇒ RELATIONDATA ⇒ SYSREL_PROJECT_LANGUAGE<br />
<br><br />
<br />
When the View is set to "Content", you can find it under Namespaces; go to ⇒ {} Comos ⇒ {} Comos.Interface ⇒ SYSREL_PROJECT_LANGUAGE<br />
<br><br />
<br />
[[File:Lang_REL_ContentView.png|400px]]<br />
<br><br />
<br />
Please open the class in the Bulk Editor.<br />
<br><br />
<br />
[[File:REL_OVERVIEW.png|1200px]]<br />
<br><br />
<br />
To create a new instance, assign a COMOS_PROJECT instance to LEFTUID and a Language object to RIGHTUID.<br />
<br><br />
<br />
Add the Microsoft LCID number for the language. Also configure the COMOS language settings to specify whether the language is the current project language and the user's default language.<br />
<br><br />
<br />
The language objects in {{UBIK}} can be found as follows:<br />
<br><br />
<br />
When the View is set to "See All", go to ⇒ SYSROOT ⇒ SYSTEM ⇒ LANGUAGE<br />
<br><br />
<br />
When the View is set to "Content", go to ⇒ {} System ⇒ {} System.Main ⇒ {} System.Main.Language ⇒ LANGUAGE ⇒ {} System<br />
<br><br />
{{Template:HowTo/End}}<br />
<br />
==See also==<br />
* [[HowTo:Add_Languages_to_UBIK]]<br />
* [https://cldr.unicode.org/ Unicode CLDR Project]<br />
* [https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/70feba9f-294e-491e-b6eb-56532684c37f Microsoft LCID]</div>LDOhttps://wiki.augmensys.com/index.php?title=Setting_Up_UBIK_for_CUI&diff=30592Setting Up UBIK for CUI2026-09-21T10:21:12Z<p>LDO: </p>
<hr />
<div>Setting up a UBIK Database for CUI Data Exchange<br />
{{Template:HowTo/Begin}}<br />
= Instructions =<br />
To set up interfacing in a UBIK database you need the following configuration MetaClasses:<br />
<br />
• (COMOS_PROJECT) Comos Project<br />
• (COMOS_LOGIN) Comos Login<br />
• (INTERFACE_ADMIN_COMOS) Interface Admin Comos<br />
• (SYSREL_PROJECT_LANGUAGE) Comos Project <-> Language<br />
<br />
<br />
= Comos Project =<br />
The best approach is to go to the MetaClass COMOS_PROJECT and derive a new Metaclass.<br />
The reason is to create a MetaClass that is cut off from this SystemMetaClass, which could be changed during a UBIK update.<br />
<br />
To find the MetaClass in {{UBIK}} where View set to „See all“ go to ⇒ SYSROOT ⇒ SYSTEMOBJECT ⇒ COMOS_PROJECT<br />
<br />
when View is set to „Content“ you can find it under Namespaces; go to ⇒ {} Comos ⇒ {} Comos.Interface ⇒ COMOS_PROJECT<br />
<br />
[[File:ComosProject_ContentView.png|400px]]<br />
<br />
After assigning a name and description to the new MetaClass, please Save; then you can generate your setting <br />
by opening the MetaClass in a Bulk Editor and create a new Instance. <br />
<br />
You can name and describe it as desired, but it is a good idea to use a name or description that is also in {{COMOS}}.<br />
<br />
The Database ID is also the same as in {{COMOS}}, on the Project settings for Mobile Solutions, <br />
the Enterprise Server here is that one from {{UBIK}} like you set up the Notification Endpoint. <br />
<br />
DATABASE_ID Comos Database ID, PROJECT_ID Comos Project SystemUID, WORKING_OVERLAY_ID Comos Working Overlay SystemUID is again form {{COMOS}}, <br />
DATABASE_ID ad PROJECT_ID are Mandatory anyway, if you want to connect with an WorkingOverly from Comos this ID is also needed. <br />
<br />
The Registration folder is only needed when you want to use XML Files for Objects that are not Classified in {{COMOS}}.<br />
<br />
[[File:New_comos_project.png|400px]]<br />
<br />
<br />
= Comos Login =<br />
Similar to COMOS_PROJECT go to MetaClass COMOS_LOGIN and derive a new Metaclass.<br />
The reason is to create a MetaClass that is cut off from this SystemMetaClass, which could be changed during a UBIK update.<br />
<br />
To find the MetaClass in {{UBIK}} where View set to „See all“ go to ⇒ SYSROOT ⇒ SYSTEMOBJECT ⇒ SERVICE_LOGIN ⇒ BASICAUTH_SERVICE_LOGIN ⇒ COMOS_LOGIN<br />
<br />
when View is set to „Content“ you can find it under Namespaces; go to ⇒ {} Comos ⇒ {} Comos.Interface ⇒ COMOS_LOGIN<br />
<br />
[[File:ComosLogin_ContentView.png|400px]]<br />
<br />
After assigning a name and description to the new MetaClass, please Save; then you can generate you setting by opening the MetaClass in a Bulk Editor and create a new Instance. <br />
<br />
You can name and describe it as desired, but it is a good idea to use a name or description that is also in {{COMOS}}.<br />
<br />
You have to link an instance from COMOS_PROJECT or its children, so link here the Instance you created befor in the new Created COMOS_PROJECT Child Class, <br />
<br />
with the checkbox "RESTAPI_PRE_AUTHENTICATE" you ask {{UBIK}} authenticates before sending data, depending on your system security requirements. <br />
<br />
In Service URL you musst set the ComosWebstartPage URL, and user name and password for COMOS login (mostly Domain user)<br />
<br />
[[File:New_Login.png|400px]]<br />
<br />
= Interface Admin Comos =<br />
Similar to the previous steps go to MetaClass INTERFACE_ADMIN_COMOS and derive a new Metaclass. <br />
The reason is to create a MetaClass that is cut off from this SystemMetaClass, which could be changed during a {{UBIK}} update.<br />
<br />
To find the MetaClass in {{UBIK}} where View set to „See all“ go to ⇒ SYSROOT ⇒ INTERFACE_ADMIN_ROOT ⇒ INTERFACE_ADMIN_COMOS<br />
<br />
when View is set to „Content“ you can find it under Namespaces; go to ⇒ {} Comos ⇒ {} Comos.Interface ⇒ {} Comos.Interface.Administration ⇒ INTERFACE_ADMIN_COMOS<br />
<br />
[[File:IA_COMOS_ContentView.png|400px]]<br />
<br />
After assigning a name and description to the new MetaClass, don't forget to link the Login object, then save;<br />
<br />
[[File:IA_CMW_LINK.png|400px]]<br />
<br />
To configure the Proxies that should be imported and exported please open the new InterfaceAdmin in a RelationEditor. <br />
<br />
Then drag an drop all the relevant Proxy to the InterfaceAdmin MetaClass.<br />
<br />
[[File:IA_RELATIONS.png|800px]]<br />
<br />
<br />
= Relation between Comos Project and Language =<br />
Different to before RelationalClass SYSREL_PROJECT_LANGUAGE stays the SystemMetaClass.<br />
<br />
To find the MetaClass in {{UBIK}} where View set to „See all“ go to ⇒ RELATIONDATA ⇒ SYSREL_PROJECT_LANGUAGE<br />
<br />
when View is set to „Content“ you can find it under Namespaces; go to ⇒ {} Comos ⇒ {} Comos.Interface ⇒ SYSREL_PROJECT_LANGUAGE<br />
<br />
[[File:Lang_REL_ContentView.png|400px]]<br />
<br />
Please open the Class in a Bulk Editor;<br />
<br />
[[File:REL_OVERVIEW.png|1200px]]<br />
<br />
To Create a new Instance set a COMOS_PROJECT Instance to LEFTUID and a Language Object to the RIGHTUID.<br />
<br />
Add the Microsoft LCID number for your Language. And also the Comos settings witch Language is the current Project, and User Default. <br />
The languages from {{UBIK}} you find in <br />
<br />
To find the MetaClass in {{UBIK}} where View set to „See all“ go to ⇒ SYSROOT ⇒ INTERFACE_ADMIN_ROOT ⇒ INTERFACE_ADMIN_COMOS <br />
<br />
when View is set to „Content“ you can find it under Namespaces; go to ⇒ {} System ⇒ {} System.Main ⇒ {} System.Main.Language ⇒ LANGUAGE ⇒ {} System<br />
<br />
{{Template:HowTo/End}}<br />
<br />
==See also==<br />
* [[HowTo:Add_Languages_to_UBIK]]<br />
* [https://cldr.unicode.org/ Unicode CLDR Project]<br />
* [https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-lcid/70feba9f-294e-491e-b6eb-56532684c37f Microsoft LCID]</div>LDOhttps://wiki.augmensys.com/index.php?title=HowTo:Set_Up_CUI_Rest_API&diff=30577HowTo:Set Up CUI Rest API2026-09-07T14:32:31Z<p>LDO: </p>
<hr />
<div>==Overview==<br />
<br />
The COMOS®-UBIK® Interface (CUI) is a standard data exchange function between the {{COMOS}} and {{UBIK}} systems. It provides bidirectional communication based on the COMOS Web REST API and the UBIK CUI Plugin (UBIK.Interface.CUI.dll).<br />
<br><br />
<br />
For {{COMOS}}, make sure that you have a working installation of {{COMOS}} and COMOS Web with access to its {{COMOS}} database. You also need the license called "COMOS_Mobile_Worker_Server".<br />
<br><br />
<br />
On the UBIK side, start by installing {{UBIK}}, the UBIK database, its Web Services, and the Enterprise Server(s).<br />
<br><br />
<br />
* [[HowTo:Install_UBIK_Studio]]<br />
* [[HowTo:Install_UBIK_Database]]<br />
* [[HowTo:Install_UBIK_Web_Service]]<br />
* [[Configure_Enterprise_Service_for_CUI]]<br />
<br><br />
<br />
After that, you have two possible ways to proceed:<br />
* Create a {{UBIK}} MetaClass structure manually <br />
* Import it from {{COMOS}}.<br />
<br><br />
<br />
If you want to export data from {{COMOS}}, the first step is to review, update, or create the required templates as described in the PDF document available for download below:<br />
<br><br />
<br />
[[:File:Admin_Comos_UBIK_Interface_2025_10_EN.pdf]]<br />
<br><br />
<br />
Once the template structure in COMOS includes all MetaClasses and properties required on the UBIK side, export these {{COMOS}} templates as meta information for {{UBIK}}.<br />
<br><br />
<br />
In the standard COMOS iDB, there is a module section called M67 for COMOS Mobile Worker (UBIK). For a standard MRO use case, predefined templates are available.<br />
<br><br />
<br />
These templates are connected to COMOS CDevices that use Functional Classification C270 (iDB). For cDB installations, Classification C2 is available.<br />
<br><br />
<br />
Before proceeding, make sure that the project settings for the CUI interface exist and are active. You can find them in the COMOS Project Settings.<br />
<br><br />
<br />
Also, make sure that the "Active" checkbox for the COMOS Mobile Worker Interface is selected.<br />
<br><br />
<br />
First, ensure that the interface is set to "Active" in the project settings of SO1 (or your selected working layer).<br />
<br><br />
<br />
[[File:Project_activation.png|400px]]<br />
<br><br />
<br />
Next, open the ComosBaseObject in SO1. It can be found in the iDB databases at "@30|M67|A50|A20|A10". Please ensure that the file path for the XML file exists.<br />
<br><br />
<br />
[[File:Export_from_Comos.png|400px]]<br />
<br><br />
<br />
To import the data into a {{UBIK}} database, use {{UBIK}} Smart Studio.<br />
<br><br />
<br />
* [[Smart_Modelling]]<br />
* [[Setting_Up_UBIK_for_CUI]]<br />
<br></div>LDOhttps://wiki.augmensys.com/index.php?title=Configure_Comos_for_CUI&diff=30576Configure Comos for CUI2026-09-07T14:31:49Z<p>LDO: </p>
<hr />
<div>[[File:Wiki_Under_Construction_Start.PNG|1000px]]<noinclude><br />
<br />
To run or extend the COMOS®-UBIK® Interface (CUI), you must configure certain settings on the {{COMOS}} side or, at a minimum, obtain configuration data from {{COMOS}}.<br />
<br />
As {{COMOS}} is not an Augmensys product, please contact your local Siemens representative or Siemens partner for any {{COMOS}} changes or adaptations.<br />
<br />
<!-- DO NOT REMOVE THIS -->{{Template:HowTo/Begin}}<!-- DO NOT REMOVE THIS --><br />
<br />
= Idea and Concept =<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
The integration of {{COMOS}} and {{UBIK}} depends on three key aspects:<br />
<br />
* The data structures available in {{COMOS}}<br />
* The mechanism used to exchange data between {{COMOS}} and {{UBIK}}, for example through XML files or a REST API<br />
* How the transferred data is processed within {{UBIK}}<br />
<br />
To transfer the primary information required from {{COMOS}} to {{UBIK}}, only *.xml files can be used. This is because the {{COMOS}} side writes the data to a fixed *.xml schema that {{UBIK}} can read and import.<br />
<br />
This process is called metadata transfer. It transfers information about CDevices, Attributes, StandardTables, PhysicalUnits, and DocumentTypes from {{COMOS}} to an *.xml file.<br />
<br />
When imported into {{UBIK}} SmartStudio, the metadata is converted into the corresponding {{UBIK}} structures. These include:<br />
* ComosMetaProxies and their corresponding MetaClasses<br />
* ComosMetaProxyProperties and their corresponding MetaProperties<br />
* SelectiveLists and SelectiveItems<br />
* SIUnits and UnitItems<br />
* ComosDocumentTypeProxies<br />
<br />
For detailed information about the {{UBIK}} MetaClass, please see:<br />
<br><br />
<br />
* [[MetaProxy]]<br />
* [[MetaClass]]<br />
* [[SELECTIVELIST]]<br />
* [[SELECTIVEITEM]]<br />
* [[UNIT]]<br />
<br />
= Comos =<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
<br />
Using or extending the COMOS®-UBIK® Interface (CUI) requires specific configuration information from COMOS®. This information must either be configured on the COMOS® side or made available by the COMOS® administrator.<br />
<br />
COMOS Web requires the following web services:<br />
<br />
* ComosEvents<br />
* ComosGatewayServices<br />
* ComosWebStartPage<br />
<br />
[[File:Screenshot 2026-08-13 091304.png]]<br />
<br />
In the {{COMOS}} project settings, under the "Mobile Solutions" section, ensure that the URL of your ComosWebStartPage (including the port number) is configured correctly. Also, make sure that the COMOS Web database key is configured.<br />
<br />
[[File:Screenshot 2026-08-13 093803.png]]<br />
<br />
Note: Within a single domain, the database key must be unique.<br />
<br />
In the "COMOS Mobile Worker Interface" section of the project settings, you will find the configuration values for the active COMOS project. If the WorkingLayer key is empty, the released area is connected. Otherwise, a specific WorkingLayer can be connected to UBIK® for each project.<br />
<br />
[[File:Screenshot 2026-08-13 094922.png|1000px]]<br />
<br />
= UBIK =<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
<br />
[[HowTo:Set_Up_CUI_Rest_API]]<br />
<br />
<!-- DO NOT REMOVE THIS -->{{Template:HowTo/End}}<!-- DO NOT REMOVE THIS --><br />
<br />
==See also==<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
<br />
For more detailed information please check your {{COMOS}} documentation for "Guide COMOS Mobile Worker"<br />
<br />
or ask Siemens: [https://www.siemens.com/en-us/products/comos/mobile-worker/ comos-mobile-worker]</div>LDOhttps://wiki.augmensys.com/index.php?title=HowTo:Set_Up_CUI_Rest_API&diff=30575HowTo:Set Up CUI Rest API2026-09-07T13:58:53Z<p>LDO: </p>
<hr />
<div>==Overview==<br />
<br />
The CUI -> "{{COMOS}} {{UBIK}} Interface" is a standard data exchange function between the {{COMOS}} and {{UBIK}} systems. It provides bidirectional communication based on the COMOS Web REST API and the UBIK CUI Plugin (UBIK.Interface.CUI.dll).<br />
<br><br />
<br />
For {{COMOS}}, make sure that you have a working installation of {{COMOS}} and COMOS Web with access to its {{COMOS}} database. You also need the license called "COMOS_Mobile_Worker_Server".<br />
<br><br />
<br />
On the UBIK side, start by installing {{UBIK}}, the UBIK database, its Web Services, and the Enterprise Server(s).<br />
<br><br />
<br />
* [[HowTo:Install_UBIK_Studio]]<br />
* [[HowTo:Install_UBIK_Database]]<br />
* [[HowTo:Install_UBIK_Web_Service]]<br />
* [[Configure_Enterprise_Service_for_CUI]]<br />
<br><br />
<br />
After that, you have two possible ways to proceed:<br />
* Create a {{UBIK}} MetaClass structure manually <br />
* Import it from {{COMOS}}.<br />
<br><br />
<br />
If you want to export data from {{COMOS}}, the first step is to review, update, or create the required templates as described in the PDF document available for download below:<br />
<br><br />
<br />
[[:File:Admin_Comos_UBIK_Interface_2025_10_EN.pdf]]<br />
<br><br />
<br />
Once the template structure in COMOS includes all MetaClasses and properties required on the UBIK side, export these {{COMOS}} templates as meta information for {{UBIK}}.<br />
<br><br />
<br />
In the standard COMOS iDB, there is a module section called M67 for COMOS Mobile Worker (UBIK). For a standard MRO use case, predefined templates are available.<br />
<br><br />
<br />
These templates are connected to COMOS CDevices that use Functional Classification C270 (iDB). For cDB installations, Classification C2 is available.<br />
<br><br />
<br />
Before proceeding, make sure that the project settings for the CUI interface exist and are active. You can find them in the COMOS Project Settings.<br />
<br><br />
<br />
Also, make sure that the "Active" checkbox for the COMOS Mobile Worker Interface is selected.<br />
<br><br />
<br />
First, ensure that the interface is set to "Active" in the project settings of SO1 (or your selected working layer).<br />
<br><br />
<br />
[[File:Project_activation.png|400px]]<br />
<br><br />
<br />
Next, open the ComosBaseObject in SO1. It can be found in the iDB databases at "@30|M67|A50|A20|A10". Please ensure that the file path for the XML file exists.<br />
<br><br />
<br />
[[File:Export_from_Comos.png|400px]]<br />
<br><br />
<br />
To import the data into a {{UBIK}} database, use {{UBIK}} Smart Studio.<br />
<br><br />
<br />
* [[Smart_Modelling]]<br />
* [[Setting_Up_UBIK_for_CUI]]<br />
<br></div>LDOhttps://wiki.augmensys.com/index.php?title=HowTo:Set_Up_CUI_Rest_API&diff=30574HowTo:Set Up CUI Rest API2026-09-07T13:57:02Z<p>LDO: </p>
<hr />
<div>==Overview==<br />
<br />
The CUI -> "{{COMOS}} {{UBIK}} Interface" is a standard data exchange function between the {{COMOS}} and {{UBIK}} systems. It provides bidirectional communication based on the COMOS Web REST API and the UBIK CUI Plugin (UBIK.Interface.CUI.dll).<br />
<br><br />
<br />
For {{COMOS}}, make sure that you have a working installation of {{COMOS}} and COMOS Web with access to its {{COMOS}} database. You also need the license called "COMOS_Mobile_Worker_Server".<br />
<br><br />
<br />
On the UBIK side, start by installing {{UBIK}}, the UBIK database, its Web Services, and the Enterprise Server(s).<br />
<br><br />
<br />
* [[HowTo:Install_UBIK_Studio]]<br />
* [[HowTo:Install_UBIK_Database]]<br />
* [[HowTo:Install_UBIK_Web_Service]]<br />
* [[Configure_Enterprise_Service_for_CUI]]<br />
<br><br />
<br />
After that, you have two possible ways to proceed:<br />
* Create a {{UBIK}} MetaClass structure manually <br />
* Import it from {{COMOS}}.<br />
<br><br />
<br />
If you want to export from {{COMOS}}, the first step is to check, update, or create templates as described in the following PDF:<br />
<br><br />
<br />
[[:File:Admin_Comos_UBIK_Interface_2025_10_EN.pdf]]<br />
<br><br />
<br />
Once the template structure in COMOS includes all MetaClasses and properties required on the UBIK side, export these {{COMOS}} templates as meta information for {{UBIK}}.<br />
<br><br />
<br />
In the standard COMOS iDB, there is a module section called M67 for COMOS Mobile Worker (UBIK). For a standard MRO use case, predefined templates are available.<br />
<br><br />
<br />
These templates are connected to COMOS CDevices that use Functional Classification C270 (iDB). For cDB installations, Classification C2 is available.<br />
<br><br />
<br />
Before proceeding, make sure that the project settings for the CUI interface exist and are active. You can find them in the COMOS Project Settings.<br />
<br><br />
<br />
Also, make sure that the "Active" checkbox for the COMOS Mobile Worker Interface is selected.<br />
<br><br />
<br />
First, ensure that the interface is set to "Active" in the project settings of SO1 (or your selected working layer).<br />
<br><br />
<br />
[[File:Project_activation.png|400px]]<br />
<br><br />
<br />
Next, open the ComosBaseObject in SO1. It can be found in the iDB databases at "@30|M67|A50|A20|A10". Please ensure that the file path for the XML file exists.<br />
<br><br />
<br />
[[File:Export_from_Comos.png|400px]]<br />
<br><br />
<br />
To import the data into a {{UBIK}} database, use {{UBIK}} Smart Studio.<br />
<br><br />
<br />
* [[Smart_Modelling]]<br />
* [[Setting_Up_UBIK_for_CUI]]<br />
<br></div>LDOhttps://wiki.augmensys.com/index.php?title=Configure_Comos_for_CUI&diff=30573Configure Comos for CUI2026-09-07T13:19:49Z<p>LDO: </p>
<hr />
<div>[[File:Wiki_Under_Construction_Start.PNG|1000px]]<noinclude><br />
<br />
To run or extend the {{COMOS}} – {{UBIK}} Interface => CUI, you must configure certain settings on the {{COMOS}} side or, at a minimum, obtain configuration data from {{COMOS}}.<br />
<br />
As {{COMOS}} is not an Augmensys product, please contact your local Siemens representative or Siemens partner for any {{COMOS}} changes or adaptations.<br />
<br />
<!-- DO NOT REMOVE THIS -->{{Template:HowTo/Begin}}<!-- DO NOT REMOVE THIS --><br />
<br />
= Idea and Concept =<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
The integration of {{COMOS}} and {{UBIK}} depends on three key aspects:<br />
<br />
* The data structures available in {{COMOS}}<br />
* The mechanism used to exchange data between {{COMOS}} and {{UBIK}}, for example through XML files or a REST API<br />
* How the transferred data is processed within {{UBIK}}<br />
<br />
To transfer the primary information required from {{COMOS}} to {{UBIK}}, only *.xml files can be used. This is because the {{COMOS}} side writes the data to a fixed *.xml schema that {{UBIK}} can read and import.<br />
<br />
This process is called metadata transfer. It transfers information about CDevices, Attributes, StandardTables, PhysicalUnits, and DocumentTypes from {{COMOS}} to an *.xml file.<br />
<br />
When imported into {{UBIK}} SmartStudio, the metadata is converted into the corresponding {{UBIK}} structures. These include:<br />
* ComosMetaProxies and their corresponding MetaClasses<br />
* ComosMetaProxyProperties and their corresponding MetaProperties<br />
* SelectiveLists and SelectiveItems<br />
* SIUnits and UnitItems<br />
* ComosDocumentTypeProxies<br />
<br />
For detailed information about the {{UBIK}} MetaClass, please see:<br />
<br><br />
<br />
* [[MetaProxy]]<br />
* [[MetaClass]]<br />
* [[SELECTIVELIST]]<br />
* [[SELECTIVEITEM]]<br />
* [[UNIT]]<br />
<br />
= Comos =<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
<br />
Using or extending the COMOS®-UBIK® Interface (CUI) requires specific configuration information from COMOS®. This information must either be configured on the COMOS® side or made available by the COMOS® administrator.<br />
<br />
COMOS Web requires the following web services:<br />
<br />
* ComosEvents<br />
* ComosGatewayServices<br />
* ComosWebStartPage<br />
<br />
[[File:Screenshot 2026-08-13 091304.png]]<br />
<br />
In the {{COMOS}} project settings, under the "Mobile Solutions" section, ensure that the URL of your ComosWebStartPage (including the port number) is configured correctly. Also, make sure that the COMOS Web database key is configured.<br />
<br />
[[File:Screenshot 2026-08-13 093803.png]]<br />
<br />
Note: Within a single domain, the database key must be unique.<br />
<br />
In the "COMOS Mobile Worker Interface" section of the project settings, you will find the configuration values for the active COMOS project. If the WorkingLayer key is empty, the released area is connected. Otherwise, a specific WorkingLayer can be connected to UBIK® for each project.<br />
<br />
[[File:Screenshot 2026-08-13 094922.png|1000px]]<br />
<br />
= UBIK =<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
<br />
[[HowTo:Set_Up_CUI_Rest_API]]<br />
<br />
<!-- DO NOT REMOVE THIS -->{{Template:HowTo/End}}<!-- DO NOT REMOVE THIS --><br />
<br />
==See also==<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
<br />
For more detailed information please check your {{COMOS}} documentation for "Guide COMOS Mobile Worker"<br />
<br />
or ask Siemens: [https://www.siemens.com/en-us/products/comos/mobile-worker/ comos-mobile-worker]</div>LDOhttps://wiki.augmensys.com/index.php?title=Configure_Comos_for_CUI&diff=30561Configure Comos for CUI2026-09-07T06:59:10Z<p>LDO: </p>
<hr />
<div>[[File:Wiki_Under_Construction_Start.PNG|1000px]]<noinclude><br />
<br />
To run or extend the {{COMOS}} – {{UBIK}} Interface => CUI, you must configure certain settings on the {{COMOS}} side or, at a minimum, obtain configuration data from {{COMOS}}.<br />
<br />
As {{COMOS}} is not an Augmensys product, please contact your local Siemens representative or Siemens partner for any {{COMOS}} changes or adaptations.<br />
<br />
<!-- DO NOT REMOVE THIS -->{{Template:HowTo/Begin}}<!-- DO NOT REMOVE THIS --><br />
<br />
= Idea and Concept =<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
The interfacing of data depends on three aspects:<br />
<br />
* The available data representation in {{COMOS}}<br />
* The transfer mechanism, such as an *.xml file or a REST API interface<br />
* The processing of the provided information in {{UBIK}}<br />
<br />
To transfer the primary information required from {{COMOS}} to {{UBIK}}, only *.xml files can be used. This is because the {{COMOS}} side writes the data to a fixed *.xml schema that {{UBIK}} can read and import.<br />
<br />
This process is called metadata transfer. It transfers information about CDevices, Attributes, StandardTables, PhysicalUnits, and DocumentTypes from {{COMOS}} to an *.xml file.<br />
<br />
When {{UBIK}} SmartStudio imports this file, it generates ComosMetaProxies with corresponding target MetaClasses, ComosMetaProxyProperties with corresponding target MetaProperties, SelectiveLists and SelectiveItems, SIUnits and UnitItems, as well as ComosDocumentTypeProxies.<br />
<br />
For detailed information about the {{UBIK}} MetaClass, please see:<br />
<br><br />
<br />
* [[MetaProxy]]<br />
* [[MetaClass]]<br />
* [[SELECTIVELIST]]<br />
* [[SELECTIVEITEM]]<br />
* [[UNIT]]<br />
<br />
= Comos =<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
<br />
For the connection between {{COMOS}} and {{UBIK}} via the REST API, please ensure that COMOS Web is installed and that the license "COMOS_Mobile_Worker_Server" is available in {{COMOS}}.<br />
<br />
COMOS Web requires the following web services:<br />
<br />
* ComosEvents<br />
* ComosGatewayServices<br />
* ComosWebStartPage<br />
<br />
[[File:Screenshot 2026-08-13 091304.png]]<br />
<br />
In the {{COMOS}} project settings, under the "Mobile Solutions" section, ensure that the URL of your ComosWebStartPage (including the port number) is configured correctly. Also, make sure that the COMOS Web database key is configured.<br />
<br />
[[File:Screenshot 2026-08-13 093803.png]]<br />
<br />
Note: Within a single domain, the database key must be unique.<br />
<br />
In the "COMOS Mobile Worker Interface" section of the project settings, you will find the configuration values for the active COMOS project. If the WorkingLayer key is empty, the released area is connected. Otherwise, a specific WorkingLayer can be connected to UBIK® for each project.<br />
<br />
[[File:Screenshot 2026-08-13 094922.png|1000px]]<br />
<br />
= UBIK =<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
<br />
[[HowTo:Set_Up_CUI_Rest_API]]<br />
<br />
<!-- DO NOT REMOVE THIS -->{{Template:HowTo/End}}<!-- DO NOT REMOVE THIS --><br />
<br />
==See also==<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
<br />
For more detailed information please check your {{COMOS}} documentation for "Guide COMOS Mobile Worker"<br />
<br />
or ask Siemens: [https://www.siemens.com/en-us/products/comos/mobile-worker/ comos-mobile-worker]</div>LDOhttps://wiki.augmensys.com/index.php?title=How_to_set_up_a_database_for_MaTaP&diff=29975How to set up a database for MaTaP2026-06-17T13:26:09Z<p>LDO: </p>
<hr />
<div>= MATAP System Setup Guide =<br />
<br />
This document describes how to set up the MATAP system and its related components. It is intended as a step-by-step reference for administrators or engineers performing a new installation.<br />
<br />
== Recommended Setup Order ==<br />
<br />
# Install and configure the Webservice(s)<br />
# Configure the SQL Database<br />
# Verify access using Studio and AdminTool<br />
# Configure the Enterprise Service<br />
# Configure the Enterprise Orchestrator Service<br />
# Create scheduled jobs in Task Scheduler<br />
# Create multiple slots (optional)<br />
# Test access with client(s)<br />
<br />
== Required Plugins ==<br />
<br />
The following plugins are needed for setting up MaTaP, these should be included automatically in your AdminTool package:<br />
* UBIK.Interface.Module.Excel.dll<br />
* UBIK.Interface.Module.Json.dll<br />
* UBIK.Interface.Module.MaTaP.dll<br />
* UBIK.Interface.Module.MRO.dll<br />
* UBIK.Module.Push.dll<br />
* UBIK.Interface.Module.iCalendar.dll<br />
* NodaTime.dll<br />
* Ical.Net.dll<br />
* Portable.System.DateTimeOnly.dll<br />
* Syncfusion.XlsIO.Base.dll<br />
* Syncfusion.Licensing.dll<br />
* Syncfusion.Compression.Base.dll<br />
<br />
== 1. Webservice Setup ==<br />
<br />
=== Purpose ===<br />
The webservice hosts the MATAP application endpoints and provides the basis for slot-based deployment.<br />
<br />
=== Required Services ===<br />
* CONTENT<br />
* PUSH<br />
* USAM<br />
<br />
These services are required for the system to function correctly.<br />
<br />
=== Application Pools ===<br />
<br />
==== Purpose ====<br />
It is necessary to create a dedicated application pool for each slot. This is required to support the Recycle Application Pool functionality, enabling individual slots to be recycled after specific job executions.<br />
<br />
==== Configuration Notes ====<br />
<br />
'''Plugins''' <br><br />
The plugins needed for the injection folder can be fetched from the AdminTool package.<br />
<br />
'''AppSettings''' <br><br />
Configure the AppSettings as usual for your environment.<br />
<br />
'''Language Configuration''' <br><br />
Set the LanguageID according to the required language. This should be done via the AppSettings of the CONTENT webservice. Currently the following are supported:<br />
* English - 1<br />
* German - 0<br />
<br />
=== Slot Naming Convention ===<br />
<br />
We recommend creating a folder named MATAP that contains all slot webservices. While this is not required for functionality, it helps to clearly separate these services from others. Each webservice should use the following naming convention:<br />
<br />
<pre><br />
C:\inetpub\wwwroot\MATAP<br />
\Slot01<br />
- CONTENT<br />
- USAM<br />
- PUSH<br />
\Slot02<br />
- CONTENT<br />
- USAM<br />
- PUSH<br />
\Slot03<br />
- CONTENT<br />
- USAM<br />
- PUSH<br />
...<br />
</pre><br />
<br />
{{Hint|Do not deviate from this naming convention (Slot01, Slot02..) as this is necessary for the PUSH to work properly. }}<br />
<br />
== 2. SQL Database Setup ==<br />
<br />
=== Configuration ===<br />
<br />
Connect to an empty Database via the UBIK.Studio and a SystemDefinitionsUpgrade window will appear where the highest version needs to be chosen for each component.<br />
After the SystemDefinitionsUpgrade the basic data structure for MaTaP is in the database.<br />
<br />
[[File:DB_upgrade.png|600px]]<br />
<br />
==== Configure database settings ====<br />
<br />
In the top left there is a tab called "Database" from where the Database settings window can be opened. The following settings need to be configured.<br />
<br />
[[File:DB_setting1.png]]<br />
<br />
'''Data Path''' <br><br />
Select a data path for your database.<br />
<br />
'''Web Service Base Url''' <br><br />
Enter the base URL of the web service. Example: If the URL to the content web service of Slot01 is eg. "https://dev.mycompany.net:888/UBIK/MATAP/Slot01/CONTENT/UBIKContent.svc" the base URL would be "https://dev.mycompany.net:888/UBIK/MATAP".<br />
<br />
{{Hint|The MaTaP web services need to be structured in a certain way. The base URL/path can be chosen as liked. From there, a folder for every slot is needed and under each slot folder, there are the Content, Push and Usam folders containing the web service.}}<br />
<br />
[[File:DB_setting2.png]]<br />
<br />
= Customizing and ACM =<br />
<br />
The Customizing of the database needs to be build (F6) and released.<br />
The ACMs (MetaDefinitions) need to be build and released for each used slot context.<br />
<br />
== 3. Enable Recycle App Pool Functionality ==<br />
As the recycling of application pools must be performed via the AdminTool, additional configuration steps are required.<br />
<br />
To do this, open the Application instance in the Bulk Editor using UBIK Studio. This instance can be found under the namespace: System.Matap.General<br />
The instance created by the MATAP plugin is named: APP_MATAP<br />
<br />
=== Configuration of Properties ===<br />
<br />
'''APPLICATION_POOL_NAME''' <br><br />
As the name suggests, this property must contain the exact name of the corresponding Application Pool.<br />
<br />
'''CONTENT_SERVICE_URL''' <br><br />
This property should contain the URL path to the Content Webservice, like so: https://myserver:port/matap/slot01/CONTENT/UBIKContent.svc<br />
<br />
== 4. Required Tools ==<br />
<br />
=== UBIK Studio ===<br />
Needed to initially set up the database and configure the necessary database settings (Check Point 2)<br />
<br />
=== Plugins ===<br />
The plugins needed for the injection folder can be fetched from the AdminTool package.<br />
<br />
=== UBIK AdminTool ===<br />
Needed to import and view the data and execute other calculations<br />
<br />
'''Database Connection''' <br><br />
To connect to the database, you can either configure it manually in AdminTool or import an .smconnection file which can be then provided to others as well. An example of such an .smconnection file is listed below.<br />
<br />
=== .smconnection Example ===<br />
<pre><br />
<?xml version="1.0" encoding="utf-8"?><br />
<DBSettingsProxy xmlns:i="http://www.w3.org/2001/XMLSchema-instance" z:Id="1" xmlns:z="http://schemas.microsoft.com/2003/10/Serialization/" xmlns="http://schemas.datacontract.org/2004/07/UBIK.SmartStudio"><br />
<AutoConnect>false</AutoConnect><br />
<AutoSaveTime>-1</AutoSaveTime><br />
<DataBase z:Id="2">YOUR DATABASE</DataBase><br />
<DataSource z:Id="3">YOUR DATABASE SERVER</DataSource><br />
<Language z:Id="4">en</Language><br />
<Name z:Id="5">DATABASE NAME</Name><br />
<Password z:Id="6">YOUR SQL PASSWORD</Password><br />
<RecordLifeTime>10</RecordLifeTime><br />
<RequestedPlugIns xmlns:d2p1="http://schemas.datacontract.org/2004/07/UBIK.SmartModelling.UI.Environment.ViewModels" z:Id="7" z:Size="0" /><br />
<User z:Id="8">YOUR SQL USER</User><br />
<WindowsAuthentication>false</WindowsAuthentication><br />
</DBSettingsProxy><br />
</pre><br />
<br />
=== Notes ===<br />
<br />
'''RecordLifeTime''' <br><br />
Ensure that the RecordLifeTime is set to 10. If this value is not configured correctly, the refresh functionality in the AdminTool may not work properly when connected to the database.<br />
<br />
'''Language''' <br><br />
Set the language according to your project configuration. Supported options are:<br />
* German (de)<br />
* English (en)<br />
<br />
== 5. Enterprise Service Setup ==<br />
<br />
=== Folder Structure ===<br />
* Create a copy of the Studio package and name the containing folder Enterprise<br />
* Create a folder named json in it<br />
* Create two files based on the the example MATAP.json and MATAP.PARAM.json below to the json folder and configure them accordingly<br />
<br />
=== Configuration MATAP.json ===<br />
<pre><br />
{<br />
"RepeateEveryMinutes": 0.2,<br />
"SqlConnectionDefinition": {<br />
"SSPI": false,<br />
"SQLUser": "YOUR SQL USER",<br />
"SQLPassword": "YOUR SQL PASSWORD",<br />
"SQLServer": "YOUR SQL SERVER",<br />
"SQLInitialCatalog": "YOUR DATABASE"<br />
},<br />
"Tasks":<br />
[<br />
{<br />
"ClassFullname": "UBIK.ServiceTask.Orchestration.ScheduledOrchestrator",<br />
"MethodName": "Apply",<br />
"MethodParameterPathFullName": "C:\\PATH\\Enterprise\\json\\MATAP.PARAM.json" <br />
}<br />
]<br />
}<br />
</pre><br />
<br />
=== Notes ===<br />
'''RepeateEveryMinutes''' <br><br />
No, RepeateEveryMinutes is not a typo – please don’t fix it otherwise it unfortunately won’t work.<br />
<br />
'''Path to Json file''' <br><br />
Ensure to escape the Backslashes!<br />
<br />
=== Configuration MATAP.PARAM.json ===<br />
<pre><br />
{<br />
"InterfaceAdmin": "DDEAD266-7CB6-4894-A1CA-96E8FE81F510"<br />
}<br />
</pre><br />
<br />
=== Configuration UBIK.EnterpriseService.config.exe ===<br />
In order for the json files to be considered by the enterprise, the following changes need to be made in the respective Enterprise Service config:<br />
<pre><br />
<add key="PluginExecutionConfigPath" value="C:\Path\Enterprise\json\MATAP.json" /><br />
<add key="ExecuteTaskByJsonFile" value="1" /><br />
</pre><br />
<br />
== 6. Enterprise Orchestrator Service Setup ==<br />
<br />
* Create a copy of the Studio package and name the containing folder Enterprise_Orchestrator<br />
* Create a folder named json in it<br />
* Create three files, based on the examples RecalculateProjectJob.json, PublishCommissioningWallaper.json and RecycleAllAppPools.json below, save them to the json folder and configure them accordingly<br />
<br />
=== Configuration RecalculateProjectJob.json ===<br />
<pre><br />
{<br />
"SSPI": false,<br />
"SQLUser": "YOUR SQL USER",<br />
"SQLPassword": "YOUR SQL PASSWORD",<br />
"SQLServer": "YOUR SQL SERVER",<br />
"SQLInitialCatalog": "YOUR DATABASE",<br />
"ClassFullname": "UBIK.MATAP.RecalculateProjectJobOrchestrator",<br />
"MethodName": "Apply" <br />
}<br />
</pre><br />
<br />
=== Configuration PublishCommissioningWallaper.json ===<br />
<pre><br />
{<br />
"SSPI": false,<br />
"SQLUser": "YOUR SQL USER",<br />
"SQLPassword": "YOUR SQL PASSWORD",<br />
"SQLServer": "YOUR SQL SERVER",<br />
"SQLInitialCatalog": "YOUR DATABASE",<br />
"ClassFullname": "UBIK.MATAP.PublishCommissioningWallpaperJobOrchestrator",<br />
"MethodName": "Apply" <br />
}<br />
</pre><br />
<br />
=== Configuration RecycleAllAppPools.json ===<br />
<pre><br />
{<br />
"SSPI": false,<br />
"SQLUser": "YOUR SQL USER",<br />
"SQLPassword": "YOUR SQL PASSWORD",<br />
"SQLServer": "YOUR SQL SERVER",<br />
"SQLInitialCatalog": "YOUR DATABASE",<br />
"ClassFullname": "UBIK.MATAP.RecycleAppPoolJobOrchestrator",<br />
"MethodName": "Apply" <br />
}<br />
</pre><br />
<br />
=== Executables ===<br />
Copy and paste the already existing UBIK.EnterpriseService.BasicClient.App.exe + the UBIK.EnterpriseService.BasicClient.exe.config so you have three each and name them the following:<br />
<br />
* RecalculateProjectJob.exe & RecalculateProjectJob.exe.config<br />
* PublishCommissioningWallpaperJob.exe & PublishCommissioningWallpaperJob.exe.config<br />
* RecycleAllAppPoolsJob.exe & RecycleAllAppPoolsJob.exe.config<br />
<br />
=== Notes ===<br />
Ensure that the config ends with .exe.config, when copying and pasting the exe part sometimes gets removed which makes the config unusable.<br />
<br />
=== Configuration RecalculateProjectJob.config.exe ===<br />
<pre><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFile" value="C:\Path\Enterprise_Orchestrator\json\RecalculateProjectJob.json" /><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFileList" value="" /><br />
</pre><br />
<br />
=== Configuration PublishCommissioningWallpaperJob.config.exe ===<br />
<pre><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFile" value="C:\Path\Enterprise_Orchestrator\json\PublishCommissioningWallpaperJob.json" /><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFileList" value="" /><br />
</pre><br />
<br />
=== Configuration RecycleAllAppPoolsJob.config.exe ===<br />
<pre><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFile" value="C:\Path\Enterprise_Orchestrator\json\RecycleAllAppPoolsJob.json" /><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFileList" value="" /><br />
</pre><br />
<br />
=== Notes ===<br />
It’s already defined in the configuration part but wanted to clarify that you must remove the content of the key PathToBasicEnterpriseServiceRequestJsonFileList, otherwise the value will be considered from the BasicClient exe.<br />
<br />
=== Configuration UBIK.EnterpriseService.config.exe ===<br />
In order for the BasicClient exe’s being executed accordingly, the following change needs to be made in the respective Enterprise config:<br />
<pre><br />
<add key="ExecuteWebInterface" value="1" /><br />
</pre><br />
<br />
== 7. Windows Task Scheduler ==<br />
* Create three tasks for each job<br />
<br />
=== Configuration Tasks ===<br />
For each task you must point to the respective BasicClient exe which was created in the steps above. This can be done via the tab Actions in the Task Scheduler when creating a task. The needed action is Start a program and below the path defined to the respective exe.<br />
<br />
=== Execution Order ===<br />
The timing of the jobs must be adapted as needed for the project use case, usually we plan them for the night when no one is working. The only thing that needs to be considered is the sequence which is the following.<br />
<br />
# RecalculateProjectJob<br />
# PublishCommissioningWallpaperJob<br />
# RecycleAllAppPoolsJob<br />
<br />
== 8. Multiple Slot Setup ==<br />
If there is the need to create multiple slots for a project, some things must be considered. For each new slot webservice there is the need to create a new application, context and view.<br />
The respective MetaClasses for these can be found below.<br />
<br />
=== Application Namespace ===<br />
System.Matap.General.MATAPAPPLICATION<br />
<br />
'''Note''' <br><br />
Make sure to adapt the Application Pool Name and Content Service URL properties accordingly as described in point 3.<br />
<br />
=== Context Namespace ===<br />
System.Matap.General.MATAPCONTEXT<br />
<br />
'''Note''' <br> <br />
No need to configure everything, just use the template view (CTX_MATAP_TEMPLATE) to derivate from it. <br />
Make sure to adapt to the correct slot in property SHOW_ON_WALLPAPER.<br />
<br />
=== View Namespace ===<br />
System.Matap.Content.MATAP_VIEW<br />
<br />
'''Note''' <br> <br />
No need to configure everything, just use the template view (VIEW_MATAP_TEMPLATE) to derivate from it. <br />
Make sure to adapt to the correct slot in property SHOW_ON_WALLPAPER.<br />
<br />
== 9. Access to Clients ==<br />
The client installation packages can be provided either by our project engineers or developers responsible for the MATAP product.<br />
<br />
=== Matap Desktop Client & Customizing ===<br />
Currently we also provide the Desktop Matap client via the Microsoft Store. Make sure this client is fitting for your project use case by getting in contact with the development team. The XAML Customizing can be fetched from our Matap Repository depending on your project use case. Please get in contact with the development team to access them.<br />
<br />
=== Matap Mobile Client & Customizing ===<br />
As there is no specific Matap Mobile Client, you can just download the newest Xamarin or Maui version from either the Android Play Store or Apple Appstore. The XAML Customizing can be fetched from our Matap Repository depending on your project use case. Please get in contact with the development team to access them.<br />
<br />
[[Category:How-To|How to set up a database for MaTaP]]<br />
[[Category:MaTaP|How to set up a database for MaTaP]]</div>LDOhttps://wiki.augmensys.com/index.php?title=How_to_set_up_a_database_for_MaTaP&diff=29971How to set up a database for MaTaP2026-06-17T12:38:56Z<p>LDO: </p>
<hr />
<div>= MATAP System Setup Guide =<br />
<br />
This document describes how to set up the MATAP system and its related components. It is intended as a step-by-step reference for administrators or engineers performing a new installation.<br />
<br />
== Recommended Setup Order ==<br />
<br />
# Install and configure the Webservice(s)<br />
# Configure the SQL Database<br />
# Verify access using Studio and AdminTool<br />
# Configure the Enterprise Service<br />
# Configure the Enterprise Orchestrator Service<br />
# Create scheduled jobs in Task Scheduler<br />
# Create multiple slots (optional)<br />
# Test access with client(s)<br />
<br />
== Required Plugins ==<br />
<br />
The following plugins are needed for setting up MaTaP, these should be included automatically in your AdminTool package:<br />
* UBIK.Interface.Module.Excel.dll<br />
* UBIK.Interface.Module.Json.dll<br />
* UBIK.Interface.Module.MaTaP.dll<br />
* UBIK.Interface.Module.MRO.dll<br />
* UBIK.Module.Push.dll<br />
* UBIK.Interface.Module.iCalendar.dll<br />
* NodaTime.dll<br />
* Ical.Net.dll<br />
* Portable.System.DateTimeOnly.dll<br />
* Syncfusion.XlsIO.Base.dll<br />
* Syncfusion.Licensing.dll<br />
* Syncfusion.Compression.Base.dll<br />
<br />
== 1. Webservice Setup ==<br />
<br />
=== Purpose ===<br />
The webservice hosts the MATAP application endpoints and provides the basis for slot-based deployment.<br />
<br />
=== Required Services ===<br />
* CONTENT<br />
* PUSH<br />
* USAM<br />
<br />
These services are required for the system to function correctly.<br />
<br />
=== Application Pools ===<br />
<br />
==== Purpose ====<br />
It is necessary to create a dedicated application pool for each slot. This is required to support the Recycle Application Pool functionality, enabling individual slots to be recycled after specific job executions.<br />
<br />
==== Configuration Notes ====<br />
<br />
'''Plugins'''<br />
The plugins needed for the injection folder can be fetched from the AdminTool package.<br />
<br />
'''AppSettings'''<br />
Configure the AppSettings as usual for your environment.<br />
<br />
'''Language Configuration'''<br />
Set the LanguageID according to the required language. This should be done via the AppSettings of the CONTENT webservice. Currently the following are supported:<br />
* English - 1<br />
* German - 0<br />
<br />
=== Slot Naming Convention ===<br />
<br />
We recommend creating a folder named MATAP that contains all slot webservices. While this is not required for functionality, it helps to clearly separate these services from others. Each webservice should use the following naming convention:<br />
<br />
<pre><br />
C:\inetpub\wwwroot\MATAP<br />
\Slot01<br />
- CONTENT<br />
- USAM<br />
- PUSH<br />
\Slot02<br />
- CONTENT<br />
- USAM<br />
- PUSH<br />
\Slot03<br />
- CONTENT<br />
- USAM<br />
- PUSH<br />
...<br />
</pre><br />
<br />
Important: Do not deviate from this naming convention (Slot01, Slot02..) as this is necessary for the PUSH to work properly.<br />
<br />
== 2. SQL Database Setup ==<br />
<br />
=== Configuration ===<br />
<br />
Connect to an empty Database via the UBIK.Studio and a SystemDefinitionsUpgrade window will appear where the highest version needs to be chosen for each component.<br />
After the SystemDefinitionsUpgrade the basic data structure for MaTaP is in the database.<br />
<br />
[[File:DB_upgrade.png|600px]]<br />
<br />
==== Configure database settings ====<br />
<br />
In the top left there is a tab called "Database" from where the Database settings window can be opened. The following settings need to be configured.<br />
<br />
[[File:DB_setting1.png]]<br />
<br />
'''Data Path''': Select a data path for your database.<br />
<br />
'''Web Service Base Url''': Enter the base URL of the web service. Example: If the URL to the content web service of Slot01 is eg. "https://dev.mycompany.net:888/UBIK/MATAP/Slot01/CONTENT/UBIKContent.svc" the base URL would be "https://dev.mycompany.net:888/UBIK/MATAP".<br />
<br />
{{Hint|The MaTaP web services need to be structured in a certain way. The base URL/path can be chosen as liked. From there, a folder for every slot is needed (have to be called "Slot01", "Slot02", ...) and under each slot folder, there are the Content, Push and Usam folders containing the web service.}}<br />
<br />
[[File:DB_setting2.png]]<br />
<br />
= Customizing and ACM =<br />
<br />
The Customizing of the database needs to be build (F6) and released.<br />
The ACMs (MetaDefinitions) need to be build and released for each used slot context.<br />
<br />
== 3. Enable Recycle App Pool Functionality ==<br />
<br />
As the recycling of application pools must be performed via the AdminTool, additional configuration steps are required.<br />
<br />
To do this, open the Application instance in the Bulk Editor using UBIK Studio. This instance can be found under the namespace: System.Matap.General<br />
The instance created by the MATAP plugin is named: APP_MATAP<br />
<br />
=== Configuration of Properties ===<br />
<br />
'''APPLICATION_POOL_NAME'''<br />
As the name suggests, this property must contain the exact name of the corresponding Application Pool.<br />
<br />
'''CONTENT_SERVICE_URL'''<br />
This property should contain the URL path to the Content Webservice, like so: https://myserver:port/matap/slot01/CONTENT/UBIKContent.svc<br />
<br />
== 4. Required Tools ==<br />
<br />
=== UBIK Studio ===<br />
Needed to initially set up the database and configure the necessary database settings (Check Point 2)<br />
<br />
=== Plugins ===<br />
The plugins needed for the injection folder can be fetched from the AdminTool package.<br />
<br />
=== UBIK AdminTool ===<br />
Needed to import and view the data and execute other calculations<br />
<br />
Plugins<br />
Already located in the AdminTool package.<br />
<br />
To connect to the database, you can either configure it manually in AdminTool or import an .smconnection file which can be then provided to others as well. An example of such an .smconnection file is listed below.<br />
<br />
=== .smconnection Example ===<br />
<br />
<pre><br />
<?xml version="1.0" encoding="utf-8"?><br />
<DBSettingsProxy xmlns:i="http://www.w3.org/2001/XMLSchema-instance" z:Id="1" xmlns:z="http://schemas.microsoft.com/2003/10/Serialization/" xmlns="http://schemas.datacontract.org/2004/07/UBIK.SmartStudio"><br />
<AutoConnect>false</AutoConnect><br />
<AutoSaveTime>-1</AutoSaveTime><br />
<DataBase z:Id="2">YOUR DATABASE</DataBase><br />
<DataSource z:Id="3">YOUR DATABASE SERVER</DataSource><br />
<Language z:Id="4">en</Language><br />
<Name z:Id="5">DATABASE NAME</Name><br />
<Password z:Id="6">YOUR SQL PASSWORD</Password><br />
<RecordLifeTime>10</RecordLifeTime><br />
<RequestedPlugIns xmlns:d2p1="http://schemas.datacontract.org/2004/07/UBIK.SmartModelling.UI.Environment.ViewModels" z:Id="7" z:Size="0" /><br />
<User z:Id="8">YOUR SQL USER</User><br />
<WindowsAuthentication>false</WindowsAuthentication><br />
</DBSettingsProxy><br />
</pre><br />
<br />
=== Notes ===<br />
<br />
'''RecordLifeTime'''<br />
Ensure that the RecordLifeTime is set to 10. If this value is not configured correctly, the refresh functionality in the AdminTool may not work properly when connected to the database.<br />
<br />
'''Language'''<br />
Set the language according to your project configuration. Supported options are:<br />
* German (de)<br />
* English (en)<br />
<br />
== 5. Enterprise Service Setup ==<br />
<br />
=== Folder Structure ===<br />
* Create a copy of the Studio package and name the containing folder Enterprise<br />
* Create a folder named json in it<br />
* Create two files based on the the example MATAP.json and MATAP.PARAM.json below to the json folder and configure them accordingly<br />
<br />
=== Configuration MATAP.json ===<br />
<pre><br />
{<br />
"RepeateEveryMinutes": 0.2,<br />
"SqlConnectionDefinition": {<br />
"SSPI": false,<br />
"SQLUser": "YOUR SQL USER",<br />
"SQLPassword": "YOUR SQL PASSWORD",<br />
"SQLServer": "YOUR SQL SERVER",<br />
"SQLInitialCatalog": "YOUR DATABASE"<br />
},<br />
"Tasks":<br />
[<br />
{<br />
"ClassFullname": "UBIK.ServiceTask.Orchestration.ScheduledOrchestrator",<br />
"MethodName": "Apply",<br />
"MethodParameterPathFullName": "C:\\PATH\\Enterprise\\json\\MATAP.PARAM.json" <br />
}<br />
]<br />
}<br />
</pre><br />
<br />
=== Notes ===<br />
'''RepeateEveryMinutes'''<br />
No, RepeateEveryMinutes is not a typo – please don’t fix it otherwise it unfortunately won’t work.<br />
<br />
'''Path to Json file'''<br />
Ensure to escape the Backslashes!<br />
<br />
=== Configuration MATAP.PARAM.json ===<br />
<pre><br />
{<br />
"InterfaceAdmin": "DDEAD266-7CB6-4894-A1CA-96E8FE81F510"<br />
}<br />
</pre><br />
<br />
=== Configuration UBIK.EnterpriseService.config.exe ===<br />
<pre><br />
<add key="PluginExecutionConfigPath" value="C:\Path\Enterprise\json\MATAP.json" /><br />
<add key="ExecuteTaskByJsonFile" value="1" /><br />
</pre><br />
<br />
== 6. Enterprise Orchestrator Service Setup ==<br />
<br />
* Create a copy of the Studio package and name the containing folder Enterprise_Orchestrator<br />
* Create a folder named json in it<br />
* Create three files, based on the examples RecalculateProjectJob.json, PublishCommissioningWallaper.json and RecycleAllAppPools.json below, save them to the json folder and configure them accordingly<br />
<br />
=== Configuration RecalculateProjectJob.json ===<br />
<pre><br />
{<br />
"SSPI": false,<br />
"SQLUser": "YOUR SQL USER",<br />
"SQLPassword": "YOUR SQL PASSWORD",<br />
"SQLServer": "YOUR SQL SERVER",<br />
"SQLInitialCatalog": "YOUR DATABASE",<br />
"ClassFullname": "UBIK.MATAP.RecalculateProjectJobOrchestrator",<br />
"MethodName": "Apply" <br />
}<br />
</pre><br />
<br />
=== Configuration PublishCommissioningWallaper.json ===<br />
<pre><br />
{<br />
"SSPI": false,<br />
"SQLUser": "YOUR SQL USER",<br />
"SQLPassword": "YOUR SQL PASSWORD",<br />
"SQLServer": "YOUR SQL SERVER",<br />
"SQLInitialCatalog": "YOUR DATABASE",<br />
"ClassFullname": "UBIK.MATAP.PublishCommissioningWallpaperJobOrchestrator",<br />
"MethodName": "Apply" <br />
}<br />
</pre><br />
<br />
=== Configuration RecycleAllAppPools.json ===<br />
<pre><br />
{<br />
"SSPI": false,<br />
"SQLUser": "YOUR SQL USER",<br />
"SQLPassword": "YOUR SQL PASSWORD",<br />
"SQLServer": "YOUR SQL SERVER",<br />
"SQLInitialCatalog": "YOUR DATABASE",<br />
"ClassFullname": "UBIK.MATAP.RecycleAppPoolJobOrchestrator",<br />
"MethodName": "Apply" <br />
}<br />
</pre><br />
<br />
=== Executables ===<br />
<br />
Copy and paste the already existing UBIK.EnterpriseService.BasicClient.App.exe + the UBIK.EnterpriseService.BasicClient.exe.config so you have three each and name them the following:<br />
<br />
* RecalculateProjectJob.exe & RecalculateProjectJob.exe.config<br />
* PublishCommissioningWallpaperJob.exe & PublishCommissioningWallpaperJob.exe.config<br />
* RecycleAllAppPoolsJob.exe & RecycleAllAppPoolsJob.exe.config<br />
<br />
=== Notes ===<br />
<br />
Ensure that the config ends with .exe.config, when copying and pasting the exe parts sometimes gets removed which makes the config unusable.<br />
<br />
=== Configuration RecalculateProjectJob.config.exe ===<br />
<pre><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFile" value="C:\Path\Enterprise_Orchestrator\json\RecalculateProjectJob.json" /><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFileList" value="" /><br />
</pre><br />
<br />
=== Configuration PublishCommissioningWallpaperJob.config.exe ===<br />
<pre><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFile" value="C:\Path\Enterprise_Orchestrator\json\PublishCommissioningWallpaperJob.json" /><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFileList" value="" /><br />
</pre><br />
<br />
=== Configuration RecycleAllAppPoolsJob.config.exe ===<br />
<pre><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFile" value="C:\Path\Enterprise_Orchestrator\json\RecycleAllAppPoolsJob.json" /><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFileList" value="" /><br />
</pre><br />
<br />
=== Notes ===<br />
<br />
It’s already defined in the configuration part but wanted to clarify that you must remove the content of the key PathToBasicEnterpriseServiceRequestJsonFileList, otherwise the value will be considered from the BasicClient exe.<br />
<br />
=== Configuration UBIK.EnterpriseService.config.exe ===<br />
<pre><br />
<add key="ExecuteWebInterface" value="1" /><br />
</pre><br />
<br />
== 7. Windows Task Scheduler ==<br />
<br />
* Create three tasks for each job<br />
<br />
=== Configuration Tasks ===<br />
For each task you must point to the respective BasicClient exe which was created in the steps above.<br />
<br />
=== Execution Order ===<br />
# RecalculateProjectJob<br />
# PublishCommissioningWallpaperJob<br />
# RecycleAllAppPoolsJob<br />
<br />
== 8. Multiple Slot Setup ==<br />
<br />
If there is the need to create multiple slots for a project, some things must be considered.<br />
<br />
=== Application Namespace ===<br />
System.Matap.General.MATAPAPPLICATION<br />
<br />
Note <br />
Make sure to adapt the Application Pool Name and Content Service URL properties accordingly as described in point 3.<br />
<br />
=== Context Namespace ===<br />
System.Matap.General.MATAPCONTEXT<br />
<br />
Note <br />
No need to configure everything, just use the template view (CTX_MATAP_TEMPLATE) to derivate from it. <br />
Make sure to adapt to the correct slot in property SHOW_ON_WALLPAPER.<br />
<br />
=== View Namespace ===<br />
System.Matap.Content.MATAP_VIEW<br />
<br />
Note <br />
No need to configure everything, just use the template view (VIEW_MATAP_TEMPLATE) to derivate from it. <br />
Make sure to adapt to the correct slot in property SHOW_ON_WALLPAPER.<br />
<br />
== 9. Access to Clients ==<br />
<br />
The client installation packages can be provided either by our project engineers or developers responsible for the MATAP product.<br />
<br />
=== Matap Desktop Client & Customizing ===<br />
Currently we also provide the Desktop Matap client via the Microsoft Store. Make sure this client is fitting for your project use case by getting in contact with the development team. The XAML Customizing can be fetched from our Matap Repository depending on your project use case. Please get in contact with the development team to access them.<br />
<br />
=== Matap Mobile Client & Customizing ===<br />
As there is no specific Matap Mobile Client, you can just download the newest Xamarin or Maui version from either the Android Play Store or Apple Appstore. The XAML Customizing can be fetched from our Matap Repository depending on your project use case. Please get in contact with the development team to access them.<br />
<br />
[[Category:How-To|How to set up a database for MaTaP]]<br />
[[Category:MaTaP|How to set up a database for MaTaP]]</div>LDOhttps://wiki.augmensys.com/index.php?title=How_to_set_up_a_database_for_MaTaP&diff=29913How to set up a database for MaTaP2026-06-09T12:48:57Z<p>LDO: </p>
<hr />
<div>= MATAP System Setup Guide =<br />
<br />
This document describes how to set up the MATAP system and its related components. It is intended as a step-by-step reference for administrators or engineers performing a new installation.<br />
<br />
== Recommended Setup Order ==<br />
<br />
# Install and configure the Webservice(s)<br />
# Configure the SQL Database<br />
# Verify access using Studio and AdminTool<br />
# Configure the Enterprise Service<br />
# Configure the Enterprise Orchestrator Service<br />
# Create scheduled jobs in Task Scheduler<br />
# Create multiple slots (optional)<br />
# Test access with client(s)<br />
<br />
== Required Plugins ==<br />
<br />
The following plugins are needed for setting up MaTaP, these should be included automatically in your AdminTool package:<br />
* UBIK.Interface.Module.Excel.dll<br />
* UBIK.Interface.Module.Json.dll<br />
* UBIK.Interface.Module.MaTaP.dll<br />
* UBIK.Interface.Module.MRO.dll<br />
* Syncfusion.XlsIO.Base.dll<br />
* Syncfusion.Licensing.dll<br />
* Syncfusion.Compression.Base.dll<br />
<br />
== 1. Webservice Setup ==<br />
<br />
=== Purpose ===<br />
The webservice hosts the MATAP application endpoints and provides the basis for slot-based deployment.<br />
<br />
=== Required Services ===<br />
* CONTENT<br />
* PUSH<br />
* USAM<br />
<br />
These services are required for the system to function correctly.<br />
<br />
=== Application Pools ===<br />
<br />
==== Purpose ====<br />
It is necessary to create a dedicated application pool for each slot. This is required to support the Recycle Application Pool functionality, enabling individual slots to be recycled after specific job executions.<br />
<br />
==== Configuration Notes ====<br />
<br />
'''Plugins'''<br />
The plugins needed for the injection folder can be fetched from the AdminTool package.<br />
<br />
'''AppSettings'''<br />
Configure the AppSettings as usual for your environment.<br />
<br />
'''Language Configuration'''<br />
Set the LanguageID according to the required language. This should be done via the AppSettings of the CONTENT webservice. Currently the following are supported:<br />
* English - 1<br />
* German - 0<br />
<br />
=== Slot Naming Convention ===<br />
<br />
We recommend creating a folder named MATAP that contains all slot webservices. While this is not required for functionality, it helps to clearly separate these services from others. Each webservice should use the following naming convention:<br />
<br />
<pre><br />
C:\inetpub\wwwroot\MATAP<br />
\Slot01<br />
- CONTENT<br />
- USAM<br />
- PUSH<br />
\Slot02<br />
- CONTENT<br />
- USAM<br />
- PUSH<br />
\Slot03<br />
- CONTENT<br />
- USAM<br />
- PUSH<br />
...<br />
</pre><br />
<br />
Important: Do not deviate from this naming convention (Slot01, Slot02..) as this is necessary for the PUSH to work properly.<br />
<br />
== 2. SQL Database Setup ==<br />
<br />
=== Configuration ===<br />
<br />
Connect to an empty Database via the UBIK.Studio and a SystemDefinitionsUpgrade window will appear where the highest version needs to be chosen for each component.<br />
After the SystemDefinitionsUpgrade the basic data structure for MaTaP is in the database.<br />
<br />
[[File:DB_upgrade.png|600px]]<br />
<br />
==== Configure database settings ====<br />
<br />
In the top left there is a tab called "Database" from where the Database settings window can be opened. The following settings need to be configured.<br />
<br />
[[File:DB_setting1.png]]<br />
<br />
'''Data Path''': Select a data path for your database.<br />
<br />
'''Web Service Base Url''': Enter the base URL of the web service. Example: If the URL to the content web service of Slot01 is eg. "https://dev.mycompany.net:888/UBIK/MATAP/Slot01/CONTENT/UBIKContent.svc" the base URL would be "https://dev.mycompany.net:888/UBIK/MATAP".<br />
<br />
{{Hint|The MaTaP web services need to be structured in a certain way. The base URL/path can be chosen as liked. From there, a folder for every slot is needed (have to be called "Slot01", "Slot02", ...) and under each slot folder, there are the Content, Push and Usam folders containing the web service.}}<br />
<br />
[[File:DB_setting2.png]]<br />
<br />
= Customizing and ACM =<br />
<br />
The Customizing of the database needs to be build (F6) and released.<br />
The ACMs (MetaDefinitions) need to be build and released for each used slot context.<br />
<br />
== 3. Enable Recycle App Pool Functionality ==<br />
<br />
As the recycling of application pools must be performed via the AdminTool, additional configuration steps are required.<br />
<br />
To do this, open the Application instance in the Bulk Editor using UBIK Studio. This instance can be found under the namespace: System.Matap.General<br />
The instance created by the MATAP plugin is named: APP_MATAP<br />
<br />
=== Configuration of Properties ===<br />
<br />
'''APPLICATION_POOL_NAME'''<br />
As the name suggests, this property must contain the exact name of the corresponding Application Pool.<br />
<br />
'''CONTENT_SERVICE_URL'''<br />
This property should contain the URL path to the Content Webservice, like so: https://myserver:port/matap/slot01/CONTENT/UBIKContent.svc<br />
<br />
== 4. Required Tools ==<br />
<br />
=== UBIK Studio ===<br />
Needed to initially set up the database and configure the necessary database settings (Check Point 2)<br />
<br />
=== Plugins ===<br />
The plugins needed for the injection folder can be fetched from the AdminTool package.<br />
<br />
=== UBIK AdminTool ===<br />
Needed to import and view the data and execute other calculations<br />
<br />
Plugins<br />
Already located in the AdminTool package.<br />
<br />
To connect to the database, you can either configure it manually in AdminTool or import an .smconnection file which can be then provided to others as well. An example of such an .smconnection file is listed below.<br />
<br />
=== .smconnection Example ===<br />
<br />
<pre><br />
<?xml version="1.0" encoding="utf-8"?><br />
<DBSettingsProxy xmlns:i="http://www.w3.org/2001/XMLSchema-instance" z:Id="1" xmlns:z="http://schemas.microsoft.com/2003/10/Serialization/" xmlns="http://schemas.datacontract.org/2004/07/UBIK.SmartStudio"><br />
<AutoConnect>false</AutoConnect><br />
<AutoSaveTime>-1</AutoSaveTime><br />
<DataBase z:Id="2">YOUR DATABASE</DataBase><br />
<DataSource z:Id="3">YOUR DATABASE SERVER</DataSource><br />
<Language z:Id="4">en</Language><br />
<Name z:Id="5">DATABASE NAME</Name><br />
<Password z:Id="6">YOUR SQL PASSWORD</Password><br />
<RecordLifeTime>10</RecordLifeTime><br />
<RequestedPlugIns xmlns:d2p1="http://schemas.datacontract.org/2004/07/UBIK.SmartModelling.UI.Environment.ViewModels" z:Id="7" z:Size="0" /><br />
<User z:Id="8">YOUR SQL USER</User><br />
<WindowsAuthentication>false</WindowsAuthentication><br />
</DBSettingsProxy><br />
</pre><br />
<br />
=== Notes ===<br />
<br />
'''RecordLifeTime'''<br />
Ensure that the RecordLifeTime is set to 10. If this value is not configured correctly, the refresh functionality in the AdminTool may not work properly when connected to the database.<br />
<br />
'''Language'''<br />
Set the language according to your project configuration. Supported options are:<br />
* German (de)<br />
* English (en)<br />
<br />
== 5. Enterprise Service Setup ==<br />
<br />
=== Folder Structure ===<br />
* Create a copy of the Studio package and name the containing folder Enterprise<br />
* Create a folder named json in it<br />
* Create two files based on the the example MATAP.json and MATAP.PARAM.json below to the json folder and configure them accordingly<br />
<br />
=== Configuration MATAP.json ===<br />
<pre><br />
{<br />
"RepeateEveryMinutes": 0.2,<br />
"SqlConnectionDefinition": {<br />
"SSPI": false,<br />
"SQLUser": "YOUR SQL USER",<br />
"SQLPassword": "YOUR SQL PASSWORD",<br />
"SQLServer": "YOUR SQL SERVER",<br />
"SQLInitialCatalog": "YOUR DATABASE"<br />
},<br />
"Tasks":<br />
[<br />
{<br />
"ClassFullname": "UBIK.ServiceTask.Orchestration.ScheduledOrchestrator",<br />
"MethodName": "Apply",<br />
"MethodParameterPathFullName": "C:\\PATH\\Enterprise\\json\\MATAP.PARAM.json" <br />
}<br />
]<br />
}<br />
</pre><br />
<br />
=== Notes ===<br />
'''RepeateEveryMinutes'''<br />
No, RepeateEveryMinutes is not a typo – please don’t fix it otherwise it unfortunately won’t work.<br />
<br />
'''Path to Json file'''<br />
Ensure to escape the Backslashes!<br />
<br />
=== Configuration MATAP.PARAM.json ===<br />
<pre><br />
{<br />
"InterfaceAdmin": "DDEAD266-7CB6-4894-A1CA-96E8FE81F510"<br />
}<br />
</pre><br />
<br />
=== Configuration UBIK.EnterpriseService.config.exe ===<br />
<pre><br />
<add key="PluginExecutionConfigPath" value="C:\Path\Enterprise\json\MATAP.json" /><br />
<add key="ExecuteTaskByJsonFile" value="1" /><br />
</pre><br />
<br />
== 6. Enterprise Orchestrator Service Setup ==<br />
<br />
* Create a copy of the Studio package and name the containing folder Enterprise_Orchestrator<br />
* Create a folder named json in it<br />
* Create three files, based on the examples RecalculateProjectJob.json, PublishCommissioningWallaper.json and RecycleAllAppPools.json below, save them to the json folder and configure them accordingly<br />
<br />
=== Configuration RecalculateProjectJob.json ===<br />
<pre><br />
{<br />
"SSPI": false,<br />
"SQLUser": "YOUR SQL USER",<br />
"SQLPassword": "YOUR SQL PASSWORD",<br />
"SQLServer": "YOUR SQL SERVER",<br />
"SQLInitialCatalog": "YOUR DATABASE",<br />
"ClassFullname": "UBIK.MATAP.RecalculateProjectJobOrchestrator",<br />
"MethodName": "Apply" <br />
}<br />
</pre><br />
<br />
=== Configuration PublishCommissioningWallaper.json ===<br />
<pre><br />
{<br />
"SSPI": false,<br />
"SQLUser": "YOUR SQL USER",<br />
"SQLPassword": "YOUR SQL PASSWORD",<br />
"SQLServer": "YOUR SQL SERVER",<br />
"SQLInitialCatalog": "YOUR DATABASE",<br />
"ClassFullname": "UBIK.MATAP.PublishCommissioningWallpaperJobOrchestrator",<br />
"MethodName": "Apply" <br />
}<br />
</pre><br />
<br />
=== Configuration RecycleAllAppPools.json ===<br />
<pre><br />
{<br />
"SSPI": false,<br />
"SQLUser": "YOUR SQL USER",<br />
"SQLPassword": "YOUR SQL PASSWORD",<br />
"SQLServer": "YOUR SQL SERVER",<br />
"SQLInitialCatalog": "YOUR DATABASE",<br />
"ClassFullname": "UBIK.MATAP.RecycleAppPoolJobOrchestrator",<br />
"MethodName": "Apply" <br />
}<br />
</pre><br />
<br />
=== Executables ===<br />
<br />
Copy and paste the already existing UBIK.EnterpriseService.BasicClient.App.exe + the UBIK.EnterpriseService.BasicClient.exe.config so you have three each and name them the following:<br />
<br />
* RecalculateProjectJob.exe & RecalculateProjectJob.exe.config<br />
* PublishCommissioningWallpaperJob.exe & PublishCommissioningWallpaperJob.exe.config<br />
* RecycleAllAppPoolsJob.exe & RecycleAllAppPoolsJob.exe.config<br />
<br />
=== Notes ===<br />
<br />
Ensure that the config ends with .exe.config, when copying and pasting the exe parts sometimes gets removed which makes the config unusable.<br />
<br />
=== Configuration RecalculateProjectJob.config.exe ===<br />
<pre><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFile" value="C:\Path\Enterprise_Orchestrator\json\RecalculateProjectJob.json" /><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFileList" value="" /><br />
</pre><br />
<br />
=== Configuration PublishCommissioningWallpaperJob.config.exe ===<br />
<pre><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFile" value="C:\Path\Enterprise_Orchestrator\json\PublishCommissioningWallpaperJob.json" /><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFileList" value="" /><br />
</pre><br />
<br />
=== Configuration RecycleAllAppPoolsJob.config.exe ===<br />
<pre><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFile" value="C:\Path\Enterprise_Orchestrator\json\RecycleAllAppPoolsJob.json" /><br />
<add key="PathToBasicEnterpriseServiceRequestJsonFileList" value="" /><br />
</pre><br />
<br />
=== Notes ===<br />
<br />
It’s already defined in the configuration part but wanted to clarify that you must remove the content of the key PathToBasicEnterpriseServiceRequestJsonFileList, otherwise the value will be considered from the BasicClient exe.<br />
<br />
=== Configuration UBIK.EnterpriseService.config.exe ===<br />
<pre><br />
<add key="ExecuteWebInterface" value="1" /><br />
</pre><br />
<br />
== 7. Windows Task Scheduler ==<br />
<br />
* Create three tasks for each job<br />
<br />
=== Configuration Tasks ===<br />
For each task you must point to the respective BasicClient exe which was created in the steps above.<br />
<br />
=== Execution Order ===<br />
# RecalculateProjectJob<br />
# PublishCommissioningWallpaperJob<br />
# RecycleAllAppPoolsJob<br />
<br />
== 8. Multiple Slot Setup ==<br />
<br />
If there is the need to create multiple slots for a project, some things must be considered.<br />
<br />
=== Application Namespace ===<br />
System.Matap.General.MATAPAPPLICATION<br />
<br />
Note <br />
Make sure to adapt the Application Pool Name and Content Service URL properties accordingly as described in point 3.<br />
<br />
=== Context Namespace ===<br />
System.Matap.General.MATAPCONTEXT<br />
<br />
Note <br />
No need to configure everything, just use the template view (CTX_MATAP_TEMPLATE) to derivate from it. <br />
Make sure to adapt to the correct slot in property SHOW_ON_WALLPAPER.<br />
<br />
=== View Namespace ===<br />
System.Matap.Content.MATAP_VIEW<br />
<br />
Note <br />
No need to configure everything, just use the template view (VIEW_MATAP_TEMPLATE) to derivate from it. <br />
Make sure to adapt to the correct slot in property SHOW_ON_WALLPAPER.<br />
<br />
== 9. Access to Clients ==<br />
<br />
The client installation packages can be provided either by our project engineers or developers responsible for the MATAP product.<br />
<br />
=== Matap Desktop Client & Customizing ===<br />
Currently we also provide the Desktop Matap client via the Microsoft Store. Make sure this client is fitting for your project use case by getting in contact with the development team. The XAML Customizing can be fetched from our Matap Repository depending on your project use case. Please get in contact with the development team to access them.<br />
<br />
=== Matap Mobile Client & Customizing ===<br />
As there is no specific Matap Mobile Client, you can just download the newest Xamarin or Maui version from either the Android Play Store or Apple Appstore. The XAML Customizing can be fetched from our Matap Repository depending on your project use case. Please get in contact with the development team to access them.<br />
<br />
[[Category:How-To|How to set up a database for MaTaP]]<br />
[[Category:MaTaP|How to set up a database for MaTaP]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Configure_UBIK_Archon_Service&diff=29633Configure UBIK Archon Service2026-03-30T06:17:18Z<p>LDO: </p>
<hr />
<div>The UBIK.Archon WebService is the central information hub that is responsible for managing the set of available licenses for one subscription<br />
This page describes how to setup the system.<br />
<br />
= Overview =<br />
* Make sure the [[HowTo:Install_UBIK_Web_Service#UBIK.C2.AE_Authentication_Web_Service_USAM.svc|USAM]] is installed on the IIS Server.<br />
* Install the UBIK Archon Webservice on the IIS Server.<br />
* If the IIS Server does not have it installed, download and install the .NET 8.0 Hosting Bundle from Microsoft. This bundle includes the .NET Runtime and the ASP.NET Core Runtime required for hosting ASP.NET Core applications on IIS.<br />
* Make sure the URL Rewrite Module is installed on the IIS Server.<br />
* Make sure all files are accessible<br />
<br />
= Installation UBIK Archon =<br />
* Download the UBIK Archon Webservice from the release portal.<br />
* Deploy the UBIK Archon Webservice to the designated web app folder on the IIS Server (web app folder needs to be created if necessary)<br />
** IIS Manager setting check: see [[Configure_EventNotification_Endpoint_and_Enterprise_Service_for_CUI#IIS_Manager|IIS Manager]]<br />
<br />
== IIS Manager ==<br />
* Add a new website under the "Sites" folder in IIS Manager.<br />
** "Site Name", "Application pool", "Physical path", "Binding", "Host Name", "Port" and "SSL Certificate" should be adapted accordingly.<br />
* ''' Example settings'''. <br/> [[Image:IIS1.PNG|300px]]<br />
<br />
{{Hint| When setting up the IIS Application Pool responsible for the Archon Service the Load User Profile setting must be set to "true". This way Archon can create the necessary files under the specified User in the File System}}<br />
<br />
= Setting up UBIK Archon =<br />
<br />
== Firewall settings ==<br />
Firewall and Router settings must adapted so the Archon service can be accessible from outside of the IIS Server<br />
* A New Inbound rule must be created in the IIS Server "Firewall Settings", using the same "Port" as the one specified in the website "Binding" settings.<br />
* A new Port forwarding rule must also be added in the Router "Firewall Settings" using the same "Port" as the one specified in the website "Binding" settings.<br />
<br />
== Secret ==<br />
The secret must be defined once for an Archon Service.<br />
Even if the secret can be defined implicit by the very first time an USAM registers at the Archon we recommend to define the secret in advance using the following URL: <br />
<br />
<source lang = "xml"><br />
https://hostname:port/PathToArchon/api/admin/_put_your_secret_here<br />
</source><br />
<br />
== USAM ==<br />
The UBIK Archon URL must be configured in the USAM's AppSettings.config file, e.g.:<br />
<source lang = "xml"><br />
<appSettings><br />
<add key="UBIK.Service.ArchonUrl" value="https://hostname:port/api"/><br />
</appSettings><br />
</source><br />
<br />
== Connecting UBIK Archon with USAM ==<br />
The UBIK Archon service has to be connected to the USAM service. ''This must be done only once for each Database.'' This can be achieved using a URL schema, the user has to provide hostname:port/path to Usam service/ the method "register" and a couple of parameters. The list of parameters differ in newer Ubik Versions.<br />
<br />
=== Parameters until Version 4.9 ===<br />
* Parameter "secret": The "secret" is the password selected by the Archon Administrator.<br />
<br />
'''Example:'''<br />
<br />
The following example URL registers the UBIK Archon service on the USAM and the USAM on the Archon service:<br />
<source lang = "xml"><br />
https://hostname:port/PathToUsam/USAM.svc/register/_put_secret_here_<br />
</source><br />
<br />
=== Parameters since Version 5.0 ===<br />
* Parameter USAM-Name: human readable name of the USAM service. We recommend to use the name of the Usecase (e.g. "Productive System").<br />
* Parameter License - Mode: The license mode defines how a license is evaluated by the Archon for the given USAM :<br />
{| class="wikitable" width=50%<br />
|-<br />
! width=10% | Value !! width=20% | Mode !! Description <br />
|-<br />
| 0 || Standard || Archon compares Login Name and Device - ID.<br />
|-<br />
| 1 || Login || Archon compares Login Name only. The Device ID will be ignored.<br />
|-<br />
| 2 || Device || Archon compares Device ID only. The Login Name will be ignored.<br />
|}<br />
<br />
* Parameter "secret" (the "secret" is the password selected by the Archon Administrator). <br />
<br />
'''Example:'''<br />
<br />
The following example URL registers the UBIK Archon service on the USAM and the USAM on the Archon service:<br />
<source lang = "xml"><br />
https://hostname:port/PathToUsam/USAM.svc/register/_put_usam-name_here_/_put_license-mode_here_/_put_secret_here_<br />
</source><br />
<br />
{{Hint|One USAM can only be registered once. If you want to register it again or use a different Archon Service you need to unregister it first.}}<br />
{{Hint|A registration key is saved encrypted in the UBIK Database (as setting).}}<br />
<br />
=== Disconnecting an USAM from the Archon ===<br />
<br />
There is also the possibility to unconnect the USAM service from the Archon Service.<br />
<source lang = "xml"><br />
https://hostname:port/PathToUsam/USAM.svc/unregister<br />
</source><br />
<br />
= Using UBIK Archon =<br />
== Archon ==<br />
=== Archon Web UI ===<br />
Using swagger a test Web UI can be accessed.<br />
* ''' Example:''' <br />
<source lang = "XML"><br />
https://hostname:port/swagger/index.html<br />
</source><br />
<br />
=== How to fetch unique Archon Id ===<br />
* ''' Example using Postman Get:''' <br />
<source lang = "XML"><br />
https://hostname:port/api/admin/key<br />
</source><br />
== USAM ==<br />
=== Session Details ===<br />
The UBIK Archon service can provide detailed Session Information. Session details can be called using a web service method and will provide additional information about the currently active sessions:<br />
* How many users were logged in, <br />
* on which day, <br />
* with how many sessions, <br />
* how many users were online simultaneously, <br />
* and average session duration.<br />
<br />
'''Example:'''<br />
<br />
<source lang = "XML"><br />
https://hostname:port/PathToUsam/USAM.svc/session-details/2024.06-11/2024.06-11<br />
[<br />
{<br />
"AverageSessionDuration": 2,<br />
"Concurrent": 7,<br />
"Day": "/Date(1718056800000+0200)/",<br />
"Logins": 25,<br />
"Sessions": 48<br />
}<br />
]<br />
</source><br />
<br />
= Archon cannot be contacted =<br />
One of the most common reasons for being unable to contact the Archon or register a USAM is the WebDAV Publishing module, which may be preinstalled on the IIS server. This module interferes with the requests sent by the Archon, preventing certain methods from executing correctly. You can verify whether WebDAV is installed by checking the Server Manager on the IIS machine.<br />
<br />
To prevent this interference, you must explicitly '''disable WebDAV''' in the Archon’s web.config file.<br />
<source lang = "XML"><br />
<system.webServer><br />
<modules><br />
<remove name="WebDAVModule" /><br />
</modules><br />
</system.webServer><br />
</source><br />
<br />
<br/><br />
However, it’s very important to note that adding this configuration when the WebDAV module is not installed can also cause communication issues with the Archon. For that reason, only apply this configuration if you have confirmed that the WebDAV module is actually present on the IIS server.<br />
<br />
=See also=<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
* [[UBIK_LICENSE_MONITORING]]<br />
* [[HowTo:Configure_Microsoft_IIS_for_UBIK]]<br />
* [[HowTo:Install_Microsoft_IIS]]<br />
<br />
[[Category:Installing|Configure UBIK Archon Service]]<br />
[[Category:Login management|Configure UBIK Archon Service]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Configure_UBIK_Archon_Service&diff=29629Configure UBIK Archon Service2026-03-26T12:35:42Z<p>LDO: </p>
<hr />
<div>The UBIK.Archon WebService is the central information hub that is responsible for managing the set of available licenses for one subscription<br />
This page describes how to setup the system.<br />
<br />
= Overview =<br />
* Make sure the [[HowTo:Install_UBIK_Web_Service#UBIK.C2.AE_Authentication_Web_Service_USAM.svc|USAM]] is installed on the IIS Server.<br />
* Install the UBIK Archon Webservice on the IIS Server.<br />
* If the IIS server does not have it installed, download and install the .NET 8.0 Hosting Bundle from Microsoft. This bundle includes the .NET Runtime and the ASP.NET Core Runtime required for hosting ASP.NET Core applications on IIS.<br />
* Make sure the URL Rewrite Module is installed on the IIS Server.<br />
* Make sure all files are accessible<br />
<br />
= Installation UBIK Archon =<br />
* Download the UBIK Archon Webservice from the release portal.<br />
* Deploy the UBIK Archon Webservice to the designated web app folder on the IIS Server (web app folder needs to be created if necessary)<br />
** IIS Manager setting check: see [[Configure_EventNotification_Endpoint_and_Enterprise_Service_for_CUI#IIS_Manager|IIS Manager]]<br />
<br />
== IIS Manager ==<br />
* Add a new website under the "Sites" folder in IIS Manager.<br />
** "Site Name", "Application pool", "Physical path", "Binding", "Host Name", "Port" and "SSL Certificate" should be adapted accordingly.<br />
* ''' Example settings'''. <br/> [[Image:IIS1.PNG|300px]]<br />
<br />
{{Hint| When setting up the IIS Application Pool responsible for the Archon Service the Load User Profile setting must be set to "true". This way Archon can create the necessary files under the specified User in the File System}}<br />
<br />
= Setting up UBIK Archon =<br />
<br />
== Firewall settings ==<br />
Firewall and Router settings must adapted so the Archon service can be accessible from outside of the IIS Server<br />
* A New Inbound rule must be created in the IIS Server "Firewall Settings", using the same "Port" as the one specified in the website "Binding" settings.<br />
* A new Port forwarding rule must also be added in the Router "Firewall Settings" using the same "Port" as the one specified in the website "Binding" settings.<br />
<br />
== Secret ==<br />
The secret must be defined once for an Archon Service.<br />
Even if the secret can be defined implicit by the very first time an USAM registers at the Archon we recommend to define the secret in advance using the following URL: <br />
<br />
<source lang = "xml"><br />
https://hostname:port/PathToArchon/api/admin/_put_your_secret_here<br />
</source><br />
<br />
== USAM ==<br />
The UBIK Archon URL must be configured in the USAM's AppSettings.config file, e.g.:<br />
<source lang = "xml"><br />
<appSettings><br />
<add key="UBIK.Service.ArchonUrl" value="https://hostname:port/api"/><br />
</appSettings><br />
</source><br />
<br />
== Connecting UBIK Archon with USAM ==<br />
The UBIK Archon service has to be connected to the USAM service. ''This must be done only once for each Database.'' This can be achieved using a URL schema, the user has to provide hostname:port/path to Usam service/ the method "register" and a couple of parameters. The list of parameters differ in newer Ubik Versions.<br />
<br />
=== Parameters until Version 4.9 ===<br />
* Parameter "secret": The "secret" is the password selected by the Archon Administrator.<br />
<br />
'''Example:'''<br />
<br />
The following example URL registers the UBIK Archon service on the USAM and the USAM on the Archon service:<br />
<source lang = "xml"><br />
https://hostname:port/PathToUsam/USAM.svc/register/_put_secret_here_<br />
</source><br />
<br />
=== Parameters since Version 5.0 ===<br />
* Parameter USAM-Name: human readable name of the USAM service. We recommend to use the name of the Usecase (e.g. "Productive System").<br />
* Parameter License - Mode: The license mode defines how a license is evaluated by the Archon for the given USAM :<br />
{| class="wikitable" width=50%<br />
|-<br />
! width=10% | Value !! width=20% | Mode !! Description <br />
|-<br />
| 0 || Standard || Archon compares Login Name and Device - ID.<br />
|-<br />
| 1 || Login || Archon compares Login Name only. The Device ID will be ignored.<br />
|-<br />
| 2 || Device || Archon compares Device ID only. The Login Name will be ignored.<br />
|}<br />
<br />
* Parameter "secret" (the "secret" is the password selected by the Archon Administrator). <br />
<br />
'''Example:'''<br />
<br />
The following example URL registers the UBIK Archon service on the USAM and the USAM on the Archon service:<br />
<source lang = "xml"><br />
https://hostname:port/PathToUsam/USAM.svc/register/_put_usam-name_here_/_put_license-mode_here_/_put_secret_here_<br />
</source><br />
<br />
{{Hint|One USAM can only be registered once. If you want to register it again or use a different Archon Service you need to unregister it first.}}<br />
{{Hint|A registration key is saved encrypted in the UBIK Database (as setting).}}<br />
<br />
=== Disconnecting an USAM from the Archon ===<br />
<br />
There is also the possibility to unconnect the USAM service from the Archon Service.<br />
<source lang = "xml"><br />
https://hostname:port/PathToUsam/USAM.svc/unregister<br />
</source><br />
<br />
= Using UBIK Archon =<br />
== Archon ==<br />
=== Archon Web UI ===<br />
Using swagger a test Web UI can be accessed.<br />
* ''' Example:''' <br />
<source lang = "XML"><br />
https://hostname:port/swagger/index.html<br />
</source><br />
<br />
=== How to fetch unique Archon Id ===<br />
* ''' Example using Postman Get:''' <br />
<source lang = "XML"><br />
https://hostname:port/api/admin/key<br />
</source><br />
== USAM ==<br />
=== Session Details ===<br />
The UBIK Archon service can provide detailed Session Information. Session details can be called using a web service method and will provide additional information about the currently active sessions:<br />
* How many users were logged in, <br />
* on which day, <br />
* with how many sessions, <br />
* how many users were online simultaneously, <br />
* and average session duration.<br />
<br />
'''Example:'''<br />
<br />
<source lang = "XML"><br />
https://hostname:port/PathToUsam/USAM.svc/session-details/2024.06-11/2024.06-11<br />
[<br />
{<br />
"AverageSessionDuration": 2,<br />
"Concurrent": 7,<br />
"Day": "/Date(1718056800000+0200)/",<br />
"Logins": 25,<br />
"Sessions": 48<br />
}<br />
]<br />
</source><br />
<br />
= Archon cannot be contacted =<br />
One of the most common reasons for being unable to contact the Archon or register a USAM is the WebDAV Publishing module, which may be preinstalled on the IIS server. This module interferes with the requests sent by the Archon, preventing certain methods from executing correctly. You can verify whether WebDAV is installed by checking the Server Manager on the IIS machine.<br />
<br />
To prevent this interference, you must explicitly '''disable WebDAV''' in the Archon’s web.config file.<br />
<source lang = "XML"><br />
<system.webServer><br />
<modules><br />
<remove name="WebDAVModule" /><br />
</modules><br />
</system.webServer><br />
</source><br />
<br />
<br/><br />
However, it’s very important to note that adding this configuration when the WebDAV module is not installed can also cause communication issues with the Archon. For that reason, only apply this configuration if you have confirmed that the WebDAV module is actually present on the IIS server.<br />
<br />
=See also=<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
* [[UBIK_LICENSE_MONITORING]]<br />
* [[HowTo:Configure_Microsoft_IIS_for_UBIK]]<br />
* [[HowTo:Install_Microsoft_IIS]]<br />
<br />
[[Category:Installing|Configure UBIK Archon Service]]<br />
[[Category:Login management|Configure UBIK Archon Service]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Configure_UBIK_Archon_Service&diff=29628Configure UBIK Archon Service2026-03-26T12:33:01Z<p>LDO: </p>
<hr />
<div>The UBIK.Archon WebService is the central information hub that is responsible for managing the set of available licenses for one subscription<br />
This page describes how to setup the system.<br />
<br />
= Overview =<br />
* Make sure the [[HowTo:Install_UBIK_Web_Service#UBIK.C2.AE_Authentication_Web_Service_USAM.svc|USAM]] is installed on the IIS Server.<br />
* Install the UBIK Archon Webservice on the IIS Server.<br />
* If the IIS server does not have it installed, download and install the .NET 8.0 Hosting Bundle from Microsoft. This bundle includes the .NET Runtime and the ASP.NET Core Runtime required for hosting ASP.NET Core applications on IIS.<br />
* Make sure the URL Rewrite Module is installed on the IIS Server.<br />
* Make sure all files are accessible<br />
<br />
= Installation UBIK Archon =<br />
* Download the UBIK Archon Webservice from the release portal.<br />
* Deploy the UBIK Archon Webservice to the designated web app folder on the IIS Server (web app folder needs to be created if necessary)<br />
** IIS Manager setting check: see [[Configure_EventNotification_Endpoint_and_Enterprise_Service_for_CUI#IIS_Manager|IIS Manager]]<br />
<br />
== IIS Manager ==<br />
* Add a new website under the "Sites" folder in IIS Manager.<br />
** "Site Name", "Application pool", "Physical path", "Binding", "Host Name", "Port" and "SSL Certificate" should be adapted accordingly.<br />
* ''' Example settings'''. <br/> [[Image:IIS1.PNG|300px]]<br />
<br />
{{Hint| When setting up the IIS Application Pool responsible for the Archon Service the Load User Profile setting must be set to "true". This way Archon can create the necessary files under the specified User in the File System}}<br />
<br />
= Setting up UBIK Archon =<br />
<br />
== Firewall settings ==<br />
Firewall and Router settings must adapted so the Archon service can be accessible from outside of the IIS Server<br />
* A New Inbound rule must be created in the IIS Server "Firewall Settings", using the same "Port" as the one specified in the website "Binding" settings.<br />
* A new Port forwarding rule must also be added in the Router "Firewall Settings" using the same "Port" as the one specified in the website "Binding" settings.<br />
<br />
== Secret ==<br />
The secret must be defined once for an Archon Service.<br />
Even if the secret can be defined implicit by the very first time an USAM registers at the Archon we recommend to define the secret in advance using the following URL: <br />
<br />
<source lang = "xml"><br />
https://hostname:port/PathToArchon/api/admin/_put_your_secret_here<br />
</source><br />
<br />
== USAM ==<br />
The UBIK Archon URL must be configured in the USAM's AppSettings.config file, e.g.:<br />
<source lang = "xml"><br />
<appSettings><br />
<add key="UBIK.Service.ArchonUrl" value="https://hostname:port/api"/><br />
</appSettings><br />
</source><br />
<br />
== Connecting UBIK Archon with USAM ==<br />
The UBIK Archon service has to be connected to the USAM service. ''This must be done only once for each Database.'' This can be achieved using a URL schema, the user has to provide hostname:port/path to Usam service/ the method "register" and a couple of parameters. The list of parameters differ in newer Ubik Versions.<br />
<br />
=== Parameters until Version 4.9 ===<br />
* Parameter "secret": The "secret" is the password selected by the Archon Administrator.<br />
<br />
'''Example:'''<br />
<br />
The following example URL registers the UBIK Archon service on the USAM and the USAM on the Archon service:<br />
<source lang = "xml"><br />
https://hostname:port/PathToUsam/USAM.svc/register/_put_secret_here_<br />
</source><br />
<br />
=== Parameters since Version 5.0 ===<br />
* Parameter USAM-Name: human readable name of the USAM service. We recommend to use the name of the Usecase (e.g. "Productive System").<br />
* Parameter License - Mode: The license mode defines how a license is evaluated by the Archon for the given USAM :<br />
{| class="wikitable" width=50%<br />
|-<br />
! width=10% | Value !! width=20% | Mode !! Description <br />
|-<br />
| 0 || Standard || Archon compares Login Name and Device - ID.<br />
|-<br />
| 1 || Login || Archon compares Login Name only. The Device ID will be ignored.<br />
|-<br />
| 2 || Device || Archon compares Device ID only. The Login Name will be ignored.<br />
|}<br />
<br />
* Parameter "secret" (the "secret" is the password selected by the Archon Administrator). <br />
<br />
'''Example:'''<br />
<br />
The following example URL registers the UBIK Archon service on the USAM and the USAM on the Archon service:<br />
<source lang = "xml"><br />
https://hostname:port/PathToUsam/USAM.svc/register/_put_usam-name_here_/_put_license-mode_here_/_put_secret_here_<br />
</source><br />
<br />
{{Hint|One USAM can only be registered once. If you want to register it again or use a different Archon Service you need to unregister it first.}}<br />
{{Hint|A registration key is saved encrypted in the UBIK Database (as setting).}}<br />
<br />
=== Disconnecting an USAM from the Archon ===<br />
<br />
There is also the possibility to unconnect the USAM service from the Archon Service.<br />
<source lang = "xml"><br />
https://hostname:port/PathToUsam/USAM.svc/unregister<br />
</source><br />
<br />
= Using UBIK Archon =<br />
== Archon ==<br />
=== Archon Web UI ===<br />
Using swagger a test Web UI can be accessed.<br />
* ''' Example:''' <br />
<source lang = "XML"><br />
https://hostname:port/swagger/index.html<br />
</source><br />
<br />
=== How to fetch unique Archon Id ===<br />
* ''' Example using Postman Get:''' <br />
<source lang = "XML"><br />
https://hostname:port/api/admin/key<br />
</source><br />
== USAM ==<br />
=== Session Details ===<br />
The UBIK Archon service can provide detailed Session Information. Session details can be called using a web service method and will provide additional information about the currently active sessions:<br />
* How many users were logged in, <br />
* on which day, <br />
* with how many sessions, <br />
* how many users were online simultaneously, <br />
* and average session duration.<br />
<br />
'''Example:'''<br />
<br />
<source lang = "XML"><br />
https://hostname:port/PathToUsam/USAM.svc/session-details/2024.06-11/2024.06-11<br />
[<br />
{<br />
"AverageSessionDuration": 2,<br />
"Concurrent": 7,<br />
"Day": "/Date(1718056800000+0200)/",<br />
"Logins": 25,<br />
"Sessions": 48<br />
}<br />
]<br />
</source><br />
<br />
=== Archon cannot be contacted ===<br />
One of the most common reasons for being unable to contact the Archon or register a USAM is the WebDAV Publishing module, which may be preinstalled on the IIS server. This module interferes with the requests sent by the Archon, preventing certain methods from executing correctly. You can verify whether WebDAV is installed by checking the Server Manager on the IIS machine.<br />
<br />
To prevent this interference, you must explicitly '''disable WebDAV''' in the Archon’s web.config file.<br />
<source lang = "XML"><br />
<system.webServer><br />
<modules><br />
<remove name="WebDAVModule" /><br />
</modules><br />
</system.webServer><br />
</source><br />
<br />
<br/><br />
However, it’s very important to note that adding this configuration when the WebDAV module is not installed can also cause communication issues with the Archon. For that reason, only apply this configuration if you have confirmed that the WebDAV module is actually present on the IIS server.<br />
<br />
=See also=<br />
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --><br />
* [[UBIK_LICENSE_MONITORING]]<br />
* [[HowTo:Configure_Microsoft_IIS_for_UBIK]]<br />
* [[HowTo:Install_Microsoft_IIS]]<br />
<br />
[[Category:Installing|Configure UBIK Archon Service]]<br />
[[Category:Login management|Configure UBIK Archon Service]]</div>LDOhttps://wiki.augmensys.com/index.php?title=SYSCLS_MIN_MAX_CLASSIFICATION&diff=28608SYSCLS MIN MAX CLASSIFICATION2025-09-04T10:12:10Z<p>LDO: </p>
<hr />
<div>{{ClassificationInfoBox<br />
| title = Min/Max Classification Object <br />
| name = {{PAGENAMEE}}<br />
| inheritance = -<br />
| namespace = System.Classification.Content<br />
| purpose = Classify properties as Min/Max to extend the set of values.<br />
| version = 4.7.0+<br />
| id = {233C318B-45E0-4C4D-A37A-5547D2F83226}<br />
}}<br />
<br />
If a property is classified as Min/Max property, it will have 2 values (Min - Value and Max - Value)<br />
<br />
== Implementation ==<br />
To classify a property using the Min/Max fields, simply set the VALUE_TYPE of the respective property to 'MinMax'. The system will automatically apply the classification, which can then be reviewed in the ACM Manager.<br />
<br />
== See also ==<br />
* [[HowTo:Create_a_new_MetaProperty#VALUE_TYPE|Value Type]]<br />
<br />
<br />
{{Category/Version|4.7.0}}<br />
<br />
[[Category:4.7.0|Min Max]]</div>LDOhttps://wiki.augmensys.com/index.php?title=SYSCLS_MIN_NORM_MAX_CLASSIFICATION&diff=28607SYSCLS MIN NORM MAX CLASSIFICATION2025-09-04T10:11:49Z<p>LDO: </p>
<hr />
<div>{{ClassificationInfoBox<br />
| title = Min/Norm/Max Classification Object <br />
| name = {{PAGENAMEE}}<br />
| inheritance = -<br />
| namespace = System.Classification.Content<br />
| purpose = Classify properties as Min/Norm/Max to extend the set of values.<br />
| version = 4.7.0+<br />
| id = {DCD66C9E-8B98-4535-A7A3-792B6A47FFDD}<br />
}}<br />
<br />
If a property is classified as Min/Norm/Max property, it will have three values (Min - Value, Normal - Value and Max - Value)<br />
<br />
== Implementation ==<br />
To classify a property using the Min/Norm/Max fields, simply set the VALUE_TYPE of the respective property to 'MinNormMax'. The system will automatically apply the classification, which can then be reviewed in the ACM Manager.<br />
<br />
== See also ==<br />
* [[HowTo:Create_a_new_MetaProperty#VALUE_TYPE|Value Type]]<br />
<br />
<br />
{{Category/Version|4.7.0}}<br />
<br />
[[Category:4.7.0|Min Value Max]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Import_Runs&diff=28479Import Runs2025-08-11T10:03:21Z<p>LDO: </p>
<hr />
<div>{{Attention|This page is under construction.}}<br />
= Equipment Import =<br />
<br />
To import Equipments following columns are required:<br />
* EquipmentID (Text)<br />
<br />
'''NOTE:''' “CoordinateLong”, “CoordinateLat” and “CoordinateAltitude” must be formatted as Number!<br />
<br />
Columns that can be imported additionally:<br />
* PIDNumber (Text)<br />
* Medium (Text)<br />
* System (Text)<br />
* SystemDescription (Text)<br />
* PlanNumber (Text)<br />
* GridCode (Text)<br />
* Location (Text)<br />
* LocationStage (Text)<br />
* LocationHeight (Text)<br />
* Plant (Text)<br />
* Tag_Nr (Text)<br />
* EquipmentDescription (Text)<br />
* Maint_Plant (Text)<br />
* AssistingSystem1 (Text)<br />
* AssistingSystem2 (Text)<br />
* Subsystem (Text)<br />
* SubsystemDescription (Text)<br />
* Zone (Text)<br />
* CoordinateLong (Number)<br />
* CoordinateLat (Number)<br />
* CoordinateAltitude (Number)<br />
* PrioritySAP (Text)<br />
* EquipmentType (Text)<br />
* EquipmentGroup (Text)<br />
<br />
= Workorder Import =<br />
<br />
<br />
To import WorkOrders following column is required:<br />
* Workorder (Text)<br />
<br />
<br />
Columns that can be imported additionally:<br />
* EquipmentID (Text)<br />
* Description (Text)<br />
* WBS (Text)<br />
* Comment (Text)<br />
* Longtext (Text)<br />
* DrainlistDocument (Text)<br />
<br />
<br />
Following columns are optional, as we recommend to import them directly using the Equipment.import instead:<br />
* EquipmentType (Text)<br />
* EquipmentGroup (Text)<br />
<br />
<br />
<br />
= Progress Operation Import =<br />
<br />
To import Operations following columns are required:<br />
* OperationID (Text)<br />
<br />
'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!<br />
<br />
Columns that can be imported additionally:<br />
* Workorder (Text)<br />
* Operation (Text)<br />
* ShortText (Text)<br />
* Number (Number)<br />
* NormalDuration (Number)<br />
* NormalDurationUnit (Text)<br />
* Work (Number)<br />
* WorkUnit (Text)<br />
* Workcenter (Text)<br />
* ActivityCode (Text)<br />
* eStart (TT/MM/JJJJ hh:mm)<br />
* eFinish (TT/MM/JJJJ hh:mm)<br />
* lStart (TT/MM/JJJJ hh:mm)<br />
* lFinish (TT/MM/JJJJ hh:mm)<br />
* Company (Text)<br />
* CompanyCode (Text)<br />
* LongText (Text)<br />
* Comment (Text)<br />
* PermitCode (Text)<br />
* Planner (Text)<br />
* Suboperation (Text)<br />
<br />
<br />
<br />
= QRF Operation Import =<br />
<br />
To import Operations following columns are required:<br />
* OperationID (Text)<br />
<br />
'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!<br />
<br />
Columns that can be imported additionally:<br />
* Workorder (Text)<br />
* Operation (Text)<br />
* ShortText (Text)<br />
* Number (Number)<br />
* NormalDuration (Number)<br />
* NormalDurationUnit (Text)<br />
* Work (Number)<br />
* WorkUnit (Text)<br />
* Workcenter (Text)<br />
* ActivityCode (Text)<br />
* eStart (TT/MM/JJJJ hh:mm)<br />
* eFinish (TT/MM/JJJJ hh:mm)<br />
* lStart (TT/MM/JJJJ hh:mm)<br />
* lFinish (TT/MM/JJJJ hh:mm)<br />
* Company (Text)<br />
* CompanyCode (Text)<br />
* LongText (Text)<br />
* Comment (Text)<br />
* PermitCode (Text)<br />
* Planner (Text)<br />
* Suboperation (Text)<br />
* QRFKey (Text)<br />
* QRFDescription (Text)<br />
<br />
<br />
<br />
= Check Operation Import =<br />
<br />
To import Operations following columns are required:<br />
* OperationID (Text)<br />
<br />
'''NOTE:''' “Number” and “NormalDuration” must be formatted as Number and all dates must be formatted as TT/MM/JJJJ hh:mm!<br />
<br />
Columns that can be imported additionally:<br />
* Workorder (Text)<br />
* Operation (Text)<br />
* ShortText (Text)<br />
* Number (Number)<br />
* NormalDuration (Number)<br />
* NormalDurationUnit (Text)<br />
* Work (Number)<br />
* WorkUnit (Text)<br />
* Workcenter (Text)<br />
* ActivityCode (Text)<br />
* eStart (TT/MM/JJJJ hh:mm)<br />
* eFinish (TT/MM/JJJJ hh:mm)<br />
* lStart (TT/MM/JJJJ hh:mm)<br />
* lFinish (TT/MM/JJJJ hh:mm)<br />
* Company (Text)<br />
* CompanyCode (Text)<br />
* LongText (Text)<br />
* Comment (Text)<br />
* PermitCode (Text)<br />
* Planner (Text)<br />
* Suboperation (Text)<br />
<br />
<br />
<br />
= Scheduling Import (for Operations)=<br />
<br />
To import scheduling data of Operations the following columns are required:<br />
* OperationID (Text)<br />
<br />
'''NOTE:''' All dates must be formatted as TT/MM/JJJJ hh:mm!<br />
<br />
Columns that can be imported additionally:<br />
* eStart (TT/MM/JJJJ hh:mm)<br />
* eFinish (TT/MM/JJJJ hh:mm)<br />
* lStart (TT/MM/JJJJ hh:mm)<br />
* lFinish (TT/MM/JJJJ hh:mm)<br />
<br />
= User Import =<br />
<br />
To import users following columns are required:<br />
* DesktopLogin (Text)<br />
<br />
Columns that can be imported additionally:<br />
* Name (Text) <br />
* NFC (Text)<br />
* MobileLogin (Text)<br />
* Password (Text) <br />
* CompanyCode (Text)<br />
* ReportingUserrights (Text)<br />
* PunchpointUserrights (Text) <br />
* ScopechangeUserrights (Text) <br />
* SuperuserUserrights (Text) <br />
* Comment (Text)<br />
* Position (Text) <br />
* Availability (Text) <br />
* Adress (Text) <br />
* Skype (Text)<br />
* Telephone (Text)<br />
* Email (Text)<br />
<br />
= Company Import =<br />
<br />
To import companies following columns are required:<br />
* CompanyCode (Text)<br />
<br />
Columns that can be imported additionally:<br />
* Company (Text)<br />
<br />
= Material Import =<br />
<br />
To import materials following columns are required:<br />
* OperationId (Text)<br />
* MaterialNr (Text)<br />
<br />
'''NOTE:''' “Quantity” must be formatted as Number!<br />
<br />
Columns that can be imported additionally:<br />
* MaterialDescr (Text)<br />
* BOMItemNr (Text)<br />
* ItemCategory (Text)<br />
'''NOTE:''' To ensure the correct icon is displayed on the client, the “ItemCategory” must have a value of either '0' which is translated to Category Stock or '1' which is translated to Category Skid!<br />
* Quantity (Number)<br />
* Unit (Text)<br />
* ReservationStatus (Text)<br />
<br />
= Preparation Document Import =<br />
<br />
To import materials following columns are required:<br />
* Workorder (Text)<br />
* FilePath (Text)<br />
<br />
Columns that can be imported additionally:<br />
* FileName (Text)<br />
<br />
{{Attention|This page is under construction.}}<br />
<br />
[[Category:MaTaP|Import Runs]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Auto_Deletion&diff=28166Auto Deletion2025-05-13T10:55:17Z<p>LDO: </p>
<hr />
<div>UBIK includes a configurable approach to automatic instance deletion, allowing flexibility in managing different MetaClasses.<br />
This can be done via the MetaClass DELETE_CONFIGURATION which is provided from a UBIK database and can be found under System.Main.Base.<br />
<br />
The deletion configuration is divided into two main categories:<br />
===Soft Deletion===<br />
A soft delete limit can be set, specifying the number of days beyond which records older than the CTS (Creation Timestamp) will be marked as soft-deleted. When an instance undergoes soft deletion, its delete status is updated to deleted, making it invisible within UBIK. However, the record remains in the SQL database, where it is marked as deleted for reference purposes.<br />
<br />
===Hard Deletion===<br />
''(Not Yet Functional)'' A hard delete limit can be configured, specifying the number of days where soft-deleted records are marked as hard-deleted and can be permanently removed from the database. While soft deletion is currently functional, hard deletion is planned for future implementation. <br />
<br />
====Example====<br />
Delete Configuration for the Progress Task MetaClass where limit is set to 30 days<br />
[[File:Example_DeleteConfig.png]] <br />
<br /> <br />
Result: All Instances of this MetaClass which have an older CTS than 30 days will be marked for soft-deletion.<br />
<br />
===Deletion Workflow===<br />
The DeleteManager component needs to be initialized (via WhoBert for example) to handle the deletion process.<br />
Within the DeleteManager, this method must be executed:<br />
<br />
ExecuteSoftDelete: This method itertaes through all instances which are marked for soft-deletion, updates the instance's delete status and ensures it can no longer be accessed in UBIK Studio while retaining the record in SQL for reference.<br />
Future steps involve finalizing the DeleteManager and implementing hard deletion to complete the workflow.<br />
<br />
<source lang = "csharp"><br />
DeleteManager delmanager = new DeleteManager();<br />
delManager.ExecuteSoftDelete();<br />
</source></div>LDOhttps://wiki.augmensys.com/index.php?title=Auto_Deletion&diff=28165Auto Deletion2025-05-13T10:52:32Z<p>LDO: </p>
<hr />
<div>UBIK includes a configurable approach to automatic instance deletion, allowing flexibility in managing different MetaClasses.<br />
This can be done via the MetaClass DELETE_CONFIGURATION which is provided from a UBIK database and can be found under System.Main.Base.<br />
<br />
The deletion configuration is divided into two main categories:<br />
===Soft Deletion===<br />
A soft delete limit can be set, specifying the number of days beyond which records older than the CTS (Creation Timestamp) will be marked as soft-deleted. When an instance undergoes soft deletion, its delete status is updated to deleted, making it invisible within UBIK. However, the record remains in the SQL database, where it is marked as deleted for reference purposes.<br />
<br />
===Hard Deletion===<br />
''(Not Yet Functional)'' A hard delete limit can be configured, specifying the number of days where soft-deleted records are marked as hard-deleted and can be permanently removed from the database. While soft deletion is currently functional, hard deletion is planned for future implementation. <br />
<br />
====Example====<br />
Delete Configuration for the Progress Task MetaClass where limit is set to 30 days<br />
[[File:Example_DeleteConfig.png]] <br />
<br /> <br />
Result: All Instances of this MetaClass which have an older CTS than 30 days will be marked for soft-deletion.<br />
<br />
===Deletion Workflow===<br />
The DeleteManager component needs to be initialized (via WhoBert for example) to handle the deletion process.<br />
Within the DeleteManager, this method must be executed:<br />
<br />
ExecuteSoftDelete: This method updates the record's delete status and ensures it can no longer be accessed in UBIK Studio while retaining the record in SQL for reference.<br />
Future steps involve finalizing the DeleteManager and implementing hard deletion to complete the workflow.<br />
<br />
<source lang = "csharp"><br />
DeleteManager delmanager = new DeleteManager();<br />
delManager.ExecuteSoftDelete();<br />
</source></div>LDOhttps://wiki.augmensys.com/index.php?title=Auto_Deletion&diff=28164Auto Deletion2025-05-13T10:49:49Z<p>LDO: </p>
<hr />
<div>UBIK includes a configurable approach to automatic instance deletion, allowing flexibility in managing different MetaClasses.<br />
This can be done via the MetaClass DELETE_CONFIGURATION which is provided from a UBIK database and can be found under System.Main.Base.<br />
<br />
The deletion configuration is divided into two main categories:<br />
===Soft Deletion===<br />
A soft delete limit can be set, specifying the number of days beyond which records older than the CTS (Creation Timestamp) will be marked as soft-deleted. When an instance undergoes soft deletion, its delete status is updated to deleted, making it invisible within UBIK. However, the record remains in the SQL database, where it is marked as deleted for reference purposes.<br />
<br />
===Hard Deletion===<br />
''(Not Yet Functional)'' A hard delete limit can be configured, specifying the number of days where soft-deleted records are marked as hard-deleted and can be permanently removed from the database. While soft deletion is currently functional, hard deletion is planned for future implementation. <br />
<br />
====Example====<br />
Delete Configuration for the Progress Task MetaClass where limit is set to 30 days<br />
[[File:Example_DeleteConfig.png]] <br />
<br /> <br />
Result: All Instances of this MetaClass which have an older CTS than 30 days will be marked for soft-deletion.<br />
<br />
===Deletion Workflow===<br />
The DeleteManager component needs to be initialized (via WhoBert for example) to handle the deletion process.<br />
Within the DeleteManager, this method must be executed:<br />
<br />
ExecuteSoftDelete: This method updates the record's delete status and ensures it can no longer be accessed in UBIK Studio while retaining the record in SQL for reference.<br />
Future steps involve finalizing the DeleteManager and implementing hard deletion to complete the workflow.<br />
<br />
<source lang = "csharp"><br />
DeleteManager delmanager = new DeleteManager();<br />
delManager.ExecuteSoftDelete();<br />
</source><br />
<br />
[[Category:Pages with broken file links|Auto Deletion]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Auto_Deletion&diff=28163Auto Deletion2025-05-13T10:49:31Z<p>LDO: </p>
<hr />
<div>UBIK includes a configurable approach to automatic instance deletion, allowing flexibility in managing different MetaClasses.<br />
This can be done via the MetaClass DELETE_CONFIGURATION which is provided from a UBIK database and can be found under System.Main.Base.<br />
<br />
The deletion configuration is divided into two main categories:<br />
===Soft Deletion===<br />
A soft delete limit can be set, specifying the number of days beyond which records older than the CTS (Creation Timestamp) will be marked as soft-deleted. When an instance undergoes soft deletion, its delete status is updated to deleted, making it invisible within UBIK. However, the record remains in the SQL database, where it is marked as deleted for reference purposes.<br />
<br />
===Hard Deletion===<br />
''(Not Yet Functional)'' A hard delete limit can be configured, specifying the number of days where soft-deleted records are marked as hard-deleted and can be permanently removed from the database. While soft deletion is currently functional, hard deletion is planned for future implementation. <br />
<br />
====Example====<br />
Delete Configuration for the Progress Task MetaClass where limit is set to 30 days<br />
[[File:Example_DeleteConfig.png]] <br />
Result: All Instances of this MetaClass which have an older CTS than 30 days will be marked for soft-deletion.<br />
<br />
===Deletion Workflow===<br />
The DeleteManager component needs to be initialized (via WhoBert for example) to handle the deletion process.<br />
Within the DeleteManager, this method must be executed:<br />
<br />
ExecuteSoftDelete: This method updates the record's delete status and ensures it can no longer be accessed in UBIK Studio while retaining the record in SQL for reference.<br />
Future steps involve finalizing the DeleteManager and implementing hard deletion to complete the workflow.<br />
<br />
<source lang = "csharp"><br />
DeleteManager delmanager = new DeleteManager();<br />
delManager.ExecuteSoftDelete();<br />
</source><br />
<br />
[[Category:Pages with broken file links|Auto Deletion]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Auto_Deletion&diff=28162Auto Deletion2025-05-13T10:48:44Z<p>LDO: </p>
<hr />
<div>UBIK includes a configurable approach to automatic instance deletion, allowing flexibility in managing different MetaClasses.<br />
This can be done via the MetaClass DELETE_CONFIGURATION which is provided from a UBIK database and can be found under System.Main.Base.<br />
<br />
The deletion configuration is divided into two main categories:<br />
===Soft Deletion===<br />
A soft delete limit can be set, specifying the number of days beyond which records older than the CTS (Creation Timestamp) will be marked as soft-deleted. When an instance undergoes soft deletion, its delete status is updated to deleted, making it invisible within UBIK. However, the record remains in the SQL database, where it is marked as deleted for reference purposes.<br />
<br />
===Hard Deletion===<br />
''(Not Yet Functional)'' A hard delete limit can be configured, specifying the number of days where soft-deleted records are marked as hard-deleted and can be permanently removed from the database. While soft deletion is currently functional, hard deletion is planned for future implementation. <br />
<br />
====Example====<br />
Delete Configuration for the Progress Task MetaClass where limit is set to 30 days<br />
[[File:DeleteConfigExample.PNG]]<br />
Result: All Instances of this MetaClass which have an older CTS than 30 days will be marked for soft-deletion.<br />
<br />
===Deletion Workflow===<br />
The DeleteManager component needs to be initialized (via WhoBert for example) to handle the deletion process.<br />
Within the DeleteManager, this method must be executed:<br />
<br />
ExecuteSoftDelete: This method updates the record's delete status and ensures it can no longer be accessed in UBIK Studio while retaining the record in SQL for reference.<br />
Future steps involve finalizing the DeleteManager and implementing hard deletion to complete the workflow.<br />
<br />
<source lang = "csharp"><br />
DeleteManager delmanager = new DeleteManager();<br />
delManager.ExecuteSoftDelete();<br />
</source><br />
<br />
[[Category:Pages with broken file links|Auto Deletion]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Auto_Deletion&diff=28161Auto Deletion2025-05-13T10:48:14Z<p>LDO: </p>
<hr />
<div>UBIK includes a configurable approach to automatic instance deletion, allowing flexibility in managing different MetaClasses.<br />
This can be done via the MetaClass DELETE_CONFIGURATION which is provided from a UBIK database and can be found under System.Main.Base.<br />
<br />
The deletion configuration is divided into two main categories:<br />
===Soft Deletion===<br />
A soft delete limit can be set, specifying the number of days beyond which records older than the CTS (Creation Timestamp) will be marked as soft-deleted. When an instance undergoes soft deletion, its delete status is updated to deleted, making it invisible within UBIK. However, the record remains in the SQL database, where it is marked as deleted for reference purposes.<br />
<br />
===Hard Deletion===<br />
''(Not Yet Functional)'' A hard delete limit can be configured, specifying the number of days where soft-deleted records are marked as hard-deleted and can be permanently removed from the database. While soft deletion is currently functional, hard deletion is planned for future implementation. <br />
<br />
====Example====<br />
Delete Configuration for the Progress Task MetaClass where limit is set to 30 days<br />
[[File:Example DeleteConfig.PNG]]<br />
Result: All Instances of this MetaClass which have an older CTS than 30 days will be marked for soft-deletion.<br />
<br />
===Deletion Workflow===<br />
The DeleteManager component needs to be initialized (via WhoBert for example) to handle the deletion process.<br />
Within the DeleteManager, this method must be executed:<br />
<br />
ExecuteSoftDelete: This method updates the record's delete status and ensures it can no longer be accessed in UBIK Studio while retaining the record in SQL for reference.<br />
Future steps involve finalizing the DeleteManager and implementing hard deletion to complete the workflow.<br />
<br />
<source lang = "csharp"><br />
DeleteManager delmanager = new DeleteManager();<br />
delManager.ExecuteSoftDelete();<br />
</source><br />
<br />
[[Category:Pages with broken file links|Auto Deletion]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Auto_Deletion&diff=28160Auto Deletion2025-05-13T10:45:12Z<p>LDO: </p>
<hr />
<div>UBIK includes a configurable approach to automatic instance deletion, allowing flexibility in managing different MetaClasses.<br />
This can be done via the MetaClass DELETE_CONFIGURATION which is provided from a UBIK database and can be found under System.Main.Base.<br />
<br />
The deletion configuration is divided into two main categories:<br />
===Soft Deletion===<br />
A soft delete limit can be set, specifying the number of days beyond which records older than the CTS (Creation Timestamp) will be marked as soft-deleted. When an instance undergoes soft deletion, its delete status is updated to deleted, making it invisible within UBIK. However, the record remains in the SQL database, where it is marked as deleted for reference purposes.<br />
<br />
===Hard Deletion===<br />
''(Not Yet Functional)'' A hard delete limit can be configured, specifying the number of days where soft-deleted records are marked as hard-deleted and can be permanently removed from the database. While soft deletion is currently functional, hard deletion is planned for future implementation. <br />
<br />
====Example====<br />
Delete Configuration for the Progress Task MetaClass where limit is set to 30 days<br />
[[File:Example_DeleteConfig.PNG]]<br />
Result: All Instances of this MetaClass which have an older CTS than 30 days will be marked for soft-deletion.<br />
<br />
===Deletion Workflow===<br />
The DeleteManager component needs to be initialized (via WhoBert for example) to handle the deletion process.<br />
Within the DeleteManager, this method must be executed:<br />
<br />
ExecuteSoftDelete: This method updates the record's delete status and ensures it can no longer be accessed in UBIK Studio while retaining the record in SQL for reference.<br />
Future steps involve finalizing the DeleteManager and implementing hard deletion to complete the workflow.<br />
<br />
<source lang = "csharp"><br />
DeleteManager delmanager = new DeleteManager();<br />
delManager.ExecuteSoftDelete();<br />
</source><br />
<br />
[[Category:Pages with broken file links|Auto Deletion]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Auto_Deletion&diff=28159Auto Deletion2025-05-13T10:44:42Z<p>LDO: </p>
<hr />
<div>UBIK includes a configurable approach to automatic instance deletion, allowing flexibility in managing different MetaClasses.<br />
This can be done via the MetaClass DELETE_CONFIGURATION which is provided from a UBIK database and can be found under System.Main.Base.<br />
<br />
The deletion configuration is divided into two main categories:<br />
===Soft Deletion===<br />
A soft delete limit can be set, specifying the number of days beyond which records older than the CTS (Creation Timestamp) will be marked as soft-deleted. When an instance undergoes soft deletion, its delete status is updated to deleted, making it invisible within UBIK. However, the record remains in the SQL database, where it is marked as deleted for reference purposes.<br />
<br />
===Hard Deletion===<br />
''(Not Yet Functional)'' A hard delete limit can be configured, specifying the number of days where soft-deleted records are marked as hard-deleted and can be permanently removed from the database. While soft deletion is currently functional, hard deletion is planned for future implementation. <br />
<br />
Example: Delete Configuration for the Progress Task MetaClass where limit is set to 30 days<br />
[[File:Example_DeleteConfig.PNG]]<br />
Result: All Instances of this MetaClass which have an older CTS than 30 days will be marked for soft-deletion.<br />
<br />
===Deletion Workflow===<br />
The DeleteManager component needs to be initialized (via WhoBert for example) to handle the deletion process.<br />
Within the DeleteManager, this method must be executed:<br />
<br />
ExecuteSoftDelete: This method updates the record's delete status and ensures it can no longer be accessed in UBIK Studio while retaining the record in SQL for reference.<br />
Future steps involve finalizing the DeleteManager and implementing hard deletion to complete the workflow.<br />
<br />
<source lang = "csharp"><br />
DeleteManager delmanager = new DeleteManager();<br />
delManager.ExecuteSoftDelete();<br />
</source><br />
<br />
[[Category:Pages with broken file links|Auto Deletion]]</div>LDOhttps://wiki.augmensys.com/index.php?title=File:Example_DeleteConfig.png&diff=28158File:Example DeleteConfig.png2025-05-13T10:43:55Z<p>LDO: </p>
<hr />
<div></div>LDOhttps://wiki.augmensys.com/index.php?title=Auto_Deletion&diff=28157Auto Deletion2025-05-13T10:41:53Z<p>LDO: </p>
<hr />
<div>UBIK includes a configurable approach to automatic instance deletion, allowing flexibility in managing different MetaClasses.<br />
This can be done via the MetaClass DELETE_CONFIGURATION which is provided from a UBIK database and can be found under System.Main.Base.<br />
<br />
The deletion configuration is divided into two main categories:<br />
===Soft Deletion===<br />
A soft delete limit can be set, specifying the number of days beyond which records older than the CTS (Creation Timestamp) will be marked as soft-deleted. When an instance undergoes soft deletion, its delete status is updated to deleted, making it invisible within UBIK. However, the record remains in the SQL database, where it is marked as deleted for reference purposes.<br />
<br />
===Hard Deletion===<br />
''(Not Yet Functional)'' A hard delete limit can be configured, specifying the number of days where soft-deleted records are marked as hard-deleted and can be permanently removed from the database. While soft deletion is currently functional, hard deletion is planned for future implementation. <br />
<br />
Example: Delete Configuration for the Progress Task MetaClass where limit is set to 30 days<br />
[[File:Example_DeleteConfig.png|350x100px]]<br />
Result: All Instances of this MetaClass which have an older CTS than 30 days will be marked for soft-deletion.<br />
<br />
===Deletion Workflow===<br />
The DeleteManager component needs to be initialized (via WhoBert for example) to handle the deletion process.<br />
Within the DeleteManager, this method must be executed:<br />
<br />
ExecuteSoftDelete: This method updates the record's delete status and ensures it can no longer be accessed in UBIK Studio while retaining the record in SQL for reference.<br />
Future steps involve finalizing the DeleteManager and implementing hard deletion to complete the workflow.<br />
<br />
<source lang = "csharp"><br />
DeleteManager delmanager = new DeleteManager();<br />
delManager.ExecuteSoftDelete();<br />
</source><br />
<br />
[[Category:Pages with broken file links|Auto Deletion]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Auto_Deletion&diff=28156Auto Deletion2025-05-13T10:39:41Z<p>LDO: Created page with "UBIK includes a configurable approach to automatic instance deletion, allowing flexibility in managing different MetaClasses. This can be done via the MetaClass DELETE_CONFIGU..."</p>
<hr />
<div>UBIK includes a configurable approach to automatic instance deletion, allowing flexibility in managing different MetaClasses.<br />
This can be done via the MetaClass DELETE_CONFIGURATION which is provided from a UBIK database and can be found under System.Main.Base.<br />
<br />
The deletion configuration is divided into two main categories:<br />
===Soft Deletion===<br />
A soft delete limit can be set, specifying the number of days beyond which records older than the CTS (Creation Timestamp) will be deleted. When an instance undergoes soft deletion, its delete status is updated to deleted, making it invisible within UBIK. However, the record remains in the SQL database, where it is marked as deleted for reference purposes.<br />
<br />
===Hard Deletion===<br />
''(Not Yet Functional)'' A hard delete limit can be configured, specifying the number of days where soft-deleted records are permanently removed from the database. While soft deletion is currently functional, hard deletion is planned for future implementation. <br />
<br />
Example: Delete Configuration for the Progress Task MetaClass where limit is set to 30 days<br />
[[File:Example_DeleteConfig.png|350x100px]]<br />
Result: All Instances of this MetaClass which have an older CTS than 30 days will be marked for soft-deletion.<br />
<br />
===Deletion Workflow===<br />
The DeleteManager component needs to be initialized (via WhoBert for example) to handle the deletion process.<br />
Within the DeleteManager, this method must be executed:<br />
<br />
ExecuteSoftDelete: This method updates the record's delete status and ensures it can no longer be accessed in UBIK Studio while retaining the record in SQL for reference.<br />
Future steps involve finalizing the DeleteManager and implementing hard deletion to complete the workflow.<br />
<br />
<source lang = "csharp"><br />
DeleteManager delmanager = new DeleteManager();<br />
delManager.ExecuteSoftDelete();<br />
</source></div>LDOhttps://wiki.augmensys.com/index.php?title=Version_4.9.0_(Server)&diff=27978Version 4.9.0 (Server)2025-03-18T09:19:56Z<p>LDO: </p>
<hr />
<div>= Kernel =<br />
== Features ==<br />
* UBIK provides the possibility to customize an online text search. See [[SYSCLS_CUSTOMTEXTQUERY|Custom Text Search Classification]].<br />
* Human-readable database views can be created in the same database instance where the data is stored.<br />
* Custom code for MetaProxies can now be edited and transported using SmartStudio.<br />
* UBIK.Studio provides the possibility to define the UID for a new derived MetaClass now.<br />
* UBIK CUI Interface supports the (re)import of undeleted Comos objects now.<br />
* UBIK StandardImport supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.<br />
* A custom query-based search is now available to be used in customizing.<br />
* UBIK OLEDB Plugin supports customizing the OLEDB provider string now.<br />
* An improved configuration dialog for the auto-create MetaClassScope drag & drop action was created.<br />
<br />
<br />
== Bug Fixes ==<br />
* A bug in managing changelog/history items for properties with configured MetaAttributes was fixed.<br />
* A problem in handling references to deleted objects was fixed: misleading exceptions are not thrown anymore.<br />
* An issue where custom code couldn't be transported for system meta classes using SmartStudio was fixed.<br />
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time in SmartStudio and AdminTool.<br />
* New instances created in the AdminTool are now also saved if a refresh occurs beforehand.<br />
* A problem in the new support to undelete CUI objects was fixed: the ID of the target object does not change when executing the undelete.<br />
* System.Memory.dll is now provided in the release packages.<br />
* OSIPI and ModuleReporting Plugins support the newest version of System.Memory now.<br />
* A bug in the UBIK.NotificationEndPoint Service was fixed: it can handle subfolders in the Queue directory now.<br />
* A bug when flattening Annotations and Hotspots into Document Revisions was fixed.<br />
* Improved Exception Handling when saving objects and proxies during the interface execution, result in a higher stability as customizing related crashes do not stop the process any more.<br />
* Fixed an issue in the AdminTool that permitted manipulation of locked properties.<br />
* An issue where values for new languages weren't saved was fixed.<br />
* A bug in the handling of History/Changelog items for MRO tasks was fixed: if the value is set directly to N.A., a changelog item gets created now.<br />
* A Issue was fixed where the PunchPoint link was not visualized in the "Punchpoint Attachments" use case<br />
<br />
<br />
== Enhancements ==<br />
* UBIK Standard-Import supports null values for strings, (nullable) GUIDs, and geodata now. Depending on the import configuration, these null values will be processed and imported to the ubiqule.<br />
* A possibility to customize "real" property values for system design objects via Plugin was provided. Further, CUI system definitions can now be used without deriving.<br />
* MetaProxy properties are now modeled more consistently in SmartStudio.<br />
* A set of vulnerable 3rd party components were updated.<br />
* For reduced RAM consumption, a system classification SYSCLS_PREVENT_CACHING was provided, and future measures were triggered.<br />
* UBIK supports *.docx as standard filetype now<br />
<br />
<br />
== MaTaP Improvements and fixes ==<br />
* Fixed an issue where QRF and Check Operations were not included in Mile Stone Calculation of Workorder.<br />
* Predefined views get saved and are available for Admin Tools now.<br />
* The Project Usecase in the MATAP Admin Tool is standardized now: Job Descriptions + presented columns.<br />
* MATAP supports encrypted passwords for imported MATAP users now.<br />
* MATAP supports Quality Record Forms now.<br />
* MATAP supports Check Tasks now.<br />
* MATAP Wallpaper Client supports project-related Punchpoint columns now.<br />
* The Project Status is now managed on the Project Instance itself.<br />
* UBIK MATAP supports project-related data caching on the View Cache now.<br />
* The communication feature is now available in MATAP.<br />
* All operation imports support the import of a work property.<br />
* MATAP supports reports now.<br />
* Admin Tool shows the duration of a successful job run now instead of presenting start and end timestamps.<br />
* MATAP supports the import and presentation of materials per operation now.<br />
* In the Admin Tool, the (Turnaround) Project Usecase does not show SAP-specific columns anymore.<br />
* In the Admin Tool, the Operation Usecases do not show SAP and Primavera-specific columns anymore.<br />
* Identified an issue where activity codes were cut off when the project name was too long.<br />
* Identified an issue where companies were cut off when the project name was too long.<br />
* Deletion of default activity codes works now.<br />
* Reimporting deleted objects is now possible.<br />
* Wallpaper Client does not crash when opening a Scope Change anymore.<br />
* A bug in evaluating the code was fixed. Configured grouped codes are no longer ignored.<br />
* The Admin Tool is now able to download the customizing.<br />
* Operations being set to Not Applicable show the right status color now (gray).<br />
* Scheduling import works now for check and QRF operations too.<br />
* Wallpaper does not crash anymore during progress reporting.<br />
* Location assigning performance was improved.<br />
* A misconfiguration that caused duplicated scope changes to also duplicate the progress was fixed.<br />
* Fixed an issue where Punchpoint numbers were overwritten multiple times causing the number to unnecessarily increase.<br />
* Fixed the bug where the Instance Picker results were not shown when clicking the three-dot symbol for the first time.<br />
* MATAP now provides the possibility to schedule nightly app pool restarts for all active projects.<br />
* MATAP imports will not overwrite once edited string data with empty values anymore.<br />
* The "Turnaround Project" use case was renamed to "Project".<br />
* The description for the Currency Setting Property was wrong. It shows "Currency Settings" now.<br />
* The currency on projects is now set to "€" by default.<br />
* Key and unique filename have now been removed from the Plot Plans use case.<br />
* Description has been replaced with Name in the Plot Plans use case (Admin Tool)<br />
* The Plot Plan Name is now displayed in Plant Layouts (Client)<br />
* Removed columns "Offline Sync Configuration" and "Branch Download" from Admin Tool "Functionality" use case.<br />
* Removed columns "Unique Filename" and "Path to local file" from Admin Tool "Daily HSE" use case.<br />
* Vertical and horizontal scroll bars now remain in their last set position after the saving process.<br />
* The Zone column is now available in the Commissioning Package Usecase.<br />
* Systems and subsystems are available in the Commissioning Tasks use case now.<br />
* Documents below work orders are sorted by their type now.<br />
* Names for systems and subsystems show in the expected order now.<br />
* MATAP allows project names with a length of up to 100 characters now.<br />
* New instances are now also saved if a refresh occurs beforehand.<br />
* SC Desc., Operation No., and Estimated Costs are now displayed as saved after saving.<br />
* Timesheets calculation issue for standard operations was solved.<br />
* A sorting error for operations was fixed.<br />
* When selecting import files, the file picker now remembers its last position.<br />
* Template Usecases will now be replicated including their column configurations.<br />
* Precom Activity Code cells show default operations information on the Turnaround Wallpaper now.<br />
* An unused property (MATAP_PROJECT_ID) has been removed from the standard property pool.<br />
* A new property (MATAP_ID) has been added to the standard property pool and integrated into the Activity Code Use Cases.<br />
* The Admin Tool Turnaround Project Usecase now provides project creation status information.<br />
* A problem in the Admin Tool which led to random warnings is solved now.<br />
* MATAP Wallpaper Client now shows correct labels for Check/Operation detail tabs.<br />
* Fixed recurring warnings in UBIK.Studio.<br />
* Fixed recurring warnings in Admin Tool.<br />
* The key column for MATAP users gets automatically filled if the object is created manually.<br />
* Document system property will not be delivered to the client anymore.<br />
* Fixed the issue where setting an operation status to N/A could cause the client to freeze or crash.<br />
* The scope change workflow shows the user details again.<br />
* A problem in the View Item Setup for the Communication Feature was fixed.<br />
* Cells on the Commissioning Wallpaper only show the last change date if the task is considered to be finished.<br />
* CODE_TYPE property doesn't get replicated when creating a Scope Change.<br />
* A bug was fixed where empty Meta Classes were created after removing the MATAP plugin.<br />
* Performance improvements and general bug fixes for Admin Tool.<br />
* The Bulk Editor scroll bars now retain their positions after a refresh.<br />
* Admin Tool shows the name of the referenced project when displaying use cases now.<br />
* Punchpoints show a changelog for the 'Responsibility' property now.<br />
* The Admin - Tool Scope Change Usecase shows scope changes only now.<br />
* Import of EquipmentGroup and EquipmentType data is standardized now: the standard import supports import via the Equipment instance.<br />
* The Admin - Tool Scope Change Attachment Usecase works now.<br />
* Import of Equipments support a complex plant-system-subsystem structure as well as plant zone structure. it is not required any more that system and subsystem names are unique.<br />
* Execution Documents show the Local Full Path in the AdminTool now.<br />
* Punchpoints now show a changelog for the 'Responsibility' and 'Due Date' properties.<br />
* A digit counter was added for Operation, Operation Description and ScopeChange Description in the Wallpaper Client.<br />
* The current Project Status can now be seen in the project header of the start screen.<br />
* In the Admin Tool, the Task - Progress is now displayed in the corresponding column.<br />
* The filtering of instances in the Picker within the Admin Tool is now possible without reopening the popup.<br />
* A Issue was fixed where the link to the PunchPoint was not visualized in the PunchpointAttachment usecase in the Admin Tool<br />
* Users can change a project name only until the creation is finished.<br />
<br />
<br />
== Known Issues ==<br />
* Exclusive Access is not fully supported (missing aspect: lock on database level)</div>LDOhttps://wiki.augmensys.com/index.php?title=View_Cache_Launcher&diff=27612View Cache Launcher2024-12-17T12:34:41Z<p>LDO: </p>
<hr />
<div>={{UBIK}} View Cache Launcher (VCL)=<br />
<br />
The VCL is an installable windows system service which can be used to automaically trigger one or more UBIK contexts(s) provided by an UBIK IIS service to build up its view cache.<br />
<br />
After unpacking the VCL binaries and config-files, move the files to a directory where the local system account (or the specified one configured to run the VCL service) is allowed to execute the "install.bat". This file installs the UBIK.VCL.Service.exe as a service.<br />
<br />
The VCL is configured in “UBIK.VCL.Service.exe.config":<br />
<br />
{| class="wikitable" | width = "100%"<br />
|-<br />
! Attribute!!Purpose!!Optional!!Obsolete (since V4.8+)<br />
|-<br />
| '''Protocol'''|| choose your wanted transport-protocol (https, http) || ||<br />
|-<br />
| '''Url'''|| URL of the webserver || ||<br />
|-<br />
| '''Port'''|| port which is assigned to the webserver || ||<br />
|-<br />
| '''Path'''|| specify the path where the CONTENT webservice is placed || ||<br />
|-<br />
| '''App'''|| application name of your use-case|| ||<br />
|-<br />
| '''Context'''|| context name of your use-case|| ||<br />
|-<br />
| '''TriggerInterval'''|| specify the interval in seconds how often a viewcache rebuild is triggered || ||<br />
|-<br />
| '''OfflineCheckInterval'''|| specify the interval in seconds how often the server-status is checked || ||<br />
|-<br />
| '''Inactive'''|| possibility to configure a timespan in which no rebuild is triggered (from;to) in (hh:mm;hh:mm) || X ||<br />
|-<br />
| '''LogPath'''|| specify the path where your logs should be placed || || <br />
|-<br />
| '''USAMUrl'''|| Webserver URL of the USAM || || X<br />
|-<br />
| '''USAMPort'''|| port which is assigned to the USAM webserver || || X<br />
|-<br />
| '''USAMProtocol'''|| choose your wanted transport-protocol (https, http) || || X<br />
|-<br />
| '''USAMPath'''|| specify the path where the USAM webservice is placed || || X<br />
|-<br />
| '''USAMLogin'''|| specify the login name which is used for triggering the viewcache build || || X<br />
|-<br />
| '''USAMPwd'''|| specify the password which is used for triggering the viewcache build|| || X<br />
|-<br />
| '''USAMDeviceName'''|| specify the device name which is used for triggering the viewcache build || || X<br />
|-|-<br />
| '''PushUrl'''|| Webserver URL of the PUSH || X || X<br />
|-<br />
| '''PushPort'''|| port which is assigned to the PUSH webserver || X || X<br />
|-<br />
| '''PushProtocol'''|| choose your wanted transport-protocol (https, http) || X || X<br />
|-<br />
| '''PushPath'''|| specify the path where the PUSH webservice is placed || X || X<br />
|-<br />
| '''Action'''|| Two options: ''ViewCacheUpdate'' (default value if the parameter is not set specifically); ''GetContent'' (can update one specific content object via an UID set with the Content parameter) || X ||<br />
|-<br />
| '''Content'''|| UID of a content object || X ||<br />
|}<br />
<br />
===Example===<br />
<br />
<source lang="xml"><br />
<?xml version="1.0" encoding="utf-8" ?><br />
<configuration><br />
<startup> <br />
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5.1" /><br />
</startup><br />
<appSettings><br />
<add key="Protocol" value="https"/><br />
<add key="Url" value="127.0.0.1"/><br />
<add key="Port" value="443"/><br />
<add key="Path" value="UBIKService/CONTENT"/><br />
<add key="App" value="APP_01"/><br />
<add key="Context" value="CXT_01"/><br />
<add key="TriggerInterval" value="3000" /><br />
<add key="OfflineCheckInterval" value="64" /><br />
<add key="LogPath" value="C:\UBIK\VCL\log\log.txt"/> <br />
</appSettings><br />
</configuration><br />
</source><br />
<br />
====Configure more than one service and/or context to be updated====<br />
<br />
Please duplicate the entries used and add a number suffix. Here is an example:<br />
<source lang="xml"><br />
<add key="Protocol" value="https" /><br />
<add key="Protocol01" value="https" /><br />
</source><br />
'''Remark''': The number should be continously incremented by one, if there is a number missing in-between (-> e.g. Protocol, Protocol01, Protocol03,..), the last executed will be Protocol01.</div>LDOhttps://wiki.augmensys.com/index.php?title=Communication&diff=27214Communication2024-09-16T07:52:53Z<p>LDO: </p>
<hr />
<div>= Functionality =<br />
The Communication functionality is designed to prvide a clear and organized view of companies and users involved in a project. The hierarchical view allows users to easily navigate through the different companies and their sub-companies. This functionality ensures that project managers and team members can easily access and manage information about the companies and users involved in their projects.<br />
<br />
[[File:Overview_Communication.PNG|600px]]<br />
<br />
== Companies Overview ==<br />
When entering communication, the company section initially displays a list of all companies associated with the project. Sub-companies are shown under their parent companies, providing a clear organizational structure.<br />
<br />
== Users Overview ==<br />
When entering communication, the user section initially displays a list of all users associated with the project. Users can view more detailed information about their roles and activities within the project.<br />
Clicking on a company name will filter the right section to show only the users associated with that company and its sub-companies.<br />
<br />
[[File:CompanyAndUsers3.PNG|600px]]<br />
<br />
[[Category:Pages with broken file links|Communication]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Communication&diff=27213Communication2024-09-16T07:52:27Z<p>LDO: </p>
<hr />
<div>= Functionality =<br />
The Communication functionality is designed to prvide a clear and organized view of companies and users involved in a project. The hierarchical view allows users to easily navigate through the different companies and their sub-companies. This functionality ensures that project managers and team members can easily access and manage information about the companies and users involved in their projects.<br />
<br />
[[File:Overview_Communication.PNG|600px]]<br />
<br />
== Companies Overview ==<br />
When entering communication, the company section initially displays a list of all companies associated with the project. Sub-companies are shown under their parent companies, providing a clear organizational structure.<br />
<br />
== Users Overview ==<br />
When entering communication, the user section initially displays a list of all users associated with the project. Users can view more detailed information about their roles and activities within the project.<br />
Clicking on a company name will filter the right section to show only the users associated with that company and its sub-companies.<br />
<br />
[[:File:CompanyAndUsers3.PNG|600px]]<br />
<br />
[[Category:Pages with broken file links|Communication]]</div>LDOhttps://wiki.augmensys.com/index.php?title=File:CompanyAndUsers3.PNG&diff=27212File:CompanyAndUsers3.PNG2024-09-16T07:51:37Z<p>LDO: File uploaded with MsUpload</p>
<hr />
<div>File uploaded with MsUpload</div>LDOhttps://wiki.augmensys.com/index.php?title=File:Overview_Communication.PNG&diff=27211File:Overview Communication.PNG2024-09-16T07:51:36Z<p>LDO: File uploaded with MsUpload</p>
<hr />
<div>File uploaded with MsUpload</div>LDOhttps://wiki.augmensys.com/index.php?title=Communication&diff=27210Communication2024-09-16T07:50:44Z<p>LDO: </p>
<hr />
<div>= Functionality =<br />
The Communication functionality is designed to prvide a clear and organized view of companies and users involved in a project. The hierarchical view allows users to easily navigate through the different companies and their sub-companies. This functionality ensures that project managers and team members can easily access and manage information about the companies and users involved in their projects.<br />
<br />
[[File:Overview2.png|600px]]<br />
<br />
== Companies Overview ==<br />
When entering communication, the company section initially displays a list of all companies associated with the project. Sub-companies are shown under their parent companies, providing a clear organizational structure.<br />
<br />
== Users Overview ==<br />
When entering communication, the user section initially displays a list of all users associated with the project. Users can view more detailed information about their roles and activities within the project.<br />
Clicking on a company name will filter the right section to show only the users associated with that company and its sub-companies.<br />
<br />
[[File:CompanyAndUsers2.png|600px]]<br />
<br />
[[Category:Pages with broken file links|Communication]]</div>LDOhttps://wiki.augmensys.com/index.php?title=File:Overview2.PNG&diff=27208File:Overview2.PNG2024-09-16T07:50:34Z<p>LDO: File uploaded with MsUpload</p>
<hr />
<div>File uploaded with MsUpload</div>LDOhttps://wiki.augmensys.com/index.php?title=File:CompanyAndUsers2.PNG&diff=27209File:CompanyAndUsers2.PNG2024-09-16T07:50:34Z<p>LDO: File uploaded with MsUpload</p>
<hr />
<div>File uploaded with MsUpload</div>LDOhttps://wiki.augmensys.com/index.php?title=Communication&diff=27207Communication2024-09-16T07:48:51Z<p>LDO: </p>
<hr />
<div>= Functionality =<br />
The Communication functionality is designed to prvide a clear and organized view of companies and users involved in a project. The hierarchical view allows users to easily navigate through the different companies and their sub-companies. This functionality ensures that project managers and team members can easily access and manage information about the companies and users involved in their projects.<br />
<br />
[[File:Overview.png|600px]]<br />
<br />
== Companies Overview ==<br />
When entering communication, the company section initially displays a list of all companies associated with the project. Sub-companies are shown under their parent companies, providing a clear organizational structure.<br />
<br />
== Users Overview ==<br />
When entering communication, the user section initially displays a list of all users associated with the project. Users can view more detailed information about their roles and activities within the project.<br />
Clicking on a company name will filter the right section to show only the users associated with that company and its sub-companies.<br />
<br />
[[File:CompanyAndUsers.png|600px]]<br />
<br />
[[Category:Pages with broken file links|Communication]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Communication&diff=27206Communication2024-09-16T07:48:02Z<p>LDO: </p>
<hr />
<div>= Functionality =<br />
The Communication functionality is designed to prvide a clear and organized view of companies and users involved in a project. The hierarchical view allows users to easily navigate through the different companies and their sub-companies. This functionality ensures that project managers and team members can easily access and manage information about the companies and users involved in their projects.<br />
<br />
[[File:Overview.png|600px]] [[File:Overview.png|600px]]<br />
<br />
== Companies Overview ==<br />
When entering communication, the company section initially displays a list of all companies associated with the project. Sub-companies are shown under their parent companies, providing a clear organizational structure.<br />
<br />
== Users Overview ==<br />
When entering communication, the user section initially displays a list of all users associated with the project. Users can view more detailed information about their roles and activities within the project.<br />
Clicking on a company name will filter the right section to show only the users associated with that company and its sub-companies.<br />
<br />
[[File:CompanyAndUsers.png|600px]] [[File:CompanyAndUsers.png|600px]]<br />
<br />
[[Category:Pages with broken file links|Communication]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Communication&diff=27205Communication2024-09-16T07:47:30Z<p>LDO: Created page with "= Functionality = The Communication functionality is designed to prvide a clear and organized view of companies and users involved in a project. The hierarchical view allows u..."</p>
<hr />
<div>= Functionality =<br />
The Communication functionality is designed to prvide a clear and organized view of companies and users involved in a project. The hierarchical view allows users to easily navigate through the different companies and their sub-companies. This functionality ensures that project managers and team members can easily access and manage information about the companies and users involved in their projects.<br />
<br />
[[File:Overview.png|600px]] [[File:Overview.png|600px]]<br />
<br />
== Companies Overview ==<br />
When entering communication, the company section initially displays a list of all companies associated with the project. Sub-companies are shown under their parent companies, providing a clear organizational structure.<br />
<br />
== Users Overview ==<br />
When entering communication, the user section initially displays a list of all users associated with the project. Users can view more detailed information about their roles and activities within the project.<br />
Clicking on a company name will filter the right section to show only the users associated with that company and its sub-companies.<br />
<br />
[[File:CompanyAndUsers.png|600px]] [[File:CompanyAndUsers.png|600px]]</div>LDOhttps://wiki.augmensys.com/index.php?title=File:CompanyAndUsers.PNG&diff=27204File:CompanyAndUsers.PNG2024-09-16T07:46:59Z<p>LDO: File uploaded with MsUpload</p>
<hr />
<div>File uploaded with MsUpload</div>LDOhttps://wiki.augmensys.com/index.php?title=File:Overview.PNG&diff=27203File:Overview.PNG2024-09-16T07:46:58Z<p>LDO: File uploaded with MsUpload</p>
<hr />
<div>File uploaded with MsUpload</div>LDOhttps://wiki.augmensys.com/index.php?title=HowTo:Implementing_Live_Values&diff=26962HowTo:Implementing Live Values2024-07-04T10:24:54Z<p>LDO: </p>
<hr />
<div>Check out the [[Live_Values|Overview of Live Values]] before!<br />
<br />
== How Live Values Work ==<br />
Live values are special properties without a value that is persisted in the database. Instead, they get their current value frequently from a live value server, including a measurement quality indicator and a read timestamp, among other details. Live values can be used to display trends and current values (e.g., sensor values) from dynamic sources like process control systems (e.g., via OPC-UA).<br />
<br />
In {{UBIK}}, live value properties are defined by a special kind of [[MetaProperty]], a live value meta property. So, if you want to add a live value to a {{UBIK}} object, you first need to add such a meta property to the metaclass of the object in question. You can get such a live value meta property from creating an instance of the [[MetaClass]] ''LIVEVALUE_METAPROPERTY''. This way, for example, you could define a property "temperature" on a metaclass "cooling unit". <br />
<br />
So, following this example, how do individual "cooling unit" instances know their specific "temperature" values? An individual live value property holds the answer: It actually ''has'' a persisted value - a reference to a so-called live value data point. Such a data point knows a live value server (providing access to a process control system for example), and an identifier of (or path to) a dynamic variable, e.g. representing a specific temperature sensor in the process control system. This means, for a specific "cooling unit" instance, we want to configure the correct live value data point as a value of the "temperature" live value property.<br />
<br />
Hence, we require a live value data point and a live value server. There is a {{UBIK}} plugin UBIK.Interface.Module.OPCUA which we can use for getting those. That module implements a specific kind of live value server, namely the OPC-UA live value server. It is represented by a metaclass ''OPC_SERVER'', and instances thereof can be used to configure a connection to a specific OPC server. Similarly, there is a metaclass ''OPC_DATAPOINT'' representing variable configurations. We want to have a data point instance with a link to a server instance (and a path to the variable we need). This data point instance must be set on the "temperature" property in our example.<br />
<br />
With the UBIK.Interface.Module.OPCUA plugin, {{UBIK}} will detect that there is a live value server and it will host a live value data service, supplying our "cooling unit" objects with their current "temperature" values.<br />
<br />
== Implementing Live Values in {{UBIK}} Studio ==<br />
First of all, download the UBIK.Interface.Module.OPCUA from the ''Augmensys Realease Portal/Plugins'' and copy them into the injections folder from your {{UBIK}} Studio as well as in the injection folder of the Web Service.<br />
<br />
# Navigate to the [[MetaClass]] ''OPC_SERVER'' via the ''[[Class Browser]]''.<br/> [[File:OPCServer.PNG|330 px|border]]<br />
# Add a new instance (OPC Server) to the [[MetaClass]] by using the [[Bulk Editor]].<br />
# Navigate to the [[MetaClass]] ''OPC_DATAPOINT'' via the ''[[Class Browser]]''.<br/> [[File:OPCDATAPOINT.PNG|330 px|border]]<br />
# Add a new instance (OPC Datapoint) to the [[MetaClass]] by using the [[Bulk Editor]]. Configure the correct path to the OPC variable represented by this datapoint. As ''REF_OPC_SERVER'' take the server created before in step 2.<br/> [[File:OPCDatapointInstance.PNG|770 px|border]]<br />
# Navigate to the [[MetaClass]] ''LIVEVALUE_METAPROPERTY'' via the ''[[Class Browser]]''.<br/> [[File:LMP.PNG|330 px|border]]<br />
# Add a new instance (Live Value MetaProperty) to the [[MetaClass]] by using the [[Bulk Editor]].<br />
# Add the newly created ''Live Value MetaProperty'', from step 6, to the ''Metaclass'' where you want to have the live Values to be shown. <br />
# Add the created Datapoint from step 4 to an instance of the above ''Metaclass'' to which it concerns. <br/> [[File:AddDatapoint.PNG|770 px|border]]<br />
# Save the changes with {{key press|Ctrl|S}} or the save command.<br />
<br />
<br />
== Accessing Live Values in {{UBIK}} Studio ==<br />
Example how a LiveValue can be accessed within WhoBert for debugging purposes for example. Can also be adapted to be used within the database code customizing.<br />
<br />
The first part of the code ensures that live value servers are initialized and running before attempting to retrieve live values.<br />
Afterwards Live Value Information can be used as it retrieves and logs information about live values, such as their value, read timestamp, and age.<br />
<br />
<source lang="csharp"><br />
using System;<br />
using System.Windows.Forms;<br />
using UBIK.Kernel;<br />
using UBIK.Runtime;<br />
using UBIK.Runtime.Sys;<br />
using UBIK.Compiler;<br />
using System.Linq;<br />
using UBIK.Interface;<br />
using UBIK.Injection;<br />
using System.Collections.Generic;<br />
<br />
namespace Studio<br />
{<br />
public class ObjectTest<br />
{<br />
public void TestObject (params BaseClass[] InVariables)<br />
{<br />
Debugger.Output(this, "*** Started");<br />
foreach (BaseClass obj in InVariables)<br />
{<br />
List<IUBIKLiveValueServer> servers = obj.Environment.GetInjectionManager().Plugins<IUBIKLiveValueServer>(TargetApplication.UBIK_WebService);<br />
foreach (IUBIKLiveValueServer server in servers) <br />
{ <br />
if (!server.GetStatus().Running)<br />
{<br />
server.InitLiveValueServer(obj.Environment);<br />
server.Startup();<br />
}<br />
UBIK.Interface.LiveValues.ILiveValueInformation value;<br />
//UID from the LiveValue Datapoint<br />
if (server.TryGetLiveValue(new Guid("UID"), out value))<br />
{<br />
if (value.Value != null)<br />
Debugger.Output(this, value.Value.ToString());<br />
<br />
if (value.ReadTimeStamp != null)<br />
Debugger.Output(this, value.ReadTimeStamp.ToString());<br />
<br />
if (value.Age != null)<br />
Debugger.Output(this, value.Age.ToString());<br />
}<br />
Debugger.Output(this, server.GetStatus().ToString());<br />
}<br />
}<br />
Debugger.Output(this, "*** Finished");<br />
}<br />
}<br />
}<br />
<br />
</source><br />
<br />
=== ILiveValueInformation ===<br />
The method TryGetLiveValue delivers LiveValueInformation objects:<br />
<source lang="csharp"><br />
namespace UBIK.Interface.LiveValues<br />
{<br />
public interface ILiveValueInformation<br />
{<br />
/// <summary><br />
/// Gets the value.<br />
/// </summary><br />
/// <value><br />
/// The value.<br />
/// </value><br />
object Value { get; }<br />
<br />
/// <summary><br />
/// Gets the quality.<br />
/// </summary><br />
/// <value><br />
/// The quality.<br />
/// </value><br />
QualityTypes Quality { get; }<br />
<br />
/// <summary><br />
/// Gets the quality description.<br />
/// </summary><br />
/// <value><br />
/// The quality description.<br />
/// </value><br />
string QualityDescription { get; }<br />
<br />
/// <summary><br />
/// Gets the read time stamp.<br />
/// </summary><br />
/// <value><br />
/// The read time stamp.<br />
/// </value><br />
DateTime? ReadTimeStamp { get; }<br />
<br />
/// <summary><br />
/// Gets the age.<br />
/// </summary><br />
/// <value><br />
/// The age.<br />
/// </value><br />
int? Age { get; }<br />
}<br />
}<br />
</source><br />
<br />
Information can be also extended using: <br />
<source lang="csharp"><br />
namespace UBIK.Interface.LiveValues<br />
{<br />
public interface ILiveValueInformationV264 : ILiveValueInformation<br />
{<br />
/// <summary><br />
/// Attributes provides a possibility to add (any) information to a live value.<br />
/// This gives us the possibility to hand over any back end server specific information to the client.<br />
/// </summary><br />
/// <value><br />
/// The attributes.<br />
/// </value><br />
UBIK.Service.DTO.V264.LiveValueAttribute[] Attributes { get; }<br />
}<br />
}<br />
</source><br />
== See also ==<br />
* [[Plugins]]<br />
* [[HowTo:Add a MetaProperty to a MetaClass]]<br />
<br />
[[Category:How-To|Live Values]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Version_4&diff=25183Version 42023-08-09T06:37:13Z<p>LDO: </p>
<hr />
<div><h2>'''Under Construction'''</h2><br />
{{RoadmapDetailHeader}}<br />
<br />
{{RoadmapDetailItem <br />
| version=4.6<br />
| date=2024 <br />
| status={{RoadmapChip-Announced}} <br />
| content=<br />
{{RoadmapDetailFeature | feature=Prefilter Objects with the same QR code. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Xamarin}} | feature=Customizable Visibility of appbar Menu Button.}}<br />
{{RoadmapDetailFeature | feature=Productization of MaTaP Features. }}<br />
}}<br />
<br />
{{RoadmapDetailItem <br />
| version=4.5<br />
| date=October 2023<br />
| status={{RoadmapChip-Announced}} <br />
| content=<br />
{{RoadmapDetailFeature | product={{RoadmapChip-CUI}} | feature=Reset of Proxies. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-CUI}} | feature=Support of Comos Reference Documents. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-CUI}} | feature=Support of Comos DocObjs. }}<br />
{{RoadmapDetailFeature | feature=Properties as Live Value Attributes. }}<br />
{{RoadmapDetailFeature | feature=Support for Bing Road Map. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-WinX}} | feature=Auto Search and Highlight on PDF Preview. }}<br />
}}<br />
<br />
{{RoadmapDetailItem <br />
| version=4.4<br />
| date=October 2023<br />
| status={{RoadmapChip-Announced}} <br />
| content=<br />
{{RoadmapDetailFeature | feature=Experimental SSO features. | descr=Experimental SSO features are now available in the Xamarin Android client and the web client.}}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Xamarin}} | feature=Scanning of small QR-Codes. }}<br />
{{RoadmapDetailFeature | feature=Lazy Loading Queries. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Studio}} | feature=Classification-Based Creation of MetaProperties. }}<br />
{{RoadmapDetailFeature | feature=n-to-1: Optical Code Scanning. }}<br />
{{RoadmapDetailFeature | feature=Focus highlight text in PDF. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-iOS}} | feature=Signature Editing. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-CUI}} | feature=Support of Non-native Comos Documents. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-CUI}} | feature=Import DisplayValue with Unit. | descr=CUI MetaProxy Properties support a new configuration setting called "Import Type" The default value "Standard" will import Property Values as before If set to "DisplayValue" CUI will import the Display Value including the physical Unit from a Comos Specification. Export of such MetaProxy Properties is no supported. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-CUI}} | feature=Support of GeoData. | descr=CUI supports the import and export of Properties of type GeoData? now. For this a MetaProxyProperty of type string must be used on the MetaProxy. }}<br />
}}<br />
<br />
[[Category:Client|Version 4]]<br />
[[Category:Release notes|Version 4]]<br />
[[Category:Server|Version 4]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Version_4&diff=25182Version 42023-08-09T06:36:52Z<p>LDO: </p>
<hr />
<div><p>'''Under Construction'''</p><br />
{{RoadmapDetailHeader}}<br />
<br />
{{RoadmapDetailItem <br />
| version=4.6<br />
| date=2024 <br />
| status={{RoadmapChip-Announced}} <br />
| content=<br />
{{RoadmapDetailFeature | feature=Prefilter Objects with the same QR code. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Xamarin}} | feature=Customizable Visibility of appbar Menu Button.}}<br />
{{RoadmapDetailFeature | feature=Productization of MaTaP Features. }}<br />
}}<br />
<br />
{{RoadmapDetailItem <br />
| version=4.5<br />
| date=October 2023<br />
| status={{RoadmapChip-Announced}} <br />
| content=<br />
{{RoadmapDetailFeature | product={{RoadmapChip-CUI}} | feature=Reset of Proxies. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-CUI}} | feature=Support of Comos Reference Documents. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-CUI}} | feature=Support of Comos DocObjs. }}<br />
{{RoadmapDetailFeature | feature=Properties as Live Value Attributes. }}<br />
{{RoadmapDetailFeature | feature=Support for Bing Road Map. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-WinX}} | feature=Auto Search and Highlight on PDF Preview. }}<br />
}}<br />
<br />
{{RoadmapDetailItem <br />
| version=4.4<br />
| date=October 2023<br />
| status={{RoadmapChip-Announced}} <br />
| content=<br />
{{RoadmapDetailFeature | feature=Experimental SSO features. | descr=Experimental SSO features are now available in the Xamarin Android client and the web client.}}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Xamarin}} | feature=Scanning of small QR-Codes. }}<br />
{{RoadmapDetailFeature | feature=Lazy Loading Queries. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-Studio}} | feature=Classification-Based Creation of MetaProperties. }}<br />
{{RoadmapDetailFeature | feature=n-to-1: Optical Code Scanning. }}<br />
{{RoadmapDetailFeature | feature=Focus highlight text in PDF. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-iOS}} | feature=Signature Editing. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-CUI}} | feature=Support of Non-native Comos Documents. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-CUI}} | feature=Import DisplayValue with Unit. | descr=CUI MetaProxy Properties support a new configuration setting called "Import Type" The default value "Standard" will import Property Values as before If set to "DisplayValue" CUI will import the Display Value including the physical Unit from a Comos Specification. Export of such MetaProxy Properties is no supported. }}<br />
{{RoadmapDetailFeature | product={{RoadmapChip-CUI}} | feature=Support of GeoData. | descr=CUI supports the import and export of Properties of type GeoData? now. For this a MetaProxyProperty of type string must be used on the MetaProxy. }}<br />
}}<br />
<br />
[[Category:Client|Version 4]]<br />
[[Category:Release notes|Version 4]]<br />
[[Category:Server|Version 4]]</div>LDOhttps://wiki.augmensys.com/index.php?title=Template:RoadmapOverview&diff=25042Template:RoadmapOverview2023-08-07T07:19:34Z<p>LDO: </p>
<hr />
<div><br />
<br />
<!--VERSION: Roadmap--><br />
<div style="display: flex; justify-content: space-between; align-items: center; font-size: 23px; flex-wrap: wrap;"><br />
<p style="margin-right: 10px;">'''Product Roadmap'''</p><br />
<div style="display: flex; align-items: center;"><br />
<div style="display: flex; align-items: center;"><br />
<p style="margin-right: 10px;">All v4 Releases</p><br />
<p style="margin: 0;">|</p><br />
<p style="margin-left: 10px;">All Older Releases</p><br />
</div><br />
</div><br />
</div><br />
<br />
<div style="display: flex; background-color: #FFFFFFFF; justify-content: space-evenly; flex-wrap: wrap;"><br />
<!--VERSION: Latest Release--><br />
<div style="left: 0px; border-radius: 2px; background-color: #F5F5F5; margin: 10px; display: flex; flex-direction: column; min-height: 100px;"><br />
<p style="font-size: 23px; padding-left: 14px; padding-right: 50px; padding-top: 10px;">'''Latest Release'''</p><br />
<div style="background-color: #FFFFFF; padding-right: 20px; flex-grow: 1; display: flex; flex-direction: column;"><br />
<div style="display: flex; align-items: center;"><br />
<p style="font-size: 23px; padding-left: 14px; flex: 1; margin: 0;">'''v4.3'''</p><br />
<div style="margin-left: auto; border-radius: 2px; width: 68px; height: 22px; background-color: #8CCE59; text-align: center;"><br />
<p style="font-size: 13px; line-height: 22px; margin: 0;">'''12.04.23'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">'''Developer Mode.'''</p><br />
<div style="display: block; margin-left: 10px; width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">'''Dynamic Live Mode (DLM).'''</p><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">'''In-PDF Searching.'''</p><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<p style="padding-left: 14px; font-size: 13px; margin: 0;">'''View Details'''</p><br />
</div><br />
</div><br />
<!--VERSION: Latest Release--><br />
<!--VERSION: Next Release--><br />
<div style="left: 0px; border-radius: 2px; background-color: #F5F5F5; margin: 10px; display: flex; flex-direction: column; min-height: 100px;"><br />
<p style="font-size: 23px; padding-left: 14px; padding-right: 50px; padding-top: 10px;">'''Next Release'''</p><br />
<div style="background-color: #FFFFFF; padding-right: 20px; flex-grow: 1; display: flex; flex-direction: column;"><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; padding-top: 5px; font-size: 23px;">'''v4.4'''</p><br />
<div style="margin-left: 147px; margin-top: 10px; border-radius: 2px; width: 68px; height: 22px; border: 2px solid #8CCE59;"><br />
<p style="padding-left: 8px; padding-top: 1px; font-size: 13px;">'''Q3 2023'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">'''Signature.'''</p><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: block; margin-left: 10px; width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">''' '''</p><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<p style="padding-left: 14px; font-size: 13px;">'''View Details'''</p><br />
</div><br />
</div><br />
<!--VERSION: Next Release--><br />
<!--VERSION: Future Planned Releases--><br />
<div style="left: 0px; border-radius: 2px; background-color: #F5F5F5; margin: 10px;"> <br />
<p style="font-size: 23px; padding-left: 14px; padding-right: 50px; padding-top: 10px;">'''Future Planned Releases'''</p><br />
<div style="display: flex; width: 100%; height: 100%;"><br />
<div style="background-color: #FFFFFFFF; padding-right: 20px; width: 100%; height: 100%;"><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; padding-top: 5px; font-size: 23px;">'''v4.5'''</p><br />
<p style="padding-left: 10px; padding-top: 15px; font-size: 13px;">'''2024'''</p><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px; flex-wrap: none;">'''Cool Feature.'''</p><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: block; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">'''Exciting Feature!'''</p><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">''' '''</p><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<p style="padding-left: 14px; font-size: 13px;">'''View Details'''</p><br />
</div><br />
<div style="padding-left: 50px; height: 100%; background-color: #FFFFFFFF;"><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; padding-top: 5px; font-size: 23px;">'''v4.6'''</p><br />
<p style="padding-left: 10px; padding-top: 15px; font-size: 13px;">'''tbd.'''</p><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">'''A Feature.'''</p><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">''' '''</p><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">''' '''</p><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
</div><br />
</div><br />
</div><br />
<!--VERSION: Future Planned Releases--><br />
<br />
<div style="padding: 10px;"></div><br />
</div><br />
<br />
<!--VERSION: Roadmap--><br />
<br />
<!-- DIV: SPACER ROW --><br />
<div id="mainPageDiv" >&nbsp;</div><br />
<!-- DIV: SPACER ROW --><br />
<br />
<!-- DIV: BOX 1 --><br />
<div class="table" style="width:100%;border: none;background: #fff;"><br />
<!-- DIV: BOX 1 TABLE ROW --><br />
<div class="tableRow"><br />
<br />
</div><br />
<!-- DIV: BOX 1 TABLE ROW --><br />
</div><br />
<!-- DIV: BOX 1 --><br />
<br />
<br /></div>LDOhttps://wiki.augmensys.com/index.php?title=Template:RoadmapOverview&diff=25038Template:RoadmapOverview2023-08-03T11:25:54Z<p>LDO: </p>
<hr />
<div><br />
<br />
<!--VERSION: Roadmap--><br />
<div style="display: flex; justify-content: space-between; align-items: center; font-size: 23px; flex-wrap: wrap;"><br />
<p style="margin-right: 10px;">'''Product Roadmap'''</p><br />
<div style="display: flex; align-items: center;"><br />
<div style="display: flex; align-items: center;"><br />
<p style="margin-right: 10px;">All v4 Releases</p><br />
<p style="margin: 0;">|</p><br />
<p style="margin-left: 10px;">All Older Releases</p><br />
</div><br />
</div><br />
</div><br />
<br />
<div style="display: flex; background-color: #FFFFFFFF; justify-content: space-evenly; flex-wrap: wrap;"><br />
<!--VERSION: Latest Release--><br />
<div style="left: 0px; border-radius: 2px; background-color: #F5F5F5; margin: 10px; display: flex; flex-direction: column; min-height: 100px;"><br />
<p style="font-size: 23px; padding-left: 14px; padding-right: 50px; padding-top: 10px;">'''Latest Release'''</p><br />
<div style="background-color: #FFFFFF; padding-right: 20px; flex-grow: 1; display: flex; flex-direction: column;"><br />
<div style="display: flex; align-items: center;"><br />
<p style="font-size: 23px; padding-left: 14px; flex: 1; margin: 0;">'''v4.3'''</p><br />
<div style="margin-left: auto; border-radius: 2px; width: 68px; height: 22px; background-color: #8CCE59; text-align: center;"><br />
<p style="font-size: 13px; line-height: 22px; margin: 0;">'''12.04.23'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">'''Developer Mode.'''</p><br />
<div style="display: block; margin-left: 10px; width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">'''Dynamic Live Mode (DLM).'''</p><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">'''In-PDF Searching.'''</p><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<p style="padding-left: 14px; font-size: 13px; margin: 0;">'''View Details'''</p><br />
</div><br />
</div><br />
<!--VERSION: Latest Release--><br />
<!--VERSION: Next Release--><br />
<div style="left: 0px; border-radius: 2px; background-color: #F5F5F5; margin: 10px; display: flex; flex-direction: column; min-height: 100px;"><br />
<p style="font-size: 23px; padding-left: 14px; padding-right: 50px; padding-top: 10px;">'''Next Release'''</p><br />
<div style="background-color: #FFFFFF; padding-right: 20px; flex-grow: 1; display: flex; flex-direction: column;"><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; padding-top: 5px; font-size: 23px;">'''v4.4'''</p><br />
<div style="margin-left: 147px; margin-top: 10px; border-radius: 2px; width: 68px; height: 22px; border: 2px solid #8CCE59;"><br />
<p style="padding-left: 8px; padding-top: 1px; font-size: 13px;">'''Q3 2023'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">'''Signature.'''</p><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: block; margin-left: 10px; width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">''' '''</p><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<p style="padding-left: 14px; font-size: 13px;">'''View Details'''</p><br />
</div><br />
</div><br />
<!--VERSION: Next Release--><br />
<!--VERSION: Future Planned Releases--><br />
<div style="left: 0px; border-radius: 2px; background-color: #F5F5F5; margin: 10px;"> <br />
<p style="font-size: 23px; padding-left: 14px; padding-right: 50px; padding-top: 10px;">'''Future Planned Releases'''</p><br />
<div style="display: flex; width: 100%; height: 100%;"><br />
<div style="background-color: #FFFFFFFF; padding-right: 20px; width: 100%; height: 100%;"><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; padding-top: 5px; font-size: 23px;">'''v4.5'''</p><br />
<p style="padding-left: 10px; padding-top: 15px; font-size: 13px;">'''2024'''</p><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px; flex-wrap: none;">'''Cool Feature.'''</p><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: block; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">'''Exciting Feature!'''</p><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">''' '''</p><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<p style="padding-left: 14px; font-size: 13px;">'''View Details'''</p><br />
</div><br />
<div style="padding-left: 50px; height: 100%; background-color: #FFFFFFFF;"><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; padding-top: 5px; font-size: 23px;">'''v4.6'''</p><br />
<p style="padding-left: 10px; padding-top: 15px; font-size: 13px;">'''tbd.'''</p><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">'''A Feature.'''</p><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">''' '''</p><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
<div style="display: flex;"><br />
<p style="padding-left: 14px; font-size: 13px;">''' '''</p><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 1px; padding-left: 8px; font-size: 13px;">'''Mobile'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-left: 3px; font-size: 13px;">'''Android'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 38px; height: 21px; border: 2px solid #96A3D9; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 6px; font-size: 13px;">'''IOS'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 59px; height: 21px; background-color: #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 8px; font-size: 13px;">'''Server'''</p><br />
</div><br />
<div style="display: none; margin-left: 10px; min-width: 40px; height: 21px; border: 2px solid #96D9CD; border-radius: 2px;"><br />
<p style="padding-top: 0px; padding-bottom: 1px; padding-left: 3px; font-size: 13px;">'''UWP'''</p><br />
</div><br />
</div><br />
</div><br />
</div><br />
</div><br />
<!--VERSION: Future Planned Releases--><br />
<br />
<div style="padding: 10px;"></div><br />
</div><br />
<br />
<!--VERSION: Roadmap--><br />
<br />
<!-- DIV: SPACER ROW --><br />
<div id="mainPageDiv" >&nbsp;</div><br />
<!-- DIV: SPACER ROW --><br />
<br />
<!-- DIV: BOX 1 --><br />
<div class="table" style="width:100%;border: none;background: #fff;"><br />
<!-- DIV: BOX 1 TABLE ROW --><br />
<div class="tableRow"><br />
<br />
</div><br />
<!-- DIV: BOX 1 TABLE ROW --><br />
</div><br />
<!-- DIV: BOX 1 --><br />
<br />
<br /><br />
<!-- ROW FOOTER --><br />
<!-- Impressium --><br />
<div id="UBIK" class="mainpage-bottom" align="center"><br />
[[File:Augmensys_Logo_2019_small.png|center|link=Augmensys GmbH]]<br />
<div id="user" style="font-size:85%;">[[Special:Statistics|{{NUMBEROFUSERS}}]] users registered</div><br />
<div id="online" style="font-size:85%;">[[Special:Statistics|{{NUMBEROFACTIVEUSERS}}]] users active in the last 30 days</div><br />
<div id="articlecount" style="font-size:85%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles currently added</div><br />
</div><br />
<!-- ROW FOOTER --><br />
<br />
<!-- Hide Desktop content from Mobile view --><br />
</div><br />
<!-- MAIN DESKTOP DIV --><br />
<br />
<!-- MAIN MOBILE DIV --><br />
<div class="nodesktop"><br />
{{:Main_Page_Mobile}}<br />
</div><br />
<!-- MAIN MOBILE DIV --><br />
<br />
__NOTOC____NOEDITSECTION__<br />
{{DISPLAYTITLE:<span style="display:none">{{FULLPAGENAME}}</span>}}</div>LDOhttps://wiki.augmensys.com/index.php?title=Template:RoadmapDetailItem&diff=24877Template:RoadmapDetailItem2023-07-25T12:01:36Z<p>LDO: Created page with "<!--Header--> <div style="display: flex;"> <p style="padding-left: 28px; font-size: 13px;">'''''Version'''''</p> <p style="font-size: 13px; padding-left: 60px;">'''''E..."</p>
<hr />
<div><!--Header--><br />
<div style="display: flex;"><br />
<p style="padding-left: 28px; font-size: 13px;">'''''Version'''''</p><br />
<p style="font-size: 13px; padding-left: 60px;">'''''Expected / Release Date'''''</p><br />
<p style="font-size: 13px; padding-left: 40px;">'''|'''</p><br />
<p style="font-size: 13px; padding-left: 40px;">'''''Feature Status'''''</p><br />
<p style="font-size: 13px; padding-left: 45px;">'''''Release Notes'''''</p><br />
<p style="font-size: 13px; padding-left: 480px;">'''View All Older Releases'''</p><br />
</div><br />
<!--Header--><br />
<br />
<!--Body: List--><br />
<div style="margin-left: 10px; margin-right: 10px; margin-bottom: 50px;"><br />
<!--Version: v4.6--><br />
<div style="background-color: #FFFFFFFF;"><br />
<p style="font-size: 23px; padding-left: 15px; padding-top: 10px;">v4.6</p><br />
<div style="background-color: #F5F5F5; width: 100%;"><br />
<div style="display: flex;"><br />
<p style="font-size: 13px; padding-left: 18px; padding-top: 10px; padding-bottom: 10px; margin: 0px;">'''Highly Experimental Feature.'''</p><br />
<p style="font-size: 13px; padding-top: 10px; margin: 0px; padding-left: 150px;">'''Announced'''</p><br />
</div><br />
</div><br />
</div><br />
<!--Version: v4.6--><br />
<!--Version: v4.5--><br />
<div style="background-color: #FFFFFFFF;"><br />
<div style="display: flex;"><br />
<p style="font-size: 23px; padding-left: 15px; padding-top: 10px;">v4.5</p><br />
<p style="font-size: 23px; padding-top: 10px; padding-left: 71px;">2024</p><br />
<div style="width: 92px; height: 22px; border: 2px solid #858585; border-radius: 2px; margin-top: 16px; margin-left: 10px;"><br />
<p style="font-size: 12px; padding-left: 11.5px;">'''Announced'''</p><br />
</div><br />
</div> <br />
<div style="background-color: #F5F5F5; width: 100%;"><br />
<div style="display: flex;"><br />
<p style="font-size: 13px; padding-left: 18px; padding-top: 10px; padding-bottom: 10px; margin: 0px;">'''Cool Feature.'''</p><br />
<div style="width: 59px; height: 21px; background-color: #96D9CD; margin-left: 5px; margin-top: 10px; border-radius: 2px;"><br />
<p style="font-size: 12px; padding-top: 1px; padding-left: 9px;">'''Server'''</p><br />
</div><br />
<p style="font-size: 13px; padding-top: 10px; margin: 0px; padding-left: 189px;">'''Announced'''</p><br />
</div><br />
<div style="display: flex;"><br />
<p style="font-size: 13px; padding-left: 18px; padding-top: 10px; padding-bottom: 10px; margin: 0px;">'''Often Requested Feature.'''</p><br />
<p style="font-size: 13px; padding-top: 10px; margin: 0px; padding-left: 177px;">'''Announced'''</p><br />
</div><br />
</div><br />
</div><br />
<!--Version: v4.5--><br />
<!--Version: v4.4--><br />
<div style="background-color: #FFFFFFFF;"><br />
<div style="display: flex;"><br />
<p style="font-size: 23px; padding-left: 15px; padding-top: 10px;">v4.4</p><br />
<p style="font-size: 23px; padding-top: 10px; padding-left: 71px;">September 2023</p><br />
<div style="width: 118px; height: 22px; border: 2px solid #8CCE59; border-radius: 2px; margin-top: 16px; margin-left: 10px;"><br />
<p style="font-size: 12px; padding-left: 13px;">'''In Development'''</p><br />
</div><br />
<p style="font-size: 13px; padding-top: 18px; padding-left: 650px;">'''View Release Notes'''</p><br />
</div> <br />
<div style="background-color: #F5F5F5; width: 100%;"><br />
<div style="display: flex;"><br />
<p style="font-size: 13px; padding-left: 18px; padding-top: 10px; padding-bottom: 10px; margin: 0px;">'''Signature.'''</p><br />
<div style="width: 38px; height: 22px; border: 2px solid #8B9AD9; margin-left: 5px; margin-top: 10px; border-radius: 2px;"><br />
<p style="font-size: 12px; padding-left: 7px;">'''iOS'''</p><br />
</div><br />
<p style="font-size: 13px; padding-top: 10px; margin: 0px; padding-left: 234px;">'''Pending'''</p><br />
<p style="font-size: 13px; padding-top: 10px; margin: 0px; padding-left: 95px;">'''Xamarin iOS now allows users to create handwritten signatures in-app.'''</p><br />
</div><br />
<div style="display: flex;"><br />
<p style="font-size: 13px; padding-left: 18px; padding-top: 10px; padding-bottom: 10px; margin: 0px;">'''App Configuration.'''</p><br />
<div style="width: 60px; height: 21px; background-color: #96A3D9; margin-left: 5px; margin-top: 10px; border-radius: 2px;"><br />
<p style="font-size: 12px; padding-top: 1px; padding-left: 11px;">'''Mobile'''</p><br />
</div><br />
<p style="font-size: 13px; padding-top: 10px; margin: 0px; padding-left: 160px;">'''Included'''</p><br />
<p style="font-size: 13px; padding-top: 10px; padding-left: 93px;">'''Xamarin Android now supports managed app configuration for rolling out up to 9 Ubik profiles in an<br/>enterprise environment.'''</p><br />
</div><br />
</div><br />
</div><br />
<!--Version: v4.4--><br />
</div><br />
<!--Body: List--></div>LDO