Jump to content

amullen

Registered Users - Approved
  • Posts

    5
  • Joined

Converted

  • FusionPro Products
    No

amullen's Achievements

Rookie

Rookie (2/14)

  • First Post Rare
  • Week One Done
  • One Month Later
  • One Year In
  • Conversation Starter Rare

Recent Badges

10

Reputation

  1. I have written several of my own user-defined functions and stored them in a .js file on my workstation. My employer uses Fusion Pro Producer API (the server) for all of our Fusion Pro compositions; our license prevents us from composing more than one record directly. My functions do not work with the server. After searching through these forums, I found that this is a known fact about Producer API. At least, it was; the most recent thread I found mentioning this fact is from 2009. These functions would go a long way toward improving efficiency and reducing errors because they are used across many different templates. My employer has tasked me with implementing them; however, it seems that Fusion Pro itself is incapable of fulfilling my needs. Is there any way I can get externally-defined functions stored in a .js file to work with the Fusion Pro Producer API? If not, are there any plans to implement this feature in the future?
  2. I'm writing a rule in which I want the output file's name to be the input file's name with a ".pdf" extension instead of ".csv." I've tried using FusionPro.Composition.inputFileName in several ways, but it only returns a null string. I also tried using GetFileName(FusionPro.Compsition.inputFileName)but that didn't work either. I haven't been able to find any other way to access the input file's name. I need to load the input file's name into a string variable so it can be utilized in specific ways. I already know how to create a new, rules-based output file. In past rules, those output files have had names that aren't based on the input file, and they work perfectly. The only sticking point is getting the output file to be named the same as the input file, but with a different extension. Can anyone help with this?
  3. FusionPro Creator and Server version 9.0.3. The output is identical whether viewed as on-screen preview, composed locally using the Desktop machine, or composed using the server. There is no mention in the .msg file of any issues regarding tags, leading, or tagged text resources.
  4. We produce any number of personalized letters every day. The body copy for each letter is stored as a tagged text resource in order to include an in-line signature graphic along with text formatting and variable elements. When previewing and composing (using FusionPro Server), the leading attributes are universally ignored. Whether the leading is set within the <p> tag or with a <leading> tag, its value is disregarded; some form of auto leading is applied instead. Changing the value of the leading attribute has no effect on the final output. When we first built the letter template, this issue did not occur. However, as we added more and more letter styles over time, it began to occur sporadically. At first, restarting the FusionPro workstation solved the problem, but now (about two months after first implenting the template, now including about two dozen different tagged file resources) it does not. Is there a solution to this issue? If it matters, the FusionPro workstation is an Intel Core2 vPro box running Windows XP 2002 SP 3.
×
×
  • Create New...