Application (Automate)

From GeoMedia Smart Client
Jump to: navigation, search
Application Actions Print Layouts Workflow Connections Resources Automate

With XMLAutomate, the third-party manufacturers of desktop or Web applications will be offered the ability to operate GeoMedia Smart Client or to export data from the GMSC. Detailled information about this topic can be found here. If you want to do this click on Automate on the right hand side at the tab Application.

A new window opens, where you either can get an Overview or create a New Entry.


If you create a New Entry you get forwarded to the next list, where you select the project in whose you will import your own XML file or export data from GMSC.



Field Description
Name Name of the feature. Use a descriptive one for better handling and usability.
Project Not available at this point anymore. You've already chosen the project a step before.
Feature Filter Filter the feature list by Feature Id or Feature Name. Click on Apply Filter to use the filter.
Feature Define the feature which should be exported. So check the box in front of the feature name.

Import/Export Settings

test To the top Pfeil new.png


Import Settings

test To the top Pfeil new.png

Blue.pngBe aware that you have to define an own folder for every XSLT tranformation.

Field Description
Import Xslt Click Select and define your XSLT file with whose it is possible to transform your own XML file into a readable XML for GMSC.
Import definition In this textfield you can define your Import definition. For example the foreign keys of your database and the database GMSC is using are different you can define here your Import definition. For example you are using using Municipality (Mun_Key) and Parcel Number (Parcel) as a foreign key and the database of GMSC is using ID as a foreign key. So you have to put the two foreign keys together. The same the other way round. In the Export definition you can split the ID of the GMSC database into Municipality (Mun_Key) and Parcel Number (Parcel).

Example 1 shows your when are using one external key:

Blue.png Select ID1 from SCHOOL_P where PARCEL = {ENTITY.PARCEL}

Example 2 shows you when you are using two external keys:


You have to use the same placeholder as the key used in the XML.

Import processor If XSLT isn't enough for your own XML or if you have to transform your own file into a XML, which then can be transformed, it is possible to define an own application. In the textfield Import processor: you have to type in the path to your application.

Blue.pngFor example (Windows 7): C:\MyFolder\MyApplication.exe or it is also possible to use environmental variables like %APPDATA% to define your path.

Import folder In this textbox you define where your own XML file is stored. Either you set it like it was mentioned before (full path or using environmental variables) or you leave the texfield blank, then the default folder is used.

Blue.pngThe default folder in Windows 7: C:\Users\MyUserName\AppData\Roaming\Intergraph\SmartClient\automate\IMPORT or %APPDATA%\Intergraph\SmartClient\automate\IMPORT.

All in all there are three possibilities to import your own files to GMSC:

  • 1. The structure of your XML file is the same as of the one of GMSC. Then it is enough to define an Import folder if your XML file isn't stored in the default folder.
  • 2. The structure of your XML is similar to the one of GMSC but a few modifications have to be done, Select your XSLT file to transform the XML file. As mentioned above you have be aware of the Import folder.
  • 3. You have a complete different file (like TXT) and you want to import it into GMSC. Define the path to your application, that converts the file in a readable XML file. The big advantage is, if your application automatically transform it to an XML file, which can be read by GMSC. If not you have additionally define your XSLT file. Be aware of your Import folder.

Export Settings

test To the top Pfeil new.png

In fact your export settings are the import settings the other way round. That means you can define your XSLT file, which converts for example the XML structure of GMSC into a structure, which is convenient for you (Export Xslt:). Then you have maybe your own application, which coverts the XML file into a binary file (Export processor). Maybe you have to set an Export definition like for the example mentioned above. If you want to set another Export folder than you can define it in the last texfield. If nothing is set in there the default folder is used.

Blue.pngExample for an Export definition: Select MUN_KEY, PARCELS from TABLENAME where ID1 in ({ENTITY.SELECTIONSET}).

Blue.pngThe default folder in Windows 7: C:\Users\MyUserName\AppData\Roaming\Intergraph\SmartClient\automate\EXPORT or %APPDATA%\Intergraph\SmartClient\automate\EXPORT.

There are some possibilities how to export something from GMSC:

Blue.pngFor an export you have to define an automateExport action. How to create new actions have a look at Actions.

  • 1. You've named your automate and checked one or more features. Then you have defined your automateExport action. If you click in the GeoMedia Smart Client on the button you have defined in your action, a XML file in the default folder is generated.
  • 2,3,4. There are the same options you have for the import settings, just the other way round.

Language: English  • slovenčina