Note: The following check is enabled on specific accounts only. You will be notified prior to its implementation on your account.
Effective November 4, 2024, we are updating Lakeside Scout by implementing an additional specification check on a per account basis. This check is performed to ensure the automated print code tag, "$PrintCode", has been placed on a text component page and its font has been fully embedded. This will expedite the check in process to ensure a timely delivery on all components to manufacturing.
Should you have a title that does not require a print code tag or wish to use a unique one, the automated print code tag must still be present to work with the automated process. In these situations, you should place the automated print code tag outside the bleed area and set its color to Paper, (i.e., CMYK = 0%).
See this article for more details about the Approve to Print process.
See this article for more details about automated print codes.
See this article for more details about embedding fonts in Adobe InDesign.
This message will display if the automated print code tag, "$PrintCode", is not found on a text component page during the specification check process. In this situation, upload a revised page containing the print code tag with its font fully embedded and insert it into its paginated location. Once content for the revised page is approved, you will be prompted to click the Approve to Print button to initiate the specification checks once more.
This message will display if the automated print code tag, "$PrintCode", is found but its font is not fully embedded during the specification check process. In this situation, upload a revised page where the print code tag font is fully embedded and insert it into its paginated location. Once content for the revised page is approved, you will be prompted to click the Approve to Print button to initiate the specification checks once more.
If neither of the above messages are displayed during the specification check process, Lakeside Scout successfully located the print code tag and determined its font was fully embedded. Lakeside Scout will then proceed with the final specification check - number of colors. If there is an issue with the number of colors in the text component, the user that clicked the approve to print button will receive an in-app and/or email notification to reconcile the issue. Note - the user must subscribe to the Specifications Warning/Errors informative event in order to receive the notification(s). See this article for more details regarding informative notifications.
Otherwise, the text component will check in and migrate to the library repository.