Technical data

Phoenix

Getting Started Guide

How are templates different from workflows and objects?

» Templates do not store pointers to non-results data, such as imported work-

sheets.

» Workflows and objects contain pointers to data sets, but templates do not.

How are templates different from project files?

» Project files save all parts of the project - all the data sets, code, rule sets,

other information objects, and all workflows and operational objects.

» Templates save the setup information for workflow and operational objects,

and any pointers to an operational object’s results data.

What are the benefits of a template?

» A workflow can be saved as a template, in order to reapply an analysis on

new data. This allows a common analysis to be pre-defined for automated

performance of repetitive analyses.

» Users can perform the same operations on different data sets without hav-

ing to recreate the original workflow that is saved in the template.

» Templates can be imported into a workflow, although templates do not save

any data sets or data mappings.

Note: When a template is imported into a workflow, it is necessary to remap any

external data sources to objects in the template.

Data

When a data set is imported into Phoenix, whatever changes are made to those

data only affects the data that is imported into Phoenix. The actual file that con-

tains the data is not affected.

This means that any changes made to data sets imported into Phoenix are not

reflected in the data set that is saved on a hard drive or other storage media. Users

can make as many changes as they want to a data set in Phoenix without chang-

ing the original data set.

What types of data does Phoenix use?

» Imported data sets such as worksheets and workbooks.