User Manual

Overview Diagram
Bounce Architect
Component Description
Policy Architect The Policy component consists of a Microsoft.Net application
for defining the sources of data that will be used in acquiring
the product information for the image generation process.
Data transformations are also created and edited within Policy
Architect. Transformations can be used when the format of
the data in the acquired data sources needs to be changed or
reformatted to represent what will be rendered in the product
image.
Schedules can also be defined within Policy Architect. A
schedule defines when data should be acquired to determine if
any changes have occurred in the data set. Any data changes
result in new images being generated. A schedule can be as
simple as a trigger based on when a data file changes, or a
more complex predefined set of times when the data should
be acquired from a remote database.
Policy Architect provides a means to preview both the
acquired data and the EPOP images that will be created from
the data.
Any policies that are defined within the Policy Architect
application can be saved and imported into Bounce Processor
as a configuration file.
Template Architect The Template component consists of a Microsoft.Net
application for defining EPOP image templates. A template
defines the information that should be displayed on an EPOP.
It consists of a set of instructions detailing where and how
data fields are rendered within the EPOP image.
Processor
Acquire,
Transform,
Render
Manager
Configure,
Assign,
Report
API
Communicate
Transmit,
Log
Template
Collection
Policy
Config
Retail Databases
Architect
Create policies &
templates