...
This is a Preps 9.0.2 limitation only. There have been no reports of these messages causing spoilage.
Workaround: Click OK.
...
Page Mark properties are not retained when saved with legacy anchor positions in Preps 9.0.0 or 9.0.1.
This is a Preps 9.0.2 limitation only for impositions using some Page Marks created/edited in Preps 9.0.0 or 9.0.1previous versions of Preps.
Workaround: To retain legacy mark positions from Preps 9.0.0 or 9.0.1, add “-RETAINLEGACYANCHORMARK:YES” to the "PrepsPrinergy.cfg.template" profile located on the Prinergy server.
Instructions: Setting Integrated Preps preferences - We recommend updating with a Windows text editor (eg. Notepad ++).
Please Note:
In most cases, “-RETAINLEGACYANCHORMARK:YES” is a viable solution. But, it has been reported that some Page Marks are shifted in Preps 9.0.2 and on VPS Output. For example, in one known case, Page Marks anchored to the Binding Edge on the back of the Signature with “-RETAINLEGACYANCHORMARK:YES” can inadvertently move the mark into the content area. Please check your VPS carefully. We are addressing these issues in Preps 9.5 (scheduled for Summer 2022 release).
...
When you use "Odd" or "Even" keywords in the SmartMark Range field, the mark will be applied only for the first press run.
...
Once you save the job for the first time you will be able to edit the name of a signature.
...
Preps mark preview limitation.
Textmarks placed too close to an adjacent page may get clipped on output. The mark will not appear clipped in Preps because Preps sandbox must preview the entire image.