KFPY scripts are special type of scripts used in place of Callas KFPX scripts in tFLOW. The difference is that KFPY scripts are actually “compound” scripts - they allow to run several KFPX scripts in sequence, optionally passing outputs of one KFPX script to input of another one. Additionally, KFPY scripts support features like running arbitrary program, moving files, copying files or make a direct pdfToolbox call passing all the needed paramters.
Basically KFPY scripts are XML files. Here is an example of a KFPY script:
<?xml version="1.0" encoding="UTF-8"?> <kfpy version="1"> <step type="callas"> <param>--visualizer</param> <param>--part=sep:"five"</param> <param>--format=images</param> <param>--imgformat=PDF</param> <param>--sep_colors</param> <param>--resolution=300</param> <param>--compression=PDF_Flate</param> <param>--outputfolder="%TEMP_FOLDER_1%"</param> <param>"%INPUT_FILE%"</param> </step> <step type="callas"> <param>--slice</param> <param>--outputfolder="%TEMP_FOLDER_1%"</param> <param>"%ASSETS_FOLDER%Slice to CUT.kfpx"</param> <param>"%INPUT_FILE%"</param> </step> <step type="callas"> <param>--slice</param> <param>--outputfolder="%TEMP_FOLDER_1%"</param> <param>"%ASSETS_FOLDER%Slice to white.kfpx"</param> <param>"%INPUT_FILE%"</param> </step> <step type="callas"> <param>--overlay</param> <param>"%TEMP_FOLDER_1%%INPUT_FILE_NAME%_2.pdf"</param> <param>"%TEMP_FOLDER_1%%INPUT_FILE_NAME%_0001_sep_five.pdf"</param> <param>-o="%TEMP_FOLDER_1%out.pdf"</param> </step> <step type="callas"> <param>--mergepdf</param> <param>"%TEMP_FOLDER_1%%INPUT_FILE_NAME%_0001.pdf"</param> <param>"%TEMP_FOLDER_1%out.pdf"</param> <param>-o="%TEMP_FOLDER_1%out1.pdf"</param> </step> <step type="callas"> <param is_kfpx="true">"%ASSETS_FOLDER%Labels Whiteink Proof V8.0.kfpx"</param> <param>"%TEMP_FOLDER_1%out1.pdf"</param> <param>-o="%OUTPUT_FILE%"</param> </step> </kfpy>
Note that the KFPY script above has six steps, and they all use different parameters and substitution variables. On the last step the system executes a regular kfpx profile. All the kfpx profiles referenced by any KFPY file must be loaded into the "Auxiliary scripts" folder in the Automation Assets area.
UTF-8
<kfpy>
version
1
param
params
is_kfpx=“true”
Note that merging of PDF nor XML reports from different Callas steps are not performed, so only one Callas step can produce reports of the whole KFPY script.
Also note that only one param tag in each step can have is_kfpx=“true” attribute.
source
target
program
KFPY scripts support a set of substitution variables which can be used in values of all tags. The basic syntax is the same as for Variable Substitution Engine, but the set of variables is different.
%TEMP_FILE_1%
%TEMP_FILE_2%
%TEMP_FILE_3%
%TEMP_FILE_4%
%TEMP_FILE_5%
%TEMP_FILE_6%
%TEMP_FILE_7%
%TEMP_FILE_8%
%TEMP_FILE_9%
%TEMP_FILE_10%
%TEMP_FOLDER_1%
%TEMP_FOLDER_2%
%TEMP_FOLDER_3%
%INPUT_FILE%
%INPUT_FILE_NAME%
%OUTPUT_FILE%
%XML_REPORT_FILE%
–report=XML,path=…
%PDF_REPORT_FILE%
–report=TEMPLATE=…,path=…
%ASSETS_FOLDER%
<param is_kfpx="true">"%ASSETS_FOLDER%PCIGrafx Normalize White.kfpx"</param>
<param is_kfpx="true" is_aux_script="true">"PCIGrafx Normalize White.kfpx"</param>
Trouble logging in? Simply enter your email address OR username in order to reset your password.
For faster and more reliable delivery, add support@aleyant.com to your trusted senders list in your email software.