JSON All-In-One Configuration
Describes the configuration of an All-In-One operation as a series of name/value pairs representing the processes (data mapping, content creation, job creation and output creation) to be completed as part of the overall operation. The value in each pair contains the parameters for that specific process.
The structure is variable, allowing for configurations containing one or more specific processes (as name/value pairs), as long as the processes specified result in a logical sequence or workflow. Used specifically with the All-In-One service.
Structure
The structure consists of an object
with the following name/value pairs:
-
datamining
– data mapping configuration parameters, consisting of anobject
with the following name/value pairs:-
identifier
– the managed file identifier (type ofnumber
) or named identifier (type ofstring
) of the data file -
config
– the managed file identifier (type ofnumber
) or named identifier (type ofstring
) of the data mapping configuration
-
-
contentcreation
– content creation configuration parameters, consisting of anobject
with the following name/value pairs:-
identifiers
– anarray
of data record entity identifiers (type ofnumber
) (optional for configurations containing data mapping parameters) -
config
– the managed file identifier (type ofnumber
) or named identifier (type ofstring
) of the input design template
-
-
jobcreation
– job creation configuration parameters, consisting of anobject
with the following name/value pairs:-
config
– the managed file identifier (type ofnumber
) or named identifier (type ofstring
) of the job creation preset (optional)
-
-
outputcreation
– output creation configuration parameters, consisting of anobject
with the following name/value pairs:-
identifiers
– anarray
of job entity identifiers (type ofnumber
) (optional for configurations containing content creation parameters) -
config
– the managed file identifier (type ofnumber
) or named identifier (type ofstring
) of the output creation preset -
createOnly
– flag to specify if output is to be only created in the server and not sent to it's final destination (type ofboolean
)
-
Specific to the use of all processes (and their parameters), an additional name/value pair can be added to restrict the print output to a set of specific records in the input data:
-
printRange
– print range configuration parameters, consisting of anobject
with a single name/value pair:-
printRange
– the range of records in the data file to output (type ofstring
)
-
Specific to the use of all processes, but with the omission of the config
job creation configuration parameter, an additional data mapping parameter can be added to the datamining
object:
-
persistDataset
– parameter to specify if data record entities are to be created/persisted in the server during the data mapping process (type ofboolean
)
Example
The following are examples of this structure:
{
"datamining":
{
"identifier": "Promo-EN-1000.csv",
"config": "Promo-EN.OL-datamapper"
},
"contentcreation":
{
"config": "letter-ol.OL-template"
},
"jobcreation":
{
"config": "4567"
},
"outputcreation":
{
"config": "5678",
"createOnly": true
},
"printRange":
{
"printRange": "1-3, 6, 10"
}
}
{
"contentcreation":
{
"identifiers": [
34567,
34568
],
"config": "letter-ol.OL-template"
},
"jobcreation": {},
"outputcreation":
{
"config": 5678,
"createOnly": false
}
}
{
"datamining":
{
"identifier": 12345,
"config": 23456
}
}
{
"datamining":
{
"identifier": "Promo-EN-1000.csv",
"config": "Promo-EN.OL-datamapper",
"persistDataset": false
},
"contentcreation":
{
"config": "letter-ol.OL-template"
},
"jobcreation": {},
"outputcreation":
{
"config": "5678",
"createOnly": false
}
}