ELIAS GmbH
Produktdokumentationen

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
~~NOTOC~~

<WRAP noprint>

> Administrator’s Guide #@IC_HTML@# > Introduction

</WRAP>

====== Overview ======

----

Program and project settings are transferred to #@IC_HTML@# as parameter files. The parameter files are written in the JavaScript Object Notation (JSON, see also [[http://www.json.org/json-en.html|here]]). The flow of input and output data can be simplified as follows.


{{ :en:infra-convert:dev:arbeiten_mit_parameterdateien_beispiel_00.png?nolink&800 |}}

\\ 

During installation, parameter files with default values are stored in the directory "%ProgramData%\ELIAS GmbH\infra-Convert". The parameter files are read either when the program is started, when a new project is created or, if required, during runtime.

^    ^  File  ^  Content  ^  Description  ^
^ Transfer on program start ^^^^
^  {{ :en:infra-convert:dev:icon_dev_einstellungen.png?nolink&80 }}  ^ settings.json | Program or basic settings | Configuration and import > [[en:infra-convert:dev:settings|"Settings" Parameter file]] |
^  {{ :en:infra-convert:dev:icon_dev_uiaccess.png?nolink&80 }}  ^ UiAccess.json | Accessibility of the user interface controls (lock or hide controls) | Configuration and import > [[en:infra-convert:dev:uiaccess|"UiAccess" Parameter file]] |
^ Transfer when creating a new project ^^^^
^  {{ :en:infra-convert:dev:icon_dev_kategorien.png?nolink&80 }}  ^ SpecialCategories.json | Categories | Configuration and import > [[en:infra-convert:dev:specialcategories|Parameter file "SpecialCategories"]] |
^  {{ :en:infra-convert:dev:icon_dev_kennzeichnungen.png?nolink&80 }}  ^ CharacteristicTags.json | Tags | Configuration and import > [[en:infra-convert:dev:characteristictags|Parameter file "CharacteristicTags"]] |
^  {{ :en:infra-convert:dev:icon_dev_stempelvorlagen.png?nolink&80 }}  ^ StampTemplates.json | Stamp templates | Configuration and import > [[en:infra-convert:dev:stamptemplates|Parameter file "StampTemplates"]] |
^  {{ :en:infra-convert:dev:icon_dev_klassen.png?nolink&80 }}  ^ CharacteristicClasses.json | Classes | Configuration and import > [[en:infra-convert:dev:characteristicclasses|Parameter file "CharacteristicClasses"]] |
^ Read during runtime ^^^^
^  {{ :en:infra-convert:dev:icon_dev_toleranztabellen.png?nolink&80 }}  ^ *.json | Tolerance tables (several files) | Configuration and import > Parameter file "Settings" > [[en:infra-convert:dev:settings#list_of_the_settings|List of the settings]] > “Project settings > Tolerance tables” menu\\ \\ Configuration and import > [[en:infra-convert:dev:toltab|Tolerance tables]] |
^  {{ :en:infra-convert:dev:icon_dev_excel.png?nolink&80 }}  ^ *.xltx\\ *.xltm\\ *.xlt | Excel test report templates | Configuration and import > Parameter file "Settings" > [[en:infra-convert:dev:settings#list_of_the_settings|List of the settings]] > “Settings > Export” menu\\ \\ User Manual > More > [[en:infra-convert:user:exceltemp|Create and customize Excel templates]] |

\\ 

===== Working with parameter files =====

The program settings ("settings.json") are loaded when #@IC_HTML@# is started. Changes made by the user (**Edit** (menu bar) > **Settings**) are directly written back to them. With the "UiAccess.json" individual controls can be locked or hidden.

{{ :en:infra-convert:dev:arbeiten_mit_parameterdateien_beispiel_01.png?nolink&800 |}}

\\ 

When a new project is created, the parameter files for categories, tags, stamp templates and classes are used as templates. This means that the definitions are read once and saved in the project. The definitions for categories, tags and stamp templates can be adjusted in the user interface (**Edit** (menu bar) > **Project Settings**). The definitions of classes cannot be changed afterwards. Saving the definitions in the project ensures the interchangeability of projects. Tolerance tables are read out during runtime as required, for example when creating a characteristic or changing characteristic properties. In the following example, the project file (*.icpx) is saved in a "Projects" directory.

{{ :en:infra-convert:dev:arbeiten_mit_parameterdateien_beispiel_02.png?nolink&800 |}}

\\ 

In the example, two drawing sheets are now imported into the project from the "Import" directory. The user creates the test plan based on these. Finally, he exports the stamped drawing sheets in PDF format and the test plan in the form of an Excel test report (*.xlsx) to the "Export" directory. The template for the test report is an Excel template file (*.xltx).

{{ :en:infra-convert:dev:arbeiten_mit_parameterdateien_beispiel_03.png?nolink&800 |}}

\\ 

===== Working with start parameter call =====

Start parameters can be used to implement automatisms that facilitate the work flow with always the same work processes. This administration is necessary when #@IC_HTML@# is integrated into a CAQ/MES system and also useful when the user is to be given standard settings and workflows. The available start parameters are combined in a start parameter file, see "Configuration and Import > [[en:infra-convert:dev:parameter|Startup parameter file]]".

> **Note** With the start parameter "forceConfigDir", a different directory than the ProgramData directory can be specified. It is the only one not passed in the start parameter file, see "Configuration and Import > [[en:infra-convert:dev:parameter|Startup parameter file]]".

The following example shows some possibilities for working with start parameter calls. In the start parameter file a "settings.json" and a "UiAccess.json" is referenced. For example, the "Configuration" directory may be located on a corporate server. When #@IC_HTML@# is started these parameter files are loaded instead of the parameter files in the ProgramData directory. The "settings.json" contains a selection of possible settings, which overwrite the local settings of the user.

{{ :en:infra-convert:dev:arbeiten_mit_parameterdateien_beispiel_04.png?nolink&800 |}}

\\ 

Des Weiteren ist in der beispielhaften Startparameterdatei vorgegeben, dass

  * nach dem Start sofort ein neues Projekt mit den Definitionen für Kategorien, Kennzeichnungen, Stempelvorlagen und Klassen aus dem Verzeichnis "Konfiguration" angelegt wird,

  * zwei Zeichnungsblätter aus einem Verzeichnis "Import" direkt in die erste Prüfplanversion geladen werden,

  * die Projektdatei im Verzeichnis "Projekte" zu speichern ist und

  * beim Speichern die gestempelten Zeichnungsblätter als PNG-Grafiken und der Prüfplan im JSONV1-Format in das Verzeichnis "Export" exportiert werden.

<WRAP noprint>

----

<WRAP group>
<WRAP col2>

<WRAP rightalign>
**Go to previous page**\\ 
Introduction > [[en:infra-convert:dev:Wiki|Tips on the Administrator’s Guide]]
</WRAP>

**Go to next page**\\ 
Configuration and Import > [[en:infra-convert:dev:parameter|Startup parameter file]]

</WRAP>
</WRAP>

</WRAP>
ELIAS GmbHProduktdokumentationen

User Tools

Site Tools

Page Tools

ELIAS GmbH
Produktdokumentationen
