Skip to content

Export item

Easit GO gives you the possibility to post, or export, an object to a URL at one specific or several events. This is made possible with the event handler function Export item and can be used to integrate Easit GO with other systems and applications or trigger Easit ProcessRunner to run a script with data from the object as input. The Export item supports HTTP, SOAP and REST as its transfer protocols and basic authentication for authorization.

This guide will try to explain how to configure the Export object function.

General

Let's say that each time a contacts first name, surname or email is updated, we want to "send" that information to our HR application.

Define what data to include in the export

We start by defining what data to include in the export. Open the control panel by clicking on the cog in the upper right corner of Easit GO, type export configuration and click in the result Integration - Import and export - Export configuration. Select the Contact module in the drop-down menu to the right and then click on Add.

Give the configuration a clear name and a description so others or future you can understand why this configuration exist.

whattoexport1

If we wanted to include any files saved on the contact or if we want to specify how datasources like category (multilevel combobox) or status (combobox) is handled we could configure this here.

whattoexport2

The last section is were we specify what fields in Easit GO to export and what property name it should have in the JSON/XML output.

whattoexport3

Define when the data should be exported

In this step we will define when the data should be exported and we do this by creating an item event handler, more on event handlers here. As we want to trigger the event handler each time a contacts first name, surname or email is updated the configuration will look like this.

whattoexport3

We have left out the sections Field rules before change and Field rules after change as they do not need any configuration in are use case. If we wanted to trigger the event handler in a more specific scenario we can add some rules here. For example, we could say that e-mail should be empty before the contact is update and not empty after the contact is updated.

Define where the data should be exported to

Last but not least, we define what should happen when the event handler is triggered. In our case we want to export the item, so we click on the + icon under Do this, select Export item and then click on OK. We then click on the cog to the right, and we should see a popup like the image below. Here we configuration our action, the Export item action.

wheretoexport

We can select what type of protocol or structure of the data to use, where to export the item (URL), how to authenticate to the URL, specify an identifier and choose what configuration that defines what data the export should include.

Resulting output

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
    {
        "importHandlerIdentifier":"updateContactInHR-system",
        "itemToImport":[
            {
                "property":[
                    {
                        "content":"John",
                        "name":"firstName",
                        "rawValue":null
                    },{
                        "content":"john@doe.com",
                        "name":"mail",
                        "rawValue":null
                    },{
                        "content":"cn=john doe,ou=users,dc=doe,dc=com",
                        "name":"fqdn",
                        "rawValue":null
                    },{
                        "content":"Doe",
                        "name":"surname",
                        "rawValue":null
                    },{
                        "content":"839475",
                        "name":"employeeNumber",
                        "rawValue":null
                    }
                ],
                "attachment":[],
                "id":"123456:2",
                "uid":"123456"
            }
        ],
        "genericRequestProperty":[
            {
                "content":"updateContactInHR-system",
                "name":"identifier"
            },{
                "content":"MC0CFHnd2e81XFZezdFIHPj5i+A/6dbPAhUAkUKMTyjRZtJ7SZ6c/3KL0aeZKd4=",
                "name":"initializedByXmlExport"
            }
        ]
    }

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
    <EasitImport type="" version="1.0">
    <Items>
        <Item uid="123456">
            <Properties>
                <Property name="firstName">John</Property>
                <Property name="mail">john@doe.com</Property>
                <Property name="fqdn">cn=john doe,ou=users,dc=doe,dc=com</Property>
                <Property name="surname">Doe</Property>
                <Property name="employeeNumber">839475</Property>
            </Properties>
            <Attachments/>
        </Item>
    </Items>
    <ClientInfo>
        <ClientName>Easit BPE</ClientName>
        <ClientProperties>
            <ClientProperty name="identifier">updateContactInHR-system</ClientProperty>
            <ClientProperty name="initializedByXmlExport">MC0CFHnd2e81XFZezdFIHPj5i+A/6dbPAhUAkUKMTyjRZtJ7SZ6c/3KL0aeZKd4=</ClientProperty>
        </ClientProperties>
    </ClientInfo>
    </EasitImport>

Once you have performed all the steps above you should have Easit GO export a contact each time a contacts first name, surname or email is updated to the HR application. The export will include e-mail, employee number, first name, surname and FQDN.