Assigning Keywords or Metadata to Composition

[Otto]

We are running into an issue trying to write keywords to our composed PDFs.

Our template has multiple pages.

Each page is unused and named based on the code#.

Pages are turned on based on the code# in the record.

We have a switch statement in our OnRecordStart that determines which code gets a certain keyword.

 

See example OnRecordStart below.

 

FusionPro.Composition.SetBodyPageUsage("Code", true)

 

switch (Field("Code")){

case "******": FusionPro.Composition.OutputFile.keywords = "UncommonBleed|";

case "******": FusionPro.Composition.OutputFile.keywords = "CommonBleed|";

}

 

The problem we are having is that when we compose a code# that is NOT the first page in the template our keywords do not carryover on output.

It seems like the first page in the template must be composed in order to have keywords honored.

Is this true?

If so, is there a known workaround?

[Dan Korn]

I can confirm this is a (very old) bug. The PDF Document info doesn't get written properly to the output file if the first page of the template is set to unused.

 

I've entered case FP-582 about this. We're looking at a fix for an upcoming version.

 

I don't know of any workaround, other than to set a "dummy" first page in the PDF template which is always output. (It could just say something like "This page intentionally left blank.")

[Dan Korn]

This will be fixed in an upcoming release, likely 12.1.4, though I don't have a release date to share yet. Please contact Support if you need access to pre-release builds.