Data Manager

A data manager saves the value of data extraction path specified in the <path-config> to perform automation. The data manager will save only the response body of a resource.

How Data Manager saves data?

The specifications provided in the <resource-config> is used for identifying which data has to be stored.

For example, consider the GET response of Trips API.

    

        
copy
        

            

        
    
    

         
{
    "trips": [
        {
            "trip_name": "Bali - John Smith",
            "trip_id": "5545974000000006871", 
            "no_of_days": 2
        },
        {
            "trip_name": "London - Emily Jones",
            "trip_id": "5545974000000006873",
            "no_of_days": 10
        },
        {
            "trip_name": "Sidney - Patrick Robinson",
            "trip_id": "5545974000000006875",
            "no_of_days": 5 
        }
    ]
}

    

Following are the <path-config> specifications provided for the trips resource in the ZSPEC.

    

        
copy
        

            

        
    
    

         
<path-config data-extraction-path="$.trips">
    <primary path="$.trip_id" />
</path-config>

    

Here, the value of the trips is an array of records. Every record will be stored with respect to their primary key (trip_id).

The data manager saves the responses in the following format,

trips > trips > Id1 - entity1, Id2 - entity2, Id3 - entity3

If your resource does not have a primary key, ZEST will save the object with respect to an integer 1. The data manager will consistently maintain the most recent version of the data. To illustrate, imagine a scenario where the GET trips API is invoked 10 times. With each call, there is a slight modification to the record data. ZEST’s data manager will invariably possess the updated data from the 10th API call.