Use the fetchState resource to create an object states package that you upload into other organizations using the loadState resource.

Creating the object states package includes a series of requests and responses, similar to the process of exporting assets. The end result is a ZIP file that contains the object states that you want to load to other organizations. To create the object states package, you perform the following tasks:

Send a lookup GET request to receive the object IDs for the object states you want to synchronize.
Informatica Intelligent Cloud Services
returns the object IDs.
See Lookup.
Send a fetchState POST request to start the job, using the object IDs returned in the lookup response.
Informatica Intelligent Cloud Services
returns the job ID for the fetchState job.
See Starting a fetchState job.
Send a fetchState GET request to get the status of the job, using the fetchState job ID for the object state package.
Informatica Intelligent Cloud Services
returns the job ID and status. The response can also include a list of the object IDs and associated object states that are in the package.
See Getting the fetchState job status.
Send a fetchState GET request to download the package.
Informatica Intelligent Cloud Services
returns the package in a ZIP file.
See Downloading an object states package.

The object states package contains state information in a JSON file for each object. Each file name uses the following format:

<task name>.<task type>.runtime.json

For example, a file with the name of

mt_MappingTask106.MTT.runtime.json

might contain the following data:

You can change the following attributes in an object state file if required:

lastRuntime in the taskRun object
value in the taskStateVariables object (for mapping tasks only)

Other changes to the files in the package can cause unexpected behavior or errors.