About Parts and Page Ranges
When you create your Product, or when you modify a JDF job, you can manually edit and create/merge parts. A number of scenarios are possible whereby the default Body part plays a special role:
•create a new part: add the pages to the page range and Apogee removes the added pages from the default part.
•assign pages to a different part: edit the part you want the pages to be part of, and add those pages to the page range. Apogee removes the added pages from the default part.
•remove a part: select the part and click the Delete button. The pages of the part return to the default part.
Keeping count of pages
While defining parts and Run List positions, you may find that the number of pages does not match the sum of the parts (if the parts overlap). In this case, Apogee displays a warning, and you cannot submit the job; you must first fix the ranges.
In a simple job, the default part hides the complexity of parts: Changing the number of Run List pages simply adds or removes pages at the end of the default part. In a multi-part job, the default part acts as the body part.
In a `simple' multi-part job, you can have one cover part and the default body part. Such a setup makes it easy to change the total number of pages without having to edit the parts: when you increase the number of pages, the default parts grows and the cover widens; when you decrease the number of pages, the default part shrinks and the cover narrows.
When you have a product with additional parts, other than a cover, the default part contains the `left-overs' from the other parts: you specify the pages in the other parts, and the default parts contains the remaining pages. It is valid to have zero pages in a part, whether it is the default part or any other.
Keeping track of page ranges
Apogee does not attempt to keep the page ranges valid across the different parts while you are busy editing the Run List, parts and page ranges. Instead, it relies on a few basic rules, and checks the ranges when you change them.
•Apogee never adjusts the ranges of custom parts automatically, except those of the Cover part (if present).
•The Cover part is automatically adjusted to the Run List: Its first two pages are set to the numbers of the first two Run List positions, and its last two pages are set to the numbers of the last two Run List positions.
•When you enlarge the Run List, the added pages go in the default part.
•When you shrink the Run List, the `removed' pages are removed from the default part, insofar they are present. They are never taken from custom parts.
•When you create a new part, the default range is set to the range of the default part.
•When you make a part range smaller, the `removed pages' move back to the default part.
•When you make a part range larger, the `added pages' are taken from the default part insofar they are present.
Range Validation
Apogee does not attempt to maintain the ranges across different parts; instead, it checks whether the entire range, covered by all parts, matches the entire Run List, with no overlaps. If not, it posts a warning message in the Problem Report and displays it in the placard above the parts table. Parts with conflicting page ranges display the range in red text. You must fix page range conflicts manually before you can submit the job.