Jump to content

ehazzard

Members
  • Posts

    41
  • Joined

Converted

  • Location
    Solana Beach, CA

Converted

  • Occupation
    Training Architect

Converted

  • FusionPro Products
    Yes

Converted

  • FusionPro VDP software version
    7.2, 8.0

Converted

  • OS
    Windows XP SP3, Windows 7

Converted

  • Acrobat Version
    Acrobat 9.x
  • User Title
    Contributor

ehazzard's Achievements

Explorer

Explorer (4/14)

  • Conversation Starter Rare
  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later

Recent Badges

10

Reputation

  1. Scott, We offer online training for FusionPro Expressions via webinar once a month which illustrates the entire process: Core components of an Expression, how to deconstruct or build an Expression and how it integrates into FusionPro VDP. The link to the schedule can be found below for dates and contact training@pti.com for registration. We can also provide you with some documentation for the process but there is also a User guide in the documentation tab in FP Expressions that is pretty detailed too. http://www.pti.com/proservices/training/
  2. This can also be done with a simple text rule as well: This rule takes the variable "date" and formats using the Long Day(ld) comma Long Month(lm) and the day(d). All formatting in the quotes will be returned as literal text; this is a pre-built rule in the Building Blocks under the Functions tab > date.
  3. Scott, Are you looking for tutorials on how to use FusionPro Expressions or integrating an Expression into FusionPro Desktop/VDP? Thanks
  4. See replies to your other post: By default, the Rule in FusionPro computes the check sum digit to the barcode for validation using the pre-built rule. You can uncheck this box in the XML Rule if the data you are passing into the template already includes this information. Sounds like you got it though.
  5. Julie, the assets.dat file actually includes the embedded fonts for the template. If you are building a template that does not have any live fonts than this file will not be created. It is OK to load the 6 collected files into the Manager for the form setup and it should not provide you with an error. the User Guide is in the documentation drop down menu in FusionPro or from the plug in palette in InDesing/Quark. Eric
  6. By default, the Rule in FusionPro computes the check sum digit to the barcode for validation using the pre-built rule. You can uncheck this box in the XML Rule if the data you are passing into the template already includes this information.
  7. Meir, This maybe something you need to submit to support directly at gfx@pti.com as frames do not typically change position on the art board. It could be associated to the graphic frame and the scaling option applied to the logo, could be an alignment issue of the text within the frame or it could be using text wrap or a different justification of the text in the frame itself. If this doesn't solve the problem, go ahead and send the Collect folder to support. Thanks.
  8. Did not see the attached screen shot and without any other information about the product here is my two cents. I have seen this type of error show up on occasions when working with Variable product types and testing the imposed output file; since there is no data file associated while Previewing and testing you may get this error with VDP product types while testing in the MCC. You may want to report this to Support so they can look at this case specifically.
  9. 1. The native file should be built at trim size. If the file contains a bleed, the bleed distance should extend past the artboard and have a negative value in the transform window. i.e. (-.125) on artboard equals correct bleed setup of 1/8 of an inch. 2. Naming conventions for Fields/Variables, Resources and Rules must not contain special characters; spaces, dashes and underscores are acceptable in naming conventions, although elimating all uses of special characters is encouraged. 3. Templates should be built from your local desktop or harddrive (MAC users), this eliminates special characters in the path name. Once Collected, template files can be stored back on a server. 4. Naming conventions for Fields/Variables, Resources and Rules can not start with a numeric value but a numeric value can be included in the name. i.e. Addr1 is acceptable, 1Addr is not acceptable. 5. Naming conventions for Fields/Variables, Resources and Rules must be greater than one character in length. i.e. RedBarn.jpg is acceptable, a.jpg is not acceptable. 6. No segregation of files. All files used in Composition must reside in the same folder on your local desktop or harddrive. Sub folders are acceptable but should not be more than 3 root levels in the working folder, however, in a production environment (where more than one computer is being used) eliminating sub folders makes the template more portable between computers. 7. Each template should be worked on in a separate folder and its recommended to never have two templates open at the same time. To prevent this, a good form of practice is to quit Acrobat and FusionPro between builds. 8. All graphic frames in the template must include either a Graphic Field or Rule in order to return the graphic image. 9. If a graphic file is called out in a Graphic Rule, then the file name must match the library file exactly . If a graphic file is called out using a Graphic Field, then any graphic file can be associated to the frame in the library; no rule is necessary. 10. If new fonts have been activated using a Font Manager during the template building process you will need to load fonts into the Acrobat Directory so that they are embedded correctly into the PDF. To Load Fonts: In Acrobat, FusionPro tab > Advanced > Load Fonts > Load All/New. 11. Two basic recommendations when Composing the template: In the Composition dialogue window, under the Output tab - always deselect Font Subset; under the Graphics tab - always select Never (Graphics at full resolution) option. 12. In the case where the user is basing a Rule on the selection of a graphic, you no longer need to include the matchPathToString Rule; it's now built in to FP 7.1. The new function is called GetFileName(). It just returns the file name from the path passed to it. i.e. return GetFileName(Field("MyGraphic")); will return the file name of whatever graphic is populating for that field, minus the path.
×
×
  • Create New...