Alex Marshall

Did you check the "Window" menu in InDesign?

InDesign CC 2017 with Acrobat DC 2017 is only supported with FusionPro 10. Lesser versions will need to upgrade to this build. If you are using FusionPro 10, reinstall FusionPro to get the plugin to load to Acrobat DC 2017.

I will email you the instructions.

InDesign CC 2017 and Acrobat DC 2017 are currently supported with FusionPro version 10 only. You can purchase the upgrade at http://www.marcom.com/fusionpro

Use the "hidephonenumberlabel" text rule in the FusionPro Rule Editor. Edit the script to match your data fields and title.. Click "Create Rules>>>New>>>Hidephonenumberlabel.... Once you have configured this Rule, use it instead of the field name in the Variable Text Editor.

Please forward this issue to fusionprosupport@marcom.com with a sample of the data and template you are using so we can provide a solution.

please submit the issue to fusionprosupport@marcom.com

Sorry for the trouble. What is the version of FusionPro you are using on both Server and client?

Add all the pages as a single PDF document. Then in FusionPro, select FusionPro>>Manage Pages>>>Page Usage. Name each page and set it to unused. Then create an Onrecordstart rule, Create Rules>>>New>>Callback>>OnRecordStart. The rule below can be simplified greatly by only activating the page you need, since all the pages are marked unused initially. So it can be reduced to this: if (Field("Addresses") == "1") FusionPro.Composition.SetBodyPageUsage("One", true); FusionPro.Composition.SetBodyPageUsage("back 1", true); if (Field("Addresses") == "2") FusionPro.Composition.SetBodyPageUsage("Two", true); FusionPro.Composition.SetBodyPageUsage("back 2", true); if (Field("Addresses") == "3") FusionPro.Composition.SetBodyPageUsage("Three", true); FusionPro.Composition.SetBodyPageUsage("back 3", true); if (Field("Addresses") == "4") FusionPro.Composition.SetBodyPageUsage("Four", true); FusionPro.Composition.SetBodyPageUsage("back 4", true); etc......

This issue was fixed in 9.3.36. Please reinstall Fusionpro using this latest patch to FP 9.3.36 http://marcom.com/resources/support-training/fusionpro-downloads/

Reinstall Fusionpro using the 9.3.36 build from the support page: http://marcom.com/resources/support-training/fusionpro-downloads/

Are you chunking the output? Did you possibly enable the "Infinite Stack" option in the FP Imposer definition file?

Did you try the text Rule for QR Contact Information ?

Create Rules>>New>>Callback>> OnRecordStart

If you want the whole frame to be hidden under certain circumstances, then name the frame and in the OnRecordStart rule hide it as appropriate. The code to hide a frame is simply this (in OnRecordStart) var frame=FindGraphicFrame("Frame1"); // replace Frame1 with the name of your frame – frame.suppress(); Just put this code in an if block in OnRecordStart and it will hide the whole frame. Note that the doublequotes might have been changed to smart quotes in your email reader & might have to be changed to straight quotes in the rule editor.

Did you check the box in the Rule Editor for "Treat Return Strings As Tagged Text"?

You indicated these were Microsoft Window fonts as originally purchased from the font foundry, correct?

The encoding types are listed and documented in the following places: • In the FusionPro Rules Guide, in the section “How to use the DataMatrixbarcode() function” (page 102). • On the Building Blocks dialog, on the Objects tab, under Barcodes -> DataMatrixBarcode -> encoding. • http://www.idautomation.com/barcode-faq/2d/data-matrix/#Encoding_Modes The Rule will look like this: var dataforbarcode = Field('First Name'); var dmbarcodeobj = new DataMatrixBarcode; dmbarcodeobj.encodingmode = "C40"; dmbarcodeobj.pointSize = 12; return dmbarcodeobj.Make(dataforbarcode);

Creating a Data Matrix barcode is simple. You have to know which encoding mode you need and use it in the script. Here is the syntax: return MakeDataMatrixBarcode(DataToEncode, ProcessTilde, EncodingMode,PreferredFormat, PointSize, NoFontTag, Font) So click “Create Rules>>New(text)>>>Empty Rule. Give the Rule a name. Enter the code. Change the fieldname to match your data file. var dataforbarcode = Field(“mydatafield”);//etc… var dmbarcodeobj = new DataMatrixBarcode; dmbarcodeobj.encodingmode = "base256"; dmbarcodeobj.pointSize = 12; return dmbarcodeobj.Make(dataforbarcode); • Data – The data that will be encoded. This can be one or more fields from your data, a result of another rule, etc. • Process Tilde – When set to "true", the format ~ddd is used to specify the ASCII code ofthe encoded character. For example, if the following text is entered in the Data field, ~029AB it will be encoded as GSAB where GS is a delimiter ASCII 29 character. This can be used in a single string to encode GS and RS characters (GS = ASCII 29 and RS =ASCII 30). Other commonly used ASCII codes are ~009 for a tab and ~013 which is a return function. These are useful when encoding multiple fields in a single symbol. Thedefault is false. • Encoding Mode – There are four encoding methods: • ASCII – encodes data that contains the first 128 ASCII characters. • C40 – encodes data that contains numeric and upper case characters. • TEXT –encodes data that contains both numeric and lowercase characters. • BASE256 – encodes 8 bit values. Now insert this Rule from the “Variable” drop box in the Variable Text Editor. Do not apply the font. The script will return the font. Test and compose.

I just sent you the patch with instructions.

Send the issue to fusionprosupport@marcom.com I will send you the patch to correct this issue

Transferring Layout and Rules from a previous job You need to make sure that if you are using FusionPro template Rules, select "FusionPro>>Edit Rules". Highlight the Rule and click "Convert To JavaScript". Click "Ok", "Ok" and save the template. Now compose one record. This will save the settings in the file This will ensure all the Rules will get transferred when using this solution If you are building an identical job that has the same layout, variable frames, rules, but different data file with the same field names, and would like to eliminate the need to reconstruct the FusionPro PDF; this tip will help. First, click "FusionPro", "Data Definition", "Wizard". Select "Import Data Source From Another Document". Click Next. Browse to the folder that contains the original pdf you want the information imported from. The name of the file will have a ".def" extension. Select it. Click "Open". Click "Finish" Click "FusionPro", "Advanced", "Import". A dialog box will appear with the following options preselected: Variable Layout, Colors, Style. Browse to the folder containing the original pdf .

Possibly corrupt fonts on your system which prevents the fonts from loading to the program. Try the following to clean your font cache on your Apple Macintosh system. Close all applications. Go to Applications:Utilities, open up Terminal program. From Terminal window, run the command in the following sequence: atsutil databases -removeUser or if you have the permission to run sudo command, try: sudo atsutil databases -remove Then run the following two commands: atsutil server -shutdown atsutil server -ping restart your computer. Reload fonts from FusionPro again.

"Legacy line leading" refers to the default leading used by FusionPro, and its predecessors, prior to version 3.1. In FusionPro 3.1 and later, it's a backwards-compatibility mode for older jobs, but new jobs should use the "new" leading. There are two main differences between the old "legacy" leading and new-style leading. The first difference is how point size changes affect leading in absolute-leading mode. In legacy leading, all point size changes would change the leading as well; basically, auto-leading was always in effect. The Variable Text Editor would work around this by outputting extra leading tags after point-size changes to maintain the absolute leading in effect. However, other point-size tags, such as from rules, could break absolute leading. This is why the CopyfitLine function does not work well with legacy leading in absolute-leading mode, because the point-size changes affect the leading. The second difference is in how leading itself is calculated and applied. In legacy leading, leading was the distance between descender lines. In the new leading, it's the distance between baselines. You won't notice the difference if the leading in a flow is all the same size; however, if you vary the leading (either with an explicit leading tag, or by changing point size in auto-leading), you will see that a line of large text followed by a line of smaller text will have less leading in between the two lines under the new leading than under legacy leading. (In severe cases, this can cause collisions, however, that is a consequence of the "baseline-to-baseline" leading model, which is also used by Adobe InDesign.) . Hope this information helps.

In Acrobat, select Fusionpro>>Advanced>>registration>>Renew Registration. A dialog box will appear with the installed license key.