00doxee Platform Quick Guide-V38

Training Quick Guide
Registered trademarks
Logos and trademarks in this manual are the property of Doxee SpA and may not be used in other manuals or presentations without Doxee
SpA's written authorization.
All rights reserved.

Errore. Nome della propriet del documento sconosciuto. 3
Errore. Nome della propriet del documento sconosciuto.
Table of contents

Chapter 1

Chapter 2

Chapter 3

10
11
12
13
14
14
19
22
28
32
39
48
48
48
49
49
52
54
55
56
57
58
61
68
73
75
76
77
79
81
82
82
83
83
85
87
Table of contents
Process Overview
Getting Access to Platform
Navigating Interface
Using the Browser Back Button
Platform & Collaboration
Creating a New Client
Creating a New Hierarchy
Creating a New Group
Creating a New User
Creating a New Procedure
Creating Data Transformation and Document Composition Resources
Data Transformation and Enrichment
Data Transformation Stages
Data Transformation interface Overview
Creating Data Transformation Pipeline
Adding Elements to the Pipeline
Adding Input and Output Pins
Concatenating Elements in the Pipeline
Breaking Concatenation
Editing the Reader Element
Adding a New File
Selecting Fields
Adding a New Rule
Working with the Toolbox
Defining Input Schema
Creating Output Schema
Populating a Schema Manually
Populating a Schema Automatically
Editing the Data Mapper
Creating a Mapping
Deleting a Mapping
Mapping with Auto Connect
Complex Mapping
Managing Pages
Manipulating Data through Mapping
Complex Mapping: Strings


Chapter 4

89
92
95
96
99
101
102
103
104
104
105
107
111
111
112
112
113
115
116
116
117
118
118
118
120
122
123
123
123
124
125
128
130
130
144
146
146
149
151
152
Complex mapping: if-else statement
Template Info Page Mapping
Account Info Page Mapping
Balance Summary Page Mapping
Account DETAILS_SECTION Mapping
Account DETAIL Mapping
Credit Card Header Page Mapping
Credit Card Detail Page Mapping
Catalogue Resource
Populating Catalog Manually
Populating Catalog Automatically
Address Page Mapping
Editing the Writer
Setting file root
Setting document root
Testing the Project
Validating the Project
Building the Project
Document Composition
Accessing the Resource
Understanding Document Composition
Understanding Document Composition Interface
Configuring the Project
Configuring Page
Configuring Text
Configuring Barcodes
Configuring Output
Understanding Targets
Configuring DEFAULT Target
Configuring Target
Configuring Font
Configuring Color Conversion
Understanding Serializers
Configuring Serializers
Creating Overprint
Configuring Data Schema
Creating Data Schema
Creating Master Pages
Creating Regions
Configuring Families


Chapter 5

Chapter 6

Chapter 7

Chapter 8

155
158
168
168
168
175
177
187
194
205
206
206
213
216
218
220
222
223
233
240
241
242
248
252
254
257
258
259
264
264
264
265
269
282
282
284
284
286
289
291
Configuring Documents
Editing Layout
Generating Contents
Statement
Logo/Banner
Address
Promotion
Statement summary
Statement details
Footer
Flyer
Financial service
Loan
Check
Preview
Build
Output Manager
Configuring Attributes
Configuring Index
Mulichannel Distribution
Preparatory configuration
Configuring an Import Endpoint
Using MD
Testing local file delivery
Configuring an Email Gateway
Testing Email Delivery
Monitoring Service Status
Export Events List
Proofing
Preparatory Configuration
Creating a Proofing Resource
Extending the DC Resource
Designing a Proofing Application
Installing the Application
Additional Configuration Files
Creating an Environment
Running the Application
Batch Production


Chapter 9

Chapter 10

Chapter 11

291
306
308
308
310
311
312
314
314
319
322
342
342
345
348
350
323
323
323
323
325
325
326
326
327
335
338
338
338
339
367
367
367
367
371
371
372
372
374
377
Designing a Batch Production Application for Printing
Configuring In-Bound
Configuring a Source
Configuring an Account
Configuring a Rule
Testing
Extending the Application for Email
Extending DT Resource
Extending BP Resource
Installing the New Version
Digital Archiving
Configuring the File System
Creating a Batch Production Application for Digital Archiving
Installing the Batch Production Application
Modifying the In-bound configuration
Designing a Digital Archiving Application
Creating a Digital Archiving Application and Environment
Configuring Document Classes
Configuring Authorization
Archiving Documents
Extracting Documents
Extracting a Document through Search Form
Extracting a Document with Extraction Document
Tracking & Reporting
Creating a New Tracking & Reporting Application
Configuring Catalogs
Configuring SLA Rules
Creating a Monitoring Line
On-Demand Production
Designing an On-Demand Production Application
Creating an On-Demand Production Application and Environment
Installing the On-Demand Production Application
Adding a New Authorization
Extracting a Document
Creating a Request
Configuring SoapUI
Typographic Conventions


Process Overview 1
From beginning to end the process that transforms a text input file to an output document is composed by four
main stages:

1 Platform & Collaboration configuration
2 Data Transformation & Enrichment (abbreviated as DT)
3 Document Composition (abbreviated as DC )
4 Batch Production (abbreviated as BP)

A this point is not import to understand all details, it is enough to remember that in Data Transformation and
Enrichment (DT) the input file, usually a TXT, is validated and transformed in a XML that Document Composition
(DC) can manipulate.

In Document Composition the graphical appearance of the output file is created and data, extracted from the XML
file produced in Data Transformation stage, are linked into it.

Batch Production (BP) is the final stage in which the production of large volumes of documents is automated.

Getting Access to Platform

1 Open the browser and connect to the URL provided by instructor.
2 Wait while the software loads.

3 Proceed with login using the user name and password provided.

Navigating Interface

After login homepage is displayed:

1 Click on Design
Breadcrumb appears at the top of the page.

Breadcrumb
Access offering
items
Exit
application
Account
settings
System
settings
Connected
user
Product
information
Design tools
Approve
application
versions
Shortcut to items used recently


2 Click on home icon to go back to home page.
3 Click on Design again and then on a client, Trai ni ng in this case.

The breadcrumb is update to represent the actual path.

4 Click on Design or Home in the breadcrumb to go back to Design or home page.

Using the Browser Back Button

1 Go to home page
2 Click Design
3 Click browser back button
A pop up is displayed

4 Click on Stay on Page to cancel or click Leave Page to reload the application.

Platform & Collaboration 2
Objectives: create a new application.

Creating a New Client
1 Click on System settings icon in the home page.

Settings page is displayed

2 Click on Platform & Collaboration

The menu is expanded.

3 Click on Clients.

Clients page is displayed.


4 Click on New Client button.

A wizard to create a new client is displayed.

5 Insert BlueBank in Name field.
6 Insert BlueBank in Description field.
7 Select en_US from Preferred Language drop-down menu.
8 Select United States from Preferred Regional setti ngs drop-down menu.
Step selector

9 Click on step More 3 in the step selector.

10 Click on Create a generic profile for this client.

A new step is added in the step selector.

11 Select Select managers later in Manager Group.
12 Click on Generic profile 4 to go the next step.

13 Insert Client Systems in Name field
14 Insert Client Systems in Description field
15 Click on Fi nish 5


16 Select Create a new hierarchy.

Once you have clicked on Apply button, client name and profile name cannot be
changed.

17 Click Apply button.

New client is created.
Hierarchy wizard is displayed.

Creating a New Hierarchy

1 Insert Default in Name field.
2 Insert Default in Description field.
3 Select Allow users to see descendant groups and their users check box.
4 Select Allow groups to i nherit privileges from their chil dren check box.
5 Select step Client 3.


6 Select BlueBank from the list of available clients.
7 Drag and drop Bl uenBank from Available clients into Hierarchys Client box.

List of available clients
Client associated to
the hierarchy

8 Click on step Fi nish 4.

9 Select Create a new Group.
10 Click Apply.

The hierarchy is saved and Group wizard is displayed.

It is not possible to modify the name of the hierarchy once you have clicked Apply.

Creating a New Group

1 Insert Client Systems in Name field.
2 Insert Client Systems in Description field.
3 Click on step Hierarchy 3.


4 Select BlueBank from the available hierarchies.
5 Click on the small grey triangle near Bl ueBank to expand it.

6 Drag and drop Client Systems into Default.

7 Click on step Privileges 4.

Drag and drop into Default


8 In the Offering item DOCCM enable:
Design data transformation
Approve content
Edit content
Review content
Design templates


9 In the Offering item Output Management enable:
Design output management

10 In the Offering item Data Management enable:
11 In the Offering item Electronic Invoici ng enable:
12 In the Offering item Tracking & Reporting dont enable any privileges.
13 In the Offering item Platform & Collaboration enable:
Manage application
Manage client
Manage platform
14 Click on Profiles 5.

15 Drag and drop Client Systems in the box on the right.



17 Select Go back to Users.
18 Click Apply.

The Users window is displayed.

Creating a New User

1 Click on New User...

New user wizard is displayed.

2 Insert Operator in Logi n name field.
3 Insert Client Systems Operator in Full name field.
List of existing users

4 Insert Sample2013! in Password field.
5 Insert 5000 in Password duration (days) field.
6 Insert operator@doxee.vm in E-mail address field.
7 Click on step Client 3.

8 Drag and drop Bl ueBank into the box below.


9 Click on Locale 4.

10 Select en_US in Preferred language drop-down menu.
11 Select United States in Regional setti ngs drop-down menu.
12 Click on step Profiles 6.


13 Drag and drop Client Systems into the box on the right.

14 Click Apply.

Creating a New Procedure

1 Click on System settings in the breadcrumb.

Settings window is displayed again.

2 Click on Procedures.

Procedures window is displayed.


3 Click New... button.

4 Insert Statement in Name field.
5 Insert Statement in Description field.
6 Click on step Client 2.


7 Drag and drop Bl ueBank into the box below.

8 Click on step App 3.

9 Click on New application under the list of available DOCCM application.

List of available DOCCM applications
Add a new DOCCM application


10 Insert Default in Name field.
11 Expand the group Bl ueBank.

12 Drag and drop Client Systems into on the box on the right.


13 Click Apply.

The new application Default is added.


15 Select Go to Procedures.
16 Click Apply.

Creating Data Transformation and Document Composition
Resources

1 Click on the home icon in the breadcrumb to go back to home page.

You are brought back to home page.

2 Click on Design icon.


3 Click on Bl ueBank.

4 Click on Statement.

5 Click on DOCCM.


6 Click on Default.

7 Click on Resources link on the right to manage resources.

The panel to manage resources is displayed.

Manage resources


8 Click on New Resource from New drop-down menu.

A new form is displayed.

List of existing resources
Toolbar
Application list


9 Insert DT in Name field.
10 Select Data Transformation & Enrichment from the Software service drop-down menu.
11 Select Web application radio button.

12 Click Apply to save.

A new resource is added to the list.

13 Drag and drop DT into the box on the right.


14 Insert DT in resource code field.
15 Press [enter] to confirm.

The resource is added.

16 Click on New Resource in the New drop-down menu.

17 Insert DC in Name field.
18 Select Document Composition in Software service drop-down menu.
19 Select Web application radio button.
20 Click Apply.
21 Drag and drop DC into the box on the right.
22 Insert DC in resource code field.
23 Press [enter] to confirm.

24 Click Apply to confirm and save all your work.
25 Click on DOCCM in the breadcrumb.
26 Click on Default.

The interface is refreshed; Data Transformation & Enrichment and Document Composition arrows
are enabled.

27 Click on Data Transformation & Enrichment arrow.

A list of shortcuts to resources is displayed.

Data Transformation & Enrichment arrow
Shortcut to DT resource

Data Transformation and Enrichment 3
Objectives: understand stages of Data Transformation and apply to a project what you have learned.
Data Transformation Stages
The purpose of Data Transformation (abbreviated as DT) is to transform an input file, which can be in many
different formats, into a standard output file that Document Composition can take as input and manipulate.

Data Transformation can be very complex, but the main stages are just three:
Read Input file.
Map values in the input file to output file.
Write the output file (an XML file).
Data Transformation interface Overview

The first time you open DT the working area is empty

Working area
Project explorer
Save

Creating Data Transformation Pipeline

Adding Elements to the Pipeline

1 Select Add Reader element from the Add drop down menu.

2 Insert CSVReader in name field.
3 Uncheck Open editor after creation.
4 Select Flat File Reader.


5 Click Apply.

In the Project expl orer frame a new element is displayed.

6 Drag and drop the reader element from Project explorer into the working area.


7 Add one Data transform element.
8 Insert DataMapper in the name field.
10 Select Data Mapper.
11 Click Apply.

12 Add one new Writer element.
13 Insert XML_Writer in name field.
15 Select XML Writer.
16 Click Apply.


17 Drag and drop the data mapper element and writer element from Project explorer into the working area.

Adding Input and Output Pins

Each element has some pins for input and output.

The Reader element has only output pins, since it is the first stage in the pipeline; on the contrary Writer element
has input pins only since it is the last stage.

The Data mapper element has input and output pins as well.


1 Select the DataMapper element.
2 Click on green plus sign to add input pin.

3 Select the XMLWriter element.
4 Click on green plus sign to add input pin.

Concatenating Elements in the Pipeline

1 Click on output pin of an element and drag it.

2 Pass over the input pin of the desired element.
3 When a pencil icon is displayed release the mouse button dropping the pin into the input pin of the desired
element connecting the two elements.

Concatenate the reader element to the data mapper and the data mapper to the writer.

Breaking Concatenation

1 Click on destination pin.

2 Drag the link outside the pin to remove the concatenation between the two elements.

Editing the Reader Element

1 Click on the name of the element CSVReader.

The specific editor for the element is displayed.

The editor for the reader is composed by two views:
Design editor view.
Data editor view.

We now focus on Design editor.
Name

Adding a New File

1 From the drop down menu select New from sample file.
2 Insert the path to the sample input file provided by the instructor.
3 Click Apply.

The view is populated.

Selecting Fields

This section is optional, verify with the instructor if needed.

It is always possible to map each field manually:
1 Select the first line.
2 Click Row analysis.

3 Insert DOCUMENT in Rule name field.
4 Select Separated by character.
5 From the drop down menu select Semicolon (;).
6 Uncheck Generate fields automatically.
7 Click Apply.


8 Select the row to map.
9 From the selection area select the orange tag.
10 Click and drag on the text to select it; select DOC.

11 Insert Field0 in Name field.

A new field is created.


Click the red cross at the end of the row to remove the rule.

From the PropertySheet box you can modify the properties of the field such as length, starting position and more.

Adding a New Rule

1 Check if there are rules already defined and remove them if present.
2 Select the first line.
3 Click Row analysis.

4 Insert DOCUMENT in Rule name field.
5 Select Separated by character.
6 From the drop down menu select Semicolon (;).
7 Check Generate fields automatically.
8 Click Apply.

A new rule is added.

Remember to save when you are satisfied with changes.


Repeat the same steps and create all rules as shown in the following table:

Row number Rule name
0 DOCUMENT
1 PROFILE-BRANCH
2 TEMPLATE_NODE
3 ACCOUNT
4 BALANCE_SUMMARY
5 DETAILS_SECTION
6 DETAIL
9 CARD
10 CARD_SECTION
11 CARD_DETAIL
19 PROMOTIONS

Check that the rules present match the following tables; if not, add and modify rules manually as
explained in the former section.

DOCUMENT
Field Name Position Start Position Length Optional
F0 F0 0 0 3
F1 date 1 4 8
F2 code 2 13 12
PROFILE-BRANCH
F0 F0 0 0 4
Properties of fields
List of fields Row representation

F1 customerCode 1 5 11
F2 firstName 2 17 6
F3 middleName 3 24 7
F4 lastName 4 32 8
F5 addressLine1 5 41 12
F6 addressLine2 6 54 9
F7 addressCity 7 64 7
F8 addressZipCOde 8 72 5
F9 addressStateShort 9 78 2
F10 customerType 10 81 6
F11 profileType 11 88 8
F12 bic 12 97 6
F13 bankName 13 104 14
F14 branchName 14 119 17
F15 branchCode 15 137 9
F16 email 16 147 18

TEMPLATE_NODE
F0 F0 0 0 3
F1 name 1 4 9

ACCOUNT
F0 F0 0 0 4
F1 accountNumber 1 5 8
F2 currency 2 14 3
F3 beginBalance 3 18 8
F4 endBalance 4 27 8
F5 totalIncome 5 36 7
F6 totalOutgo 6 44 3
F7 totalCards 7 48 1
F8 totalCardsOutgo 8 50 3
F9 totalCardsDebtDue 9 54 3
F10 totalChecks 10 58 1
F11 totalChecksOutgo 11 60 4
F12 totalChecksDebtDue 12 65 4

BALANCE_SUMMARY
F0 F0 0 0 2
F1 month1 1 3 6
F2 value1 2 10 5
F3 month2 3 16 6
F4 value2 4 23 5
F5 month3 5 29 6
F6 value3 6 36 5
F7 month4 7 42 6
F8 value4 8 49 5

F9 month5 9 55 6
F10 value5 10 62 5
F11 month6 11 68 6
F12 value6 12 75 5

DETAILS_SECTION
F0 F0 0 0 2
F1 month 1 3 6
F2 beginBalance 2 10 8
F3 endBalance 3 19 8
F4 totalIncome 4 28 7
F5 totalOutgo 5 36 6

DETAIL
F0 F0 0 0 2
F1 operationDate 1 3 8
F2 valueDate 2 12 8
F3 outgo 3 21 3
F4 income 4 25 0
F5 description 5 26 65
F6 currency 6 92 3

CARD

F0 F0 0 0 3
F1 name 1 4 12
F2 number 2 17 19
F3 expirationDate 3 37 6
F4 plafond 4 44 4

CARD_SECTION
F0 F0 0 0 3
F1 month 1 4 6
F2 totalExpenses 2 11 3

CARD_DETAIL
F0 F0 0 0 3
F1 operationDate 1 4 8
F2 valueDate 2 13 8
F3 outgo 3 22 2
F4 income 4 25 0
F5 description 5 26 21
F6 currency 6 48 3

PROMOTIONS
F0 F0 0 0 4
F1 frontPage 1 5 0
F2 backPage 2 6 18 Y


Toolbox
Elements

Working with the Toolbox

In the Toolbox, under Data Dictionary, you should have eleven entities; if not please
go back to section Editi ng the Reader Element and follow instructions.

To manage entitites you can use the toolbar:

1 Select the first entity in the toolbox and click Add entity structure.
2 Select Group.

3 Insert FILE in the Group name field.
4 Click Apply.

Add entity Document selector
Delete entity


The new Group entity is added.

5 Select DOCUMENT entity.
6 Click again Add entity structure.
7 Select Repeat.

8 Set Minimum to 0.
9 Check Unbounded.
10 Set Mode to Greedy.

11 Click Apply.

The Repeat entity is added.

Repeat the same steps and insert a new Group named DOCUMENT.
Drag and drop the entities in the tree to rearrange them in order to obtain a tree that reflects this structure:

12 Select TEMPLATE_NODE entity.
13 Create a group named TEMPLATE.
14 Drag and drop all entities except PROMOTIONS under this group.

15 Select TEMPLATE Group.
Create a Repeat entity: Repeat (0 : Unbounded), greedy.
16 Select ACCOUNT
Create a new Repeat entity: Repeat (0 : 1), greedy.

Create three new groups: DETAILS_SECTION_GRP, CARD_GRP, CARD_SECTION_GRP.
Create missing repeat entities and rearrange the objects to reflect this structure:

17 Once you are satisfied with results click Defi ne schema button to create a new schema.
18 Select DOCUMENT Group.
19 Click Defi ne the selected group as separeted document.

Defining Input Schema

1 Select now View Data editor.

2 In the Rules column click on DOCUMENT to select it.
3 In the Rule identifiers area click the green cross to add a new descriptor.

4 Select Fixed i dentifier.
5 Set Start posiotion to 0.
6 Set Value to letter_type.
7 Click Apply.

A new rule identifier is displayed.

1 Select now PROFILE-BRANCH.
2 Add a new rule idenfier.
3 Check Fixed identifier.
4 Set Start position to 0.
5 Set Value to PROF.
6 Click Apply.

Repeat the same steps and create the following Rule Identi fiers:

Rule name Descriptor Value Start position
TEMPLATE_NODE TEM Fixed identifier 0
ACCOUNT ACCT Fixed identifier 0
BALANCE_SUMMARY BS Fixed identifier 0
DETAILS_SECTION DS Fixed identifier 0
DETAIL DT Fixed identifier 0
CARD CDD Fixed identifier 0
CARD_SECTION CDS Fixed identifier 0
CARD_DETAIL CDT Fixed identifier 0
PROMOTIONS PROM Fixed identifier 0

Save the project.

Creating Output Schema

1 Close the reader editor and go back to Pipeline Editor.
2 From drop down menu click Add Schema.
3 Insert OutputSchema in the Name field.
4 Click Apply.

The schema editor is opened.

There are two ways to create a new schema: automatic and manual.
The easiest and fastest way obviously is to import an existing xml file and let the software do the work.
It is always possible to manually build the schema node by node.

Populating a Schema Manually

When you select a node a contextual menu with specific tools is displayed:

1 Click on Add node.
2 In the Name field insert ACCOUNTType.
3 Set Type to Builti n:string.
4 Click Apply.

A new node is added.

1 Select the new node just created.
2 From the contextual menu add a new attribute.

3 Insert accountNumber in the Name field.
4 Set Type to builti n:string.
5 Click Apply.

A new attribute named accountNumber is added.


Continue inserting new nodes and attributes to complete the schema.


Populating a Schema Automatically

It is possible to extract the schema directly from an existing XML file:
1 Verify to have an empty schema; remove all nodes present.
2 Select default namespace .
3 Click Import XML/XSD.

4 Insert the path or browse to the XML sample file.
5 Click Apply.

The schema tree is automatically populated.


N.B.: Please note that element order is not relevant.

Editing the Data Mapper

With the Data Mapper you can take one or more attributes from input file, manipulate them and map them to one
or more attributes in the output files.

1 Click on Select Input
2 Select schema.CSVReader.
3 Click Apply.

Input schema
Mapping area
Output schema
Mapping
manipulation
tools
Page manipulation tools


If schema.CSVReader is not present go back to chapter Defini ng i nput schema.

The input schema is displayed.

Repeat the same steps selecting OutputSchema for output schema.

Output schema is displayed.

Creating a Mapping

1 Select the attribute you want to map from the input schema.
2 Click on the corresponding pin and drag it on the pin of the attribute in the output schema.

A new mapping is created
The connected pins turns blue and a persisting line representing the mapping is displayed

Deleting a Mapping

1 Click on the line representing the mapping.
2 Click on the red cross to delete it.

Mapping is deleted, line removed and pins turn white again.

Mapping with Auto Connect

When you have elements with attributes with the same name in the input and also in the output schema it is
possible to let the software maps them automatically.

1 Click on Auto connect button to enable the feature.
2 Select the element you want to map.
3 Click on the corresponding pin and connect it to the element in the other schema.

All attributes of the selected element that have the same name in the input and also in the output
schema are mapped automatically.


Complex Mapping

It is possible to map an attribute directly or manipulate it before mapping it to output.
The Toolbox in the right edge of the window contains many tools to manipulate data organized in six sets:
Aggregation.
Boolean.
Common.
Date.
Math.
String.

Managing Pages

Data mapping interface can quickly become very crowded; pages are an easy way to organize your work and keep
everything under control.

1 Edit page Page 1.
2 Insert Document info in Page name field.


3 Click Apply.

The Page name is updated.

4 Select Add page icon to add new page.
5 Insert Profile in Page name field.
6 Click Apply.

Create pages Profile, Template Info, Account Info, Balance summary, Account details section,
Account detail, Credit card header, Credit card detail, Promotions, and Address.

Manipulating Data through Mapping

1 Select Document Info from the page drop down menu.
2 Select the Date set in Toolbox.
3 Drag and drop FormatDate tool in the working area.

If tools are not completely visible or go outside the visible area use the button near
output schema to scroll the working area.

4 Connect the attribute DOCUMENT > date in the input schema to the input pin of the FormatDate
tool.
5 Connect the output pin of the tool to the attribute DOCUMENT > date in the output schema.

6 Select the wrench icon.

The configuration panel is displayed.

7 Edit the Input Format field and insert yyyyMMdd.
8 Set Output Format to dd/MM/yyyy.
9 Set Input Locale to Defaul t.
10 Set Output Locale to es_US.
11 Click Apply.
12 Connect the attribute DOCUMENT > code in the input schema, to the attribute DOCUMENT > code
in the output schema.
13 Connect the element DOCUMENT in the input schema, to the element DOCUMENT in the output
schema.

Complex Mapping: Strings

It is possible to create mapping as complex as necessary:
1 Select Profile page.
2 Drop in the working area one Substri ng tool from String set.
3 Drop in the working area one Concatenate tool from String set.
4 Drop in the working area three Constant tool from Common set.

Tools like concatenate accept multiple inputs, one for each input pin; to add more input pins click on the wrench
icon.
5 Connect middleName of PROFILE-BRANCH to in0 of Substring.
6 Connect out0 of Substring to i n0 of Concatenate.
7 Connect out0 of Constant elements to i n1 of Concatenate.
8 Click on the wrench icon of Substring.
9 Set From to 1.
10 Set Length to 10.
11 Click Apply.


12 Select the wrench icon of the Constant connected to in1 of Concatenate.
13 Set Constant to . (dot and blank).
14 Click Apply.
15 Click the wrench icon of Concatenate.
16 Uncheck Separator.
17 Click Apply.

Complex mapping: if-else statement

1 Drop in the working area a ComplexIf from Boolean set.
2 Drop in the working area a Length from String set.

A ComplexIf tool has three input pins and one output pin. You can add or remove input pins. You can use input
pins to build Boolean condition and also define Output if true value and Output if false value.

3 Connect PROFILE-BRANCH > middleName to in0 of Length.
4 Connect out0 of Length to i n0 of ComplexIf.
5 Connect out0 of Concatenate to i n1 of ComplexIf.


6 Select the wrench icon of the ComplexIf tool.
7 Remove the i n2 input pin.
8 Write in0 > 0 in the Boolean condition field.
9 Select in1 in the Output if true combo.
10 Choose No val ue in the Output if false drop down menu.

Add a Concatenate tool, click the wrench icon, add 2 inputs pin and uncheck Separator.
Add a Constant tool, set value to blank.


11 Connect PROFILE-BRANCH > firstName to in0 of Concatenate.
12 Connect the out0 of Blank Constant to i n1 of Concatenate.
13 Connect the out0 of ComplexIf to i n2 of Concatenate.
14 Connect PROFILE-BRANCH > lastName to in3 of Concatenate.
15 Connect out0 of Concatenate to PROFILE > fullName of OutputSchema.

At this point the Boolean expression defined is:
if PROFILE-BRANCH > middleName is not empty, then take the first letter and append a full stop.
The firstName, the first letter of the middleName and the lastName are separated by a blank,
concatenated and then mapped to PROFILE > fullName

16 Connect PROFILE-BRANCH > customerCode to PROFILE > customerCode.

17 Connect PROFILE-BRANCH > firstName to PROFILE > firstName.
18 Connect PROFILE-BRANCH > middleName to PROFILE > middleName.
19 Connect PROFILE-BRANCH > lastName to PROFILE > lastName.
20 Connect PROFILE-BRANCH > customerType to PROFILE > customerType.
21 Connect PROFILE-BRANCH > profileType to PROFILE > profileType.
22 Connect PROFILE-BRANCH > email to PROFILE > email.
23 Connect PROFILE-BRANCH > bic to BRANCH > bic.
24 Connect PROFILE-BRANCH > bankName to BRANCH > bankName.
25 Connect PROFILE-BRANCH > branchName to BRANCH > branchName.
26 Connect PROFILE-BRANCH > branchCode to BRANCH > branchCode.

Template Info Page Mapping

1 Select Template Info page.
2 Disable Auto connect.

Drop 6 Format Number tools from Math Toolbox.

Format Number operator is used to change the format of a number.
The operator formats the input number according to the settings defined in the options.

3 Click the wrench icon on the first Format Number tool.

4 Choose System from Input Format menu.
5 Choose Custom from Output Format.
6 Choose en_US from Custom Locale.
7 Click Apply.


Make the same steps for all the Format Number tools.

8 Connect ACCOUNT > totalIncome to the i n0 of the first Format Number tool.
9 Connect the out0 of the first Format Number to ACCOUNT > totalIncome.

You can also use the clone function to speed up the operation; right click on the
object to access the shortcut.

Repeat steps 7, 8 mapping totalOutgo, totalCardsOutgo, totalCardsDepbtDue, totalChecksOutgo,
totalChecksDebtDue from ACCOUNT InputSchema, to ACCOUNT in the OutputSchema, using the
five Format Number tools.


10 Connect TEMPLATE_NODE element in the InputSchema to the TEMPLATE element in the
OutputSchema.
11 Connect TEMPLATE_NODE > name to TEMPLATE > name.
12 Connect ACCOUNT element in the InputSchema to ACCOUNT element in OutputSchema.
13 Connect ACCOUNT > totalCards in the InputSchema to ACCOUNT > totalCards in the
OutputSchema.
14 Connect ACCOUNT > totalChecks in the InputSchema to ACCOUNT > totalChecks in the
OutputSchema.
The mapping of the page Template Info is now complete.

Account Info Page Mapping

Drop two Format Number tools in the mapping area and configure them as seen above.
Map the attributes as shown in the image.

Select System from Input Format drop down menu, Custon from Output Format and en_US from
Custom Locale.

Balance Summary Page Mapping

1 Select Balance summary page.
2 Drop a FormatDate Tool in the mapping area.
3 Connect BALANCE_SUMMARY > month1 to i n0.
4 Connect out0 to BALANCE_SUMMARY > BALANCE_MONTH1 > month.

Configure it as follows:
Input Format: yyyyMM
Output Formato: MMMM
Input Local: Default
Output Locale: en_US

Add five more FormatDate tools and configure it as seen above.
Connect the FormatDate as shown in the following table:


Tool type in0 out0
Format Date
(already configured)
(Input Schema)
BALANCE_SUMMARY >
month1
(Output Schema)
BALANCE_SUMMARY > BALANCE_MONTH1 >
month
Format Date
(Input Schema)
BALANCE_SUMMARY >
month2
(Output Schema)
month
Format Date
(Input Schema)
BALANCE_SUMMARY >
month3
(Output Schema)
month
Format Date
(Input Schema)
BALANCE_SUMMARY >
month4
(Output Schema)
month
Format Date
(Input Schema)
BALANCE_SUMMARY >
month5
(Output Schema)
month
Format Date
(Input Schema)
BALANCE_SUMMARY >
month6
(Output Schema)
month

5 Drop a FormatNumber Tool.
6 Connect BALANCE_SUMMARY > val ue1 to i n0.


7 Connect out0 to BALANCE_SUMMARY > BALANCE_MONTH1 > balance.

Configure it as shown below:

Add six more FormatNumber. Map the elements as shown in the following table:

Tool Type in0 (Input Schema) out0 (Output Schema)
Format Number 1 BALANCE_SUMMARY > value1
bal ance
Format Number 2
(Input Schema)
BALANCE_SUMMARY > value2
bal ance
Format Number 3

bal ance
bal ance
Format Number 5
(Input Schema)
bal ance
bal ance

Repeat the steps already shown to complete the mapping as follows:

Account DETAILS_SECTION Mapping

Format Date
DETAILS_SECTION_GRP >
DETAILS_SECTION > month
ACCOUNT > DETAILS > DETAILS_SECTION >
month
Format Number
DETAILS_SECTION >
beginBalance
beginBalance
Format Number
DETAILS_SECTION > endBal ance
endBal ance
Format Number
DETAILS_SECTION > t otalIncome
total Income
Format Number
DETAILS_SECTION > t otal Outgo
total Outgo

FormatDate configuration:
Input Format: YYYYmm
Output Format: MMMM yyyy
Input Locale: Default


FormatNumber configuration (the same for the 4 tools):
Input Format: System
Output Format: Custom
Custom Locale: en_US
Pattern: empty

Account DETAIL Mapping

FormatDate
DETAILS_SECTION_GRP > DETAIL >
operationDate
ACCOUNT > DETAILS > DETAIL > operat ionDat e
FormatDate DETAILS_SECTION_GRP > DETAIL > valueDat e ACCOUNT > DETAILS > DETAIL > valueDat e
FormatNumber DETAILS_SECTION_GRP > DETAIL > outgo ACCOUNT > DETAILS > DETAIL > outgo
FormatNumber DETAILS_SECTION_GRP > DETAIL > income
income

1 Connect DETAILS_SECTION_GRP > DETAIL element in the Input schema to ACCOUNT > DETAILS > DETAIL in the
Output schema.
2 Connect DETAILS_SECTION_GRP > DETAIL > description in the Input schema to ACCOUNT > DETAILS > DETAIL >
descri ption in the Output schema.
3 Connect DETAILS_SECTION_GRP > DETAIL > currency in the Input schema to ACCOUNT > DETAILS > DETAIL >
currency in the Output schema.

FormatDate configuration:
Input Format: yyyyMMdd
Output Format: MM/dd/yyyy
Output Locale: Default

FormatNumber configuration (the same for the 4 tools):
Pattern: empty


Credit Card Header Page Mapping

Tool Type in0 out0
direct
connection
(Input schema) (Output Schema)
CARD_GRP > CARD > name CREDIT_CARDS > CARD > name
direct
connection
CARD_GRP > CARD > number CREDIT_CARDS > CARD > number
FormatDate
CARD_GRP > CARD > expirationDat e
CREDIT_CARDS > CARD >
expirat ionDat e
FormatNumber
CARD_GRP > CARD > plafond CREDIT_CARDS > CARD > plafond
FormatDate
CARD_GRP > CARD_SECTION_CRP >
CARD_SECTION > month
CARD_SECTION > month
FormatNumber
CARD_GRP > CARD_SECTION_CRP >
CARD_SECTION > total Expenses
CARD_SECTION > total Expenses

Configure Format Date of expirationDate as follows:
Input Format: yyyyMM

Configure Format Date of month as follows:
Input Format: MMyyyy

Configure Format Number tools as follows:

Credit Card Detail Page Mapping

Tool Type in0 out0
direct
connection
CARD_GRP > CARD CREDIT_CARDS > CARD
direct
connection
CARD_GRP > CARD_SECTION_GRP >
CARD_SECTION
CREDIT_CARDS > CARD > CARD_SECTION
direct
connection
CARD_DETAIL
> TRANSACTION
FormatDate
CARD_DETAIL > operati onDate
CREDIT_CARDS > CARD > expirationDat e
FormatDate
CARD_DETAIL > val ueDat e
CREDIT_CARDS > CARD > plafond
FormatNumber
CARD_DETAIL > outgo
> month
FormatNumber
CARD_DETAIL > i ncome
> totalExpenses
direct
connection
CARD_DETAIL > descri ption
> totalExpenses
direct
connection
CARD_DETAIL > currency
> totalExpenses

Configure Format Date tools as follows:
Input Format: yyyyMMdd
Output Format: MM/dd/yyyy
Output Locale: Default

Configure Format Number tools as follows:

Catalogue Resource

To complete the mapping you have to create a catalog:
1 Go back to Pipeline Editor view.
2 From the drop down menu select Add Resource.
3 Set Name to UStates.
4 Select Catalog.
5 Click Apply.

The Catalog editor is opened.

Populating Catalog Manually

This section is optional, verify with the instructor if needed.

As already seen before to populate the catalog you can use a manual procedure or an automatic one. To populate
the catalog manually:

1 Click Add Fields.
2 Set Name to short.
3 Click Apply & New.
4 Set Name to full.

5 Click Apply.

6 Click Add Record.
7 Click on each field individually and insert text.
8 Click on an empty area to unselect the field and confirm text.
9 Click Validate.

Populating Catalog Automatically

1 Click Data Source.
2 Select Delimited.
3 Set Delimiters to Semicolon.
4 Set Text qualifier to (none).
5 Set Encodi ng to UTF-8.
6 Check First line contai n fields defi nition (Override existing field structure).
7 Set Valid data start from line to 2.
8 Insert the path to the CSV sample file containing the catalog.
9 Select Import data from source.
10 Click Apply.
11 Click Validate.


The catalog is populated.

12 Click the key icon in the column short.
13 Save changes.


Address Page Mapping

1 Drop in the working area one Constant tool from the Common set.
2 Insert a blank in the Constant field.

3 Drop in the working area one Concatenate tool from String set.
4 Add input pins: i n2, i n3, i n4.
5 Uncheck Separator.
6 Click Apply.
7 Connect PROFILE-BRANCH > firstName to in0.
8 Connect Constant out0 to i n1.
9 Connect PROFILE-BRANCH > middleName to in2.
10 Connect Constant out0 to i n3.
11 Connect PROFILE-BRANCH > lastName to in4.
12 Connect PROFILE-BRANCH > firstName to in0.


13 Drop in the working area, one Case tools from String set.

14 In the Case drop down menu select UpperCase.
15 Click Apply.

16 Connect the Concatenate out0 pin to the i n0 Case pin.
17 Connect the out0 Case pin to PROFILE > fullNameAddress.

Add a new Case tool configured as seen above (UpperCase) and connect int i n0 pin with PROFILE-
BRANCH > addressLine1 in the input schema.

Add one Replace tool from String set:
Find: ,
Uncheck Use regular expression

18 Connect the out0 pin of the Case tool to the i n0 pin of the Replace tool.

Add another Replace tool
Find: .
Uncheck Use regular expression
19 Connect out0 of the first Replace tool to the i n0 of the second Replace tool.
20 Connect out0 of the second Replace tool, to PROFILE > addressLine1 in the output schema.

Repeat the same steps and concatenate there tools: Case (UpperCase), Replace (,) and Replace (.).

21 Connect PROFILE-BRANCH > addressLine2 to the i n0 pin of the Replace tool.
22 Connect out0 of the second Replace tool to PROFILE > addressLine2 in the output schema.

Repeat the same steps and concatenate there tools: Case (UpperCase), Replace (,) and Replace (.).

23 Connect PROFILE-BRANCH > addressCity to in0 of the Replace tool.
24 Connect out0 of the second Replace tool to PROFILE > addressCity in the output schema.

25 Connect PROFILE-BRANCH > addressZipCode in the input schema to PROFILE > addressZipCode in
the output schema.
26 Drop in the working area a Catalog from set Common.

27 Click on the wrench icon to configure the Catalog.
28 Select short from the Keys drop down menu.
29 In Output section check full.
30 Click Apply.


Add two Case tools, select UpperCase value.
Map PROFILE-BRANCH > addressStateShort in the input schema to PROFILE > addressStateShort
and PROFILE > addressStateLong in the output schema as shown below:

Editing the Writer

Setting file root

1 Open the writer editor.
2 Click on the FILE element to select it.
3 Click Sets the selected.

The file root is set and a file icon is displayed near FILE.

Setting document root

1 Open writer editor.
2 Click on the DOCUMENT element to select it.
3 Click Sets Document root.

The document root is set
A file icon is displayed near DOCUMENT


If the working area in writer editor is empty verify to have created and saved an
output schema. To know how to create an output schema go back to chapter
Creating output schema

Testing the Project

1 In the Pipeline Editor click Test.

Testing and preview editor is displayed.


2 In Profile properties select the Input/Output tab.
3 Click on CSVReader.
4 Click on Upload button.
5 Select the sample input file provided.
6 Click Save.
7 From the drop down menu Resources selected the file you just uploaded.

Start preview button is enabled.

8 Click Start preview to generate a preview.

Validating the Project

Once the three stages are complete, you can verify and build the application.

1 In the Pipeli ne Editor click the validate icon.

Results of validation or building are reported in the bottom edge of Pipeline Editor.
If you did everything right the message Validation successful is displayed.

2 Click on Message consol e to see validation report.

3 If validation fails, click on Message console and fix the error reported.

Building the Project

1 If validation was successful, click on the build icon.

In the left bottom corner of the page a message is displayed.

2 Click on Message consol e and check the building report.

If validation completed successfully, builds should run smoothly; if its just not the
case click on Message console and fix the errors reported.

Document Composition 4
Objectives: understand the process to design a document layout, design a new document and generate a
document preview.
Accessing the Resource

Get access to the platform as usual.

1 Click on Design icon in the home page.
2 Click on client Bl ueBank.
3 Click on procedure Statement.
4 Click on offering item DOCCM.
5 Click on application Default.
6 Click on Document Composition arrow.

A list of shortcuts to available resources is displayed.

7 Click on DC to start editing.

If the resource you are looking for has not been enabled, click on Resources link on
the right to see all resources defined in the procedure.

Enabled resources
Go to available resources

Understanding Document Composition

Doxee Document Composition is a unique product used to create highly advanced variable data customized
documents (Variable Data Printing) which are TransPromo type documents, that is those whose variable aspects
are affected by both "marketing" and "transactional" contents according to the complexity of the data file. The
product comes with all the tools needed to create layouts and manage the reusable components.
When using Document Composition the entire document composition process is managed as seen below:
Defini ng the layout
Definition of the minimum elements which characterize the general structure of the document. Each layout
consists in specific rectangular boxes placed on the page inside which contents can flow during automatic page
layout phases. The layout boxes will be used in the next phases.
Classification of documents
Definition of document categories (families), each of which contains an unlimited number of documents.
Defini ng the layout fl ow
Defining the behavior of the layout boxes inside the page in relation to the formatting process. Generally speaking,
the flow definition refers to the relations between the boxes which can have feedback and impacts during the
subsequent processing phases.
Defini ng the graphic contents
Detailed description of the document composition that defines what is to be placed inside the pre-established
boxes. Using Document Composition to define the contents makes it possible to specify variable behavior
(business rules) that is piloted by data which is input during the formatting process.
Generati ng document
The items described above are used to generate all the various types of documents that can be produced.
Generating a document requires sequential structural elements (document sections), resources for determining
the specific behavior of each section, and variable data instances to pilot all high level decisions.
The product is entirely based on web 2.0 applications and is implemented using RIA (Rich Internet Application); it
is designed to be integrated within any existing IT infrastructure.

Understanding Document Composition Interface

The most important elements in Document Composition interface are just two:
Section menu:
from this menu you can select one section and open the corresponding configuration.
Working area:
the aspect of this area depends on the section you are in and will be explained in details in the next
paragraphs.

Configuring the Project

The first time you open a project it is completely empty and need some configurations before you can start
creating your layout.

Configuring Page

1 Click on Project tab in the section menu.
2 Click on PROJECT SETTINGS in the contextual menu on the left.

Section menu
Working area

PROJECT SETTINGS is expanded.

3 Click on Page.

Working area is updated consequently.

4 In the working area select i n to set inches as default unit.

5 Double click on A4 (Preset) to change the name of the page format.
Unit selector Configured page formats

6 Insert US Letter.
7 Click on an empty area to confirm.
8 Double click on width value to change it.
9 Insert 8.5.
11 Double click on height value to change it.
12 Insert 11.
13 Press [RETURN] to confirm.

The US Letter page format is configured.

Configuring Text

1 Click on Text in the contextual menu on the left.

The working area is updated.


2 Copy and paste the text provided by the instructor in the working area.

The text inserted is checked and saved if correct and status message is updated.

Status message


Inserted text must be valid; if syntax is not correct an error message is displayed.

Copy and paste the text again if an error is displayed.

Configuring Barcodes

1 Click on Barcodes in the contextual menu on the left.

Insert the text provided in the working area as seen for Text.
Verify results as seen for Text.


Configuring Output

1 Click on Output tab in the section menu.

The section is completely empty except for General Confi guration and DEFAULT target.

Understanding Targets

A target provides the instructions for print spool generation in accordance with specific configurations. Multiple
targets can be created for the same project. The build operation will issue a separate, independent group of files
for each target configured.
Whenever a print spool generation process is triggered, a target for execution is selected. For example, to produce
a print spool that will be dispatched by fax, settings which issue the spool in black and white will be chosen. To
produce a print spool that will be dispatched by email, settings for the use of color will be chosen.

Configuring DEFAULT Target

DEFAULT target configuration is divided in four steps:
Target.
Selection column

Font.
Color.
External project image library.

Configuring Target

1 Click on DEFAULT target.

The working area is updated.

2 Click on Target tab in the working area.
3 Select PDF, PDF/A check box in Spool formats.
4 Uncheck AFDPS check box.


Configuri ng Font

1 Click on Font tab in the working area.

2 Click on New button to create a new font family.

A new popup window is displayed.

List of font families
Create a new font family
Delete a font family Delete a Target
Properties of the font family


1 Insert Arial in Name field.
2 Click New button.

A new font family is created.

3 Select enable checkbox.

Embed check box, File name field and Codepages enabled frame are enabled.

Codepages available and activated

4 Select embed checkbox.
5 Insert arial.ttf in File name field.
6 Select Western (1252) codepage.

Repeat the configuration for Style: bold and insert arialbd.ttf in File name field.

Repeat the configuration for Style: italic and insert ariali.ttf in File name field.

Repeat the configuration for Style: bold italic and insert arialbi.ttf in File name field.


Configuri ng Color Conversion

1 Select Color tab.
2 Check Enable color.
3 Select CMYK radio button.

Color conversion panel is enabled.

4 Click on green plus icon to add a new row in conversion table.

5 Click on the color picker to expand it.


6 Insert 06A1DC.
7 Press [ENTER] to confirm.

8 Insert 75 for C.
9 Insert 20 for M.
10 Insert 0 for Y.
11 Insert 0 for K.

Add a new conversion
color code 9FC9EB
C 35 M 10 Y 0 K 0
color code D2EDF3
C 16 M 0 Y 3 K 0
color code EEF8F6
C 5 M 0 Y 3 K 0

Understanding Serializers

Document Composition generates print spools in two phases. The first phase is known as document composition,
the second one as output management. At the end of the first phase a sequence of pages is produced for each
shipment. In the second phase the sequence of pages is manipulated, subdivided and channeled into one or more
files which constitute the final output.
A serializer contains the configuration used to manipulate the sequence of pages. A large number of different
serializers can be configured but only one can be chosen for each print spool generation.
Different serializers are often used to modify the operating mode depending on the type of recipient of the print
spool. For example, a specific type of file subdivision and specific accompanying indexes are needed to send the
spool for printing while the organization is different if a spool is sent for archiving. Two different serializers can be
defined for the two different cases.

Configuring Serializers

1 Select Serializers from the tree on the left.
2 Serializer settings are empty.

3 Click New to create a new serializer.

A new window is displayed.


4 Insert DEFAULT in field Code.
5 Click New.

The tree on the left is updated.

6 Expand DEFAULT.
7 Select Lots.
8 Click on New to create a new lot.

9 Insert DEFAULT in field Code.
10 Click New.


The tree is updated.

11 Select Files and metadata.
12 Click New...

13 Insert PRINT in field Code.
14 Click New.

Create a new Files and metadata named EMAIL.
Create a new Files and metadata named ARCHIVE.

Create a new Overprint named PRINT.


15 Select Serializers > DEFAULT > Files and metadata > PRINT.
16 Click on New index icon.


17 Insert TRACKING550P in Code field.
18 Click New.

The Index properties window is updated.


19 Click on Attributes management

20 Click on the green plus sign String


21 Insert TR550_FILENAME in Code field.
22 Click New.
23 In Properties area change Length to 256.

24 In Assignment tree select the Apply expression to the selected node icon.

25 Click on plus sign Constant in Type of node area.


A line in table below the button becomes editable.

26 Insert 00550_ELOGDATA_000_

27 Select System tab in Allowed attributes area.
28 Search for External lot identifier.
29 Drag and drop the attribute from Allowed attributes into Value table in the center of the page.


Add a new constant and insert .packager.

30 Click Close.
31 Drag and drop the attribute TR550_FILENAME just created into File name: field in Index properties.

Inserting a new XML setting file will overwrite the current configuration.

32 Click on Open the XML settings input panel icon.
33 Copy and paste the XML file provided.

All attributes are added automatically and Allowed attributes table is populated.

34 Select TRACKING550P index.
35 Click on New event for selected i ndex icon.

36 Select print job start from drop down menu.
37 Click New.
38 Select print job start event.
39 Click on New record for selected event icon.


Record properties area is displayed.

40 Insert Header in Name field.
41 Insert | in Separator field.
42 Search for TR550H_00_RECORDTYPE in Allowed attributes table.
43 Drag and drop TR550H_00_RECORDTYPE in Val ues table on Record properties.


Repeat the same steps and add:
TR550H_02_LOTID
TR550H_03_CLIENTID
TR550H_04_ACCOUNTID
TR550H_05_JOBID
TR550H_06_WORKTYPE
TR550H_07_WORKSTAGE
TR550H_08_OWNER
TR550H_09_HOSTNAME
TR550H_10_APPTYPE
TR550H_11_PROCEDURE
TR550H_12_PROCVERS
TR550H_13_JOBRESULT
TR550H_14_AUTOCLOSE
TR550H_15_CUSTOM01
TR550H_16_CUSTOM02
TR550H_17_ CUSTOM03
TR550H_18_ CUSTOM04
TR550H_19_ CUSTOM05


Repeat the same steps and add a new shipment end event.

Add a new Detail record with | as separator.


Add the following attributes to Val ues table:
TR550D_00_RECORDTYPE
TR550D_02_ID_ISTANZA
TR550D_03_ID_MISSIVA
TR550D_04_ID_LOTTO
TR550D_05_NOME_LOTTO
TR550D_06_SIZE_LOTTO
TR550D_07_CODICE_P_P
TR550D_08_ID_CONTAIN
TR550D_09_NOME_CONTA
TR550D_10_TS_CREAZIO
TR550D_11_ID_SOURCE_
TR550D_12_FILENAME
TR550D_13_FILEPATH
TR550D_14_FILE_SIZE
TR550D_15_FILE_TYPE
TR550D_16_ID_PROD


The configuration contains many elements and is too complex to be explained in
details in this guide.
Import the file that comes with this guide to complete the configuration.
The import destroys all former changes.

Creating Overprint

1 Select Serializers > DEFAULT > Overprint > PRINT.
2 Select print job from Type drop down menu.
3 Select first sheet of each document from Apply on drop down menu.
4 Click on Front button.

5 Click on barcode icon.

A new barcode element is added.

6 Select the barcode element.
7 Click on Barcode tab.
8 Select Intelli gent Mail Barcode from Barcode drop down menu.

Barcode element is updated.

9 Click on Size tab.
10 Set X to 0.9055.
11 Set Y to 1.0156.
12 Select the barcode.
13 Select IMB_VALUE from the Data schema table.
14 Click Insert.

The barcode is updated.

Configuring Data Schema

Click on Data tab to start.

Creating Data Schema

The first time you open the Data tab the working area is empty.

1 To create a new data schema follow the big arrow and click Enter.

The configuration editor is displayed.

Working area
Enter / Change button
Document selector Shipment selector


2 Copy and paste the configuration provided by the instructor inside the text area.

The text insert is verified automatically and a message is displayed consequently in the bottom edge of
the window. A message is displayed and Apply button is enabled.

3 Click Apply.

Text insert must be valid XML; if syntax is not correct an error message is displayed
and Apply button is not enabled.

Verify the syntax of the text and opening/closing tags.

Working area is populated with Data schema representation and Enter button is substituted by Change.

4 From Shipment selector drop down menu select DOCUMENT.
5 From Document selector drop down menu select TEMPLATE.

Creating Master Pages

When you open the Page Masters tab the working area is completely empty.

1 Click the green plus button in Master pages area.

A new master page is created.

Master pages
Shared flows
Working area
Grid toolbar
Zoom
Region toolbar


2 Select the master page New master page (US letter).

3 Click on the gear icon.
4 In the Name field insert First page.
5 Click Apply.

Repeat these steps and create three more master pages named Flyer body, Footer and Transactional
inter pages.

Front side
Back side

Creating Regions

1 Select First page master page.
2 Click the plus icon in the region toolbar.

A new region is added on both sides of the page.

3 Click on Name field and change Region 1 to Header/Logo.
4 From the drop down menu Locate i n select both sides.
5 Set Width to 8.5.
6 Set Height to 2.2236.
7 Set X to 0.
8 Set Y to 0.

Repeat the same steps to create the following regions:

Master page Name Locate i n X Y Width Height
First Page Address both
sides
0.9055 2.35 2.988 1.2381
First Page Promotion both
sides
0.5941 3.8677 3.3 3.9567
First Page Statement summary both
sides
4.1137 2.3626 4.1137 5.4618
First Page Transaction both
sides
0.5115 7.9772 7.8333 2.2931
Flyer body Flyer body both
sides
0 0 8.5 11
Footer Footer both
sides
0.5941 10.2843 7.6333 0.5837
Transactional inter pages Transactions both
sides
0.4941 0.6021 7.8333 9.6728

Configuring Families

Families are a way to organize documents in a hierarchy. There could be multiple families; one family can contain
multiple documents but one document can be contained in only one family.
It is convenient in this case to consider a family similar to a directory where documents are saved.

List of families
Rules editor
Family properties


1 Click the plus icon in the List of families area to add a new family.
2 In the Family property area change the Name field to Default.
3 Check Enabled.
4 In the Rules editor area open the drop-down menu Defaul t family and select Default.

A red label DEFAULT FAMILY is displayed in family properties area.

5 Click on Authorize attributes button in Family properties area.

The authorization window is displayed.


6 Keep pressed [SHIFT] and then select DOCUMENT check box.

All attributes are selected at once.

7 Click Apply.

Configuring Documents

Documents tab is organized in two views: Rules and Layout.
With Rules view is possible to create and edit new rules used to select the right document when a specific
keyword or value is present in the input file.

1 Select Rules view.
2 Select Default family in the List of documents area.
3 Click plus icon to add a new document.
4 In the Document property area change the Name to Flyer.
5 Check Enabled.

A new document is added in the list of documents area and also in the rules editor.

View selector
List of documents created
Family created in former chapter
Rules editor
Document properties


6 In the Rules editor click on Select operands.

The data schema is displayed.


7 Select DOCUMENT > TEMPLATE > name.
8 Click on Insert column icon below data schema.

A new column LETTER-TYPE is added.

9 From the drop down menu in name column select equal sign =.
10 Insert flyer in the empty field.

Add the operand to the selection rule


Repeat the same steps to create a new document named Statement with a rule that matches when name
= statement.

11 Click on Authorize attributes in Document properties area.
12 Keep pressed [SHIFT] and select DOCUMENT to select all attributes at once.
13 Click Apply.

Editing Layout

Documents can have a really complex structure but always follow these simple rules:
one document is composed by one or more sections.
one section is composed by one or more master pages.
one master page can contains one or more regions.
to one region can be associated one flow.
one normal flow can be assigned to one region.

one transactional flow can be assigned to one or more regions.

Master pages are ready already, now we are going to create sections, associate master pages to sections, create
flows and then assign flows to regions.

1 Select Layout view.

2 Select Flyer in the List of documents area.
3 Click on the Add section icon.

A new section is added under document Flyer and in the working area.

View selector
Working area
Scope selector Properties
Flows
Master pages


4 Change the Name field in properties area to Flyer body.
5 From Scope drop-down menu select Body.

6 Drag and drop Flyer body master page from Master pages area into working area.

Master page Flyer body is assigned to section Flyer body.


7 Click the plus icon in Document flow area to add a new flow.

A new properties window is displayed.


8 Change Name to Flyer content.
9 Click Apply.

A new flow is added.

10 Click on the gun sight icon.

The mouse cursor changes to a gun sight.

Assign the flow to a region


11 Click on Flyer body region to assign the flow to it.
12 Click on Assi gnment complete to finish assignment and save.

Section name
Master page name
Region name
Flow name

Create a new section Body in Statement document.
Assign First page and Transactional i nter page to scope Body.

Create five new flows:
Address
Footer
Logo/Banner
Promotion
Statement summary

1 Click on the green plus sign in the flow area.
2 In Name field insert Account summary chart.
3 Check transactional check box to make the flow transactional.
4 Click Apply.

Create a new transactional flow Statement details.

Colors may vary.

Assign Address flow to Address region.
Assign Logo/Banner flow to Header/Logo region.
Assign Promotion flow to Promotion region.
Assign Statement summary flow to Statement summary region.
Assign Statement details flow to Transaction region in First page master page and also in
Transactional i nter pages.


Notice that Transaction regions have a blue circle in the top right corner with a white
1 in it; it indicates that the region has a transactional flow and is populated for first by
Statement details flow.
If you have one transactional flow assigned to more than one region in the same
master page, the number indicates the order in which the regions are populated.

5 Select scope Every page.
6 Drag and drop Footer master page in Foreground area.

7 Assign Footer flow to Footer region.

Generating Contents

In the Contents tab you can actually create pages and their content.

Statement

Logo/Banner

1 Click on Contents tab.

2 Select document Statement.
3 Click on Edit button in Operations area to start editing.

The flow editor is displayed.

List of documents
Operations
Document Validation
Family


4 Click on View tab.

5 Check Show Frames.

An orange frame is displayed around regions. The frame turns light blue when region is selected.

6 Click on Flows tab.
7 Click on Logo/Banner flow.

The list of contents and rules are displayed in the box below.
Toolbar Working area
Content properties
Flow tools and properties
Zoom


8 Click on Root element to select it.
9 Click on the green plus sign to add a new static content.

A new static content is also added in the working area.

10 Select the new content.
11 Click on the gear icon.

A new pop up window with content properties is shown.


12 Insert Logo/Banner in Name field.
13 Click Apply.
14 Click on image icon.

A new placeholder is added in the content and the Images tab is selected.


15 Select the image placeholder.

The Images tab is enabled.

16 Click on the green plus sign in Images tab to upload a new image.

A new pop up window is displayed.

17 Browse the file system and select the image provided for the logo.
18 Click Open.

A new pop up window is displayed and upload started.

Upload an image Image placeholder


When upload is completed a new pop up is displayed.


19 Insert Bluebank Banner in Name field.
20 Set Resolution slider to the forth step.
21 Click Apply.

The image is displayed.
A swim lane (blue line with blue triangle ending) is displayed below the image.

The swim lane is used during design to restrict the area in which object can be
moved.
The swim lane is hidden when not selected; to show the swim lane again, click inside
the area it delimits.

22 Select the swim lane.
23 Drag the blue triangle at the end of swim lane to enlarge the area.
24 Select the image.
26 Insert 0.3892 in Y field.

The image is shifted vertically.

Address

1 Select Address region.

Add a new static content named Address.
Drag the swim lane to enlarge the work area.
A simple text element should be already added with the static content; if not, add it now.

1 Select the simple text element.
2 Click on the right border and drag it to the end of static content.

3 Select text inside simple text element.
4 Delete the text.
5 From the Data column on the right select DOCUMENT > PROFILE > fullNameAddress.
6 Click Insert.
7 Verify in Text tab that the font select to be Arial and size 10.

Repeat the same steps and insert a simple text with DOCUMENT > PROFILE > addressLine1 inside and
Y set to 2.5606.
Insert a simple text with DOCUMENT > PROFILE > addressLine2 inside and Y set to 2.7712.
Insert a simple text with DOCUMENT > PROFILE > addressZipCode and addressCity inside, set Y to
2.9818.

You can now create a preview if you like.
Creating a preview is not mandatory at this point but is a good way to verify that what
you are doing is correct and error proof.
To create a preview read the chapter Preview later on in this manual.

Promotion

1 Select Promotion flow.
2 Expand the green plus sign and click add set of rules.

Add a static content named Life insurance.
Add a static content named Mortgage.
Add a static content named Generic Loan.
Add a static content named Student Loan.
Rename the rule Promotion type.

Select Life i nsurance static content and insert the leftbl ue image.


Insert the Family image provided, set X to 0.7748 and Y to 4.0206.

3 Insert a rich text element.
4 Select the rich text element and select Size tab.
6 Set Width to 2.8317.
7 Set X to 0.7644.
8 Set Y to 5.7119.
9 Insert the text PROTECT YOUR FAMILY.

10 Select the text and click on Text tab.
11 Set font to Arial.
12 Set Size to 16.
13 Click on center alignment icon.
14 Expand the color picker and select white.

15 Inside the same rich text element add another line with a life insurance.
16 Select the last line and select Text tab.
18 Set font Size to 10.
19 Set italic style .

20 Add an empty line.
21 Add another line: The BlueBank Family Security Solution offers you a way to protect your familys
future in the event that you were no longer there to care for them.

22 Insert a simple text element.
23 Click on Multiline icon to transform the element to a multiline simple text.
24 Set alignment to right.
28 Set X to 0.6324.
29 Set Y to 7.225.
30 Insert text:
CALL 555 123 1234


31 Insert a simple text.
32 Click on Multiline icon.
33 Select Size tab.
36 Set X to 0.8956.
37 Set Y to 7.5245.
38 Insert text Or visit www.doxeebluebank.com/insurance
39 Set color to white.
40 Set alignment to right.
41 Select the text just inserted.
42 Click on Text tab.
44 Set Size to 8.


Repeat the same steps for Mortgage static content but use mortgage image and the following text:
YOUR NEW HOME
with our premium mortgage

With BlueBank Premium Mortgage Plans the keys to your new house are already in your hands.
We put people into homes!
CALL 555 123 1234
Or visit www.doxeebluebank.com/mortgage


Repeat the steps for Generic Loan and insert Loan2 image and the following text; set the Size values to:
Height 0.9927, Width 2.8317, X 0.8956, Y 6.1278:
YOUR DREAMS
coming true!

Do you really want that bike?
Well then, take it!
CALL 555 123 1234
Or visit www.doxeebluebank.com/loans

Repeat the same steps for Student Loan. Insert image University-loan and the following text; set the Size
values to: Height 1.3793, Width 2.8317, X 0.95136, Y 5.8057:
THE CHANCE OF A LIFETIME
Give your children the best schools.
With BlueBank Premium Student Loans everyone can get a head start!
CALL 555 123 1234
Or visit www.doxeebluebank.com/studentloans


45 Select Promotion type rule set.
46 Click on gear icon.

Properties window is displayed.


47 Click on Select operand button.
48 Select Document > TEMPLATE > PROMOTIONS > frontPage
49 Click on Insert column icon


50 Insert life insurance in frontPage column.
51 Insert mortgage.
52 Insert generic loan.
53 Insert student loan.

54 Click Apply.

Statement summary

Select Statement summary flow and add a new static content named Summary.
Insert the rightgrid image provided by instructor; set X to 4.2735 and Y to 2.4669.

Instead of copy and paste you can also use duplicate tool.

Insert a multiline simple text element.
Font Arial, font size 10, font color white, bold, text alignment right
Size: Height: 0.2106, Width: 1.1811, X:4.8646, Y: 2.4669
Text: Customer
Font Arial, font size 10, font color 06A1DC, bold, text alignment right
Text: Account number
Size: Height: 0.2106, Width: 1.1811, X:4.8646, Y: 3,0226
Text: Customer type
Text: Profile

Text: Branch

Font Arial, font size 10, font color 06A1DC, bold, text alignment left
Text: ACCOUNT SUMMARY
Font Arial, font size 9, font color black, text alignment left
Text: Begin balance
Font Arial, font size 9, font color black, bold, text alignment left
Text: Total outgo
Text: Total income
Text: End balance

Text: CREDIT SUMMARY
Text: Credit cards
Text: Total outgo
Text: Total debt due

Text: CHECKING SUMMARY

Text: Total checks
Text: Total outgo
Text: Total debt due

Font Arial, font size 10, font color white, bold, text alignment right
Size: Height: 0.2106, Width: 2.0244, X: 6.1914, Y: 2.5165
Data: DOCUMENT > PROFILE > fullName
Font Arial, font size 10, font color black, text alignment right
Data: DOCUMENT > TEMPLATE> ACCOUNT > accountNumber
Size: Height: 0.2106, Width: 1.1811, X: 6.1914, Y: 3,0226
Data: DOCUMENT > PROFILE > customerType
Data: DOCUMENT > PROFILE > profileType
Data: DOCUMENT > PROFILE > BRANCH > branchName

Data: DOCUMENT > TEMPLATE> ACCOUNT > beginBalance
Data: DOCUMENT > TEMPLATE> ACCOUNT > totalOutgo
Data: DOCUMENT > TEMPLATE> ACCOUNT > totalIncome

Data: DOCUMENT > TEMPLATE> ACCOUNT > endBalance

Data: DOCUMENT > TEMPLATE> ACCOUNT > totalCards
Data: DOCUMENT > TEMPLATE> ACCOUNT > totalCardsOutgo
Data: DOCUMENT > TEMPLATE> ACCOUNT > totalCardsDebtDue

Data: DOCUMENT > TEMPLATE> ACCOUNT > totalChecks
Data: DOCUMENT > TEMPLATE> ACCOUNT > totalChecksOutgo
Data: DOCUMENT > TEMPLATE> ACCOUNT > totalChecksDebtDue


1 Insert a simple text element.
2 Insert data DOCUMENT > TEMPLATE> ACCOUNT > currency in it.
3 Click on the Reference to attribute icon.

The simple text element turns to an anchor.

4 Set size X: 6.7265.
5 Set Y: 4.2805.


Repeat the same steps and create another Reference to attribute identical to the last one.
Set Size X: 6.7265 and Y: 4.2877.
Set Size X: 6.7265 and Y: 4.4908.
Set Size X: 6.7265 and Y: 4.6939.
Set Size X: 6.7265 and Y: 4.897.

Set Size X: 6.7265 and Y: 5.6251.
Set Size X: 6.7265 and Y: 5.8282.
Set Size X: 6.7265 and Y: 6.0313.


Set Size X: 6.7265 and Y: 6.9752.
Set Size X: 6.7265 and Y: 7.1783.
Set Size X: 6.7265 and Y: 7.3814.


Statement details

Create a static content named Account Details header and Insert the image transactional-header
provided (just push the image to the top of the region).
Insert a simple text element: font Arial, font size 12, font color white, bold, text Account details, Width
2.6128, X: 0.950, Y: 8.0641.


1 Expand the green plus menu and click on add binding icon.

A new pop up window is displayed for data section selection.

If binding is disabled in the menu you forgot to check transactional checkbox in flow
properties.

2 Select DETAILS_SECTION.
3 Click Confirm.

Binding is added to content tree.


4 Open binding properties.
5 Select Borders and background tab.
6 Check Enable.
7 Open color picker.
8 Insert color code D2EDF3.
9 Press [ENTER] .

10 Click Apply.

Add a static content named Account details section header.

Insert a simple text multiline:
Font Arial, size 12
color 06A1DC
alignment left
Size: Height 0.2194, Width 2.3553, X 0.6983, Y 8.4011
Data: DOCUMENT > TEMPLATE> ACCOUNT > DETAILS > DETAILS_SECTION > month
Insert a simple text multiline:
Font Arial, size 10
color 06A1DC
alignment right
Size: Height 0.2194, Width 5, X 3.1582, Y 8.4011
Text: Begin balance: DOCUMENT > TEMPLATE> ACCOUNT > DETAILS > DETAILS_SECTION >
begi nBalance End balanace: DOCUMENT > TEMPLATE> ACCOUNT > DETAILS >
DETAILS_SECTION > endBalance

11 Click on Rectangle icon and insert a new rectangle.
12 Select Background tab.
13 Check Enable.
14 Open color picker and set white.
15 Set Opacity to 100%.
16 Set Size: Height 0.2571 Width 7.5603 X 0.6671 and Y 8.4011.
17 Click on Disposition icon.

A pop up menu is displayed.


18 Click On the background.

Add a new static content named Account details section legend
Add a simple text element multiline
Font Arial, size 10, bold
color 06A1DC
alignment right
Text: Date
Size: Height 0.2106 Width 0.9843 X 1.0052 and Y 8.6578
color 06A1DC
alignment right
Text: Currency
color 06A1DC
alignment right
Text: Outgo
color 06A1DC
alignment right
Text: Income

color 06A1DC
alignment center
Text: Description

Add a new binding DETAIL.

Insert a new static content named Detail content.

Insert a simple text element multiline, reference to attribute
Font Arial, size 8, alignment right
Data: DOCUMENT > TEMPLATE> ACCOUNT > DETAILS > DETAILS_SECTION > DETAIL >
operationDate
Size: X 1.7402 and Y 8.871.
Data: DOCUMENT > TEMPLATE> ACCOUNT > DETAILS > DETAILS_SECTION > DETAIL > currency
Size: X 2.73 and Y 8.8771.
Data: DOCUMENT > TEMPLATE> ACCOUNT > DETAILS > DETAILS_SECTION > DETAIL > outgo
Size: X 3.7143 and Y 8.8771.

Data: DOCUMENT > TEMPLATE> ACCOUNT > DETAILS > DETAILS_SECTION > DETAIL > i ncome
Size: X 4.6998 and Y 8.8771.
Insert a simple text element
Font Arial, size 8, alignment left, italic
Data: DOCUMENT > TEMPLATE> ACCOUNT > DETAILS > DETAILS_SECTION > DETAIL >
description
Size: Height 1.38, Width 2.75, X 5.4876 and Y 8.8771.

Select Root and add another binding CARD.

Add a static content Credit card header.

Add the same background image as for Account details header.

Add a simple text
Font Arial, size 12, color white, bold, alignment left
Size: Width 2.6128, X 0.9091, Y 0.6897
Data: DOCUMENT > TEMPLATE> CREDIT_CARDS > CARD > name
Add a simple text
Font Arial, size 12, color white, bold, alignment right
Size: Width 3.1813, X 4.9248, Y 0.6897
Data: DOCUMENT > TEMPLATE> CREDIT_CARDS > CARD > number

Add a new binding CARD_SECTION.

Add a new static content Card section header.

Add a simple text multiline
Font Arial, size 12, color 06A1DC, alignment right
Size: Width 2.3553, X 0.7744, Y 8.3991
Data: DOCUMENT > TEMPLATE> CREDIT_CARDS > CARD > CARD_SECTION > month
Add a simple text multiline
Font Arial, size 12, color 06A1DC, alignment left
Size: Width 4.9744, X 3.1994, Y 8.3991
Text: Total expenses: DOCUMENT > TEMPLATE> CREDIT_CARDS > CARD > CARD_SECTION >
totalExpenses

Add a rectangle
color: white

Add a static content named Credit card legend

Add simple text element multiline
font Arial, size 10, color 06A1DC, bold, alignment right
Size: Width 0.9843, X 1.0052, Y 8.6161
Text: Date
Size: Width 0.9843, X 1.9894, Y 8.6161
Text: Value date
Size: Width 0.9843, X 2.9737, Y 8.6161
Text: Currency
Size: Width 0.9843, X 3.958, Y 8.6161
Text: Outgo
Size: Width 0.9843, X 4.9422, Y 8.6161
Text: Income
font Arial, size 10, color 06A1DC, bold, alignment center
Size: Width 1.9822, X 5.9265, Y 8.6161
Text: Description


Add a new binding TRANSACTION.

Add a new static content named Card transaction content.


Insert a simple text element, reference to attribute
Data: DOCUMENT > TEMPLATE > CREDIT_CARDS > CARD > CARD_SECTION > TRANSACTION >
operationDate
Size: X 1.7402 and Y 8.8771
val ueDate
Size: X 2.7951 and Y 8.8329
currency
Size: X 3.7456 and Y 8.8329
outgo
Size: X 4.7202 and Y 8.8329
income
Size: X 5.7225 and Y 8.8329
Font Arial, size 8, alignment right, italic
description
Size: Height 1.3807, Width 1.8893, X 5.7225 and Y 8.8329


Footer

1 Select the Map tab.
2 Click on drop down menu and select Every page.
3 Click on Flows tab.
4 Select Footer flow.
5 Add a static content named Footer.
6 Insert the image provided by the instructor named footer.

Flyer

Financial service

1 Open the Contents tab again.
2 Select Flyer from documents list.
3 Click on Edit button.
4 Select Flyer content flow.
1 Expand the green plus sign drop-down menu.
2 Click on Add set of rules.

A new rule named New set of rules is added.

3 Select the element New set of rules.
4 Expand the plus sign drop-down menu.
5 Click on Add static content.

Add another static content.


6 Select the last static content.
7 Click on the gear icon to edit its properties.


8 Insert Loan in Name field.
9 Click Apply.

Change the name of the other static content to Financial services.

10 Select New set of rules.
11 Click on gear icon.
12 Insert Flyer selector in Name field.
13 Click on Select operands button.
14 Select DOCUMENT > TEMPLATE > PROMOTIONS > flyer.
15 Click on insert column icon.

A new column is added to rules table.

16 Insert financial services in the first field.
17 Insert loan in the second field.

18 Click Apply.

Content tree is updated.

19 Select Financial service.

Insert a rectangle element
Size: Height 0.1911, Width 8.5, X 0, Y 0
Color 06A1DC

Insert the picture personal_adviser provided
Size: Y 0.1911

Insert a rectangle
color 06A1DC
Size: Height 1.4454, Width 5.4201, X 2.9602 Y 4.294

Insert a rich text element
color white
alignment right

First line:
font Arial, size 28
Text: How much could you save?
Second line:
font Arial, size 12
Text: <empty line> Contact one of our personal advisers today and discover how your life could be
much easier with BlueBank!

font Arial, size 24
Size: Width 3.127, X 0.1668, Y 6.0432

Insert a simple text multiline
font Arial, size 14, alignment right
Text:
BlueBank Private Banking
BlueBank Investment Banking
Global Mutual Fund
Home loan interest rate 10%
Educations loan up to 4 years
Senior Citizen 9% Interest on fixed amount


font Arial, size 20, alignment left
Size: Width 2.8490, X 0.1668, Y 6.0594
Text:
We cover everything

font Arial, size 14, alignment left
Text:
Now you can access your account from
anywhere, anyplace.
Just login

Insert a rectangle
color 06A1DC
Size: Height 0.7874 Width 8.5, X 0, Y 10.2043

font Arial, size 14, alignment center, color white
Text:
Doxee Blue Bank
2033 Gateway Place, Suite 500, San Jose, CA


Insert the doxee-logo image provided
Size: X 7.1169, Y 6.0432
Insert the iPad image provided
Size: X 0.1668, Y 6.635

Loan

1 Open Fi nancial service.
2 Click on the first rectangle at the top of the page.
3 Click on copy icon.
4 Open Loan.
5 Click on paste icon.

The element is pasted in the new static content in the same position.

Copy and paste does not work for images.

Depending on the order you follow to copy and paste elements the visibility of such
elements change. Some elements can hide others. Use the Disposition icon to
rearrange elements.

Repeat the same steps to copy and paste all other elements.


Edit the text element that report How much could you save? [] with the following text:
The best treatment?

You can achieve everything with our premium loans!
Contact BlueBank today.


Insert the Loan image provided
Size: X 0, Y 0.1969
Insert the iPad image provided
Size: X 0.1668, Y 6.635
Insert the doxee-logo image provided
Size: X 7.1169, Y 6.0432

Check

It is possible to check the documents you have created before creating a preview.
1 Click on Contents tab.
2 Select Flyer document.
3 Click Check button.

If everything is ok a green icon is displayed.

4 Click Approve.

5 Click Approve.

A small green check mark is displayed on document icon.

If check fails read the error in Report area and using the manual verify to have gone
through all steps without errors.

Preview

It is possible to generate preview to verify the result before starting mass production.

1 Click on Preview tab.
2 Click on Advanced setti ngs.
3 Select Output tab.
4 Select the DEFAULT target.
5 Check Enable output setti ngs.
6 Select DEFAULT serializer.
7 Select PRINT file and metadata.
8 Check PRINT overprint.

9 Click Apply.
10 Select all documents.
11 Check Duplex.


12 Click Start.


13 Browse the file system and choose input.xml file.
14 Click Open.

The preview process is started.

The PDF is generated and displayed in a new window.

If preview fails read the error in Report area and check the project.

Build

A build is mandatory to start batch mass production.

1 Click on Project tab.
2 Click on BUILD AND EVENTS.
3 Click on Check and Build.

4 Click on Start build button.

Build process is started.

A new build is created.


5 Click on download icon to get the build.

If build fails click on Failed link in Status column and check errors reported.


Output Manager 5
Objectives: understand how output management works and how to create a custom configuration.

The production of documents is composed by three phases:
Design phase.
Build generation phase.
Print spool generation phase.
During design phase the user designs the graphical contents and manages variables that will be filled in the final
documents by actual values read from input file.
A package, known as build, is created in the second phase. A build contains all the software needed to generate a
print spool.
In the last phase the build is run and generates a print spool that contains the final documents.
The output management configuration, created in the design phase, defines the final arrangement of the print
spool created in the last phase.

Configuring Attributes

This manual will focus on metadata management.
The preparatory activities are not explained in this manual.
Before start please verify to have the XML configuration files that come with this
guide used to configure automatically the environment.

2 Get access to the project as usual.
3 Click on Data tab in the section menu.

Any former changes will be overwritten by the XML configuration file.

4 Click on Change button on the right.


5 Open the XML file provided that contains the data schema.
6 Copy and paste the content of the file in the window.
7 Click Apply.

The file syntax is analyzed and verified. In the bottom edge of the window a message shows if the file is
valid or not. If an error is displayed please close the window, verify to have copied the whole file and paste
it again.

8 Click on Output tab in the section menu.

The section is displayed; it is completely empty except for General Confi guration and DEFAULT target

Any former changes will be overwritten by the XML configuration file.

Selection column

9 Click on Open the XML settings input panel.


10 Open the XML file provided.
11 Copy and paste the file content in the window.

The file syntax is analyzed and verified. In the bottom edge of the window a message shows if the file is
valid or not. If an error is displayed please close the window, verify to have copied the whole file and paste
it again.

12 Click Apply.

The element tree on the left is populated.

13 Click on New menu in the bottom left corner of the window.

14 Add a new File and metadata setti ngs

A new pop up is displayed.


15 Insert PRINT in Code field.
16 Click Apply.

The Files and metadata configuration is added.

17 Click on Attributes management

The attributes management page is displayed.


18 Click on String to add a new string.

19 Insert LOT_NAME in Code field.
20 Click New.

The new attributed is added and properties are displayed.

21 Click on Apply constant to the select node icon in Assi gnment tree area.
22 Insert DEFAULT in the Text val ue box.

23 Click on String to add a new attribute.
24 Insert EMAIL_BODY_NAME in Code field.
25 Click on Apply expression to the selected node icon.
26 Select concatenate from Operator drop down menu.
27 Select variable length.
28 Leave empty the Separator field.

29 Select User tab in All owed attributes table.
30 Drag and drop the attribute EMAIL_BASE_NAME in the Value table.
31 Click on Constant.

A new editable row is added to Val ue table.

32 Click on the new row added.
33 Insert .html.


34 Click on String
35 Insert PRX_CUSTOMER_NAME in Code field.
36 Click New.
37 Click on Apply reference to another attribute to the sel ected node.

The Type of node section is updated.

38 In the Allowed attributes section select Data schema tab.
39 Drag and drop the attribute /FILE/DOCUMENT/PROFILE/@fullName in the x=y field.


40 Click Close.

All other attributes have been already configured by the XML configuration file.

Configuring Index

1 Select the PRINT configuration for Files and metadata.
2 Select Spool sets setti ngs tab.
3 Select Single lot row in Lot table.

4 Search for PDF_ALL_NAME in the allowed attributes list on the right.
5 Drag and drop the PDF_ALL_NAME attribute in the Name field.

6 Click on Spool set i ndexes in the box in the bottom left corner.




8 Insert HEADER in Code field.
9 Select spool set from Level menu.
10 Select in a separate file in Located menu.
11 Click New.

The window is updated.


12 Search for IDX_HEADER_NAME attribute in Allowed attributes.
13 Drag and drop IDX_HEADER_NAME attribute in File name field.
14 Check Enable.
15 Select ANSI in Encodi ng menu.

16 Select the HEADER index.


18 Select spool set start from Type drop down menu.
19 Click New.

A new event is added.

20 Click on New record for the selected event icon.

The window is updated.


21 Insert RECORD1 in Name field.
22 Select crlf from Terminator menu.
23 Select variable length in Concatenation menu.
24 Insert | in Separator field.
25 Search for 400H_TS_START attribute in Allowed attributes table.
26 Drag and drop the attribute 400H_TS_START in the Val ue table.

27 Drag and drop the attribute 400H_TS_END in Value table.
28 Drag and drop the attribute 400H_HOSTNAME.
29 Drag and drop the attribute 400H_APPLICATION_TYP.


30 Click on Constant button.

A new editable row is added to Val ue the table.

31 Insert 00.

Create a new index at spool:
Code TAIL
Level spool set
Located in a separate file
File name IDX_TAIL_NAME

Create a new event
Type envelop end

Create a new record
Name RECORD2
Terminator crlf
Concatenation variable length

Separator |
Values 400D_ID_SOURCE_FILE, 400D_OUTPUT_FILENAME, 400D_OUTPUT_PATHNAME,
400D_RECORD_START, 400D_RECORD_END

Mulichannel Distribution 6
Once configured Multichannel distribution (MD in short) is used to send automatically digital messages like emails,
files, SMSs and more.
A client application generates some messages, groups them in a lot and then saves them on the file system in an
Import Endpoint.
MD acquires one or more message lots and delivers them as configured using a gateway.
A gateway is a delivery method specifically configured with a distribution channel and a schedule.

Preparatory configuration

Multichannel Distribution needs at least 3 different folders on the file system to work properly: one for importing
lots, one for storing lots and one for storing event notifications.
These folders may reside everywhere in the file system but it is strongly suggested to follow the server convention;
please check where other applications store their folders and use the same root directory.
A good start point is the folder md_work, a folder used by MD to manage files internally. Your directory should
reside in the same file system and share the most part of the path.
In our case all applications use /opt/doxee/batch_production/repository/distribution as root dir.
The folders you need to create therefor are:
/opt/doxee/batch_production/repository/distribution/BlueBankIn for reading input message lots.
/opt/doxee/batch_production/repository/distribution/BlueBankOut for storing output message lots.
/opt/doxee/shared/BlueBankExport for storing event notification files.

Please refer to your system administrator to create these folders on your file system.

Verify with your system administrator file permissions.
The file must be readable and writable by the user running the application server.

Configuring an Import Endpoint

This manual takes for granted that a client application that writes message lots is
already available.
It is also possible to copy manually the lot files in the input directory if a client
application is now available.

MD will acquire new message lots reading from the Import endpoints configured.
1 Get access to the Platform and Collaboration as usual.
2 Click on System Settings.
3 Click on Multichannel Distribution.

4 Click on SYSTEM SETTINGS menu.
5 Click on Import endpoi nts.
6 Click on New Import endpoi nt



7 Insert file:///opt/doxee/batch_production/repository/distribution/BlueBankIn in the Path field.
8 Select Multiple gateway from Distribution mode menu.
9 Click Apply.

The new gateway is created and enabled.

10 Select Gateways.
11 Click on New gateway

By default the configuration for remote file transfer is displayed.


12 Select File (local) from Distribution channel menu.

The configuration page is updated for local file transfer.

13 Insert MoveToLocalDir in Name field.
14 Check Dedicated to make this gateway available for one account only and not for all.
15 Select the Transfer tab.
16 Insert /opt/doxee/batch_production/repository/distribution/BlueBankOut in Local path field.

17 Check Abort on duplicated file to stop the file transfer and report an error in case the file is already
present in the destination folder.
18 Select the Scheduli ng tab.
19 Verify the gateway to be always available.

The gateway is added and enabled to the list of available gateway.
The gateway is still not used at the moment.

20 Select Accounts.
21 Click on New account

All available import endpoints are displayed.


22 Insert BlueBank in the Name field.
23 Insert Account for BlueBank in the Description field.
24 Drag the import endpoint created from Available import endpoi nts and drop it in All owed import
endpoi nts.

25 Select the Gateways tab.
26 Drag the gateway created from Available gateways and drop it in All owed gateways.
27 Click Apply.

The account is added but not enabled.

28 Select the account created and click on Enable

Using MD

1 Get access to Platform and Collaboration as usual.
2 Click on Run.
3 Click on tick button in the Multichannel Distribution column.
4 Click on ACCOUNT OPTIONS.
5 Click on Accounts.

6 Click on Bl ueBank link.

7 Click on New profile link.
8 Insert test.
9 Press [ENTER] to confirm.

The new distribution profile test is created and Add import endpoi nt and Add gateway links are
displayed.

10 Click on Add import endpoi nt

11 Select the import endpoint created in the former chapter.
12 Click Add.

13 Click on Add gateway

14 Select the gateway created.
15 Click on Add.


16 Click on Apply.

The configuration is complete and MD is now ready to delivery massage lots.

Testing local file delivery

1 Get access Platform and Collaboration.
2 Click on Run.
3 Click on LOT PRODUCTION.
4 Click on All.

To copy files on the server you can use the shell command scp for Linux/Unix
systems or Winscp for Windows systems.

5 Copy the folder provided with this guide in the input folder
/opt/doxee/batch_production/repository/distribution/BlueBankIn.

In a couple of second the folder is removed and a new entry is added in the LOT PRODUCTION
monitoring pages. The lot should be in Sendi ng phase.

6 Click on the refresh button until the status changes.

The lot status is refreshed.

Refresh


The output file file1.txt has been moved in the output folder
/opt/doxee/batch_production/repository/distribution/BlueBankOut.

Configuring an Email Gateway

A working SMTP serve is needed to send email.
Please verify to have the server address and credentials to access the SMTP server.
The values used here are specific and may be different for your environment.

1 Get access to Platform and Collaboration.
2 Click on System settings.
3 Click on Multichannel Distribution.
4 Click on SYSTEM SETTINGS.
5 Click on Gateways.
6 Click on New gateway
7 Insert SendEmail in Name field.
8 Select Email from Distribution channel menu.
9 Check Dedicated.
10 Select the Connection tab.
11 Insert 127.0.0.1 in Host field.
12 Insert 25 in Port field.
13 Insert doxee in Username field.
14 Insert doxee in Password field.
15 Select None from Security menu.
16 Select Normal password from Authentication menu.

17 Verify in Scheduli ng tab that the gateway is always available.

18 Click Apply.

20 Click on Bl ueBank link.
21 Select Gateways tab.
22 Drag SendMail gateway from Available gateways table and drop it in All owed gateways.

23 Click Apply.
25 Click on Run.
26 Click on tick button in the Multichannel Distribution column.
29 Select the test distribution profile.
30 Select MoveToLocalDir gateway.
31 Click on the red cross icon to remove MoveToLocalDir gateway.

32 Click on Add gateway

33 Select SendEmail.
34 Click Add.

Testing Email Delivery

1 Open the folder provided with this guide.
2 Edit the file email.lotxml.
3 Customize the text <address>change-me@doxee.com</address> with your email address.
4 Customize the text <name>Change Me</name> with your name.

Open the monitoring panel in Platform and Collaboration > Run > Multichannel Distribution > LOT
PRODUCTION > All.

Copy the lot folder provided with this guide in the import endpoint created.

Check the lot status in the monitoring panel.

After a while the status should change to Completed.

In case of problems while connecting with the SMTP server the system will keep
trying forever.
To abort the sending phase, open Sendi ng entry in LOT PRODUCTION menu,
select the lot and click Abort.

After a while an email with the document attached should be received at the address specified in the
.lotxml file.

Monitoring Service Status

4 Click on Service status.

The green light shows the service is up and running.
The services that are stopped have a red light.
If your service is stopped, click on the play button to try to start it.

5 Click on EVENTS.
6 Click on Browse events.

All system events (info, warning and errors) are displayed.

Export Events List

1 Get access to system settings.
3 Open Multichannel Distributi on.
5 Select Export endpoi nts.
6 Click on New export endpoi nt

7 Insert file:///opt/doxee/shared/BlueBankExport in the Path field.
8 Click Apply.

The new endpoint is added but not enabled.

9 Select the export endpoint
10 Click on Enable


11 Click on Enable.
12 Click on Plans.
13 Click on New plan

The following configuration is for testing purpose only and may overload a production
environment.
Disable the plan when all tests are completed.

14 Insert BlueBankPlan in the Name field.
15 Select Recurring in Scheduli ng type.
16 Select Every in Run every day of the week, execute menu.
17 Set the spinner to 1.
18 Select Minutes from drop down menu.
19 Insert 12:00 in Starting at field.
20 Select am.
21 Insert 11:59 in Endi ng at field.
22 Insert your current date in Valid from field.
23 Select Export of monitoring events V2 from Executi ng the plan to menu.
24 Select file:///opt/doxee/shared/Bl ueBankExport from Export endpoi nt menu.


25 Click Apply.

The Plan is created and enabled.

27 Click on Bl ueBank.
28 Select Export endpoi nts tab.
29 Select file:///opt/doxee/shared/Bl ueBankExport and drop it in the Allowed export endpoi nts table.


30 Click Apply.
31 Get access to the Platform and collaboration.
32 Click on Run.
33 Select Multichannel Distribution.
36 Select the Export events tab.
37 Check Export events.
38 Select file:///opt/doxee/shared/Bl ueBankExport from the Through the export endpoi nt menu.
39 Insert 01/01/2000 in the Recorded from menu.


40 Click Apply.

41 Click Apply.

In a minute a new file with all events will be written in the folder
file:///opt/doxee/shared/Bl ueBankExport.

Proofing 7
Proofing (PR in short) is used to test the production of a small amount of documents and to verify the configuration
of all resources used. The proofing application reads an input file, generates one or more PDF files and creates in
the web interface one clickable link for each file generated.
Proofing configuration is very similar to Batch Production configuration and is an introductory step for it.


Please verify to have correctly configured Platform and Collaboration, Data Transformation and Document
Composition before starting. Refer to the corresponding quick guides for any doubts.

Creating a Proofing Resource

You should have already an application with a working resource for Data Transformation, called DT, and one for
Document Composition, called DC; if it is not the case, follow instructions in quick guides and complete the
configuration for both resources.
Two ZIP files are attached to this guide with the two resources; you can also create a new DOCCM application
and import the two files.
1 Get access to the project and open the application.
2 Create a new Proofing resource named PR.
3 Enable the resource also using PR as name.

Enabled resources
Available resources

Extending the DC Resource

As already said the proofing application in the end creates one clickable link for each file generated. To create
correctly the links the list of generated files is needed; DC is responsible for creating the index that tracks the files
generated.

1 Open the DC resource.
2 Open the Output tab.
3 Open the PRINT configuration under File and metadata.
4 Open the Spool sets setti ngs tab.
5 Expand the Spool set i ndexes.

Note: There may be other indexes already present under Spool set indexes.

7 Insert DOCUMENTLIST in the Code field.
8 Select in a separate file.
9 Click New.

10 Click on Attributes management to create a new attribute.
11 Click on String button.
12 Insert DOCUMENTLIST_FILE in Code field.
13 Insert 20 in Length field.
14 Insert proofing_doclist.xml in Text val ue box.
15 Click on Close to save and close.
16 Drag and drop the DOCUMENTLIST_FILE attribute just created in File name field.

17 Select the DOCUMENTLIST index.

19 Select print job start from Type menu.
20 Click New.
21 Click on New record for the selected event.
22 Insert Header in the Name field.
23 Click on Constant button to add a new line.
24 Insert <?xml version=" 1.0" encoding=" ISO8859-1" standalone=" no" ?>.
25 Add another constant.
26 Insert <doclist timestamp=" .
27 Drag and drop Process-start timestamp from System attributes.
28 Add another constant.
29 Insert " > .

30 Add a new record named Body.
31 Create a new string attribute named DOCUMENTLIST_BODY.
32 Set Length to 500.
33 In the Assignment tree select the function button.
34 Select the concatenate Operator.
35 Add a Constant.
36 Insert
<doc nprog=" 1" k1=" " k2=" " k3=" " k4=" " k5=" " k6=" " k7=" " k8=" " k9=" " k10=" " k11="" k12=" "
k13=" " k14=" " k15=" " k16=" " k17="" k18=" " k19=" " k20=" " pdf="
37 Drag and drop the attribute PRINT_FILE_NAME.
38 Add a Constant.
39 Insert " /> .


40 Click on Close to save and exit.

Note: K fields can be customized for special needs but are not used in this guide.

41 Drag and drop the DOCUMENTLIST_BODY attribute in the Body record.

42 Add a record named Tail.

43 Insert a Constant.
44 Insert </doclist> .

45 Close DC.

Designing a Proofing Application

1 Open the PR resource.

Save
Validate
Properties


Your work is not saved unless you explicitly click on Save button.

2 Click on the link Click here to engage the first service.

A new service column is added.

3 Click on Click to select Service.

A menu with all different types of services is displayed.

4 Select Proofing.

A new Proofing service is added.

5 Move the mouse on the Proofing service.

A green plus icon is displayed.

6 Click on the plus icon.

A new menu with all different task types is displayed.

7 Select Unpack.

A new Unpack task is added.

8 Click on the task just created.

The column on the right shows the task properties.

9 Insert UnpackTask in Task Label.
10 Click on Add Input.


11 Select BOM from the Input drop down menu.
12 Click Apply.

The new input is displayed in the properties column.

13 Select the Configuration tab.
14 Insert r in the Switches field.

The option inserted in the Switches field is passed to the unpack task while inflating the input file.


15 Move the mouse near the right edge of the service column.

A vertical line is displayed.

16 Click on the triangle on the top to add a new service.


Add a new Data Transformation & Enrichment service.
Add a new Formatter task.
Name the Formatter task DTTask.

The two tasks are automatically connected.
To disable this behavior uncheck the Auto-Connect check box.

17 Insert DT in the Resource field.


Resource names must match the labels defined in the Application defi niti on box in
Platform and Collaboration.

19 From the Input menu select UnpackTask.

20 Click Apply.

Resource names



22 Click on Add Reader.

The name inserted here must match the name of the reader defined in the Data
Transformation resource.
For any doubts open the resource DT and verify names used.
The image shows the pipeline defined before.

23 Insert CSVReader in Name field.
24 Select UnpackTask-null from Input data bi nd menu.
25 Select UTF-8 from Encoding menu.
26 Select LF+CR from Line Separator menu.
27 Click Apply.


28 Click on Add Writer.
29 Insert XMLWriter in the Name field.
31 Select Generate a si ngle output with name.
32 Insert dtout.xml in the input field.
33 Click Apply.

Add a new Document Composition service.
Add a Spooling task with Task Label DCTask,.

Insert DC in Resource and select DTTask as Inputs.

35 Insert DEFAULT in the Target field.

The name inserted must match the Target defined in DC resource.
For any doubts open the DC resource.

36 Select PDF, PDF A-1b in the Output spool format menu.
37 Select Duplex in the Duplex menu.
38 Insert DEFAULT in the Serializer field.
39 Insert PRINT in the File Management Profile.


The DCTask configuration must match the Output configuration in DC resource.

40 Click on Validate icon.

41 Click Ok.
42 Save
Output configuration in DC resource Proofing Spooling Configuration


Two configuration files, doxee.mf and appSettings.xml, are needed to install a Proofing application. The two files
are packaged in a ZIP file and inserted in the application. A ZIP file named appSettings.zip with the two files is
attached to this guide.

Additional Configuration Files

Doxee.mf content is used to tell the system that the package contains configuration files and is just one line:

deploy.target=config

The actual configuration is in appSettings.xml:

<?xml version="1.0" encoding="UTF-8"?>
<appSettings description="PR appSettings" schemaVersion="1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance" >
<target>
<bpmSettings>
<proofing>
<jobType>
<batchLite dataType="ZIP">
</batchLite>
</jobType>
</proofing>
</bpmSettings>
</target>
<config>
<notifications>
<notificationEvent eventType="genericError">
<mailingList locale="it">no-reply@doxee.com</mailingList>
</notificationEvent>
</notifications>
</config>
</appSettings>

1 Open the application as usual.
2 Expand the New menu.
3 Click on New Resource
4 Insert SETTINGS in the Name field.
5 Select Proofing from Software service menu.
6 Select Content upload.

7 Check Upload now.
8 Click on Browse and select the appSetti ngs.zip file.

9 Click Apply.
10 Enable the SETTINGS resource with the same name.

Creating an Environment

1 Click on the System settings icon in the home screen.
2 Expand the Platform & Collaboration menu.
3 Click on the Environment And Plans.
4 Click on New environment
5 Select the application just created.
6 Insert BlueBank-Proofing-Enviroment in the Name field.
7 Select Test in the Scope menu.
8 Check Allow versions to be created and restored.
9 Insert 0 in the Retai ns at least field.

10 Drag and drop the groups that can use the environment in Authorized groups box.
11 Click Apply.

The new environment is created.


1 Go back to home screen.
2 Click on Validate button.
3 Open the environment BlueBank-Proofing-Enviroment just created.
4 Expand the New menu.
5 Click on New version

6 Insert Version1 in Name field.

7 Click Apply.
8 Select the version just created.

9 Click on Install

10 Click on Apply.

The new version is installed.

Running the Application

1 Click on the Run button in the home screen.
2 Click on the green tick button in the Proofi ng column.


3 Click on the name of the environment created.

4 Click on New job
5 Insert Test Job in the Description fiel d.
6 Click on Select

Please notice that the input file used here is the same file used for DT resource that
has been zipped.
The input file will be read by the DT resource and transformed in an XML file than
read by DC resource that produces the final PDF.

7 Select the data-transformation-i nput.zip file attached to this guide.


8 Click Apply.

A new job is created; the input file is read and used to create the PDF document.

9 Click on the refresh button to check if the job has been completed.

10 Click on the Documents link to open the document view and download the PDF.

Batch Production 8

This guide takes for granted that you completed the configuration of Proofing.

The Batch Production (BP in short) is the final stage in which the production of large volumes of documents is
automated.
The BP is quite complex and different modules work together to elaborate and manage this phase.
BP is composed by 4 components:
In-Bound.
PS UI.
BPM Service (Business Process Management).
Grid Service.

The In-Bound Service acquires the files sent by the client.
The In-Bound component is actually composed by two pieces working together. The In-Bound Watcher polls
sources (local folders, FTPs or others) for new input files sent by clients. The In-Bound Watcher then passes the
files to the In-Bound Service that creates a BOM (Bill Of Material), that is a structure composed by an index (an
XML file with the list of attached files) and one or more files that will be processed. Attached files are mapped in
the BOM index file to work packages (WP) and work units (WU).
Work packages and work units influence the number of jobs that will be created to generate documents.
The PS UI module reads the BOM index file and creates a new job for each work package (WP) present in the
BOM; on the contrary all work units present in work units are aggregated and elaborated by the same job. The PS
UI provides also a graphical interface that lets the user interact with the system.
The BPM module takes care of new jobs created by PS UI and creates processes.
The Grid Service module splits the processes in many tasks that are then ran on a distributed environment.



Import and enable the DT resource with name DT that comes with this guide.
Open the resource and run a build to verify that the resource is complete and completely functional.

Import and enable the DC resource with name DC that comes with this guide.
Open the resource and validate, publish and approve all contents.

Designing a Batch Production Application for Printing

1 Create a new Batch Production resource named BP.
2 Open the BP resource.

Your work is not saved unless you explicitly ask to.
Remember to click on the save button from time to time.

3 Click on the link Click here to engage the first service.
Save
Validate
Properties column



4 Click on Click to select Service.

A menu with all different types of services is displayed.

5 Select Batch Producti on.

A new Batch Production service is added.

6 Move the mouse on the Batch Production service.

A green plus sign is displayed.

7 Click on the plus sign.

A new menu with all different task types is displayed.

8 Select Unpack.

A new Unpack task is added.

9 Click on the task just created.

The properties column on the right shows the task properties.

10 Insert UnpackTask in Task Label.


12 Select BOM from the Input drop down menu.
13 Click Apply.

Please notice that r is mandatory. The application wont be installed if this option is
not well configured.

15 Insert r in Switches field.
16 Move the mouse near the right edge of the service column.

A vertical line is displayed.

17 Click on the triangle on the top to add a new service.


Add a new Data Transformation & Enrichment service.
Click on the plus icon to add a new Formatter task.


The two tasks are automatically connected.
To disable this behavior uncheck the Auto-Connect check box.

18 Change the Task Label to DTTask.
19 Insert DT in the Resource field.

The Data Transformation resource must be enabled; code must match the label
inserted in the Resource field.
Verify the resource code in the Resource catalog.

If the BP resource is enabled it has a green dot next to it.
In this case resource names and resource codes are the same.

21 From the Input menu select UnpackTask.

22 Click Apply.


24 Click on Add Reader.

The name inserted here must match the name of the reader defined in the pipeline in
Data Transformation.
The Data Transformation resource has been defined in DOCCM Quick Guide, for any
doubts refer to the guide.
The image shows the pipeline defined in the resource.

25 Insert CSVReader in the Name field.
26 Select UnpackTask-null from Input data bi nd menu.
28 Select LF+CR from Line Separator menu.

29 Click Apply.

30 Click on Add Writer.
31 Insert XMLWriter in the Name field.
33 Select Generate a si ngle output with name.
34 Insert PRINT.XML in the input field.
35 Click Apply.

PAGING task is mandatory only if you have a Staging and Aggregation task in your
Batch Production resource.
It is not used in this guide.

Add a Document Composition Service.
Add a Spooling task. Insert DCTask in Task Label field and DC in Resource.

37 Select DTTask from the Input menu.
38 Click Apply.

The names used in Target, Serializer and Overprint profiles must match the
names used in the Output configuration in DC resource.
For any doubt check your DC resource.

40 Insert DEFAULT in the Target field.
41 Select PDF, PDF A-1b from Output spool format menu.
42 Select Duplex from the Duplex menu.
43 Insert DEFAULT in the Serializer field.
44 Insert PRINT in the File Management Profile field.
45 Click Add Overpri nt.
46 Insert PRINT in the Overprint field.

47 Click Apply.

Add a Batch Production service.
Add a Packaging task and insert PackagingTask in the Task Label.

49 Select DCTask from Input menu.
50 Check Only Data matched by the followi ng expression.


Please note that the regular expression inserted at this stage is always the same.
This is a peculiar configuration that deliberately excludes all files, it is deliberately
meant to never match.
The service works despite the regular expression because the input is actually being
defined in the package configuration.

51 Insert . (a dot).

52 Click Apply.
53 Select Configuration tab.
54 Click Add Package.
55 Insert PrintPackage in the Package Identifier field.

The value inserted in the Deli very End Poi nt field must match Multichannel
Distribution configuration.
Please check your configuration and refer to Multichannel Distribution Quick Guide
for any doubts.

56 Insert ftp/PROVIDER_PRINT/PRINT in the Delivery End Point field.
57 Click on Add file link to add a file to the output package.

A new file is added and the tree is updated.

58 Click on the new file just added.
59 Select DCTask from the Source Task menu on the right.
60 Check Only data matched by the followi ng expression.
61 Insert *.lotxml.

62 Select Archi ves tab.
63 Click on Add Archi ve to add a ZIP file to the output package.

A tree with the ZIP structure is displayed.

64 Click on Add File to add a new file to the ZIP package.
65 Select DCTask from Source Task menu.
66 Insert *.pdf in Pattern field.

67 Click Apply.

Add a new Batch Producti on service.
Insert a new Delivery task and insert DeliveryTask in the Task Label.

Delivery tasks are configured in the Multichannel Distributi on configuration in
System settings.
Please check your configuration.

68 Save.

The Batch Production for printing file is now complete.


Create a new Batch Production resource named BP-SET and upload the appSettings.zip that comes with
this guide.

Please check the Proofing Quick Guide for more information on how appSettings
works and why it is needed.

The appSettings.zip contains two files as always:
doxee.mf
appSettings.xml
The first file just identifies the package as a configuration package; the actual configuration is in appSettings.xml.
File content should be:

<appSettings description="BlueBank Batch Production" schemaVersion="1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
<target>
<bpmSettings taskLocalStorageCleanup="true">
<batch enableTrackingReporting="false">
<jobType>
<batchHeavy sourceRefId="BlueBankBP">
<schedulingPolicy>
<automatic profile="1"></automatic>
</schedulingPolicy>
</batchHeavy>
</jobType>
</batch>
</bpmSettings>

</target>
<config>
<notifications>
<notificationEvent eventType="genericError">
<mailingList locale="it">no-reply@doxee.com</mailingList>
</notificationEvent>
</notifications>
</config>
</appSettings>

The value in sourceRefId must match the value inserted in the Tag field in the In-
Bound configuration explained later in this guide.

Enable BP resource with name BP and BP-SET with BP-SET.

Create a new test environment named BlueBankBPEnv that allows creating new version and retains 0
versions; enable group as well.

Create a new version of the application with name Ver1 in the environment just created and install it.

Configuring In-Bound

The configuration of the In-Bound Service and Watcher requires direct access to the
servers where they run and to the Database.
An error in the configuration may lead to an unstable and potentially corrupted
system.
Ask the instructor for credentials.

In-Bound Watcher polls a source, such as a local folder or a remote FTP site. Different clients can upload file in a
different relative path in the same source, effectively sharing it.
Each Client has one or more accounts; each account is connected to exactly one source.
One or more In-Bound rules are defined for each account. A rule contains one or more regular expressions that
match input files in the source.
Database tables used to specify sources, accounts and rules are:
PS_INBOUND_SOURCE
PS_INBOUND_ACCOUNT
PS_INBOUND_RULE

Configuring a Source

Tuple Description Tuple
ID_SOURCE Primary key. Number
CODE Source name. String
WATCHER_BEAN_ID Source type.
FtpXfer (simple FTP)
SFtp (FTP tunneled through ssh)
LocalFolder
String
LAST_MODIFICATION_DATE Date of the last modification of the source. It triggers
configuration update on Watcher.
Date
PROPS Source properties*. String
WATCHER_NAME Name of the In-Bound Watcher as specified in the
Watcher configuration file.
String

PROPS strictly follows this representation:
{key1: value1, key2: value2}

Keys and values are specific for a source type:

Source Type Key Value Description Optional
FtpXfer
SFtp
serviceRootDir* Path Base path accessible by In-Bound
Service.

watcherRootDir* Path Base path accessible by In-Bound
Watcher.

duplicatedAllowed true or false If false, duplicated files are ignored. Yes
logRootDir Path Path to FTP log file.
filenamePattern Regular expression Filename Pattern
filenameGzPattern Regular expression Filename Pattern Yes
Interval Milliseconds Polling interval
LocalFolder
serviceRootDir* Path Base path accessible by In-Bound
Service.

watcherRootDir* Path Base path accessible by In-Bound
Watcher.

duplicatedAllowed true or false If false, duplicated files are ignored. Yes
Interval Milliseconds Polling interval

*In-Bound Service and Watcher may run on different servers; the Watcher may, for example, run on a server in
DMZ exposed to the Internet while the Service may run in the internal network. The two servers may mount the
root dir on different paths and thats why the two keys are needed.

The configuration presented in this guide takes for granted that In-Bound Watcher
and Service are running on the same server.

1 Connect to the server.
2 Create a folder named bluebank1 that will be used as root dir for In-Bound Watcher and Service.
Ask instructor for details about path and privileges.
3 Connect to the database with the tool suggested by the instructor.
4 Look for table PS_INBOUND_SOURCE.
Note that other sources may be already present.
5 Insert the smallest number not used yet in ID_SOURCE field.
6 Write down the number inserted.
7 Insert BlueBank1LocalFolder in CODE field.
8 Insert LocalFolder in WATCHER_BEAN_ID field.
9 Insert the present date in LAST_MODIFICATION_DATE field.
10 In PROPS field insert:
{serviceRootDir: '/opt/ftp_root_dir', watcherRootDir: '/opt/ftp_root_dir', interval: '5000',
duplicatedAllowed: 'true'}

The name of the watcher may vary, please check with instructor.

11 Insert inbound-watcher-1 in WATCHER_NAME field.
12 Set the present date and time in LAST_MODIFICATION_DATE field.
13 Commit modifications.

Configuring an Account

ID_ACCOUNT Primary key. Number
CODE Identifies the path under the root dir. String
ID_SOURCE Foreign key to the source configured. Number
CLIENT_DN Client name. String
ENABLED 1 if enabled; 0 if disabled. Number
LAST_MODIFICATION_DATE Modification date, it triggers Watcher update. Date
PROPS Account properties. String

CODE has a different meaning depending on source type:
If the source is a local folder, CODE is the name of the folder under the root dir where files are saved.
If the source is an FTP, CODE is the name of an FTP user and is used to filter the FTP log file and
monitor incoming files.

PROPS:

Key Value Description Optional
acccountLevel Number Descend at most this number of
levels of directories below the root
dir.

1 Connect to the database.
2 Look for table PS_INBOUND_ACCOUNT.
3 Insert the smallest number that have not been used yet in ID_ACCOUNT field.
4 Write down the number inserted.
5 Insert bluebank1 in CODE field.
6 Insert the number just inserted in ID_SOURCE field while configuring the PS_INBOUND_SOURCE table.
7 Insert Bl ueBank in CLIENT_DN field.
Note: the name must match the name of your client.
8 Insert 1 in ENABLED field.
9 Insert present date in LAST_MODIFICATION_DATE field.
10 Insert {accountLevel: '0'} in PROPS field.
11 Commit changes.

Configuring a Rule

ID_RULE Primary key. Number
ID_ACCOUNT Foreign key to the account just configured. Number
APP_KEY Name of the Batch Production application linked to
this In-Bound configuration.
String
RULE_TYPE BOMFileExist if the client directly sends BOM files,
BOMFilePattern if sends unpackaged files.
String
BOM_RULE XML code used to create a BOM from input files. String
ENABLED 1 if enabled; 0 if disabled. Number
USE_CASE Use case name, always batch in this case. String
TEST 0 if uses a production environment; 1 if it uses a test
environment
String

The BOM rule is XML code that must follow this structure:

Example of a BOM rule:

<?xml version=1.0 encoding=UTF-8?>
<inbound-rule xmlns=http://www.doxee.com/ps/inbound/rule
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
xsi:schemaLocation=http://www.doxee.com/ps/inbound/rule inbound-rule.xsd >
<file-pattern-rule>
<condition card-max=1 card-min=1 filepath-regexp=.*\.txt />
</file-pattern-rule>
</inbound-rule>

In this case when the In-Bound watcher finds a file with extension .txt in the configured folder waits 90 seconds
and then moves it in .loaded folder and creates the BOM; if the file has been modified during the last 90 seconds,
the Watcher resets the timer and checks the file after 90 seconds and so on.

1 Open PS_INBOUND_RULE table.
2 Insert the smallest number not used yet in ID_RULE.
3 Insert the number insert in ID_ACCOUNT in PS_INBOUND_ACCOUNT table.
4 Insert BlueBankBP in APP_KEY field.
This value must match the one inserted in sourceRefId in appSettings.xml.
5 Insert BOMFilePattern in RULE_TYPE, in this way a new BOM will be created automatically by the
system.
6 In BOM_RULE insert:
<?xml version=" 1.0" encoding=" UTF-8" ?>
<inbound-rule xmlns=http://www.doxee.com/ps/inbound/rule
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
xsi:schemaLocation=" http://www.doxee.com/ps/inbound/rule inbound-rule.xsd " >
<file-pattern-rule>
<condition card-max=" 1" card-min=" 1" filepath-regexp=" .*\.zip" />
</file-pattern-rule>
</inbound-rule>
7 Insert 1 in ENABLED.
8 Insert batch in USE_CASE.
9 Insert 1 in TEST.
10 Commit changes.

Testing

Verify with instructor how to get access to input folder and privileges.

1 Copy the ZIP file attached to this guide test.zip in the input folder /opt/ftp_root_dir/bluebank1.
2 Go back to home screen.
3 Click on Run.
4 Click on Batch Production button.
5 After a couple of minutes a new job will appear.

6 Select Jobs in PRODUCTION CONSOLE menu.

7 Click on Id link to see the job report

Extending the Application for Email

The procedure to create a Batch Production process to send email is quite similar to the one already seen for
printing files.
The process just created is going to be extended with email management.
It is necessary to update Data Transformation and Batch Production resources.

Extending DT Resource

1 Get access to the Data Transformation resource DT as usual.
2 Click on XMLWriter element name to edit the writer configuration.

3 Select DOCUMENT element.

4 Select When the foll owi ng conditi ons are met radio button from Incl ude output menu.

A new configuration panel is displayed.

5 Click on the green plus sign to add a new filter condition.

6 Move the mouse over the var row.

A key icon is displayed in Path field.


7 Click on the key icon to select the element or attribute to filter data.

8 Select FILE > DOCUMENT > PROFILE > customerType.

A key icon is displayed next to the attribute.

9 Click on the key icon to select the attribute.
10 Click on Apply.

11 Select = from drop down menu in Operator column.
12 Insert Corporate in Value column.

13 Click on the green tick icon to validate the rule.

14 Click on Ok button.
15 Save and close XMLWriter configuration panel.

Add a new writer named EmailWriter in the working area.
Connect the writer to DataMapper.


Open the EmailWriter.
Add a new filter on DOCUMENT as already seen but this time insert Retail in Val ue column.
Validate the rule and save your work.

16 Go back to home screen
17 Click on Test link.
18 Select EmailWriter in Writers box.
19 Check Use a specific file name pattern.
20 Insert EMAIL.XML.


Start a preview and view outcome.

Use the Output menu to view output from PRINT.XML and EMAIL.XML files.

Save and create a build.

Extending BP Resource

1 Get access to the BP resource as already seen.
2 Select DTTask.

Add a new writer named EmailWriter that generates a single output file with name EMAIL.XML.

3 Select DCTask.
4 Modify the Input so that reads only data matching PRINT.XML.
5 Select the Document Composition service column.
6 Add a new service named DCTaskEmail.

Select DCTaskEmail and set DTTask as input.
It must read only data matching EMAIL.XML.
Select Configuration tab and insert DEFAULT in Target, select PDF, PDF A-1b and Duplex,
insert DEFAULT in Serializer and EMAIL in File Management Profile.
Overprint is not used in this case.


Add a new packaging task named PackagingTaskEmail.
Connect DCTaskEmail to PackagingTaskEmail.
Set DCTaskEmail as PackagingTaskEmail input.

7 Select PackagingTaskEmail.
8 Select Configuration tab.
9 Click on Add Package.
10 Insert MailPackage in Package Identifier field.
11 Insert ftp/PROVIDER_MAIL/MAILER in Deli very End Point field.
12 Add a file to the package.
13 Select DCTaskEmail from Source Task.
14 Check Only data matched by the followi ng expression.
15 Insert *.pdf.
16 Click Apply.
17 Connect PackagingTaskEmail to DeliveryTask.


Installing the New Version

Uninstall Ver1.

Create a new version named Ver2 and installed it.

Test as already seen.


Digital Archiving 9
Digital Archiving (DA in short) is used to store documents in a reliable way for later view.
Documents are saved in folders on the file system and can then be extracted.

Please notice that documents stored with Digital Archiving are not signed and DA
does not ensure legal soundness.

In order to have a working example a Batch Production application (with a Digital Archiving task) and a Digital
Archiving application are needed.
A DA application is quite unusual as it doesnt contain any resources; the configuration is made on the
environment that contains the application.
The DA task inside the Batch Production application is bound to the configuration of the DA environment through
the Digital Archiving Authorization Tag.


Configuring the File System

To configure DA at least one folder is needed to store documents.
If the resend function is enabled, a second folder is needed to store packages ready to be resent.
Verify with the Instructor how to create folders on the server.
In this guide the folder /opt/doxee/digital_archi vi ng/repository is used.

Creating a Batch Production Application for Digital Archiving

This guide takes for granted that you read the Batch Production Quick Guide.

A Batch Production application, configured accordingly, is needed in order to use Digital Archiving.


DA and BP resources must be in the same procedure.

Create a new resource Batch Production name BP-DA-SET and import the appSetti ngs-DA.zip
package.
Create a new Batch Production resource named BP-DA.

1 Open the resource BP-DA.
2 Add a new Service column.
3 Add a Batch Production Service.
4 Add an Unpack task named UnpackTask.
5 Add BOM to the Inputs.
6 Add in the Switches r in Configuration panel as usual.
7 Add a Digital Archi ve Service.
8 Add a DA-Loader task named DATask.
9 Insert DA in Resource field.
10 Click on Add Input
11 Add UnpackTask to the Inputs.
12 Select Only Data Matched by the followi ng expression.

The use of the . for filtering input from another task has been already explained in
the Batch Production guide.

13 Insert a single dot . in the field.

14 Click Apply.

15 Insert DATaskTag in the Digital Archi vi ng Authorization Tag field.

16 Validate.
17 Save.

Installing the Batch Production Application

Create a new environment for the Batch Production application named BlueBankBP-DAEnv of Scope
Test, that allows new versions and that retains 0 versions; enable also the groups needed.
Open the Validate menu as usual and create a new version named Ver1 in the new environment with DT,
DC, BP-DA and BP-DA-SET.
Install the version.

Modifying the In-bound configuration

The In-Bound service has been configured in the Batch Production Quick Guide to use Bl ueBankBP application.

Have a look inside appSettings-DA.zip to see where the RefId, BlueBankBP-DA is
defined.

It is now necessary to modify this configuration in order to use the new application BlueBankBP-DA.

1 Connect to the data base.
2 Open the PS_INBOUND_RULE table.
3 Modify the value in the APP_KEY column, from BlueBankBP to BlueBankBP-DA.
4 Commit changes.

Designing a Digital Archiving Application

Creating a Digital Archiving Application and Environment

Create a new Digital Archiving application named DA, as already seen for other applications, in the same
procedure where the BP-DA resource is.

An environment is needed to configure correctly

1 Open System settings.
2 Click on Environment and Plans.
4 Expand the Bl ueBank tree.
5 Select the Digital Archi vi ng sub-tree.
6 Select the DA application just created.
7 Click on Select.

8 Insert BlueBankDAEnv in the Name field.
9 Select Test in Scope menu.
10 Check Allow versions to be created and restored.
11 Insert 0 in Retai n at least version field.
12 Authorize needed groups.

13 Click Apply.

The new environment is created and is now available in Di gital Archi vi ng menu in System settings.

Configuring Document Classes

A document class is just a type of document that will be archived using DA.
For each document class are defined some indexing values that will be used to search files.
Configured indexes are populated during the loading phase using an XML file.

1 Open the Digital Archi vi ng menu in System settings.

2 Click on the name of environment created, BlueBankDAEnv.
The Document Classes configuration interface is displayed.


3 In the Document storage location field insert /opt/doxee/digital_archiving/repository.
4 Click on the green plus icon to add a new Document Class.

A new pop-up window is displayed.

5 Insert Invoice in the Name field.
6 Click Apply.

A new column Invoice is added.

Document Class Authorized Client/Group


Click on a class name to edit it.

7 Enable BlueBanks group.
8 Click on More Groups link to authorize more group to use this class.

9 Select the group you want to authorize and drag and drop it in the box on the right.
10 Click Apply.

A new row is added to column Invoice.

11 Select the checkbox to enable groups to see Invoice class in the Run menu.
13 Open the home screen again.
14 Select the Run menu.
15 Select Digital Archi vi ng

16 Click on Bl ueBankDAEnv.

N.B.: Since there are no searchable indexes defined, theres nothing to search.

Open the Document Classes configuration interface again.

17 Click on DATE_1.



18 Select Searchable checkbox.
19 Click Apply to close the window.

Open Digital Archi vi ng in the Run menu again and select BlueBankDAEnv.

The DATE_1 field is now displayed.

Open the Document Classes configuration interface again.

21 Click on DATE_1 link to edit the index.
22 Insert ISSUE_DATE in Code field.
23 Insert Issue Date in Label field.
24 Select between from Operator menu.
25 Select Searchable checkbox to allow searching on this index in the Run menu.
26 Select View in Detail checkbox to enable the panel Detail in Run menu.
27 Select View in tables of results checkbox to display the index column in Results table.

28 Click Apply.

29 Click on the red cross icon to remove all other indexes.

30 Click on More indexes link.


31 Select STRING_1.
32 Select NUMBER_1.
33 Click Apply.

Two new indexes, STRING_1 and NUMBER_1, are added.

34 Select all checkboxes to enable the indexes created.
35 Click on STRING_1 to edit it.
36 Insert TITLE in Code field.
37 Insert Title in Label field.
38 Select like in Operator menu.
39 Select Searchable.
40 Select View in Detail.
41 Select View in tables of results.
43 Click on NUMBER_1 to edit it.
44 Insert CONTRACT_NUMBER in Code field.
45 Insert Contract Number in Label field.
46 Select = in Operator menu.
47 Select Searchable.
48 Select View in Detail.
49 Select View in tables of results.


Documents stored using DA can then be extracted one at the time using the web
interface or using a CSV file.
Csv field order enables the use of the index in the CSV file and assigns to it a
specific a position in the file.
This option is not used in this guide.

Configuring Authorization

The Authorization configuration links the DA task inside the Batch Production application to the DA configuration
just created.
In particular the value in the column Tag must match the name of the task in the Batch Production application.

1 Click on Authorization tab.

The configuration of DA application may seem quite counterintuitive.
Just remember that you are binding environments together.

2 Click on Add Authorization button.

Client
Environment
t
Environment
t
Application
Application
Procedure


3 In Select DA Environment box select the environment BlueBankDAEnv.
4 In Select Production Environment box select the BlueBankBP-DAEnv environment.
5 In the Name field insert DATaskTag.

The name used here must match the name of the tag used for the DA task in the
Batch Production application.

Save, exit and go back to Digital Archive configuration in System settings.

Tag

The authorization is created.

Archiving Documents

Verify with instructor what is the input folder of BlueBankBP-DA

Copy the file test.zip attached to this guide in /opt/ftp/bl uebank1.
As already seen in Batch Production Quick Guide, open the Batch Production interface under Run menu.
Verify that the job completed correctly.
Verify that the files have been stored under /opt/doxee/digital_archiving/repository.

Extracting Documents

There are two ways to extract document archived:
Search form.
CSV extraction document.

Extracting a Document through Search Form

1 Open the Run menu.
2 Open the environment BlueBankDAEnv.
3 Select the document classes that will be searched.


Fields in Search Parameters area are updated based on the document classes enabled.
Fields of all document classes enabled are displayed.

4 Fill in the form with search terms.
5 Click Search to start searching.

Results table is populated.

6 Move the mouse over the document you want to download.
7 Click on the arrow icon to download it.
8 Click on Downl oad All link to download all documents returned by search.

Extracting a Document with Extraction Document

Open the Run menu, select the environment and then enable document classes.

1 Click on Extraction document button.


2 Click on browse button.
3 Select the CSV file.
4 Click Apply.

Results table is populated.

5 Download documents.


Tracking & Reporting 10
Creating a New Tracking & Reporting Application

Get access to the platform as usual.

8 Click on System settings icon.
9 Click on Procedures.
10 Click on Bl ueBank procedure.
11 Click on App. tab.

12 Click on New application link application under Tracki ng & Reporting frame.
13 Insert Statement Tracking in Name field.
14 Expand the Bl ueBank group in Available groups list.
15 Expand Default.
16 Drag and drop Client Systems into Selected groups on the right.

17 Click on Apply.

The application is added to the Tracking & Reporting applications.


18 Click Apply.

The new application is created.

19 Click on Environment & Plans.
20 Click on Environments.


22 Expand Bl ueBank, Statement and Tracki ng & Reporting.
23 Select Statement Tracking.
24 Click Select.
25 Fill in the Name field with TR.
26 Expand Bl ueBank.
27 Drag and drop Client Systems into Authorized groups box on the right.


28 Click Apply.

The environment is created.

Configuring Catalogs

2 Click on Tracki ng & Reporting.
3 Click on CATALOGS.
4 Click on Provider.

The list of configured providers is displayed.


5 Click on New Provider.
6 Type EBI in the Code field.
7 Type DOXEE in the Name field.

A new provider is created.


Create a new provider:
Code: POS
Name: Poste Italiane
Code: PST
Name: Postel
Code: TNT
Name: TNT
Code: ND
Name: Not defined

8 Click on Media Format.
9 Click on New Format.

A new row is added to the format list.

10 Click on Code cell to edit the cell content.
11 Insert 01.
12 Click on an empty area to confirm the value inserted.
13 In the Short Description cell insert AFPDS.
14 In the Long Description cell insert Paper Media.

Insert a new Media Format:
Code: 02.
Short Description: PDF.
Long Description: PDF Format.

Configuring SLA Rules

2 Click on Tracki ng & Reporting.
3 Click on SLA RULES.
4 Click on New rule.

A new rule is added.

5 Click on rule name to edit it.

Rule properties are displayed.


Its possible to use any name for rules but it is a best practice to use a name that
reflects the rule validity time.

A comprehensive rule is:
Progressive id Start day End day s: deadline dda: the SLA starts after these
number of days ddh: the SLA starts after these number of hours.

For example: 1-Mon-Fri s: 20 dda:1
Is the first rule.
It is valid from Monday to Friday.
The deadline is 20:00 (8 pm). Anything received after 20:00 is not
considered to be in the SLA of the day.
SLA calculation starts from 00:00 (12 am) of the next day.

6 In the name field insert 1-Mon-Fri s:20 dda:1
7 Select Monday in Start Day drop down menu.
8 Select Friday in End Day drop down menu.
9 Insert 12:00 in From hour field.
10 Select AM.
11 Insert 08:00 in To.
12 Select PM.
13 Insert 12:00 in Start time when acquisition is time over threshold of the next worki ng day.
14 Select AM.


Insert a new SLA rule
Name: 2-Mon-Fri s:14 dda:1
Start Day: Monday
End Day: Friday
From hour: 12:00 AM
To: 02:00 PM
Start time when acquisition is time over threshold of the next working day: 12:00 AM
Insert a new SLA rule
Name: 3-Mon-Sat s:0 dda:0
Start Day: Monday
End Day: Saturday
From hour: 12:00 AM
To: 11:59 PM
Start time when acquisition is time over threshold of the next working day: 12:00 AM

Creating a Monitoring Line

Go back to Design and get access to the Tracking & Reporting application as usual.


No Resources are defined at the moment. Create and enable a new resource as already seen in
former chapter; fill in the Name field with TR and select Tracking & Reporti ng as Software service.

You cannot save your work until:
A tracking line is complete with at least one delivery phase.
All processing phases belong to a contract.
Do not close the browser or push the back button.

1 Open the TR resource.

Working area
Properties


In the working area there are 5 columns:
Production
Transfer
Validation
Print & Email
Delivery
You dont need to populate all columns to get a working line.
When you pass over one of the five areas a plus sign is shown.

2 Click on the plus sign in the Production area to add a new phase to the monitoring line.

A new phase is added.

3 Click on the new phase.

A blue glow is shown around the phase and the properties area is updated.
Phase name
Supplier/plant name


4 From Provider Code drop down menu select EBI|DOXEE.

The provider name is updated.

5 Set SLA counter to 2 days.

Delete phase


6 Click on plus sign in Transfer area

7 Select Spool file Transfer.
8 Click on the Production phase.
9 Drag and drop the circle in Production phase on the top left edge of Transfer phase.


The two phases are connected.

10 Select the transfer phase just selected.
11 From the Provider Code menu select EBI|DOXEE.
12 Set SLA counter to 2 days.
13 Select the production phase.
14 Keep pressed the [CONTROL] button.
15 Select also the transfer phase.

Both phases are selected.

Group phases and create a contract

16 Click on the grouping icon.

A new contract without definition is created and a new grey box that contains both phases is displayed.

17 Click on the contract to select it.

The properties area is updated.


18 Insert Production for Print and Mail in the Name field.
19 Select Doxee in the Provider menu.
20 Click on Start date calendar icon.
21 Select 2013/01/01.
22 Click on End date calendar icon and select 2016/01/01.

23 Select SLA tab.
24 From SLA calculation rule drop down menu select the second element Mon-Fri s:14 dda:1.


Add a validation phase of type Print Validation and connect the transfer phase to the new validation
one. Select TNT|TNT as provider and set SLA to 1.

Add a new Print & Mail phase and connect the validation phase to this one.
Select TNT|TNT from Provider Code and set SLA to 1 days.


Add a new delivery phase and connect the print & mail phase to this one.
Select Bulk Mail|01 from Delivery Product menu.
Select AFPDS|01 from Media Format menu.
Select TNT_TNT|TNT->TNT from the Distribution Channel Code menu.
Select TNT|TNT from Provider Code menu.
Set SLA to 5 days.


Group the Validation, Print & Mail and Delivery phases.
Insert Contract for Print & Mail in the Name field.
Select TNT from Provider menu.
Set Start date to 2013/01/01.
Set End date to 2016/01/01.
From SLA calculation rule menu the first entry: Mon-Fri s: 20 dda:1.

The first tracking line is now complete.

25 Click on the Save button.


26 Click Ok to save and overwrite the former configuration.

The window is automatically closed.

27 Open again the TR resource.
28 Add a new validation phase.


29 Connect the transfer phase to the new Validation phase.

A new branch is added and all phases are connected.

30 Select POS|Postel from Provider Code menu.
31 Set SLA to 1 days.

Add a new Print & Mail phase and connect the Postel validation phase to it.
Select POS|Postel from Provider Code.
Set SLA to 2 days.


Group the two phases just created.
Insert Contract for Print & Mail in Name field.
Select Postel from Provider menu.
From SLA calculation rule select the first entry.
Set Shipment SLA to Fi xed Val ue and 4 days.

Add a new delivery phase of type Postal Delivery and connect the Print & Mail phase to it..
From Delivery Product select Bulk Mail|01.
From Media Format select AFPDS|01.
From Distribution Channel Code select POS_PMA|POS->PMA.
From Provider Code select PMA|Poste Italiane.
Set SLA to 300 days.
Select From previous task in Task Start/End radio button box.


Group the phase just created.
Insert Delivery Contract in Name field.
Select Poste Italiane from Provider menu.
From SLA calculation rule select the second entry.
Set SLA Settings to Fi xed Val ue and 300 days.


Save and open the resource again.

Add a new production phase.
Select EBI|DOXEE from Provider Code.
Set SLA to 1 days.

Add a new transfer phase of type Spool/File Transfer.
Set SLA to 1 days.

Add a delivery phase of type Digital Archi vi ng.
From Delivery product select Digital Archi vi ng|02.
From Media Format select PDF|02.
From Distribution Channel Code select EBI_EBI|EBI->EBI.
From Provider Code select EBI|DOXEE.
Set SLA to 0 days.
From Task Start/End radio button box select From previous task.

Group all 3 phases.
Insert Producti on for Archi vi ng in Name field.
From Provider menu select DOXEE.
From SLA calculation rule select the third entry Mon-Sat s:0 dda:0.

Add a new production phase.
Set SLA to 1 days.

Add a new transfer phase of type Email Transfer.
Set SLA to 24 hours.

Add a delivery phase of type Email Delivery.
From Delivery product select Email|04.
From Media Format select PDF|02.
From Distribution Channel Code select EBI_EBI|EBI->EBI.
From Provider Code select EBI|DOXEE.
Set SLA to 48 hours.
From Task Start/End radio button box select From events.

Group all 3 phases.
Insert Producti on for Email in Name field.
From Provider menu select DOXEE.
From SLA calculation rule select the third entry Mon-Sat s:0 dda:0.

Save.

On-Demand Production 11
On-Demand Production (ODP in short) is used to retrieve or generate again documents on-demand.
To retrieve documents a REST web service is used.
An XML file is sent to the web service with all information needed to identify one document.
The web service returns just one document as a base64 string.

Before proceeding be sure to have completed the Digital Archive guide and to have a
working environment.


An external program is needed to contact the web service; in this guide SoapUI is used for all examples.
SoapUI is open source and java-based, so it works on Linux, Windows and Mac.
Actually any software that can connect to REST web services can be used, feel free to use the one you prefer.

The request sent to the web service contains base64 encoded strings; a tool to encode and decode base64 strings
is needed as well. On Linux you can use the command base64 but feel free to use the tool you prefer; many on-
line services also exist.

Designing an On-Demand Production Application

The design of an On-Demand Production application is composed by two steps:
Creation of the ODP application.
Creation of the authorization that links the DA environment and the ODP environment.

Creating an On-Demand Production Application and Environment

Create a new On-Demand Production application named ODP, as already seen for other applications.

1 Open the ODP application.

2 Add a new Service column, as already seen for Batch Production.
3 Select Digital Archi ve as service type.
4 Add a new Data Extraction task named DAExtTask.

5 Add an Input.
6 Select BOM.
7 Select the Configuration panel.
8 Insert DAExtTaskTag in Digital Archi vi ng Authorization Tag field.
The tag is used to identify the task as already seen for DA configuration.
Write down the name of the tag as it will be used later.

The next fields are used to identify tags and attributes in the XML file used to request a document.

Values inserted here must match with the input file and also with the DA
configuration, as seen in Digital Archive Quick Guide.


9 Select Document and metadata radio button in Extraction returns.
10 Insert QUERY in Query Element XPath. This is the tag name used in the XML file contains query
attributes.
11 Insert docClass in Document Category Attribute. The attribute docClass will contain the name of the
document class configured in the DA Quick Guide (that is Invoice).
12 Click on Add Query to map the attribute in the QUERY tag to the index defined for the document class.


13 Insert contractNumber in Attribute field.
14 Insert CONTRACT_NUMBER in Index Name field.
15 Select = from the Operator menu.

A new mapping between the attribute contractNumber in the XML input file and the index
CONTRACT_NUMBER defined in DA is created.

An attribute is added in the Query Attributes table.

16 Insert a new On Demand Production column.
17 Insert a Packagi ng task named PackagingTask.
18 Add DAExtTask as input.
19 Select Only Data matched by the foll owi ng expression.
20 Insert a dot . in the field below.
21 Click Apply.
22 Open the Configuration tab.
23 Add a package.
24 Insert ODPPack in Package Identifier field.
25 Select Direct Response.
26 Select Files and Directories tab.
27 Click on Add file link.
28 Click on the link file_1 just created.
29 Select DAExtTask from Source Task menu.
30 Select Only data matched by the followi ng expression.
31 Insert *.pdf in the field below.
32 Click Apply.
33 Validate.
34 Save.

Installing the On-Demand Production Application

Create a new On-Demand Production resource and upload the file ODP-SET.zip attached to this guide as
already seen for Batch Production and Digital Archive.

Create an environment BlueBankODPEnv with scope Test, that allows new version and that retains 0
versions. Enable groups as usually.

Install the application using resources ODP and ODP-SET.

Adding a New Authorization

The new ODP application has to be linked to the DA environment created in Digital Archiving Quick Guide.

2 Open Digital Archi vi ng.
3 Select Authorization tab.

4 Click on Add Authorization.
5 Select BlueBankDAEnv in Select DA Environment box.
6 Select BlueBankODPEnv in Select Production Environment box.
7 Insert DAExtTaskTag in Name field.
8 Click Apply.

The new authorization is added.

Extracting a Document

Creating a Request

An XML file is used to ask for a document. The content is base64 encoded and sent as a string to the web service.
The web service then returns a document also base64 encoded.
Following a file example:

<FILE>
<DOCUMENT>
<TEMPLATE name="default">
<QUERY contractNumber="1" docClass="Invoice" />
</TEMPLATE>
</DOCUMENT>
</FILE>

The first three tags FILE, DOCUMENT and TEMPLATE are mandatory.
The forth tag contains the actual query and can be customized; the tag used here is QUERY but can be changed
to any valid string. This tag must match with configuration as specified in Creating an On-Demand Production
Application chapter.
The research can be on any of the attributes defined for the specific document class but the query must always
return only one document. In this example only one attribute named contractNumber is used.
An attribute to identify the document class is mandatory but the name can be customized; in this example
docClass is used.
Personalize the input file to extract the document of interest. In this case the only variable that can be changed
is the number in contractNumber.

Encode the content. The result should something similar to:
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCjxGSUxFPg0KCTxET0NVTUVOVD4NCgk
JPFRFTVBMQVRFIG5hbWU9ImRlZmF1bHQiPg0KCQkJPFFVRVJZIGNvbXBhbnk9IkJsdWVCYW5rIiBjb250c
mFjdE51bWJlcj0iMSIgZG9jQ2xhc3M9Ikludm9pY2UiIC8+DQoJCTwvVEVNUExBVEU+DQoJPC9ET0NVTUV
OVD4NCjwvRklMRT4=

Actually a request requires also a BOM configuration.
Following an example:

<bom xmlns="http://www.doxee.com/ps/bom"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.doxee.com/ps/bom
http://www.doxee.com/ps/bom/bom.xsd"
creationDate="20131203" label="BOM_00001" name="BOM_00001" inceptionId="sss"
requestId="sss">
<material>
<workUnit creationDate="20130828" size="4882" name="test.xml" />
</material>
</bom>

The configuration must be present but is actually ignored in this scenario.

Encode the text. The result s should be something similar to:
PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCjxib20geG1sbnM9Imh0dHA6Ly93d3cuZG94Z
WUuY29tL3BzL2JvbSINCiAgICB4bWxuczp4c2k9Imh0dHA6Ly93d3cudzMub3JnLzIwMDEvWE1MU2NoZW1hLWl
uc3RhbmNlIg0KICAgIHhzaTpzY2hlbWFMb2NhdGlvbj0iaHR0cDovL3d3dy5kb3hlZS5jb20vcHMvYm9tIGh0dHA6Ly
93d3cuZG94ZWUuY29tL3BzL2JvbS9ib20ueHNkIg0KICAgIGNyZWF0aW9uRGF0ZT0iMjAxMzEyMDMiIGxhYmVs
PSJCT01fMDAwMDEiIG5hbWU9IkJPTV8wMDAwMSIgaW5jZXB0aW9uSWQ9InNzcyIgcmVxdWVzdElkPSJzc3Mi
Pg0KICAgIDxtYXRlcmlhbD4NCiAgICAgICAgPHdvcmtVbml0IGNyZWF0aW9uRGF0ZT0iMjAxMzA4MjgiIHNpemU
9IjQ4ODIiIG5hbWU9InRlc3QueG1sIiAvPg0KICAgIDwvbWF0ZXJpYWw+DQo8L2JvbT4=

Configuring SoapUI

1 Create a new REST Project.

2 Click on Import WADL


Please verify with instructor the address of the web service and of WADL file for your
environment. The placeholder <web_address> is used instead of the real address.

3 Insert http://<web_address>/ondemand-ws/test/application.wadl in Ini tial WADL.
4 Click OK.

A new project is created.

5 Open applicati on > applicati on > /{client} > POST getDocument > Request 1.
6 Set Method to POST.
7 Insert http://<web_address> in Endpoi nt field.

A strange behavior of SoapUI has been noticed on Windows; the Resource field may
be wrongly refreshed and the string ondeman-ws/test// appended many time.
If Resource field shows multiple times ondeman-ws/test, try deleting the complete
string and insert {client}/{procedure}/{application}/{environment} instead.

8 Insert /ondemand-ws/test/{client}/{procedure}/{application}/{environment} in Resource field.
9 Select Request tab.

10 Insert ODP%20QuickGuide for application.

11 Insert BlueBankODPEnv for environment.
12 Insert BlueBank for client.
13 Insert BlueBank for procedure.
14 Click on Adds a parameter to the parameter table icon.

A new row is added.

15 Insert dataXml as name.
16 Insert the first base64 string create with the query in the Creating a Request paragraph.
17 Add another row.
18 Insert bomXml as name.
19 Insert the second base64 string created for BOM configuration in the Creating a Request paragraph.
20 Select Post QueryStri checkbox in the Media Type box.
21 Click on the play button to run the query.

A long string containing also the document encoded in base64 is returned.

Extract the base64 string inside CDATA[] and decode it.

Save the converted string inside a text file and then change the extension to .pdf.

Typographic Conventions
The table below describes typographic conventions and/or styles used in this manual so it can be read and
understood more easily.

Convention Meani ng
Save Buttons, windows, tabs; software modules.
Keyboard keys.
service.xml Files, pathnames, folders.
"Finished OK" Program messages.
true Value entered or selected.
P Prerequisite Preceding condition required before an action.
Action Single action.
5 Step Step of a sequence of actions.
Outcome Result of an action or a sequence of actions.

<attribute>
</attribute>

Block of code.
<attribute> Code.

Important warning.

N.B.: Additional note to the information given.

Suggestion.

00doxee Platform Quick Guide-V38

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

00doxee Platform Quick Guide-V38

Загружено:

Авторское право:

Доступные форматы

Training Quick Guide

Вам также может понравиться