Tick to set the table to hold static data. Static data is reference or "look up" data that is used as part of a table calculation.

Updating a static table

In general, static tables are not updated during an analysis run that is initiated on another table in the model. The exception is when an incoming push pipe is triggered, as this will force the table to update itself.

Instead, to update the data in a static table you must run analysis directly on the table via:

• the model
• a task plan.

Select the time period for the table:

• Transactional: allows multiple users to run independent analysis tasks at the same time.
• Non-transactional
  • Daily: generate or collect data every day.
  • Monthly: generate or collect data every month.
  • Variable: generate or collect data since the more recent run of the table to the current date.

This option affects the following items for which this is the backing table:

• views
• screens
• card components.

Select which recordset data is displayed.

• Latest: displays the records from the latest recordset only. Recommended when recordsets are updated by batch process, and therefore have a Period of Daily or Monthly. 
  
• All: displays the records from all recordsets. Recommended when recordsets are updated incrementally and therefore have a Period of Transactional or Variable.
  

If no option is is selected, PhixFlow assumes the default data range is All.

You can override this setting using the options Use Custom Data Range and Data Range available:

• on a Screen.
• on a card; see Component.

You cannot override this setting for a view.

Select the table type; see Types of Table and When to Use Them. The type indicates the function that operates on the data.

• Aggregate Table
• Calculate Table
• CalculateBySet Table
• Cartesian Table
• Merge Table

Select a loop pipe from the list of those available. 

A loop pipe links the table back to itself. It compares new data records to the existing data records. If there is a repeated record PhixFlow uses the new one in the table and marks  the old one as superseded.

do ( $aRange = [], addElement($aRange, rng.RangeFrom), addElement($aRange, rng.RangeTo), $bRange = [], addElement($bRange, $aRange), $bRange )

Where rng.RangeFrom = 500 and rng.RangeTo = 1000, the above example evaluates to [[500,1000]], which is a list containing 1 element, which is itself a list containing 2 elements. An input multiplier that evaluates to [3,4,7,8] would run the Table 4 times.
Because Input Multipliers are evaluated first in the PhixFlow Timing Cycle they are often used to look up values that can be passed to Database or other Collectors.

See Expressions and PhixScripts.

ifNull(in.ASSET, [1,10,12] , // else do [5,7] )

do( lookup(lkin, $num = in.BNumber), lkin )

will return a list of records which match the lookup on the lkin pipe. In this case the required data can be extracted from the Output Multiplier using the following expression :

do ( $values = _type, $values.account_num )

If the output multiplier expression evaluates to _NULL, an empty list of values or an empty list of records then a single output record will be produced with _type set to _NULL, _NULL or an empty record respectively.

See Expressions and PhixScripts.

You can select a subset of records to output to the next modelling object. You select records using the data in any attribute that is in the table output. Enter an expression that should evaluate to true or false (equivalently 1 or 0).  

When the expression evaluates to true or 1, the records found by the expression are selected and output to the next modelling object.

For example:

• A table containing data about accounts has an attribute called "active".
• You only want to include "active" accounts in the following tables. 
• Active accounts have the value 1.

To select active accounts, enter the expression  _out.active.
All records that have the active attribute set to any other value are ignored.

See Expressions and PhixScripts.

When a table-data-delete task runs for a table and:

• Keep for X Days only is set, PhixFlow deletes table data that is older than N days.
• Keep for Y Recordsets only is set, PhixFlow keeps the most recent X recordsets and deletes recordsets that exceed X.
• both Keep for X Days and Keep for Y Recordsets are set, PhixFlow deletes the table data that meets both conditions.
• neither Keep for N Days nor Keep for X Recordsets are set, PhixFlow keeps table data indefinitely. This can lead to performance issues.

The number of recordsets to keep in the table.

In a table where the superseded date is tracked, the table data contains a mixture of active records and records that have been superseded.

When a table-data-delete task runs for a table and:

• Keep Superseded for N Days only is set, PhixFlow deletes data records that were superseded more than N days ago.
• Keep Superseded for X Recordsets only is set, PhixFlow  deletes superseded records from the recordsets that exceed X.
• both Keep Superseded for N Days and Keep Superseded for X Recordsets are set, PhixFlow deletes the superseded records that meet both conditions.
• neither Keep Superseded for N Days nor Keep Superseded for X Recordsets are set, PhixFlow keeps superseded records indefinitely. This can lead to performance issues.

Available when Track Superseded Data is selected.

Enter the number of recent recordsets that will retain their superseded data records.

Use this property if your database administrator wants to query table data in the PhixFlow database.

Enter a string in the format v_xxxx. When the table is published to the database, PhixFlow creates a  view. If the table is deleted, the next system task that runs will clear the associated view from the database.

By default, this field is blank and no view is created in the database.

See also Configuring Access to Database Views.

• All: indexes on the table are optimised for selecting from all recordsets (non-historied reads).
• Latest: indexes on the table are optimised for selecting from the latest recordset (i.e. for historied reads).
• Superseded: indexes on the table are optimised for self-updating tables which have a mostly superseded records.
• None: no indexes are created on the table.
• Partitioned: this index scheme is specific to partitioned tables; see Storage Type below. Partitioned tables must use this index scheme, and only partitioned tables can use it.

• Database: Store the data in a regular table within the PhixFlow database. This is the most common option
• Database (Partitioned): Store the data in a partitioned table within the PhixFlow database. This option provides improved performance for rollback and retaining very large recordsets. The option is only available if "partitioning" is available within your database installation.
• In Memory: Data for the table will not be written to the database. This option can be used (for example) when you want to aggregate large amounts of unsorted data which can then be written to a stored table.

This option relates to an actionflow with a save node that inserts a new record into a table. Each new record requires a unique value for the record's primary key. Use this option to specify how PhixFlow generates the primary key value.

• Internal: PhixFlow generates unique primary key values automatically. This is equivalent to setting the attribute expression to _NULL. 
• Sequence: display the Primary Key Generator Sequence option, in which you can select a sequence of values.

Available when Primary Key Generator is Sequence.

Select a sequence to assign a new value to the primary key attribute of a new record; see Sequence.

The new record takes the next primary key value in a sequence. This is equivalent to setting the attribute expression to nextValue("sequenceName".

 Tick so that, whenever the analysis engine needs to generate data for this table, it will first wait for all running tasks to complete before it starts.

Any additional analysis tasks submitted while this table is waiting to start, or while it is generating data, will wait until this table has completed its analysis before they start.