...
...
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
...
...
Aggregate Attributes define the aggregated properties that are available when data is read from an aggregating Pipe.
...
...
...
...
...
...
The Analysis Engine is initiated whenever the generation of a Stream Set is requested. Users can do this by configuring Analysis Tasks in a Task Plan.
...
A task to archive Stream Sets from Streams with archiving configured on them.
...
An object that contains an ordered list of other objects.
...
PhixFlow provides an extensive list of Attribute Functions which may be used within all expression strings.
...
Details of an individual audited action performed on a PhixFlow object.
...
...
...
...
PhixFlow objects that have auditing switched on to allow for any changes in the system to be tracked.
...
Candidate sets are a fundamental concept of function calculation in PhixFlow.
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Used to write information from PhixFlow to external files.
...
...
The data columns that a File Collector expects to be present when importing a file.
...
...
...
If you move your mouse pointer to the bottom of the screen the PhixFlow Form Bar will appear. Contains links to all open forms (both open and minimised).
...
A file system that is reachable via the FTP protocol.
...
Groups the pipe data into candidate set, forms key for candidate set. However if data is coming from database or file collector, order by fields need to be specified in the collector SQL.
...
Hypertext transfer protocol - the language of the internet. In the context of PhixFlow, it means using standard internet communication as means of importing and exporting data.
...
Collect data from an HTTP Datasource.
...
A web site, web service or some other target that allows XML, HTML or text data to be collected from it, or exported to it, over HTTP. Data is collected from an HTTP Datasource using a HTTP Collector , and exported to an HTTP Datasource using a HTTP Exporter.
An HTTP Datasource Instance must define at least one HTTP Datasource Instance.
An HTTP Datasource Instance may define multiple XML Namespaces to support XPath expressions on HTTP Collectors .
...
An HTTP Datasource Instance provide a default username, password and URL to an HTTP Collector or HTTP Exporter.
...
Export data to an HTTP Datasource.
...
Pre-defined variables for use in PhixFlow Expressions.
...
The display language of the user.
...
A record of a task or action completed in PhixFlow, including any messages output and details about stream sets created.
...
Within each log list, log messages are output by the Analysis Engine as it performs analysis.
...
A macro is a user-defined function that can be called from other Expressions.
A macro can be called with parameters. These parameters are available within the body of the macro as $arg.
...
The individual objects that make up an Analysis Model e.g. streams, file collectors etc. These elements are added via drag and drop controls and context menus.
...
Where a list is displaying more data than can be viewed in the display grid, paging allows the user to scroll through the whole list, e.g. log messages, Stream Set data.
...
A period is set on a Stream. This can be either a regular period, or variable. There are four possible settings:
- 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 stream to the current date.
- Transactional: allows multiple users to run independent analysis tasks at the same time.
...
A pipe is a connector that links two elements in a PhixFlow model.
...
Privileges are used to define what actions can be performed in PhixFlow.
...
A record set is a list of records returned, usually by a pipe, where each record consists of named attributes, each with a value.
...
Represents an action that once completed will cause the enclosing view to be refreshed.
...
Roles represent the type of access required to do specific tasks (e.g. Designer, Operator etc.)
Roles are assigned to User Groups (or vice versa)
...
Deletes a specified set of Stream Sets from a Stream and updates the tidemarks for that Stream.
...
A Rollback Task can be configured to rollback one or more streams. Users can do this by configuring Rollback Tasks in a Task Plan.
...
A Sequence is used to generate a numeric sequence of values.
The Sequence lets you define the properties of the sequence e.g. the starting value.
The nextValue function returns the next value in the sequence each time it is called.
The curValue function returns the most recent value returned by nextValue.
...
SQL query used to retrieve data from, or SQL or PL/SQL statement used to update data in, a Datasource.
...
Represent a structured store of data within PhixFlow receiving data from one or more components, processing it then storing it.
...
Defines a set of updates to the values of a Stream Item.
A Stream Action can be applied from a Stream View from a Stream Item Details form.
...
Each Stream Action Attribute defines the new value to be assigned to a single field of a Stream Item. The new value is defined as an Glossary / Index, which can refer to the original values of the Stream Item.
When a Stream Action is applied, each attribute's expression is evaluated in turn and the result is saved back to the Stream Item.
...
Define the type, precision and expressions of how each individual attribute is calculated based on the inputs to the Stream.
...
...
...
Individual record in a Stream Set.
...
A Stream Item Details form can be opened from a Grid Stream View by opening the view, selecting a Stream Item then selecting Show Stream Item Details from the context menu.
...
Physical table in PhixFlow schema that stores the Stream data.
...
Used to customise the display of data in one or more Stream Sets.
...
Stream Attributes used in a Stream View. Each attribute has a role that defines how the data will be displayed.
...
A set of data items for a given period.
...
Where all general system wide properties are configured in PhixFlow.
...
A System Task runs standard system-wide housekeeping activities. It must be run as part of a Task Plan.
The standard housekeeping activities are:
- Deleting and (optionally) archiving Log Messages
- Deleting Managed File entries
- Deleting Email records
The parameters controlling how long to keep Log Messages / Managed Files / Emails before deleting them, and whether first to archive Log Messages to file, are set in System Configuration.
...
A Task can be set up to carry out an action or set of actions in PhixFlow. Tasks can be one of:
...
Contains a set of Tasks to run.
...
...
...
...
...
...
...
...
...
...