Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The following is a list of all key terms within PhixFlow and links to relevant help pages.


New BPMN Workflow and Action Flow Definitions

Insert excerpt
_term_bpmn_workflow
_term_bpmn_workflow
nopaneltrue

Insert excerpt
_term_action_flow
_term_action_flow
nopaneltrue

Insert excerpt
_term_micro_action
_term_micro_action
nopaneltrue


Terms A to M

Anchor
action
action
 
Insert excerpt
_term_action
_term_action
nopaneltrue

Anchor
analysisModel
analysisModel
 
Insert excerpt
_term_analysis_model
_term_analysis_model
nopaneltrue

Anchor
attribute
attribute
Anchor
streamAttribute
streamAttribute
Anchor
streamActionAttribute
streamActionAttribute
Anchor
streamViewAttribute
streamViewAttribute
 
Insert excerpt
_term_attribute
_term_attribute
nopaneltrue


Anchor
collector
collector
 
Anchor
databaseCollector
databaseCollector
Anchor
fileCollector
fileCollector
Anchor
httpCollector
httpCollector
Insert excerpt
_term_collector
_term_collector
nopaneltrue


stream attribute: see attribute

stream view attribute: see attribute

stream action attribute: see attribute

Anchor
stream
stream
 
Insert excerpt
_term_stream
_term_stream
nopaneltrue



Anchor
streamItem
streamItem
Anchor
streamItemDetails
streamItemDetails
 
Insert excerpt
_term_stream_item
_term_stream_item
nopaneltrue

Anchor
streamSet
streamSet
Insert excerpt
_term_stream_set
_term_stream_set
nopaneltrue

Anchor
streamTables
streamTables
 
Insert excerpt
_term_stream_table
_term_stream_table
nopaneltrue

Anchor
systemConfiguration
systemConfiguration
  
Insert excerpt
_term_sys_config
_term_sys_config
nopaneltrue

Anchor
systemTask
systemTask
 
Insert excerpt
_term_system_task
_term_system_task
nopaneltrue

Anchor
task
task
Anchor
taskPlan
taskPlan
 
Insert excerpt
_term_task
_term_task
nopaneltrue

Anchor
user
user
  
Insert excerpt
_term_user_group
_term_user_group
nopaneltrue

Anchor
userGroup
userGroup
 
Insert excerpt
_term_user_group
_term_user_group
nopaneltrue

Anchor
userNotificationRule
userNotificationRule
  
Insert excerpt
_term_user_notification
_term_user_notification
nopaneltrue

Anchor
xmlNamespace
xmlNamespace
 
Insert excerpt
_term_xmlnamespace
_term_xmlnamespace
nopaneltrue

Anchor
xPath
xPath
 
Insert excerpt
_term_xpath
_term_xpath
nopaneltrue



Terms M to Z



stream function
TermDescriptionRelated Glossary TermSee Page

Anchor
action
action
action

Defines a set of operations on  the values of data in a stream.

 stream item. A stream action can be applied from the stream view properties.



Anchor
actionButtons
actionButtons
action button

Used to group actions into drop-down lists or display a single 9711226488 as a button. In both cases Action Buttons are displayed on the top of 9711226488 .

stream action
Anchor
aggregateField
aggregateField
aggregate attribute

Aggregate Attributes define the aggregated properties that are available when data is read from an aggregating 9711226488.



Anchor
analysisModel
analysisModel
analysis model

Allow users to logically represent a business process / control flow using configured PhixFlow objects, e.g. streams, file collectors etc.



Anchor
analysisTask
analysisTask
analysis task

The Analysis Engine is initiated whenever the generation of a Stream Set is requested. Users can do this by configuring Analysis Tasks in a 9711226488.



Anchor
archiveTaskRun
archiveTaskRun
archive task

A task to archive 9711226488 from 9711226488 with archiving configured on them.



Anchor
array
array
array

An object that contains an ordered list of other objects.



Anchor
attributeFunction
attributeFunction
attribute function

PhixFlow provides an extensive list of Attribute Functions which may be used within all expression strings.



Anchor
auditDetail
auditDetail
audit detail

Details of an individual audited action performed on a PhixFlow object.



Anchor
auditSummary
auditSummary
audit summary

A summary of all audited action performed on PhixFlow objects. Can be viewed in the System Console.



Anchor
auditAffectedObject
auditAffectedObject
audited item

PhixFlow objects that have auditing switched on to allow for any changes in the system to be tracked.



Anchor
candidateSet
candidateSet
candidate set

Candidate sets are a fundamental concept of function calculation in PhixFlow.

Every time a function calculation is carried out, all the required input data is brought together and organised into sets of data - one set for each Key group.

The Key groups are worked out using the Pipe Grouping Attributes defined on input Pipe for each Stream.



Anchor
centerViewDatabase
centerViewDatabase
PhixFlow database

The database that stores the PhixFlow schema and all processed data



Anchor
chart
chart
chart

A Chart displays data in table form, or in one of a number of graphs styles.



Anchor
comparator
comparator
comparator

Refers to the comparator types that can be used in a filter, e.g. greater than, starts with.



Anchor
contextMenu
contextMenu
context menu

A context menu appears above each 9711226488 when the user hovers over it in a model view. This menu shows all of the actions that can be performed on that element.



Anchor
csvfile
csvfile
CSV file

A CSV (comma-separated variable) file is a plain text file where each line in the file consists of a number of fields separated by commas ','. If fields may contain spaces, commas or double quotes, they should be enclosed in double quotes '"'. A double quote may be represented by 2 double quotes.

A CSV file is always encoded using a specific character set. On Windows this is typically Cp1282, and on Unix/Linux US7ASCII, though the following are sometimes used: UTF-8, UTF-16, ISO-8859-1.

A CSV file typically has an extension '.csv'.

A CSV file can be created directly in a plain text editor (e.g. Wordpad/Notepad), in Excel (by saving as a CSV), or by some other application.



Anchor
cycle
cycle
cycle

Whenever an analysis model is run it will carry out a number of tasks e.g. read a number of files, generate a number of stream sets, export a number of files. It is possible to configure an analysis model so that in a single analysis session it will actually run several times. When a model is configured in this way, each time it runs is termed a 'cycle' and all of the items processed or generated during that cycle (i.e. the files processed, stream sets created, files exported etc) are flagged with the cycle number. This cycle number is visible in the Log File for that analysis run on each of the relevant tabs showing files and stream sets processed.

The most common reason for configuring a model in this way is to allow a number of files to be processed in a single analysis session but to have the results from each file saved in a separate stream set. In this way, whenever a file fails to process the user can simply rollback the stream sets associated with that file rather than rolling back all of the stream sets associated with all of the files for the whole analysis session.

To achieve this, a model is configured with a push pipe from the final stream in the model pointing back to itself. This push pipe is then given positive offsets. The file collector at the start of the model is then configured to process a single file at a time. When this model is run the file collector will read in one file, process it to create a stream set (or a chain of stream sets if there are several streams in the model) and will flag the file processed, the stream sets generated and any associated output files with the cycle number 1. When the last stream in the model has finished producing its stream set it will send a notification to itself down the push pipe. This notification (because of the positive offsets) will be taken as a signal to create another stream set which will effectively cause the whole model to run again. This second run of the model will be deemed to be cycle 2 and all files processed, stream sets produced or files output will be flagged with this cycle number.

When later viewing the log files the user can see which items were processed in which cycle and can choose how many cycles to roll back. In the case where the last file processed was unsuccessful the user can therefore choose to only roll back the last cycle.



Anchor
dashboard
dashboard
dashboard

A dashboard allows the user to gather into a single view a set of charts. This grouping of related reports and statistics provides the user with preconfigured overviews of selected areas, making all the data that is required to view and monitor the health of the system both accessible and easy to read.



Anchor
dataGrid
dataGrid
data grid

A Data Grid is a particular type of view which displays the data in a table format.



Anchor
driverClass
driverClass
database driver

The driver used to access the source database.

Anchor
databaseExporter
databaseExporter
database exporter

Used to write information from PhixFlow to external databases.



Anchor
datasource
datasource
datasource

Defines a connection to an external database.



Anchor
datasourceInstance
datasourceInstance
datasource instance

Allows for multiple connections for individual database instances to be configured for a specific 9711226488.



Anchor
directedPipe
directedPipe
directed pipe

A Directed Pipe is used as a secondary input to a Merge Stream.

Primary Pipes to a Merge are implemented by reading all input records from all Primary Pipes in a single operation, ordered by the Group-By fields. The primary pipes determine the key values of the Candidate Sets that will be generated.

A Directed pipe is implemented after the Primary Pipes have run, by reading records matching each Candidate Set grouping key in turn. This can result in a significant performance improvement in certain circumstances.

A Pipe can be marked as a Directed Pipe on the Pipe Details / Advanced tab.



Anchor
expression
expression
expression

An expression returns a value, usually by manipulating or transforming input data, although some expressions can be very simple: e.g. the expression "hello" always returns the string "hello" and requires no input.



Anchor
fileCollectorAttribute
fileCollectorAttribute
file collector attribute

The data columns that a File Collector expects to be present when importing a file.



Anchor
fileExporter
fileExporter
file exporter

Used to write information from PhixFlow to external files.



Anchor
filter
filter
filter

Filters are made up of a set of clauses; each clause in turn contains a number of conditions. These conditions must be satisfied for data to be passed through a pipe or returned in a filtered list.



Anchor
formBar
formBar
form bar

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).



Anchor
fTPSite
fTPSite
FTP site

A file system that is reachable via the FTP protocol.



Anchor
orderByField
orderByField
group by attribute

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.



Anchor
http
http
HTTP

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.



Anchor
httpDatasource
httpDatasource
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 9711226488 , and exported to an HTTP Datasource using a 9711226488.

An HTTP Datasource Instance must define at least one 9711226488.

An HTTP Datasource Instance may define multiple 9711226488 to support 9711226488 expressions on 9711226488 .



Anchor
httpDatasourceInstance
httpDatasourceInstance
HTTP datasource instance

An HTTP Datasource Instance provide a default username, password and URL to an 9711226488 or 9711226488.



Anchor
httpExporter
httpExporter
HTTP exporter

Export data to an 9711226488.



Anchor
internalVariable
internalVariable
internal variables

Pre-defined variables for use in PhixFlow Expressions.



Anchor
cVLocale
cVLocale
language

The display language of the user.



Anchor
logFile
logFile
log file

A record of a task or action completed in PhixFlow, including any messages output and details about stream sets created.



Anchor
logMessage
logMessage
log message

Within each log list, log messages are output by the Analysis Engine as it performs analysis.



Anchor
macro
macro
macro

A macro is a user-defined function that can be called from other 9711226488.

A macro can be called with parameters. These parameters are available within the body of the macro as $arg.



Anchor
modelElement
modelElement
model element

The individual objects that make up an 9711226488 e.g. streams, file collectors etc. These elements are added via drag and drop controls and context menus.



Anchor
paging
paging
paging

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.



Anchor
period
period
period

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.


Anchor
pipe
pipe
pipe

A pipe is a connector that links two elements in a PhixFlow model.



Anchor
privilege
privilege
privilege

Privileges are used to define what actions can be performed in PhixFlow; see Privileges.



Anchor
repository
repository
repository
The PhixFlow repository lists the files, modelling objects and application components to which you have access; see Using the Repository

Anchor
recordset
recordset
recordset

A record set is a list of records returned, usually by a pipe, where each record consists of named attributes, each with a value.



Anchor
refreshAction
refreshAction
refresh action

Represents an action that once completed will cause the enclosing view to be refreshed.



Anchor
role
role
role

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); see Roles.



Anchor
role
role
rollback

Deletes a specified set of 9711226488 from a 9711226488 and updates the tidemarks for that 9711226488.



Anchor
rollbackTask
rollbackTask
rollback task

A Rollback Task can be configured to rollback one or more streams. Users can do this by configuring Rollback Tasks in a 9711226488.



Anchor
sequence
sequence
sequence

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.



Anchor
sql
sql
SQL

SQL query used to retrieve data from, or SQL or PL/SQL statement used to update data in, a 9711226488.



Anchor
streamAction
streamAction
stream action

Defines a set of updates to the values of a stream item. A stream action can be applied from the stream view properties.



Anchor
streamFunctionFactorystreamFunctionFactory

Defines the basic Stream operation. The type of stream may be aggregate, calculate, calculate by set, cartesian or merge.




Anchor
streamFunctionFactory
streamFunctionFactory
 
Anchor
streamType
streamType
 
Insert excerpt
_term_stream_type
_term_stream_type




To do

transaction/transactional updates

analysis model

dashboard

grid - phixflow word for a table. You can show stream data in a grid (looks like an excel spreadsheet). Property tabs can also have grids to represent property information, for example for the list of users in a user group

stream attribute → attribute

stream view attribute → attribute

stream view → view

property tabs

item - anything that appears in the repository

modelling object - things that appear in analysis models

layout component - anything that can make up a layout

layout - a GUI screen in your application 

dashboard = layout the starting point for a layout

application interface, screen, form, layout screen - too generic "when you look at your computer screen"

publish - The process of writing changes to stream data in a model to the stream tables in the database.