...
The CHILI publisher Configurator for Switch allows for Switch customers to execute CHILI publisher related functions inside of Switch Flows.
“The” configurator now exists in 2 flavours:
version 3: CHILI publisher (on premise)
version 4: CHILI publisher Online
Functionally, they are the same, but due to different architecture, both versions of CHILI publisher need a different configurator.
What can I expect?
The Configurator gives access to a series of common functionalities exposed by CHILI publisher API, such as:
...
On-Prem vs CHILI publisher Online
| Note |
|---|
Switch Configurator v4 needed! |
Since the introduction of CHILI publisher Online (our SaaS offering), you will need to configure Switch to connect over the API.
Since you don’t have access to the Data Directory on the server, only the API connector will work. Functionality to select a data directory has been removed.
DataSets
All commands inside the Configurator populate DataSets in the Job, which can be used further in the Flow to determine how the job behaves. Most commands create a single dataset (of which the name is one of the properties in the Configurator).
Some (eg “Get Document Info”) will use the base dataset name and also create further DataSets (in the case of “Get Document Info”, a dataset for each set of additional document information requested through the command’s properties).
...
Each Command in the CHILI Publisher publisher Configurator requires general properties to be set:
...
CHILI Server URL | The root URL to CHILI publisher (online) |
CHILI Data Directory | For On-Prem installations Optional. If present, both CHILI and Switch can access this base DATA directory for CHILI Publisher, and this is used to pass along files (rather than upload/download them using base64 encoded arguments to CHILI API) For CHILI publisher online If you use CHILI publisher Oneline Online (CPO) you can only access CPO through the Server URL (API) since you don’t have access to the data directory. This functionality has been removed. |
CHILI Environment Name | The name of the CHILI Environment to log in to |
CHILI User | The name of the user to log in with (inside the provided Environment) |
CHILI Password | Password of the user |
DataSet Name | The name of the DataSet to attach to the current Job, holding the results of the command |
Command Type | The type of command to execute:
|
...