Run an ad hoc action on documents
- Use one of the following procedures to configure and perform ad hoc rule actions on documents from the Documents grid. You can create a package of documents, create a zip package, or create a merge package.
Create a package of documents
Use this action to create a package of documents. This
puts selected documents in a single document package.
-
From the Documents grid, select one or more documents, right-click and click
.This opens the Create Package dialog box.
-
Enter the Naming prefix for the package document.
This prefix will be added to all documents in the package.
- If you want to group documents in the package, select Grouping property and select the property to group by in the drop-down list.
-
In the Ordering properties list, select the document properties that will control the order the documents
are packaged.
Only the allowed properties selected on the Configure Document Properties Utility will display in the Ordering properties list.As you select properties, they are added to the Selected order list.
- Select properties in the Selected order list and use the Move up and Move down buttons to configure the property order.
- Click OK.
Create a zip package
Use this action to zip the selected documents.
-
In the Documents grid, select one or more documents, right-click and click
.This opens the Zip Package dialog box.
- Enter the Zip File Name in the box.
- If this rule will be used after all documents have been received into Output Manager, select the Used as a post-processing action check box.
-
In the Original documents box, select what happens after the zipped file has been created.
You can leave documents in the spooler, move them to retain them, or delete them.
- Click OK.
Create a merge package
Use this action to create a merged file.
- In the Documents grid, select one or more documents
-
Right-click the selection, and click
.This opens the Merge Package dialog box.
-
Next to Transform, click the Configure button to configure the transform.
This opens the Configure Transform dialog box.
- In the Server box, click the licensed transform server that you want to use.
-
In the Transform package box, you can select an existing transform package or you can complete the
following steps to create a transform package.
- Click New.
- On the General tab, enter the transform package Name.
- Select the transform package type.
- If you select a third-party conversion tool, verify that the EXE path is set to the correct folder. The default EXE path is @EOMTransformDir. To change the path, type the new path the box or click the browse button (...).
-
Set the Logging State.
The logging state determines if transform logs and temp files will be saved in the document folder. By default, the Logging State is set to Yes. All log files should be inspected during installation and preproduction testing to insure that fonts are correctly mapped. In a production system, the logging can be disabled to save disk space. If the transform operation returns an error (return code not zero), the log and temp files will not be deleted, and are available for troubleshooting.
-
On the Filter Profiles tab, specify how the transform
software will handle the formatting for each data type.
- To configure a profile, click the ellipsis button in the Modify/New column for the appropriate formats. In the Configure Filter Profile dialog box, configure the profile as needed. The profile contains a communications and printer definition section. See the Configuring a CpMillProfile resource topic for instructions on configuring a filter profile.
- To select a profile, click in the Configuration column for the appropriate formats and select the profile from the list.
-
On the Resources tab, specify where
the transform software will find the resources needed for the
transformation.
Example For example, PDF fonts are usually found at the location of an Adobe installation.
-
On the Fonts tab, you can control the font mapping of
input fonts to output fonts.
The defaults are typically correct, but may need to be adjusted for special cases. You can add or modify fonts directly in the grid.
- Click OK to create the transform package.
-
Select the Override input filter profile assigned to document check box to use the filter profile in the
transform package.
- Select this check box override the input filter profile assigned to the document.
- Clear this check box if you want to use the filter profile configured in the transform package.
- In the Output format list, click the format of the output file.
-
Configure the conversion of each input format in the Input formats grid, and then click
OK.
- For all unlicensed input formats and any input formats you don't want to use, click in the Configuration column and select Do Not Transform.
- For licensed input formats, you can select Use Default
Options or select a predefined configuration in the
Configuration column.
To configure a custom input format, click the browse button (...) in the Modify/New column. If Use Default Options or Do Not Transform is selected in the Configuration column, a new configuration will be created. If a predefined configuration is selected, that configuration will be modified. The custom transform options are configured on the Input Options tab, Output Options tab, and Page Layout tab. If BMP or PDF is selected as the output format, the Bitmap Output tab or PDF Output tab will also display.
-
When the transform configuration is complete, click OK.
The Merge Package dialog box indicates the transform has been configured.
-
Complete the following steps to configure Package boundaries.
-
Select Package boundaries and click Configure.
The Package Boundary Fields dialog box is displayed.
- From the grid, expand the sections to select the document properties that will be used as package boundaries.
-
Click OK.
Boundary fields are only applicable when a merged document will exceed the maximum number of exceptions (currently set at 1000). Merged documents that exceed the exception count will be split into separate documents. Boundary fields are used to control where the merged documents will be split. Each split will be on a boundary that maximizes the number of pages without exceeding the exception threshold. If you do not specify boundary fields, the split is arbitrary and will occur where the maximum number of pages can be fit.
-
Select Package boundaries and click Configure.
-
Under Merged Document Properties, determine if you want to use the document properties from the first page
in the documents or the last page in the documents.
Selecting custom properties is not yet available.
-
Complete the following steps to configure Exception fields.
-
Select Exception fields and click Configure.
This opens the Exception Fields dialog box.
- From the grid, expand the sections to select the document properties that will be used as exception fields.
- Click OK.
Exception fields specify which document properties to preserve on a per-page basis in the merged document. The document properties will be analyzed to determine the baseline and the exceptions (page overrides). -
Select Exception fields and click Configure.
- Determine if you need to Add blank pages between the documents being merged as needed for duplexing.
- Determine what will happen to the Original documents after the merged file has been created. You can leave them in the spooler, move them to retain, or delete them.
- Click OK.