Field | Description |
---|
Advanced Properties | Only use this field with advice from PhixFlow support. |
Database View | 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. |
Audit Manual Changes | This toggle is available when the Analysis Options → Period is Transactional. Insert excerpt |
---|
| _toggle_on |
---|
| _toggle_on |
---|
nopanel | true |
---|
| toggle on to update and delete initiated by actions (not those carried out by analysis runs) will automatically mark the existing record as superseded and create a new recordset. The new versions of the updated records will be placed in the new recordset. Inserts will simply create a new recordset, and add the inserted record into that recordset.When Audit Manual Changes is first set, the attributes UpdateAction , UpdatedByName , UpdatedByID and UpdatedTime will be created if they do not already exist. If you do not require these attributes, delete them. For the UpdatedByName attribute, PhixFlow creates a field of 250 characters. UpdateAction must be set to the type of action, such as INSERT, UPDATE or DELETE. The other attributes will be populated if they exist on the table:
UpdatedByName - the name of the user that performed the update, UpdatedByID - the internal id of the user that performed the update UpdatedTime - the date and time the update was made
|
Storage Options |
---|
Index Scheme | Select an option to determine how indexes on the table are organised. - 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.
|
Storage Type | Select an option to specify how data for the table should be stored:- 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.
|
Data Generation Options |
---|
Start Date | Enter the date on which this table starts or click Insert excerpt |
---|
| _calendar |
---|
| _calendar |
---|
nopanel | true |
---|
| to select a date. Data will be populated into the table from this date onwards. |
Primary Key Generator | 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.
|
Primary Key Generator Sequence | 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" . |
In Memory Cache Size | Enter the size of the cache that will be maintained when you are using an in-memory table. See Manage Unsorted Data Using an In-Memory Table. |
Allow Partial Set Processing | Insert excerpt |
---|
| _check_box_untick |
---|
| _check_box_untick |
---|
nopanel | true |
---|
| to restrict all users to the Table Download Limit. Insert excerpt |
---|
| _check_box_tick |
---|
| _check_box_tick |
---|
nopanel | true |
---|
| so that, when analysis reaches the end of a buffer block, it submits the candidate set for processing, even if the next buffer block has a different key. |
Prevent Parallel Processing | Available when Period is Transactional. Insert excerpt |
---|
| _check_box_tick |
---|
| _check_box_tick |
---|
nopanel | true |
---|
| to ensure only a single recordset can be generated at a time even if the table receives several concurrent requests to generate data.This can be useful where you want to make sure that two analysis runs do not attempt to update the same records at the same time e.g. as a result of two people selecting the same records in a view and then hitting the same action button at the same time to process those records. |
Run Alone | Insert excerpt |
---|
| _check_box_tick |
---|
| _check_box_tick |
---|
nopanel | true |
---|
| 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. |
Key Tolerances | When building a candidate set, data can be grouped together using a specific key value, e.g. Account Number. If the key value is a number, enter a key tolerance to identify numbers within the given tolerance as the same key value. |
Default View | Select the default view for the table; see Views for details of creating views on tables. |
Last Run Date (Read only) | PhixFlow displays the date and time that analysis was last run for this table. This date is taken from the "to date" of the most recent recordset for this table. |
Last Run By | PhixFlow displays the user that last ran analysis on this table. |