Custom File Names via ADOR and uStore Data
KA
We are trying to implement a production process that automates some of
the steps after a job from uStore is processed in uProduce. It
requires a file name for the PDF with the order number, the Ordered
Item ID (the product ID unique to the order), and the Product ID (the
one that is assigned to that product (for example the calendar
document), and a letter based on the product property of media type.
Actually we need more fields, but this is fine for our example here.
For automation the order number must be first, so the standard naming
from uStore (filename, orderID, product ID) won't serve us here. This
is what we desire:
Example Filenames:
93125_3874_1872_G
93125_3875_1872_M
Represents:
Order # 93125 Ordered Item # 3874 ProductID #1872 Glossy Finish
Order # 93125 Ordered Item # 3875 ProductID #1872 Matte Finish
(i.e. one order, two items placed in the cart separately, first item
is "4-seasons Calendar" on Glossy paper, second item is also the "4-
seasons Calendar" but on Matte paper)
We figured out how to make an ADOR that will pull these values from
uStore databases that we can then use in uProduce to name the PDFs. We
did this test with a single-database / multiple table Plan file (the
"Orders" table as the primary table and the others as user views),
defining the data points as variables, and creating one ADOR with a
conditional rule based on the Product Property (glossy or matte) that
will determine the filenames which are built as a combination of these
variables and static text
So far so good, but here's where I got stuck. We need to make this
work in conjunction with the campaigns that already exist. Either by
adding another data source to the original Plan files or by other
means you may know of.
The original document posted in uStore is using an .xls file. Let's
say it has ID, firstName, LastName as the schema and FirstName and
LastName are campaign dials. Obviously this database could not have
the order number since that data is generated later on the fly per
order upon submission in uStore. Of course this is the primatry data
source.
All of the data for the filename is in the uStore SQL database
(multiple tables since we need the "EncryptedOrderID" from the "Order"
table and "OrderProductID" from "OrderProduct" table, etc.
When I try to add the uStore SQL database to the existing Plan file,
and all of the uStore database tables as user views, I get errors. Is
this because I have no way to relate the two tables from their
schemas? In reality, the primary key to relate the two would be the
order number, but that is assigned from uStore, not in the XLS file,
so how could I relate them? Or is it a different problem?
Where should I go from here?
Thanks for any ideas. Examples are always appreciated.
Kristin
Dan Sideen
files to match our internal order processing system, and to add
production job instructions to the pdf.
This is what we did, and we use it for all of our uStore-generated
production, as well as static "POD" items.
1. Turn on the xml order export feature in ustore (Presets:Trigger Set
Up:Order Details xml)
2. Added our internal product number to the External ID field of each
uStore prduct. (and our Interal Customer Number to the External ID field
of the store and/or user)
3. Created a new SQL table containing the product properties that we
needed (including which output device the product should be sent to, the
stock to print it on, as well as any finishing instructions.For static
items, the location of the pdf master file)
4. Wrote a .net program that:
a. "watches" for an xml file to be generated by the store.
b. parses the xml to determine the customer and internal product
code.
c. reads the production and finishing information from the new
product table
d. generates an order in our Order Processing/Billing system.
e. prepends a Xerox job ticket to the pdf file, renames the pdf
(to include our internal order number and product code) and sends it to
the appropriate output device. (B&W printer, Colour Printer, Platesetter
or "special")
This effectively automates all of our uStore orders. System works great,
except for two things
- no control over how many and how big the jobs are that show up
on the printers. While this is a scheduling problem, having too much
work is a good problem to have!
- unapproved jobs create orders, and show up on the printer.
(uStore generates the xml file upon order submission. If the store is
set up to require approval before the order is processed, that's a
problem. We are hoping that a future ustore release will allow more
control over when the xml file is created.)
We considered using the API with uProduce to accomplish the same things,
but the solution we implemented doesn't require the API. And jobs that
we generate ourselves in uProduce tend to be very large, and can be
managed a projects rather than orders.
Hope this helps.
Hi,
Example Filenames:
93125_3874_1872_G
93125_3875_1872_M
Represents:
Kristin
--
You received this message because you are subscribed to the Google
Groups "XMPie Interest Group" group.
To post to this group, send email to xmpie...@googlegroups.com.
To unsubscribe from this group, send email to
xmpie-users...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/xmpie-users?hl=en.
This message is intended only for the addressee, it may contain privileged or confidential information. Any unauthorized disclosure is strictly prohibited. If you have received this message in error, please notify us immediately so that we may correct our internal records. Please then delete the original message. Thank you.
Ce message est une communication confidentielle et protegee et l'information qu'il contient est reservee a l'usage exclusif du destinataire. Si vous n'etes pas le destinataire vise, vous n'avez aucun droit de divulguer cette information. Si cette communication vous a ete transmise par erreur, veuillez la detruire et nous en aviser immediatement. Merci.
KA
control the filename, not the other routing stuff (all products go to
one printer), so I'd like to keep searching for a more straightforward
solution if possible. But I will keep this in mind for possible future
needs.
At this point we only want filenaming for this one store, not all jobs
out of uProduce. We are using the XML for the job ticket / billing and
need to match up the files primarily based on the information added to
the uStore tables. It would be nice not to have to make yet another
database and table!
BTW, how did you connect your new SQL table with the product
properties with the original table? Are they both in uPlan? Are they
Excel and SQL or both SQL? I feel that I am close, but missing some
crucial information to pull it off.
Thanks,
Kristin
> This message is intended only for the addressee, it may contain privileged or confidential information. Any unauthorized disclosure is strictly prohibited. If you have received this message in error, please notify us immediately so that we may correct our internal records. Please then delete the original message. Thank you.
>
>
> - Show quoted text -
Dan Sideen
Thanks,
Kristin
For more options, visit this group at http://groups.google.com/group/xmpie-users?hl=en.
This message is intended only for the addressee, it may contain privileged or confidential information. Any unauthorized disclosure is strictly prohibited. If you have received this message in error, please notify us immediately so that we may correct our internal records. Please then delete the original message. Thank you.
Ce message est une communication confidentielle et protégée et l'information qu'il contient est réservée à l'usage exclusif du destinataire. Si vous n'êtes pas le destinataire visé, vous n'avez aucun droit de divulguer cette information. Si cette communication vous a été transmise par erreur, veuillez la détruire et nous en aviser immédiatement. Merci.
