Overview

In an analysis model,

data is held in a table which consists of:

• Columns - these are the attributes.

• Rows - these are the data records.

Tables can be connected with pipes, which are used to send data from table to another. Pipes also connect other types of modelling object, such as a datasource that connects to a database or file exporter. Usually, a pipe has default settings

, this means it passes all attributes and records onto the next object. However, you can use the pipe properties to control which attributes and records from the input object you want to pass through.

For example, here we have data being imported from a database using a datasource and data collector, the data is held in its original form in a table before being passed onto a second table where is it enriched. It is possible to add a filters on any of the pipes to remove records such as a business being found with no name or a transaction being older than a specified date.

Image Added

To move data between modelling objects we must run an analysis model

. PhixFlow then uses the information in each object's properties to process the data.

Because with each analysis run

the data in a table can change,

PhixFlow keeps

the dataset for each run.

If there is a problem in the analysis run, you can delete

a dataset(s) using the Rollback feature which will revert to the selected

dataset. You can also copy or move data from a

dataset.

Viewing Data in a

Table is possible via views, the default view shows data in a grid. You can also create

your own views such as graphs and charts. View properties have lots of options to control which attributes are included in the view, which records are shown and how to sort the records.

Running Analysis

Running analysis is where PhixFlow evaluates your configuration and uses this information to processes your data. Analysis is started from a table, and then all modelling objects which proceed the table will process the data in order. It should be noted that some modelling objects can be set to static, these will not run and PhixFlow will not run any items which precede a static item. This is useful where there is information which you do not need to reprocess every time your run analysis, or want to run it on a different schedule.

To Run Analysis hover over the table and click Run Analysis:

Image Added

Streams and Time Periods

In any given moment, a streams

can contain a set of records

which we call the dataset. You can set the time period

which PhixFlow

uses to collect records. The period can be:

For non-transactional periods, PhixFlow checks for incomplete record-sets and reports an error if it finds them. However, pipes from transactional streams allow incomplete record-sets, as data is constantly changing.

Publishing Streams

Anchor
publish publish

When you make changes to a stream's properties or its attributes, PhixFlow publishes the changes to the PhixFlow database. This happens automatically in the background. Publishing many streams or streams with many attributes can take some time, and may slow performance.

If the stream properties are set incorrectly, PhixFlow will not be able to publish the stream to the database. If this happens, the

During the publishing process, PhixFlow may create temporary streams in its database. These are kept for a period, then automatically removed when a system task runs. For information about:

• the system task, see Using Tasks and Task Plans
• configuring the period that temporary streams are kept; see System Configuration → Delete Temp Streams after Days.

Learn More

• Managing Recordsets
• Managing Models and Data
• Modelling objects and Windows
  • Analysis Model Window and Toolbars
  • Analysis Model Properties
  • Table Properties
  • Attribute Properties 
  • Pipe Properties 
  • Sort Order Properties
• Rolling-back recordsets
  • Rollback Window
  • Rollback or Repeat Cycles Window