All Posts Tagged With: "Pageflex"
Document Actions Series: Text Manipulation
As I sit here watching out my windows and seeing snow fall, in early November, I can’t but think of the “The Ice Bowl”. This obviously lead me to think the NFL’s trademark rights and how that might need to be controlled in their marketing and branding world. I’ll use that as an example today. The basic premise is that the ™ symbol should be inserted after the letters “NFL” are printed on the page.
I’ll use a combination of 2 different document actions (ReplaceText, Superscript). The project requires only one variable: Text. Text must be set as Formatted Text kind.
First, I’ll create the ReplaceText action. This action does precisely what the name suggests. It takes a character set to find, and when found replaces that text with another set of characters. In this case I’m looking for “NFL” so that I can replace it with NFL™. Here is the document action definition:
Method: ReplaceText
Arguments:
SpecName (contstant) = Text
OldCharacter (Constant) = NFL
NewCharacters (constant) = NFL™
Secondly, I’ll demonstrate the use of the Superscript action. While it’s not necessary in this example I wanted to show how it can be used, even in conjunction with another document action. Here is the document action definition:
Method: Superscript
Arguments:
SpecName (constant) = Text
Character (constant) = ™
Pretty simple example, but one that I think translates into real world project needs. I suggest you follow this up by reading on the GetPositionIndex action as well as Suffix and Prefix. They are closely related to the actions discussed in this post.
This document action chaining example can be views and downloaded at the demo site. The product is named “Documents Actions Calculations”.
Popularity: 86%
To upgrade or not to upgrade: Pageflex 6
Neither Lynn Anderson nor I ever promised you a rose garden. What does that have to do with anything, you might ask. It reminds me of debates about technology upgrades. When encouraged to upgrade to the latest version of something, we (me included) are at times tempted to push back and say: I don’t want to upgrade. What I have works fine. The new version will undoubtedly have stability issues. And all my employees are trained on the current version, and now you’re setting us back. And so on. Ad nauseum.
Popularity: 48%
Training Guy: New Classes and Functionality on the Horizon
First of all, thank you to all the fine folks who filled out or training survey last week. The response has been overwhelming and a lot of folks responded with some very consistent requests. I am working out a way to deliver on some of these requests. I will let you know more when I have something official to announce.
On the Pageflex side of things, we are working on our roll-out to Pageflex 6. I have been busy writing some new lessons to go along with the features it will offer. For those of you how have gone through Pageflex training, don’t worry, the fundamentals of variable text product building will not change. You will just get some additional features to use, such as:
• Text on a path.
• More adjustments for crop marks.
• A toolbar on the spec form for your customer to do some light formatting.
Lots of fun things coming up! But no matter what the future brings, remember that Add is your friend.
Mike
Popularity: 33%
Four51 Application: Pageflex 6x
Pageflex version 6 is coming to Four51! In fact, it is partially here already.
The previous versions of Pageflex have allowed us to submit over 5.5 million jobs. Yesterday, we began running preview jobs against the new Pageflex 6.1 server in our production environment and discovered the new architecture rendered the 10,000 some jobs that were submitted quicker than the version it is replacing.
However, as with any new release of software, this hasn’t been without issues. The new Pageflex architecture required Four51 (and you) to make several changes to the nearly 90,000 variable data project files we host. Some of these changes were scripted, and others we have asked and are asking you to perform.
Luckily, there is light at the end of the tunnel. In the next few weeks we will continue to work with you to ensure your existing products work with preview, proof and production jobs. When we are confident that the transition has been made for existing products, the plan is to support project files created in the newest version of Pageflex. Among other features, these newer projects will support text on a path, document actions and simple impositions. Though transition is sometimes painful, we do like what we see at the other end of the tunnel!
John
Popularity: 14%
Radio Four51: Thoughts from the Spring Tech Conference
Our most recent podcast features Rich Landa discussing how you can add value to your business with technology-based services. The recording summarizes his presentation given at the 2008 PSDA Spring Technology Conference in Savannah, Georgia.
Rich talks about the evolution of web-to-print e-commerce from just a simple tool used for convenience’s sake to a dynamic and necessary tool that allows businesses to customize their operational workflows. Rich also touches on the ways Four51 has designed its platform to be a value-added community that can integrate with companies like SAP and Pageflex. This allows Four51 to effectively serve a wider range of print buyer, seller, and supplier needs that a lot of competitors can’t. Rich explains that when evaluating what system is best for your business, your thought process should extend far beyond just features and functionality.
Check out the podcast to hear more!
Popularity: 9%
Discover Four51: New Knowledge!
I’ve seen and heard quite a bit of positive feedback about Discover Four51. It has been active for about a week now and based on the data I have seen, it’s being used well. Thanks for helping to make the implementation smooth!
I’ll be periodically writing to let you know of new articles posted as well as to share tips and tricks for searching the knowledgebase better.
We just made four new articles live for your use. First is an article about the Pageflex MPower file size restriction and how to get it lifted. The second covers Payflow Pro’s new application that is attached to an article discussing credit card processing options. Third, for those of you wondering how to submit a case through the knowledgebase, I’ve written an article that explains the process. Lastly, we have created an article that discusses custom themes, how to create them and what basic token placeholders are needed to make your theme work with the Four51 application.
As Four51 grows and we connect more and more sellers to suppliers and buyers, our knowledge will expand as will Discover Four51. Please check back here and be sure to search the knowledgebase for your answers. You’ll never know what you don’t know unless you search for it!
Jeff
Popularity: 7%
Thoughts from Four51: Selling the application
I talked to a customer yesterday who was looking for some tips on selling the Four51 application. His questions and frustrations were nothing I hadn’t heard before, and I thought maybe some of you could benefit from the discussion.
The customer is in a great position; he is bringing Four51 to his existing customers with whom he has strong relationships, he has staff members who are trained on Pageflex, and he has a great understanding of the application and the benefits it has to offer.
The problem he is running into time and time again is that although people seem really excited about the application while they are watching a demo, getting them to actually sign up and move ahead is proving unattainable. I’ve heard this more than once from customers and here are some helpful things to think about as you take the application out to your customer base:
- Most of your customers’ needs are being met today. Even though you can save them time and money, they might not be compelled to make a change when the system they have still gets the job done. Make sure to underscore not only the ease of use they’ll enjoy, but also how you plan to help them make a smooth transition. They look to you as your partner, show them you truly are trying to help.
-Take the time to prepare for your demo. Especially when you’re in a situation where you’re working with an existing customer, look at the products they order, the quantities, the frequency, anything that will show them you understand their needs and can help make them work more efficiently.
- Think about how you’re positioning the “getting started” process–does it seem long and arduous? Are you piling on setup fees and ordering requirements that may make it seem like more trouble than it’s worth?
- Are you giving them an offer that they can refuse? Try giving a free trial or a free setup consultation to help move the process along.
- Wow them right away–in your demo, show them a site that you’ve already created for them and describe how easy it is to tailor what you’re showing them into exactly what they need. (This would be a good time to mention the tip above about a consultative session where you’ll work with them to decide what they need included…)
It’s not always an easy sale, but once you get them using the application they will wonder what took them so long!
Laura
Popularity: 6%
Advanced Technology: Layering Pageflex Variables
Template designers are often asked to build a single template to accomodate many different versions of a product. For example, a single customer’s business card may have many different versions, each version having a different layout and graphics. The rules that drive the versions may depend on anything from a person’s corporate division to the number of variable fields used. In all cases, the design of the product changes based on many different dynamic factors.
One strategy that helps when implementing these challenging projects is to use layers of variability. Layered variability means embedding variable content inside of variable content. For example, you can embed variable area templates inside variable area templates. You can embed variable text inside of variable text. You can even mix embedded variable content as long as you stay within the boundaries of Pageflex’s content rules. For example, inside a variable area template, you can embed variable text or a variable image.
Layering variables basically means creating a bunch of rules (or scripts) that control content on several different levels. According to Pageflex, there is no limit to the number of layers you can implement, giving you endless options for how to configure your projects. In the following example, we discuss how to implement a template where a user can choose from a logo selection or enter their own tagline text, but not both. Either the logo appears or the tagline appears. There are two layers of variability to this project:
Layer One: Controls whether the logo OR the tagline appears.
Layer Two: Controls the specific logo OR tagline text to appear.
Here are the general steps we used to create the example:
———————————————————————————————————
1. Draw an Area Template container on your pasteboard.
2. Place an Image container inside the Area Template.
3. Create a source variable for the logo selection:
Variable Name: LogoSelection
Kind: Plain Text
Source: Constant
4. Create an image rule for the logo:
Variable Name: LogoRule
Kind: Image
Source: Rule
Rule Definition:
If “LogoSelection” Is “Logo A” Result Is “LogoA.jpeg”
Else If “LogoSelection” Is “Logo B” Result Is “LogoB.jpeg”
Else If “LogoSelection” Is “Logo C” Result Is “LogoC.jpeg”
5. Apply “LogoRule” to the Image container inside the Area Template.
6. Select the Area Template container with your pointer tool, and then export it as a file into your Area Templates folder. Name the file “LogoVersion.xat”.
7. Delete the Image container inside the Area Template, and then draw a text container inside the Area Template container.
8. Put some default text into the Text container, and then apply a source variable. Use the following variable definition:
Variable Name: CustomerText
Kind: Plain Text
Source: Constant
9. Select the Area Template container with your pointer tool, and then export it as a file into your Area Templates folder. Name the file “TextVersion.xat”.
10. Create a rule for the Area Template container:
Variable Name: VersionRule
Kind: Area Template
Source: Rule
Rule Definition:
If “LogoSelection” Is Not Result Is “LogoVersion.xat”
Otherwise Result Is “TextVersion.xat”
11. Apply “VersionRule” to the Area Template container.
———————————————————————————————————
To see a working example of this project and to download the project files, click here.
There are several benefits to layering variables in your Pageflex projects:
1. Layered variable content make multi-version projects possible, which otherwise would require several different projects.
2. Layering variables reduces the total number of elements in a project. A common mistake amongst template designers is to create a separate static area template for each version. You can reduce the number of content files by embedding variables within your content files.
3. Using layered variable content makes modifications quicker. If you need to make a change that affects an underlying element, you only need to make the change once.
There are also drawbacks to using layering:
1. Initial setup can be complicated and difficult to grasp. Creating templates with several layers of variability requires planning. Your first few templates will take longer to setup, but after several projects, you’ll find that you save a great deal of time.
2. Troubleshooting issues can be difficult. Sifting through lots of different rules and content files to find the specific cause of an error takes some work. Projects often appear to be a tangled mess of nonsense, especially if you did not build the template.
Popularity: 9%
