Back End Programming

[Modern Postcard]

We have had some internal questions regarding our workflow with our list processing.

 

The basic process:

1. MP builds templates.

2. Client uploads list and places order.

3. MP receives order.

4. MP downloads client list and runs it through the LP workflow.

5. MP uploads replacement list (the LP version) and processes through PTI’s software.

6. High res PDFs/PPML (whatever) generated by MP hit the digital press.

7. Everyone celebrates.

 

In order to pull this off there must be some sort of switch built into each template:

·If using the CUSTOMER list then do this stuff.

·If using the PROCESSED list (the MP internal version) then do slightly different stuff.

 

I believe the way to pull this off is with a single hidden field, something that exists in the MP list format but does not exist in the customer’s file. For example, WHICHFILE. (Other candidates could be IMB, PACKAGE, PC_ABS_NO, etc.) Since this field is hidden and the client cannot map to it we can use this as the internal/external flag.

· If WHICHFILE is not populated then it’s the customer list. This triggers all the front-end behavior.

· If WHICHFILE is populated we’re dealing with the processed list. This triggers all the back-end behavior.

 

What we would do is insert this logic into each section of the templates that needs to change: a single master rule inserted into each section that needs to behave differently. If internal use this mapping and vice versa.

 

So the open questions / things we need to validate:

1. Will this hidden field as a flag work?

2. Is it possible to show the customer one thing but do another? (Similar, but slightly different, to the way watermarking works.)

a.Show the customer a placeholder indicia and barcode, but swap it out with the real list-driven one on the backend.

b. When printing offset remove the address block entirely.

3. Is there any support for environmental runtime variables?

a. Translation: If PTI generates a PROOF (PDF, JPG, whatever) do one thing. If PTI generates an OUTPUT file (PDF, PPML, whatever) do something else.

b. Examples: Proof vs. Process, Internal vs. external IP addresses, server vs. local processing, act one way on Tuesday but a different way on Wednesday.

[jwhittaker]

I'm interested in this also. I am doing almost the exact same thing.