For illustration, we provide the Fixup PLACE_TEXT_STRING_MANUAL.kfpx. The custom Fixup PLACE_TEXT_STRING_MANUAL includes:

• The variable SAMPLE_String with
• The value type String

The goal of the Fixup is to place a defined text centrally in the center of the media frame (MediaBox) of the Print Item. The text has a size of 12 pt., and the color of the text is 100% CMYK black. In the input field, the user can enter the text to be placed.

In addition to the option of creating an input field using STRING, the same input field can also be provided with a placeholder to define Variable Content. For this, the PATTERN_STRING type is required. The assignment of the type and the definition of the attributes work in the same way as with the STRING type. By setting the PATTERN_STRING entry in the type attribute, it allows the user to select Variable Content [8] within the Workflow.

You do not need to make any structural changes in either the KFPX file or the XML file. All that is required is changing the type designation in the XML file to PATTERN_STRING.

For illustration purposes, we provide the corresponding XML file PLACE_TEXT_STRING_VARIABLE_CONTENT.xml for download, where the variable is defined with the PATTERN_STRING type.

Figure 3: Fixup dialog Sample with a String with type «PATTERN_STRING»

For illustration, we provide the Fixup PLACE_TEXT_DOUBLE_MANUAL.kfpx. The custom Fixup PLACE_TEXT_DOUBLE_MANUAL includes:

• The variable SAMPLE_Double with
• The value type FLOAT

The goal of this Fixup is to position a defined text in the center of the media frame (MediaBox) of the Print Item. Using the input field, the text can be shifted along the X-axis to the left (negative values «-») or to the right (positive values «+»).

Once the KFPX file has been exported, the corresponding XML file must still be created, and the previously defined variable SAMPLE_Double must be assigned the type DOUBLE. The Fixup can only be applied to the Workflow if the KFPX and XML files match.

Figure 4: Left: Excerpt of the XML file, where the variable has been assigned the type DOUBLE; Right: The dialog of the Fixup Sample for a Double in the Workflow

To define an input field as DOUBLE in the XML, proceed as follows:

1. First, create the basic structure of the XML file. You can learn how to do this in the article Creating Fixups without a Variable.
2. In the element <fixup> … </fixup>, insert the sub-element <variables> … </variables> and add the element  <variable> … </variable>. The structure is shown in Figure 4.
3. Assign the following attributes to the element <variable> … </variable>. The following attributes should be assigned for a DOUBLE:
   • name [10] – enter the key [1] (Figure 1) of the variable that was defined in pdfToolbox.
   • type [9] – assign the type DOUBLE here to create an input field for entering valid numbers.
   • min/max [12] – specify the value range for this variable. In this example, the value range is from -1000.0 to +1000.0. If a user attempts to enter a value of 1001, a warning will appear.
   • defaultValue [13] – provide a default value that should appear in the input field. This attribute is not mandatory but should still used to give users an indication about the type of input expected.
   • modelUnit [15] – specify the unit of measurement for calculations. In this case, it is millimeters.
   • displayVariable [14] – set this value to true so that the variable is displayed in the dialog.
   • description [11] – provide a description for the input field so that users know its purpose. This description can be translated into all languages available in the Workflow. The English translation is mandatory. Fixups only work when the English translation is available. If no translation is available for a language, the English version will be shown.

For illustration purposes, we provide the corresponding XML file PLACE_TEXT_DOUBLE_MANUAL.xml for download. In this file, the variable is defined as type DOUBLE.

In addition to the option of creating an input field using a DOUBLE, the same input field can be equipped with a placeholder to define a Variable Content. For this, the type PATTERN_DOUBLE is required. The assignment of the type and the definition of the attributes work in the same way as with the type DOUBLE . By using PATTERN_DOUBLE in the type attribute, it allows selecting a Variable Content [16] in the Workflow.

You do not need to make any structural changes to the KFPX file or the XML file. You only need to change the type designation to PATTERN_DOUBLE in the XML file.

For illustration purposes, we provide the corresponding XML file PLACE_TEXT_DOUBLE_VARIABLE_CONTENT.xml for download. In this file, the variable is defined as PATTERN_DOUBLE.

Figure 5: Fixup dialog with the type PATTERN_DOUBLE

For illustration purpose, we provide the Fixup PLACE_TEXT_INTEGER_MANUAL.kfpx. The custom Fixup PLACE_TEXT_INTEGER_MANUAL includes:

• The variable SAMPLE_INTEGER with
• The value type FLOAT

The purpose of this Fixup is to place a defined text at the center of the media frame (MediaBox) of the image. Using the input field, the text can be shifted along the Y-axis, either downward (using negative values «-» that move the text down) or upward (using positive values «+» that move the text up).

Once the KFPX file has been exported, the corresponding XML file must to be created, in which the previously defined variable SAMPLE_Integer  is assigned the type Integer. The Fixup can only be applied to the Workflow when the KFPX and XML files match.

Figure 6: Left: Excerpt of the XML file where the variable is assigned the type INTEGER; Right: The Fixup dialog Sample for an Integer in the Workflow

To define an input field as INTEGER in the XML, proceed as follows:

1. First, create the basic structure of the XML file. The required structure can be found in the article Creating Fixups without a Variable.
2. In the element  <fixup> … </fixup>, insert the sub-element  <variables> … </variables> and add the element  <variable> … </variable> element within it. The structure is shown in Figure 6.
3. Assign the following attributes for the <variable>...</variable> element. The following attributes should be assigned for a INTEGER:
   • name [18] – enter the key [1] (Figure 1) of the variable that was defined in the pdfToolbox.
   • type [17] – assign the type INTEGER to create an input field for entering whole numbers.
   • min/max [20] – specify the value range for this variable. In this example, the value range is from -1000 to +1000. If a user attempts to enter a value outside this range (e.g., 1001), a warning will be diplayed.
   • defaultValue [21] – enter the value that should be displayed by default in the input field. This attribute is not mandatory but should be used to provide guidance to the user on what type of content is expected in the input field.
   • modelUnit [23] – specify the unit of measurement that is needed by default for the calculation. In this case, it is millimeters.
   • displayVariable [22] – set this attribute to true to display the variable in the dialog box.
   • description [19] – provide a description for the input field so that the user understands its purpose. This description can be translated into all languages supported by the Workflow. The English translation is mandatory. Fixups only work when the English translation is available. If a language is not translated, the English version will be displayed.

For illustration purposes, we provide the corresponding XML file PLACE_TEXT_INTEGER_MANUAL.xml for download. This file defines the variable as type INTEGER.

In addition to the ability to create an input field using an INTEGER, the same input field can also be equipped with a placeholder for defining a Variable Content. For this, the type PATTERN_INTEGER is required. The assignment of the type and the definition of the attributes function in the same way as for the INTEGER type. By specifying PATTERN_INTEGER in the type attribute, the option to select a Variable Content [24] in the Workflow is enabled.

No structural changes need to be made in the KFPX file or the XML file. You only need to change the type designation to PATTERN_INTEGER in the XML file.

For illustration purposes, we provide the corresponding XML file PLACE_TEXT_INTEGER_VARIABLE_CONTENT.xml for download. In this file, the variable is defined as PATTERN_INTEGER.

Figure 7: Dialog of the custom Fixup of type PATTERN_INTEGER

To illustrate this functionality, we provide the Fixup PLACE_TEXT_BOOLEAN_MANUAL.kfpx Fixup. The custom Fixup PLACE_TEXT_BOOLEAN_MANUAL includes:

• The variable SAMPLE_Boolean  with
• The value type BOOLEAN

The purpose of this Fixup is to place a predefined text string centered within the media frame (MediaBox) of the Print Item. The text is set in 12 pt and uses 100% CMYK black. An optional checkbox allows the user to add a white background behind the text.

Once the KFPX file has been exported, the XML file must be created and the previously defined variable SAMPLE_Boolean must be assigned the type BOOLEAN. The Fixup can only be applied to the Workflow if the KFPX and XML files are consistent and correctly aligned.

Figure 8: Left: Excerpt from the XML file showing the variable assigned the Boolean type; Right: The Fixup dialog within the Workflow

To define a checkbox using a BOOLEAN variable in an XML, follow the steps below:

1. First create the basic structure of the XML file. Instructions for this can be found in the article Creating Fixups without a Variable.
2. Within the <fixup> … </fixup> element, insert the <variables> … </variables> sub-element, and then add the <variable> … </variable> element inside it. Figure 8 illustrates the correct structure.
3. Assign the attributes to the <variable> … </variable> element. The following attributes should be defined when using a BOOLEAN type:
   • name [26] – enter the  Key [1] (Figure 1) of the variable as defined in pdfToolbox.
   • type [25] – set the value to BOOLEAN to define the variable as a checkbox.
   • defaultValue [28] – enter the value true if the checkbox should be selected by default. This attribute is optional but recommended.
   • displayVariable [29] – set to true to ensure the checkbox is visible in the dialog.
   • description [27] – provide a name for the checkbox to indicate its purpose to the user. This name can be translated into all languages offered in the Workflow. The English translation is mandatory. The Fixup will only work when the English translation is available. If a translation for the current language is not available, the English version will be displayed by default.

For reference, we provide the matching XML file PLACE_TEXT_BOOLEAN_MANUAL.xml for download. This file contains a properly defined BOOLEAN variable for illustration purposes.

In addition to defining a checkbox using the BOOLEAN type, the same checkbox can be extended with a placeholder to allow the definition of Variable Content. To achieve this, the type PATTERN_BOOLEAN is required. The assignment of the type and the definition of the attributes follow the same structure as for the BOOLEAN type. The PATTERN_BOOLEAN entry in the type attribute offers the option of selecting a Variable Content [30] in the Workflow.

No structural changes are required in either the KFPX file or the XML file. You only need to change the type name to PATTERN_BOOLEAN in the XML file.

For illustration purposes, we provide the matching XML file PLACE_TEXT_BOOLEAN_VARIABLE_CONTENT.xml for download. In this file, the variable is defined as PATTERN_BOOLEAN.

Figure 9: Dialog for the user-defined Fixup of the type PATTERN_BOOLEAN

Unlike the previously described types, a selection menu in pdfToolbox requires the input value to be limited to a specific value.

We provide the PLACE_TEXT_DROPDOWN_MANUAL.kfpx Fixup to illustrate this. The custom Fixup PLACE_TEXT_DROPDOWN_MANUAL includes:

• The variable SAMPLE_Dropdown with
• The value type PopUp

The input is restricted to the following values:

• Bottom
• Left
• Right
• Top
• Center

The purpose of this Fixup is to place a predefined text element on the Print Item. The text is set in 12 pt and uses the text color 100% CMYK black. Using the dropdown menu, the user can choose where the text positioned. Available options include center, top center, right center, bottom center and left center.

Once the KFPX file has been exported, the corresponding XML file must be created. In this file, the previously defined variable SAMPLE_Dropdown must be assigned the type String and the layout type dropdown. The Fixup can only be applied in the Workflow if the KFPX and XML files match exactly.

Figure 10: Left: Excerpt from the XML file showing the variable with type String and layout type dropdown assigned; Right: Fixup dialog as it appears in the Workflow

To define a selection menu (dropdown) in the XML, proceed as follows:

1. First, create the basic structure of the XML file. Detailed instructions can be found in the article Creating Fixups without a Variable.
2. Within the <fixup> … </fixup> element, insert the <variables> … </variables> sub-element and add the <variable> … </variable> element in it. Figure 10 shows what the structure looks like.
3. Assign the required attributes to the <variable> … </variable> element. The following attributes should be set for a STRING:
   • name [32] – the key [1] (Figure 1) of the variable as defined in pdfToolbox.
   • type [31] – assign the type STRING to create a selection menu that passes a string value.
   • defaultValue [37] – enter the value that should be selected by default in the selection menu.
   • displayVariable [38] – enter the value true so the variable is also displayed in the dialog.
   • description [33] – provide a name for the selection menu so users understand what the menu is for. This name can be translated into all languages offered in the Workflow. The English translation is mandatory. The Fixup will only work if this is available. If a language is not translated, the English version will be shown by default.
4. Within the  <variable> … </variable> element, insert the subordinate elements <options> … </options>.
5. Assign the attribute layoutType="dropdown"[34] for the <options> … </options> element. This creates the selection menu.
6. In the <options> … </options> element, insert the subordinate elements <option>...</option> an element must be defined for each entry in the selection menu.
7. Assign the attributes for the <option> … </option> element. The following attributes should be assigned for a dropdown:
   • name [35] – enter the name of the option here. This must match the respective pdfToolbox value.
   • description [36] – enter a name for the respective option here. This name can be translated into all languages offered in the Workflow. The English translation is mandatory. Fixup will only work if this is present. If a language is not translated, the English translation will be displayed.
8. Repeat steps 6 and 7 until all options have been described. Figure 10 shows the structure that this should have.

For illustration purposes, the matching XML file PLACE_TEXT_DROPDOWN_MANUAL.xml is available for download. In this file, the variable is defined as type STRING with layout type dropdown.

As with the layout type dropdown, the input values for radio buttons in pdfToolbox must be limited to predefined options.

We provide the PLACE_TEXT_RADIO_MANUAL.kfpx Fixup for illustration purposes. The PLACE_TEXT_DROPDOWN_MANUAL custom fixup contains

• The variable SAMPLE_Radio  with
• The value type PopUp

The purpose of this Fixup is to place a predefined text in the center of media frame (MediaBox) of the Print Item. The text has a font size of 12 pt. The color of the text is 100% CMYK black. Using a radio button, the user can choose whether the text should be set to Overprint or Knockout.

Once the KFPX file has been exported, the corresponding XML file must be created. In this XML file, the previously defined variable SAMPLE_Radio must be assigned the type String and the layout type radio. The Fixup can only be applied to the Workflow if the KFPX and XML files match exactly.

Figure 11: Excerpt of the XML file in which radio buttons are defined for the variable

To define radio buttons in the XML, proceed as follows:

1. First, create the basic structure of the XML file. For details on how this should look, refer to the article Creating Fixups without a Variable.
2. Within the <fixup> … </fixup> element, insert the <variables> … </variables> sub-element and add the <variable> … </variable> element. Refer to Figure 11 for an example of the structure.
3. Assign the necessary attributes to the <variable> … </variable> element. The following attributes should be assigned for a STRING:
   • name [40] – the key [1] (Figure 1) of the variable as defined in pdfToolbox.
   • type [39] – assign the type STRING to create a radio button.
   • defaultValue [45] – enter the value that should be selected by default in the selection menu.
   • displayVariable [46] – enter the value true to also display the variable in the dialog.
   • description [41] – provide a name for the radio button here so that the user understands what the menu is for. This name can be translated into all languages offered in the Workflow. The English translation is mandatory. The Fixup will only work when the English translation is present. If a language is not translated, the English translation will be displayed.
4. Inside the  <variable> … </variable> element, insert the <options> … </options> sub-element.
5. Assign the attribute layoutType="radio"[42] to the <options> … </options> element. This creates the radio buttons.
6. In the <options> … </options> element, insert the <option>...</option> sub-element – an element must be defined for each selection.
7. Assign the attributes for the <option> … </option> element. The following attributes should be assigned for a dropdown:
   • name [43] – enter the name of the option here. This must match the respective pdfToolbox value.
   • description [44] – enter a name for the respective option here. This name can be translated into all languages offered in the Workflow. The English translation is mandatory. Fixup will only work if this is available. If a language is not translated, the English translation will be displayed.
8. Repeat steps 6 and 7 until all options have been described. Figure 11 shows what the structure looks like.

For illustrative purposes, we provide the corresponding XML file PLACE_TEXT_RADIO_MANUAL.xml for download. In this file, the variable is defined as type STRING with the layout type radio.

We provide the Fixup CREATE_WHITE_SEPARATION_SLIDER_MANUAL.kfpx for illustration purposes. The CREATE_WHITE_SEPARATION_SLIDER_MANUAL custom Fixup contains

• The variable SAMPLE_Slider  with
• The value type Integer

The purpose of this Fixup is to create an Overprint Spot Color Separation for white, in the size of the TrimBox. Using the slider, the opacity of the white separation can be adjusted as needed.

Once the KFPX file has been exported, the corresponding XML file must be created. In this file, the previously defined variable SAMPLE_Slider must be assigned the type SLIDER_INTEGER. The Fixup can only be used with the Workflow if the KFPX and XML files are consistent and match in structure.

Figure 12: Left: Excerpt from the XML file where the variable is assigned the type SLIDER_INTEGER; Right: Dialog of the Fixup Sample for a Slider displayed in the Workflow

To define a SLIDER_INTEGER in XML, proceed as follows:

1. First, create the basic structure of the XML file. For guidance on this structure, refer to the article Creating Fixups without a Variable.
2. Within the <fixup> … </fixup> element, insert the <variables> … </variables> sub-element and add the <variable> … </variable> element in it. The structure is illustrated in Figure 12.
3. Assign the following attributes to the <variable> … </variable> element. The following attributes should be assigned for a SLIDER_INTEGER:
   • name [48] – the key [1] (Figure 1) of the variable as defined in pdfToolbox.
   • type [47] – assign the type SLIDER_INTEGER to create a slider.
   • defaultValue [50] – enter the value that should be displayed by default in the input field. This attribute is not mandatory but is recommended.
   • modelUnit [51] – define the unit of measurement that is required by default for the calculation. In this case, it is percent.
   • viewUnit [53] – define the unit of measurement that should be displayed in the dialog for this value in this case, percent is the correct entry. If this differs from the modelUnit, an internal conversion will occur. A typical example would be the conversion from mm to inch.
   • displayVariable [52] – set this value to true to display the variable in the dialog.
   • description [49] – provide a name for the slider, so the user understands what the slider is for. This name can be translated into all languages offered in the Workflow. The English translation is mandatory. The Fixup will only work if this is present. If a translation is missing for a particular language, the English version will be shown.

For illustration purposes, we provide the corresponding XML file CREATE_WHITE_SEPARATION_SLIDER_MANUAL.xml for download. In this file, the variable is defined as type SLIDER_INTEGER.

In pdfToolbox, a separate variable must be created for each color channel, i.e. Cyan, Magenta, Yellow and Black. In order to combine these four variables into a color picker, the following two conditions must be met:

1. The first part of the key must be the same for all four variables. This ensures that a variable name can be defined.
2. The variable must end with the respective process color name in capital letters. For example, "_CYAN" [54].

For illustration, we provide the Fixup PLACE_TEXT_COLOR_PICKER_MANUAL.kfpx. The custom Fixup PLACE_TEXT_STRING_MANUAL contains:

• The variable  SAMPLE_Color_Picker_CYAN for Cyan,
• The variable  SAMPLE_Color_Picker_MAGENTA for Magenta,
• The variable  SAMPLE_Color_Picker_YELLOW for Yellow,
• The variable  SAMPLE_Color_Picker_BLACK for Black with
• The value type Float

The aim of this Fixup is to place a defined text in the center of the media frame (MediaBox) of the Print Item. The text has a size of 12 pt. With the color picker, the user can define the CMYK values for the predefined text.

Figure 13: The dialog in pdfToolbox where the CMYK variables have been defined

Once the KFPX file has been exported, the corresponding XML file must also be created. In this XML file, the previously defined variable SAMPLE_Color_Picker must be assigned the type COLOR_PICKER. The Fixup can only be applied in the Workflow if the KFPX and XML files match.

Figure 14: Left: Excerpt from the XML file where the variable has been assigned the type Color_Picker; Right: The dialog of the Fixup in the Workflow

To define a color selection using a color picker in the XML, proceed as follows:

1. First, create the basic structure of the XML file. You can find how this should look like in the article Creating Fixups without a Variable.
2. Within the  <fixup> … </fixup> element, insert the <variables> … </variables> sub-element and add the <variable> … </variable> element. Refer to Figure 14 for an example of the structure.
3. Assign the necessary attributes to the <variable> … </variable> element. The following attributes should be set for a COLOR PICKER:
   • name [56] – the Key [1] (Figure 1) of the variable as defined in pdfToolbox. In this case, use the shared portion of the key that is common to all four defined variables.
   • type [55] – assign the type  COLOR_PICKER to create a color picker.
   • defaultValue [58] – enter the value that should be selected by default. Use special characters in the XML to define which Color Space and which values should be entered. The following special characters must be entered for the definition:
     • "spec": "CMYK","value": [0,0,0,100]
   • displayVariable [59] – set this to true so the variable is displayed in the dialog.
   • description [57] – a description is not generally required for the color picker in the user interface. However, it is still necessary to provice one for internal processing. This description will not be shown in the workflow, but it must be present for the Fixup  to function properly.

For illustration purposes, we provide the corresponding XML file PLACE_TEXT_COLOR_PICKER_MANUAL.xml for download. In this file, the variable is defined with the type COLOR_PICKER.

To illustrate this, the Fixup RENAME_MULTI_SPOTCOLOR_MANUAL.kfpx is provided. The user-defined Fixup RENAME_SINGLE_SPOTCOLOR_MANUAL includes:

• The variable name SAMPLE_Multi_Spotcolor  with
• The value type String

The purpose of this Fixup is to set selected Spot Colors to Overprint. Using the selection menu, all Spot Colors present in the Print Item can be selected.

Once the KFPX file has been exported, the corresponding XML file must also be created. In it, the previously defined variable SAMPLE_Multi_Spotcolor must be assigned the type MOTIF_SPOTCOLORS_All_MULTI. Only if the KFPX and XML files matches exactly can the Fixup be applied within the Workflow.

Figure 15: Left: Section of the XML file in which the variable was assigned the type MOTIF_SPOTCOLORS_ALL_MULTI; Right: Fixup dialog in the Workflow

To define the selection of multiple Spot Colors in an XML file, proceed as follows:

1. First, create the basic structure of the XML file. You can find details on how this structure should look like in the article Creating Fixups without a Variable.
2. WithIn the <fixup> … </fixup> element, insert the <variables> … </variables> sub-element and add the <variable> … </variable> element in it. Refer to Figure 15 for a visual representation of this structure.
3. Assign the appropriate attributes to the <variable> … </variable> element. The following attributes should be used for selecting multiple Spot Colors:
   • name [61] – enter the key [1] (Figure 1) of the variable as defined in pdfToolbox.
   • type [60] – assign the type MOTIF_SPOTCOLORS_ALL_MULTI, or the desired type that you want to use.
   • displayVariable [63] – set this value to true to ensure that the variable appears in the dialog.
   • description [62] – enter a name for the selection menu that clearly explains its purpose to the user. This name can be translated into all languages offered in the Workflow. The English translation is mandatory. The Fixup will only work when the English translation is available. If no translation is available for a selected language, the English version will be displayed by default.

For reference, the corresponding XML file RENAME_MULTI_SPOTCOLOR_MANUAL.xml is available for download. In this file, the variable is defined as type MOTIF_SPOTCOLORS_ALL_MULTI.

To allow the selection of a system-wide defined Spot Color, five variables must be defined within pdfToolbox. Similar to the color picker, one variable must be created for each of the four Process Colors (Cyan, Magenta, Yellow, Black). Additionally, since this involves a Spot Color, a separate variable for the Spot Color name must be defined. To ensure that a selection menu for a system-wide defined Spot Color is created, the following requirements must be met:

• The first part of the key must be the identical for each individual Process Color.
• As with the color picker, the respective Process Color name must be added in capital letters at the end of the key. For example, ..._CYAN.
• The first part of the key also matches the key of the variable for the Spot Color name. Only the Process Color suffix e.g...._CYAN is appended for the color-specific variables.

To illustrate this, the Fixup file SAMPLE_CREATE_LINE_ON_TRIMBOX_MANUAL.kfpx is provided. The user-defined Fixup SAMPLE_CREATE_LINE_ON_TRIMBOX_MANUAL [64] contains the following:

• The variable  SAMPLE_System_Tec_Spot for the Spot Color name with
• The value type String,
• The variable SAMPLE_System_Tec_Spot_CYAN for Cyan,
• The variable SAMPLE_System_Tec_Spot_MAGENTA for Magenta,
• The variable SAMPLE_System_Tec_Spot_YELLOW for Yellow,
• The variable SAMPLE_System_Tec_Spot_BLACK for Black with
• The value type Float

The goal of this Fixup is to create an Overprinting Line in the size of the TrimBox of the document. Using the drop-down menu, the user can select a system-wide defined Spot Color that will be used to draw the line.

Figure 16: The dialog in pdfToolbox where the variables for the CMYK channels and the Spot Color name were defined

Once the KFPX file has been exported, the corresponding XML file must be created, in which the previously defined variable SAMPLE_System_Tec_Spot is assigned the type SYSTEM_SPOTCOLORS_TEC_SINGLE_CMYK. The Fixup can only be applied in the Workflow when the KFPX and XML files match.

Figure 17: Left: Section of the XML file where the variable is assigned the type SYSTEM_SPOTCOLORS_TEC_SINGLE_CMYK; Right: The Fixup dialog in the Workflow

To define the selection of a system-wide defined Technical Color in the XML, follow these steps:

1. First, create the basic structure of the XML file. The structure can be found in the article Creating Fixups without a Variable.
2. Within the <fixup> … </fixup> element, insert the <variables> … </variables> sub-element and add the <variable> … </variable> element in it. You can refer to Figure 17 for the structure.
3. Assign the following attributes for the <variable> … </variable> element. The following attributes should be assigned for a selection menu for system-wide defined Spot Colors:
   • name [66] – enter the key [1] (Figure 1) of the variable as defined in pdfToolbox.
   • type [65] – assign the type SYSTEM_SPOTCOLORS_TEC_SINGLE_CMYK or the type you want to use.
   • displayVariable [68] – set this value to true to ensure the variable is displayed in the dialog.
   • description [67] – provide the name for the selection menu so that the user understands what the selection menu is for. This name can be translated into all languages offered in the Workflow. The English translation is mandatory. The Fixup will only work if this is available. If a language is not translated, the English translation will be displayed.

For illustration, we provide the corresponding XML file CREATE_DIELINE_ON_TRIMBOX_MANUAL.xml for download, in which the variable is defined with the type SYSTEM_SPOTCOLORS_TEC_SINGLE.

For illustration, we provide the Fixup CREATE_BLEED_MANUAL.kfpx. The user-defined Fixup CREATE_BLEED_MANUAL includes

• The variable SAMPLE_Spot_auto with
• The value type String

The aim of the Fixup is to add a Bleed of 5 mm from the TrimBox. Technical Colors are automatically excluded from the Fixup if the colors used are defined as Technical Colors in the system.

Once the KFPX file has been exported, the corresponsing XML file must be created, and the previously defined variable SAMPLE_Spot_auto must be assigned the type SYSTEM_SPOTCOLOR_TEC_AUTO. The Fixup can only be applied in the Workflow when the KFPX and XML files match.

Figure 18: Left: Excerpt from the XML file where the variable is assigned the type SYSTEM_SPOTCOLORS_TEC_AUTO; Right: The Fixup dialog in the Workflow

To exclude a system-wide defined Spot Color from a Fixup in XML, follow these steps:

1. First, create the basic structure of the XML file. The structure details can be found in the article Creating Fixups without a Variable.
2. Within the <fixup> … </fixup> element, insert the <variables> … </variables> sub-element and add the <variable> … </variable> element. Figure 18 shows what the structure looks like.
3. Assign the attributes for the <variable> … </variable> element. The following attributes should be specified for excluding system-wide defined Spot Colors:
   • name [70] – enter the key [1] (Figure 1) of the variable defined in pdfToolbox.
   • type [69] – assign the type SYSTEM_SPOTCOLORS_TEC_AUTO or the type you want to use.
   • defaultValue [72] – enter the default value that you have also defined in pdfToolbox. This attribute is optional.
   • displayVariable [73] – set this attribute to false, as the variable should not be displayed in the dialog. This ensures that the user cannot select a Spot Color, and the affected Color will be automatically excluded from the Fixup.
   • description [71] – in this case, only enter an internal description so that you can later understand why this variable was created. The addition not used indicates that this variable is not visible.

For illustration purposes, we provide the corresponding XML file CREATE_BLEED_MANUAL.xml for download. In this file, the variable is defined as type SYSTEM_SPOTCOLORS_TEC_AUTO.

For illustration, we provide the Fixup DELETE_LAYERS_MANUAL.kfpx. The custom Fixup DELETE_LAYERS_MANUAL includes:

• The variable name SAMPLE_Layers with
• The value type String

The objective of this Fixup is to remove selected layers and all objects within those layers. Using the selection menu, the user can delete the desired layers.

Figure 19: The dialog in pdfToolbox where the layer matches the RegEx expression, and the variable SAMPLE_Layers is defined for the RegEx

Once the KFPX file has been exported, the corresponding XML file must also be created. In the XML file, the previously defined variable SAMPLE_Layers must be assigned the type MOTIF_LAYERS_ALL_MULTI. The Fixup can only be applied in the Workflow when the KFPX and XML files match.

Figure 20: Left: Excerpt of the XML file where the variable is assigned the type MOTIF_LAYERS_ALL_MULTI; Right: The Fixup dialog in the Workflow

To define the selection of layers in the XML, proceed as follows:

1. First, create the basic structure of the XML file. The required structure can be found in the article Creating Fixups without a Variable.
2. Within the <fixup> … </fixup>  element, insert the <variables> … </variables> sub-element and add the <variable> … </variable> element. The structure is illustrated in Figure 20.
3. Assign the following attributes to the  <variable> … </variable>  element. The following attributes should be assigned for a selection menu for system-wide defined Spot Colors:
   • name [75] – enter the key [1] (Figure 1) of the variable defined in pdfToolbox.
   • type [74] – assign the type MOTIF_LAYERS_ALL_MULTI or the type you want to use.
   • displayVariable [77] – set this to true to ensure the variable is displayed in the dialog.
   • description [76] – provide the name for the selection menu to help the user understand its purpose. This name can be translated into all languages offered in the Workflow. The English translation is mandatory. The Fixup will only work when the English translation is available. If a language is not translated, the English translation will be displayed.

For illustration purposes, we provide the corresponding XML file DELETE_LAYERS.xml for download, where the variable is defined as type MOTIF_LAYERS_ALL_MULTI.

To illustrate this functionality, we provide the Fixup DELETE_PAGE_MANUAL.kfpx. The custom Fixup DELETE_PAGE_MANUAL includes:

• The variable name SAMPLE_Page with
• The value type STRING

The aim of this Fixup is to delete selected pages from a Multipage file. To do this, a specific string must be entered in the input field. The allowed characters and syntax for this input are explained in the accompanying info box.

Once the KFPX file has been exported, the corresponding XML file must be created. In this file, the previously defined variable SAMPLE_Page must be assigned the type PAGE_SELECTION_PATTERN. The Fixup can only be applied within the Workflow if the KFPX and XML files match exactly.

Figure 21: Left: Excerpt from the XML file where the variable is assigned the type PATTERN_SELECTION_PATTERN; Right: The Fixup dialog in the Workflow

To define a page selection as a string with an info box in the XML, proceed as follows:

1. First, create the basic structure of the XML file. You can find instructions on how to do this in the article Creating Fixups without a Variable.
2. Within the <fixup> … </fixup> element, insert the  <variables> … </variables>  sub-element and add the  <variable> … </variable>  element. The structure is shown in Figure 21.
3. Assign the following attributes for the <variable> … </variable> element. The following attributes should be assigned for a page selection:
   • name [79] – enter the Key [1] (Figure 1) of the variable as defined in pdfToolbox.
   • type [78] – assign the type PAGE_SELECTION_PATTERN to create a page selection as an input field with an info box.
   • defaultValue [81] – enter the value that should be displayed by default in the input field. This attribute is not mandatory, but should still be used to give the user an indication of what kind of content is expected in the input field.
   • displayVariable [82] – set this to true to ensure the variable appears in the dialog.
   • description [80] – enter the name for the input field to inform the user of its purpose. This name can be translated into all languages offered in the Workflow. The English translation is mandatory. The Fixup only works if this is available. If a language is not translated, the English translation is displayed.

For illustration purposes, we provide the corresponding XML file DELETE_PAGE_MANUAL.xml for download. In this file, the variable is defined as type PAGE_SELECTION_PATTERN.