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 Manual #@IC_HTML@# > Configuration and Import

</WRAP>

====== Startup parameter file ======

----

The startup parameter file is opened by transferring adjacent request parameters by executing #@IC_HTML@#. The value of the parameter is the absolute or relative path to the startup parameter file, including the file name (example syntax: "C:/Windows/Temp/StartParameterFile.json"). Additional request parameters cannot be transferred at this point.

> **Note** Up to program version 1.3.5.5, only absolute paths can be specified, both as values of the initial startup parameter and within the startup parameter file.

<WRAP group>
<WRAP indent>
<WRAP column 70%>

<code>
InfraConvertWPF.exe -parameter="C:/Windows/Temp/StartParameterFile.json"
</code>

</WRAP>
</WRAP>
</WRAP>

> **Note** Use slash characters ("/") to separate directory names in paths. Not all operating systems support the backslash ("\").

This chapter explains the structure of the startup parameter file. The file may contain any part of the transfer values presented here, but it must adhere to the provisions for setting up a JSON file.

<WRAP group>
<WRAP column 61%>

You can find a complete example of a startup parameter file here: Appendix > [[en:infra-convert:dev:parameter_beispiel|Example startup parameter file]]

</WRAP>
<WRAP column 33%>

[[en:infra-convert:dev:parameter_beispiel|{{ :en:infra-convert:dev:startparameterdatei_beispiel.png?nolink&250 |}}]]

\\ 

</WRAP>
</WRAP>


<WRAP group>
<WRAP column 61%>

A self-contained set of parameter files for direct testing can be downloaded from the link below.

</WRAP>
<WRAP column 33%>
<WRAP centeralign>

{{:en:infra-convert:dev:infraCONVERTParametertest.zip|infraCONVERTParametertest.zip}}

</WRAP>
</WRAP>
</WRAP>

Unpack the ZIP archive in the folder "C:/Windows/Temp/" and execute #@IC_HTML@# with reference to the start parameter file contained in it. You can pass the start parameter e. g. with the included Windows batch file.

<WRAP noprint>
<WRAP group>
<WRAP column 48%>
//**__Content__**//

 • [[en:infra-convert:dev:parameter#Setting the language]]\\ 
 • [[en:infra-convert:dev:parameter#Open or create project]]\\ 
 • [[en:infra-convert:dev:parameter#Open or create quality test plan]]\\ 
 • [[en:infra-convert:dev:parameter#Transfer drawing]]\\ 
 • [[en:infra-convert:dev:parameter#Export quality test plans and stamped drawings]]\\ 
 • [[en:infra-convert:dev:parameter#Invoke function]]\\ 
 • [[en:infra-convert:dev:parameter#Zoom on stamp]]\\ 
 • [[en:infra-convert:dev:parameter#Settings]]\\ 
 • [[en:infra-convert:dev:parameter#Parameter file for tags]]\\ 
 • [[en:infra-convert:dev:parameter#Parameter file for characteristic classes]]\\ 
 • [[en:infra-convert:dev:parameter#Parameter file for characteristic categories]]\\ 
 • [[en:infra-convert:dev:parameter#Parameter file for stamp templates]]\\ 
 • [[en:infra-convert:dev:parameter#Parameter file for showing/hiding/locking control elements]]\\ 
 • [[en:infra-convert:dev:parameter#Editing characteristics]]\\ 
 • [[en:infra-convert:dev:parameter#Editing tags]]

\\ 

</WRAP>
</WRAP>
</WRAP>

===== Setting the language =====

<WRAP group>
<WRAP column 40%>

Use the **LanguageCode** field to specify the language of the user interface of #@IC_HTML@#.

Without this code, the default language set in the operating system will automatically be used. If it is not supported by #@IC_HTML@#, English will always be set.


> **See also**
> User’s Manual #@IC_HTML@# > Settings > Settings > [[en:infra-convert:user:config:general|General]] > [[en:infra-convert:user:config:general#Gruppe „Sprache“|“Language” Group]]

</WRAP>
<WRAP column 55%>

<code javascript>
"LanguageCode":"de",
</code>

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ LanguageCode | String | **de** German\\ **en** English\\ **fr** French\\ **it** Italian\\ **es** Spanish\\ **ru** Russian |

</WRAP>
</WRAP>

\\ 

===== Open or create project =====

<WRAP group>
<WRAP column 40%>

With the **Project** field, specify that an existing project should open or a new project be created when #@IC_HTML@# is launched.

> **See also**
> User’s Manual #@IC_HTML@# > Functions > Projects > [[en:infra-convert:user:functions:newproject|Create new project]]
> 
> User’s Manual #@IC_HTML@# > Functions > Projects > [[en:infra-convert:user:functions:openproject|Open project]]
> 
> User’s Manual #@IC_HTML@# > Functions > Projects > [[en:infra-convert:user:functions:saveproject|Save project]]

</WRAP>
<WRAP column 55%>

<code javascript>
"Project": {
  "Path": "C:/Users/user1/Desktop/test.icpx",
  "Name":"Beispiel Projekt",
  "Action":"Open"
}
</code>

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ Path | String | Full path to the location with the file name |
^ Name | String | Project title (ignored when opening) |
^ Action | String | **Open** Opens an existing project\\ **Create** Creates a new project |

</WRAP>
</WRAP>

\\ 

===== Open or create quality test plan =====

<WRAP group>
<WRAP column 40%>

With the **InspectionPlanVersion** field, specify that an existing quality test plan should open or a new quality test plan be created when #@IC_HTML@# is launched.

A new quality test plan can only be created when a project has already been created.

> **See also**
> User’s Manual #@IC_HTML@# > Functions > Quality test Plans > [[en:infra-convert:user:functions:1stqcp|Create quality test plan]]

</WRAP>
<WRAP column 55%>

<code javascript>
"InspectionPlanVersion": {
  "Name": "Zeichnungsstand",
  "Version": "0",
  "Action": "Create"
}
</code>

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ Name | String | Quality test plan title (ignored when opening) |
^ Version | Decimal | Version of the quality test plan (ignored when opening) |
^ Action | String | **Open** Opens an existing quality test plan\\ **Create** Creates a new quality test plan |

</WRAP>
</WRAP>

\\ 

===== Transfer drawing =====

<WRAP group>
<WRAP column 40%>

Use the **Files** field to import any number of drawing sheets in a quality test plan when #@IC_HTML@# is launched.

> **See also**
> User’s Manual #@IC_HTML@# > Functions > Drawings > [[en:infra-convert:user:functions:drwimport|Import drawings]]
> 
> User’s Manual #@IC_HTML@# > More > [[en:infra-convert:user:terms#Zeichnungsdatenformat|Terms]] > Drawing date format

</WRAP>
<WRAP column 55%>

<code javascript>
"Files": [
  {
  "Path":"C:/Users/user1/Desktop/drawing_1.dxf"
  },
  {
  "Path":"C:/Users/user1/Desktop/drawing_2.igs"
  },
  {
  "Path":"C:/Users/user1/Desktop/drawing_3.pdf"
  },
  {
  "Path":"C:/Users/user1/Desktop/drawing_4.icp"
  },
  {
  "Path":"https://ftp.elias-gmbh.de/fictional_path/example.dwg"
  }
]
</code>

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ Path | String | Full path to the location with the file name\\ \\ **Note** It is possible to specify the path in URL notation, beginning with "https" and "http", from program version 1.3.5.7 onwards. |

</WRAP>
</WRAP>

\\ 

===== Export quality test plans and stamped drawings =====

<WRAP group>
<WRAP column 40%>

With the **Targets** field, specify that when the **Save project** command is executed in quality test plans and/or stamped drawings and/or drawing details in #@IC_HTML@# should be exported.

> **Note** We recommend you use the quality test plan format JSONV1 because it supports all the characteristics of #@IC_HTML@#.

> **See also**
> Administrator’s Manual #@IC_HTML@# > Export > [[en:infra-convert:dev:export:jsonv1|Quality test plan format JSONV1]]
> 
> Administrator’s Manual #@IC_HTML@# > Export > [[en:infra-convert:dev:export:dfd|Quality test plan format DFD]]

</WRAP>
<WRAP column 55%>

<code javascript>
"Targets": [
  {
    "Format":"JSONV1",
    "LanguageCode":"de",
    "Path":"C:/Temp/testplan.json"
  },
  {
    "Format":"CSV",
    "Path":"C:/Temp/CSV/testplan.csv"
  },
  {
    "Format":"DFD",
    "Path":"C:/Temp/DFD/"
  },
  {
    "Format":"PDF",
    "Path":"C:/Temp/PDF/"
  },
  {
    "Format":"Png",
    "Path":"C:/Temp/Graphics/",
  {
    "Format":"Jpg",
    "Path":"C:/Temp/Graphics/",
    "Mode":"Drawing"
  },
  {
    "Format":"Bmp",
    "Path":"C:/Temp/Graphics/",
    "Mode":"Stamps"
  }
]
</code>

The following applies for the JSONV1 quality test plan format:

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ Format | String | **JSONV1** |
^ LanguageCode | String | **de** German\\ **en** English |
^ Path | String | Full path to the location with the file name |

The following applies for the CSV quality test plan format:

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ Format | String | **CSV** |
^ Path | String | Full path to the location with the file name |

The following applies for the DFD quality test plan format:

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ Format | String | **DFD** |
^ Path | String | Full path to the location without a file name |

This applies to drawing exports in PDF und SVG format:

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ Format | String | **PDF** All drawing sheets each as a PDF file\\ **SVG** All drawing sheets each as a SVG file |
^ Path | String | Full path to the location without a file name |

This applies to drawing exports in PNG, JPG, BMP, TIF und GIF format:

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ Format | String | **Png** All drawing sheets and/or all stamped characteristics in extracts as PNG files\\ **Jpg** All drawing sheets and/or all stamped characteristics in extracts as JPG files\\ **Bmp** All drawing sheets and/or all stamped characteristics in extracts as BMP files\\ **Tif** All drawing sheets and/or all stamped characteristics in extracts as TIF files\\ **Gif** All drawing sheets and/or all stamped characteristics in extracts as GIF files |
^ Mode | String | **Drawing** Only drawing sheets\\ **Stamps** Only stamp graphics\\ \\ If **Mode** is not specified, drawing and stamp graphics are exported together |
^ Path | String | Full path to the location without a file name |

</WRAP>
</WRAP>

\\ 

===== Invoke function =====

<WRAP group>
<WRAP column 40%>

With the **Mode** field, call up a function in #@IC_HTML@# when it is launched. The function will not be executed, but it will be opened and is thus directly available to the user. The following functions are currently available (more will follow):

  * **Tag tool**\\ //AddCharacteristicTag//\\ Calls up the tag tool function, see User’s Manual > Functions > characteristics > [[en:infra-convert:user:functions:labeling|Tag]].


  * **Drawing comparison**\\ (Available from program version 1.2)\\ //Compare Documents//\\ Calls up the drawing comparison, see User's manual > User interface > Function window > [[en:infra-convert:user:interface:drwcomp|Drawing comparison]] and User’s Manual > Functions > [[en:infra-convert:user:functions:drwcompsimple|Zeichnungen vergleichen (Basic version)]] respectively [[en:infra-convert:user:functions:drwcomp|Drawing comparison (Pro version)]].

</WRAP>
<WRAP column 55%>

The following applies for the **Tag tool** function:

<code javascript>
"Mode": {
  "Name": "AddCharacteristicTag",
  "ItemId": "{5D1110CA-6093-4381-B372-CF983D515044}"
}
</code>

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ Name | String | AddCharacteristicTag |
^ ItemId | String | GUID of the tag |

The following applies for the **Drawing comparison** function:

<code javascript>
"Mode":{  
   "Name":"CompareDocuments",
   "SourceInspectionPlanVersion":{  
      "Name":"Neuer Prüfplan",
      "Version":"A"
   },
   "TargetInspectionPlanVersion":{  
      "Name":"Neuer Prüfplan",
      "Version":"B"
   },
   "SourceDocumentOriginalFileName":"ez-29002675001-84-0_1.dxf",
   "TargetDocumentOriginalFileName":"ez-29002675001-84-a_1.dxf"
}
</code>

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content ^
^ Name | String | CompareDocuments |
^ SourceInspectionPlanVersion | Field |  |
^ └ Name | String | Name of the source test plan version |
^ └ Version | String | Version number of the source test plan version |
^ TargetInspectionPlanVersion | Field |  |
^ └ Name | String | Name of the target test plan version |
^ └ Version | String | Version number of the target test plan version |
^ SourceDocumentOriginalFileName | String | File name of the source drawing sheet |
^ TargetDocumentOriginalFileName | String | File name of the target drawing sheet |

</WRAP>
</WRAP>

\\ 

<WRAP group>
<WRAP column 66.5%>
===== Zoom on stamp =====

</WRAP>
<WRAP column 25%>
> **Available from**\\ program version 1.2.0.21
</WRAP>
<WRAP column 15%>
</WRAP>

</WRAP>


<WRAP group>
<WRAP column 40%>

When opening a project, you can set the view in the drawing window to a specific stamp. #@IC_HTML@# focuses the stamp and zooms in so far that the corresponding drawing entry including the surrounding area is fitted into the window.

Each stamp in an ICPX file is assigned a GUID. Pass it in the field **ZoomToStampGuid**. If characteristics have been linked by transfer or merge in the drawing comparison, you can also transfer the ID of the original stamp, then the system zooms to the corresponding stamp of the latest inspection plan version.

If ICP files are loaded into a project, the GUIDs of the stamps may not be known. In this case, you can also pass the stamp ID. Use the field **ZoomToStampIcpId**. In this field you must also specify the test plan version and the name of the ICP file, because the ID from #@IC_OLD_HTML@# is only valid within an ICP project.


> **Note**
> #@IC_HTML@# can also be used as a viewer with the zoom functionality. Disable user interface controls (see "Configuration and Import > [[de:infra-convert:dev:uiaccess|Parameter file "UiAccess"]]") to prevent data corruption. To view ICP files, temporarily create an ICPX project and load the ICP file into a test plan version.

</WRAP>
<WRAP column 55%>
The GUID of the stamp is known:

<code javascript>
"ZoomToStampGuid":{  
   "Id":"{56422575-2376-497f-b633-8dbe06626fab}"
}
</code>

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ Id | String | GUID of the stamps |

Only the ID of the stamp in the ICP file is known:

<code javascript>
"ZoomToStampIcpId":{
   "InspectionPlanVersion":{  
      "Name":"Neuer Prüfplan",
      "Version":"A"
   },
   "DocumentName":"ez-29002675001-84-0_1.icp",
   "Id":"3"
}
</code>

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ InspectionPlanVersion | Feld |  |
^ └ Name | String | Title of the test plan version |
^ └ Version | String | Version number |
^ DocumentName | String | Name of the ICP file |
^ Id | String | ICP ID |

</WRAP>
</WRAP>

\\ 

===== Settings =====

<WRAP group>
<WRAP column 40%>

The path to the parameter file //Settings.json// is specified in the **Settings** field. #@IC_HTML@# obtains the global settings from this file.

> **Please note** Changes made by the user in the user interface are not written to the "settings.json" loaded here, but to the "settings.json" in the CommonAppData directory whose path is defined in the "settings.json" with the parameter "CommonAppDataPath".

> **See also**
> Administrator’s Manual #@IC_HTML@# > Run program > [[en:infra-convert:dev:settings|Parameter file "Settings"]]
> 
> Administrator’s Manual #@IC_HTML@# > Configuration and Import > "Settings" Parameter file > [[en:infra-convert:dev:settings#list_of_the_settings|List of the settings]] > Settings with no control elements in user interfaces 
> 
> User’s Manual #@IC_HTML@# > Settings > Settings > [[en:infra-convert:user:config:general|General]]

</WRAP>
<WRAP column 55%>

<code javascript>
"Settings": {
  "Path": "C:/ProgramData/ELIAS GmbH/infra-CONVERT/Settings.json",
}
</code>

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ Path | String | Full path to the location and file name |

</WRAP>
</WRAP>

\\ 

===== Parameter file for tags =====

<WRAP group>
<WRAP column 40%>

The path to the parameter file //CharacteristicTags.json// is specified in the **CharacteristicTagsDefinition** field. #@IC_HTML@# obtains the definitions for tags with which the project is saved from this file.

If this file does not exist, it will be created with the default settings.

> **See also**
> Administrator’s Manual #@IC_HTML@# > Run program > [[en:infra-convert:dev:characteristictags|Parameter file "CharacteristicTags"]]
>
> User’s Manual #@IC_HTML@# > Settings > Project settings > [[en:infra-convert:user:config:label|Tags]]

</WRAP>
<WRAP column 55%>

<code javascript>
"CharacteristicTagsDefinition": {
  "Path": "C:/Users/user1/AppData/CharacteristicTags.json",
}
</code>

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ Path | String | Full path to the location and file name |

</WRAP>
</WRAP>

\\ 

===== Parameter file for characteristic classes =====

<WRAP group>
<WRAP column 40%>

The path to the parameter file CharacteristicClasses.json is specified in the //CharacteristicClassesDefinition// field. #@IC_HTML@# obtains the definitions for characteristic classes with which the project is saved from this file.

> **See also**
> Administrator’s Manual #@IC_HTML@# > Configuration and Import > [[en:infra-convert:dev:characteristicclasses|Parameter file "CharacteristicClasses"]]
>
> User’s Manual #@IC_HTML@# > More > [[en:infra-convert:user:terms#Klasse (Merkmals-)|Terms]] > Class (characteristic-)

</WRAP>
<WRAP column 55%>

<code javascript>
"CharacteristicClassesDefinition": {
  "Path": "C:/Users/user1/AppData/CharacteristicClasses.json"
}
</code>

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ Path | String | Full path to the location and file name |

</WRAP>
</WRAP>

\\ 

===== Parameter file for feature categories =====

<WRAP group>
<WRAP column 40%>

The path to the parameter file //SpecialCategories.json// is specified in the **SpecialCategoriesDefinition** field. #@IC_HTML@# obtains the definitions for characteristic categories with which the project is saved from this file.

> **See also**
> User’s Manual #@IC_HTML@# > Settings > Project settings > [[en:infra-convert:user:config:cat|Categories]]
> 
> User’s Manual #@IC_HTML@# > More > [[en:infra-convert:user:terms#Kategorie (Merkmal-)|Terms]] > Category (characteristic)

</WRAP>
<WRAP column 55%>

<code javascript>
"SpecialCategoriesDefinition": {
  "Path": "C:/Users/user1/AppData/SpecialCategories.json"
}
</code>

|< 100% 33% 12% 54% >|
^  Parameter  ^  Typ  ^  Value/Content  ^
^ Path | String | Full path to the location and file name |

</WRAP>
</WRAP>

\\ 
===== Parameter file for stamp templates =====

<WRAP group>
<WRAP column 40%>

The path to the parameter file //StampTemplates.json// is specified in the **StampTemplatesDefinition** field. #@IC_HTML@# obtains the definitions for stamp templates which are saved with the project, from this file.

> **See also**
> Administrator’s Manual #@IC_HTML@# > Configuration and Import > [[en:infra-convert:dev:stamptemplates|Parameter file "StampTemplates"]]
>
> User’s Manual #@IC_HTML@# > Settings > Project settings > [[en:infra-convert:user:config:stamppattern|Stamp templates]]

</WRAP>
<WRAP column 55%>

<code javascript>
"StampTemplatesDefinition": {
  "Path": "C:/Users/user1/AppData/StampTemplates.json"
}
</code>

|< 100% 33% 12% 54% >|
^  Parameter  ^  Typ  ^  Value/Content  ^
^ Path | String | Full path to the location and file name |

</WRAP>
</WRAP>

\\ 

===== Parameter file for showing/hiding/locking control elements =====

<WRAP group>
<WRAP column 40%>

The **UiAccessDefinition** field sets the path to the //UiAccess.json// parameter file. It can be used to control which control elements in the #@IC_HTML@# user interface should be visible, locked or hidden.

If the file does not exist, it will be created with the usual default settings.

> **See also**
> Administrator's Manual #@IC_HTML@# > Configuration and Import > [[en:infra-convert:dev:uiaccess|Parameter file "UiAccess"]]

</WRAP>
<WRAP column 55%>

<code javascript>
"UiAccessDefinition": {
  "Path": "C:/Users/user1/AppData/UiAccess.json",
}
</code>

|< 100% 33% 12% 54% >|
^  Parameter  ^  Typ  ^  Value/Content  ^
^ Path | String | Full path to the location and file name |

</WRAP>
</WRAP>

\\ 

===== Editing characteristics =====

<WRAP group>
<WRAP column 40%>

The //Characteristics// field allows you to communicate to #@IC_HTML@# which characteristics have changed in an existing project since it was last edited. If new tags were assigned in a CAQ system, for instance, this method allows them to also be reassigned in the project.

> **See also**
> User’s Manual #@IC_HTML@# > User interface > Function window > [[en:infra-convert:user:interface:feature|characteristic properties]]

</WRAP>
<WRAP column 55%>

<code javascript>
"Characteristics": [
  {
    "CharacteristicId": "66a58671-5b11-4135-8210-32701be6f4a5",
    "Action":"Update",
    "CharacteristicTags": [
      "5D1110CA-6093-4381-B372-CF983D515044",
      "24C41CA8-871C-456E-B082-22EC2A20216D"
    ],
    "SpecialCategory":"{3E298F8F-02F1-49CD-82BF-BCDF26DA11FE}"
  },
  {
    "CharacteristicId": "b29bfa80-294a-4ca6-ae8f-81f4e63a39be",
    "Action":"Update",
    "CharacteristicTags": [ "5D1110CA-6093-4381-B372-CF983D515044" ],
    "SpecialCategory":"{3E298F8F-02F1-49CD-82BF-BCDF26DA11FE}"
  }
]
</code>

|< 100% 33% 12% 54% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ CharacteristicId | String | GUID of the characteristic |
^ Action | String | **Update** Action: update |
^ CharacteristicTags | String | GUID of the tag |
^ SpecialCategory | String | GUID of the category |

</WRAP>
</WRAP>

\\ 

===== Editing tags =====

<WRAP group>
<WRAP column 40%>

The **CharacteristicTags** field allows you to communicate to #@IC_HTML@# which tags have been added or changed since the last time a project was edited.

> **See also**
> User’s Manual #@IC_HTML@# > Settings > Project settings > [[en:infra-convert:user:config:label|Tags]]

</WRAP>
<WRAP column 55%>

<code javascript>
"CharacteristicTags": [
  {
    "Action": "AddOrUpdate",
    "CharacteristicTag":{
      "Id": "69A6290C-89E2-438B-A2D7-F0AA645409CA",
      "Priority": 2,
      "FriendlyName": "TagThree",
      "Color": {
        "Type": "RGB",
        "R": 0,
        "G": 255,
        "B": 0
      },
      "LocalizedProperties": [
        {
          "Name": "Tag Three ",
          "Description":"",
          "LanguageCode": "en"
        },
        {
          "Name": "Kennzeichnung Drei",
          "Description": "",
          "LanguageCode": "de"
        }
      ]
    }
  },
  {
    "Action": "AddOrUpdate",
    "CharacteristicTag":{
      "Id": "5D1110CA-6093-4381-B372-CF983D515044",
      "Priority": 2,
      "FriendlyName": "",
      "Color": {
        "Type": "RGB",
        "R": 0,
        "G": 0,
        "B": 255
      },
      "LocalizedProperties": [
        {
          "Name": "Tag Four ",
          "Description":"",
          "LanguageCode": "en"
        },
        {
          "Name": "Kennzeichnung Vier",
          "Description": "",
          "LanguageCode": "de"
        }
      ]
    }
  }
]
</code>

|< 100% 34% 12% 53% >|
^  Parameter  ^  Type  ^  Value/Content  ^
^ Action | String | **AddOrUpdate** Add or change a tag, depending on whether or not the tag exists |
^ CharacteristicTag | Feld | Contains all the properties of the tag |
^ └ Id | String | GUID of the tag |
^ └ Priority | Integer | Rank in the order of existing tags |
^ └ FriendlyName | String | Name of the tag |
^ └ Color | Feld | Stamp color of a characteristic with this tag |
^  └ Type | String | **RGB** "RGB" color system |
^  └ R | Integer | Color value for red: 0...255 |
^  └ G | Integer | Color value for green: 0...255 |
^  └ B | Integer | Color value for blue: 0...255 |
^ └ LocalizedProperties | Feld | Name of the tag (possible for multiple languages) |
^  └ Name | String | User-friendly name of the tag |
^  └ Description | String | Description of the tag (optional) |
^  └ LanguageCode | String | **de** German\\ **en** English |

</WRAP>
</WRAP>

<WRAP noprint>

----

<WRAP group>
<WRAP col2>

<WRAP rightalign>

**Go to previous page**\\ 
Introduction > [[en:infra-convert:dev:intro|Overview]]

</WRAP>

**Go to next page**\\ 
Configuration and Import  > [[en:infra-convert:dev:settings|Parameter file "Settings"]]

</WRAP>
</WRAP>

</WRAP>
ELIAS GmbHProduktdokumentationen

User Tools

Site Tools

Page Tools

ELIAS GmbH
Produktdokumentationen
