Rest API get all Templates/Datamappers/JobPreset/

1

Hi there,

I’ve been looking through the documentation but can’t seem to find anything that will return a list of all the currently uploaded

Data Mapping Configuration ID/Name:,
Template ID/Name:,
Job Creation Preset ID/Name:,
Output Creation Preset ID/Name:,

Is this sort of functionality included in the rest api?

cheers

2

You can get that information from the FileStore, through the REST api: List Resources

Note that you can also get a list of all resources that have been sent to Workflow by using the Watch.GetResources() method in a script.

3

Hi Phil,

Thanks for this info.

I’ve had a quick look at these this morning.

I’m getting different resources returned from the 2 methods.

The list resources method from the rest API is giving me the files from the filestore directory.

C:\Users<workflowUser>\Connect\filestore

These resources aren’t the resources that are available in our workflow.

But I can access the resources that are in workflow using the Watch.GetResources call with in a workflow. these are the files that are located

C:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress Watch\OLConnect\

Is this correct or is it something that we have mis-configured in out installation of work flow.

Cheers.

Michael

4

No that is correct. Users who run their jobs through Workflow send their resources to Workflow, who can then upload them on-demand to the Connect server. But you can very well upload the resources directly to the Connect server without going through Workflow first. So there can be a discrepancy between what’s stored on the Connect server and what’s on the Workflow server.

That’s why I included both links.

5

Hi Phil,

Just coming back to this after looking into the REST API. We are seeing current running workflow processes show up via the REST API calls.

We’re struggling to understand why these resources are in 2 separate locations. Is there a particular reason why the aren’t just in one location?

Cheers

Michael

6

That’s because the Connect Server and the Workflow Server are not necessarily installed on the same PC. The servers are independent from each other. In fact, my own personal preference is to install those servers on separate machines to ensure they do not compete for the same hardware resources.

You could have several Workflow Servers sending jobs to a single Connect server, just like you could have a single Workflow Server sending jobs to multiple Connect Servers. That’s why the resources are stored in separate locations.

1 Like