ThomasLewis

It's strictly for preview purposes. I want to be able to add some information on specific templates that users of lower variations would see. The users I have on FP Designer don't know the product very well but still want to be able to preview templates for a certain client. I guess you could think of this like a watermark on the preview screen.

Is there a way to check in the rule validator which variation of FusionPro the template is open on? Basically whether it's open on Designer, Desktop, or Producer. I know you can see if the composition is inBatch and you can grab the longversion number, but neither of those work to check against all variations of the product.

The part of the script that needs to be altered is the part inside the quotes, not the name of the variable. var field_id_name = "Phone Number"; Should be changed to: var field_id_name = "Phone1"; Or as you have the variable name changed already: var Phone1 = "Phone1";

Take a look at this thread here: http://forums.pti.com/showthread.php?t=3522

After looking at what I wrote, I can see my definition wasn't very clear. The example I posted above isn't using unused body pages in the FusionPro template. The original document is basically left alone. This method uses a multipage PDF resource (an Illustrator CC 2015 document called screen.pdf in the zip file) where each page has a white box with a varying level of transparency applied. This allows you to only have to create a single resource that can be reused wherever you need screens. You simply grab the percentage of transparency the user selects and call that page of the resource PDF into the overlapping graphic frame. You can see how this works in the onRecordStart rule of the fusionfile.pdf document in the zip file.

You could just make a multipage PDF where each page is a varying degree of opacity of the white box. Then set the pagenumber to display in the graphic frame based on user selection. Attached is an example. screen-example.zip

The problem with those borders is it screws up the ability to see copyfitting properly or anything at all in frames smaller than 12pt. If there were one thing I could change about FusionPro out of everything it would be the removal of those 6pt preview borders. Evan, check the attached PDF. I made some adjustments to your code and moved it into onRecordStart. One major part was changing the values for y to hundredths of points. Also, I expanded the text frames larger than 12pt to accommodate the 6pt border so when you turn on preview you can actually see content. 2015_supTest.pdf

Before you get too far into this, you need to make sure you are composing the output on Producer or Producer API for x and y movement.

See if this works for you: function zip_validator(zip) { if ((/^([0-9]){5}(([ ]|[-])?([0-9]){4})?$/).test(zip)) return zip; else return "invalid"; } return zip_validator(Field("zip"));

You need to set your input option data field to be type "Graphic". See the screen shot below. http://i.imgur.com/rO8wYsj.jpg

You mean like this? http://forums.pti.com/showthread.php?t=3163 That drove me insane for a very very long time. Somewhere around 9.2/9.3 it got fixed. You might check to make sure you are on the latest version on the server.

You can try configuring your fonts outside Acrobat by running the program here: C:\Program Files (x86)\PTI\FusionPro\configure.exe

The UI Rule is Selective Exclusion. All you need to do is ctrl click on each field you want to selectively exclude from. You just need 2 or more for it to work.

In that case it is just a matter of putting the field name in. This would go in a regular text rule. Just call the rule wherever you need to put the page count number.

I have no idea what you mean by "pulls them in". Does it create a 10,000 record input file you use in FusionPro? Where do you want the page numbers displayed? Sample files showing your input and expected output would be helpful.

Give this a shot: return CreateResource("filename.pdf", "graphic").countPages;

I don't see where the second choice is. The customer chooses the quantity from the drop down in the form, then orders 1 set of however many they chose. They shouldn't get any other options than to order 1 set. I would even hide that Qty: 1, above the add to cart button, with some css.

Here's a sample IForm dynamic pricing file that would match the configuration. Also if you do this you probably want to set the field in Marcom to also write to the SKU or Description so you know the actual quantity on the work order.IForms_DynamicPrice.zip

You might consider just having a quantity of 1 as in 1 set that is $0.00. Then configure your pricing with IForms as dynamic pricing with different values based on the "set" of 250, 500, or 1000.

You have to name your pages under FusionPro/Manage Pages/Page Usage. Then use the following in OnRecordStart: FusionPro.Composition.SetBodyPageUsage("page name", false);

Here's an updated version that should work with any ascii positions. Simply find the ascii number where the 0 is. For many Adobe Pro fonts the tabular oldstyle 0 is at 63043 and proportional oldstyle 0 is at 63280. //numerical ascii position without the var ascii = 63043; var n = "1234 S. Street, Suite 567"; return n.replace(/([0-9])/g, function(str, n) {return "" + (parseInt(n) + ascii) + ";";}).replace(/\s/g, " ");

There's a lot of good information in the links in Dan's signature. You might take a look at some of those and also learn about regular expressions. They can get quite complex depending on what you want to do. Basically in this case we are just finding any digit 0-9 and replacing it with the ascii code for the oldstyle number. Example for this specific case with Minion Pro: (These should have an & in front of the # but the forums seem to hate this) 0 = #63280; 1 = #63281; 2 = #63282; etc. The $1 is a placeholder for what the replacement found, ie if it found a 3 then $1 is a 3. As I mentioned earlier, this may not always be the case depending on where the font creator decides to put those figures.

Sure. The only thing I would caution you on is this is specific to Minion Pro. It will probably work for other Adobe Pro fonts assuming they put the numerals in the same spot. For future readers of this thread: As Dan mentioned in the thread he pointed to earlier, there is no standard so it is impossible to predict where the numerical characters are. If you were to use this for other fonts you would need to find the unicode area where they are located using a program like Character Map and then get the ascii values. In this particular case it's a fortunate coincidence (or well planned) that the last character of the ascii value is the same as the numerical value, resulting in very a straight forward regex replacement.

Go back and look at my post with the script in it. It needs to be exactly as indicated. Notice how your post where you quoted me has the code messed up. If you copied and pasted from that, then it won't work.

Create a new rule called "rule_DeliveryAddress". Paste the code in as indicated but change the Field to Field("Delivery Address"). Check the box that says "Treat returned strings as tagged text". Open text frame where you want the changed text and insert the «rule_DeliveryAddress» variable. Highlight it and change the font to Minion Pro. Go to the compose dialog and the Advanced tab. Turn off the box that says "Limit processing to Latin-1 text". Let me know how it works.