Raffle Tickets, Parking Permits, Stickers... these are just a few of the many products that need numeric sequencing, and those products are now supported in eDocBuilder.
Using a simple script, you can add sequencing to templates. Specify a start number, end number, increment, and number formatting information to the script. You can “hard code” sequencing information, allow your customer to specify the information and even have the sequencing be determined off the number of items the customer ordered. Sequencing can extend to barcoding as well. You can also apply sequences to VDP documents, and you can have multiple independent sequences on the same template.
Lets take a look at a simple sequencing template on a raffle ticket:
In this example, I will have the customer specify the starting number only. The number of tickets that will be generated will be based on the Quantity they order. We will pull these two fields together using Fields Scripting within eDocBuilder.
Picture 1: Create 3 Form Fields, one for the starting number, one for the stopping number and one for the Field Script area that will display the resulting numbers.
Here are the important settings for each of these three fields in eDoc:
- Start # (EnterStart): Field Type=User Entry, Data Capture=Text Box, Format=Hide Field.
- End # (EnterStop): Field Type= User Entry, Data Capture=Text Box and Profile Field Type will
be set to “Sequence Count” which is a new Profile Field Type added to eDoc for this feature. This profile will look at the number ordered in the Q1 field of their pricing engine, Format=Hide Field.
- Numbering Field (sequencingGroup): Field Type=Static Text or Field Scripting, Field Scripting=using VB Script as seen in Picture 2 (below).
Picture 2: For this example, we are not having the customer specify the increment pattern, or the formatting... we will hard code that in the script. Follow the scripting like you see here: sequence(EnterStart, EnterStop, “1”, “#,###”) This means the start number will come from the number the customer enters in the Start prompt, the stop number will come from the sequence profile field which will look at the number of tickets ordered in the pricing engine, it will go in increments of 1, and it will be formatted like 5,000.
The last step is to assign this template to a product and test it out!
Picture 3: You can see here that I am using a Pricing Calculator Engine that asks the customer how many ticket they want to order in the Q1 field. That number will be used as the stopping number in the template.
Picture 4: You can see here that in the eDocBuilder customization area, I request the starting number for the tickets. The stopping number prompt is hidden from the customer because it is being generated by the number ordered. In this example, where I ordered 3000 tickets, and started on 1,500. After choosing my starting number, and Updating Preview, I see 1,500 on my template. It is using the formatting #,### that I set in my VB Script.
Picture 5: Going to Page 2 in the template, I see how my next increment is 1,501 because I set my increment of “1” in my VB Script.
There are many ways to use this new feature. For more examples please refer to the eDocBuilder User Documentation Manual.