Name

Enter the name of the table-actions.

Display Name

A view can have a default table-action configured. PhixFlow runs the action

when the user double-clicks on a record in the view.

Enter the name for the default table-actions. PhixFlow displays this name on a view.

Show progress indicator after (ms)

Enter the number of milliseconds which need to pass after the table-actions is submitted before PhixFlow displays a progress indicator.

In Progress Message

Enter a message that you want the user to see with the progress indicator. If not specified, PhixFlow displays a default progress message.

In Progress Popup Message

Enter a message to display in a popup window. Use the toolbar to format the message text. You can provide additional information to the user to explain what the table-actions is doing.

Include Previous Context Parameters

Update Parent Context

Context parameters

This property has a toolbar with standard buttons. The grid contains a list of context parameters that affect whether or not the action/table-action runs. 

To edit the properties of a context parameter, double-click its name. To add a record-action to the list, click  

To remove a context parameter from the action/table-action, select it and click 

Ask for Confirmation

Please confirm that you want to apply action Action Name

To provide a customised confirmation message, use the Confirmation Message property.

Confirmation Message

Optionally, enter your own text to display as the confirmation message. Use the text formatting toolbar to format the message. The maximum length for a message string is determined by System Configuration → System Tuning → Maximum Bigstring Size.

File Upload

Use this property for an action/table-action that will upload a file.

Tag Expr.

Enter an expression that sets the value of the tag for the file. You can use this tag in a file collector to read into PhixFlow files that the table-action has uploaded.

The tag expression can refer to:

• any values entered on the Form View using: _prompt.<Form Field Name>

• the values of any Context Parameters using: _context.<ContextParameter Name>

• any attributes of any records selected on the view or screen from which the table-action was initiated using: <View name or alias>.<Attribute name or alias>

You can return a list of the names of uploaded files using the _files variable.

Validation Expression

Enter a validation expression. This expression is evaluated at the start of any Insert or Update table-actions or record-actions. If the validation expression generates any error messages (using the error function) then the action is abandoned. The validation expression is not used to decide whether or not to run the selected task plan.

The validation expression can include multiple statements by wrapping them in a do() clause. A number of internal variables are available in these expressions:

• _this: a reference to all the selected records within the view to perform the table-action.

• _prompt: a reference to all the user prompted table-action attributes.

The usual message functions debug(message), info(message), warning(message), and error(message) are all available to be used in these expressions and will result in messages being written to the system console logs.

Example 1

Validate that the sum of the selected record amounts equate to zero before allowing the action/table-action to be executed.

if(sum(_this.amount) == 0, info('OK'), error('Not performing Action as the Sum does not equate to zero'))

Example 2

Validate that the user entered comment is at least 10 characters long, else write a warning to the log.

if(stringLength(_prompt.UserComment) >= 10, info('OK'), warning('Comment should be at least 10 characters'))

Using values from other views

You can also refer to records selected in other views by using their screen zone names. E.g. if the screen also contains a screen zone name ACCTS that is bound to a view, you could use the following in your validation expression:

if(sum(ACCTS.amount) == 0, info('OK'), error('Error as ACCTS Sum does not equate to zero'))

Run Selected Task Plan

Task Plan Rules

This section has a toolbar with standard buttons and 

The grid contains a list of task plans and their associated expression. The expression is the rule to determine whether the task plan runs.

To add a task plan to the list:

1. Click 

   Insert excerpt
   _taskplan_show _taskplan_show nopanel true

    to list all the task plans in the repository.

2. Drag task plans into this list.  

To remove a task plan, use the toolbar button 

To add an expression, double-click the task plan in the grid to open a task plan rule property tab.

The first task plan whose expression evaluates to true will be run. Only this task plan will be run. If none of the expressions evaluates to true, no task plan will be run.

Double-click a task plan rule to specify:

• Order: The order in which the rules are evaluated.

• Task Plan: The task plan that will be run if the accompanying expression evaluates to true.

• Expression: If this expression evaluates to true, this task plan will be run. A blank (null) expression counts as true.

See Task Plans for details.

Close Parent Screen

If you tick this flag, the initiating screen will be closed once the action/table-action has completed.

Open Post Screen

If you tick this flag, a separate screen will be opened once the action/table-action has completed. The screen to open is determines by the screen rules. These are only available if you have ticked this flag.

Any filter of any view on the post screen can reference any context parameters set on this action/table-action. If the specified screen is already open it will be brought to the front and refreshed, rather than a second instance of the screen opening.

URL Expression

A URL which will be opened when the action/table-action has completed. This may be provided as a fixed URL or as an expression evaluating to a plain text string. The expression can reference the form fields, context parameters or attributes of records selected on the view or screen from which the action/table-action was initiated.

Screen Rules available if Open Post Screen

This field is only available if the Open Post Screen is ticked.

A list of screen that can be opened after this action/table-action, for each one a rule to determine whether this is the screen that will be opened.

The first screen whose expression evaluates to true will be opened. Only this screen will be opened. If none of the expressions evaluates to true, no screen will be opened.

For each screen rule define the following fields:

• Order: The order in which the rules are evaluated.

• Screen: The screen that will be opened if the accompanying expression evaluates to true.

• Expression: If this expression evaluates to true, this screen will be opened once the action/table-action has completed. A blank (null) expression counts as true.

Result includes Warnings

Result includes Errors

Result Message Timeout (s)

Optionally, specify the number of seconds that the result message is displayed to the user.

Enter the text for a message that PhixFlow will display when the action/table-action has completed. Use the toolbar to format the message. You can use the message to notify the user of a summary of the action, or the to provide information about the completed state.

You can include expressions within the message by enclosing each expression in curly brackets { } . PhixFlow evaluates each expression in turn before displaying the message.

For result messages that report on the status of the action/table-action, you can use the following internal variables in the expressions:

• _error: Details of the error messages generated.

• _errors: The number of error messages generated.

• _warning: Details of the warning messages generated.

• _warnings: The number of warning messages generated.

• _messages: The number of warning messages generated.

• _taskPlan: The name of the task plan that the action/table-action ran (may be null)

• _runId: The runId of any table data generated by this action/table-action (may be null).

• _action: The name of the action/table-action.

• _file: Details of files processed (imported or exported) by the action/table-action.

• _fileCount: The number of files processed by the action/table-action.

Example message showing the number of errors and warnings

Action {_action} failed with {_errors} errors and {_warnings} warnings.

You can also use context parameters and values to report different messages. For example, if you have a context parameter (called balance) that calculates the outstanding balance, you can use an expression that reports different messages depending on the calculated value.

Example of different messages around a threshold value

{if(_context.balance < 0,"Money still owed", "Balance paid")}

Prevent Parallel Processing

Wait for Selection

Target view

Enter the name of the view to which this action/table-action will apply.

Form View

You can specify a form view to appear when the user starts the action/table-action. They will be able to enter values on this form view, and the values can be used to update selected records for an update action, or populate fields for an insert action.

Select a form view

• either from the drop-down list of all forms views in PhixFlow

• or click

  Insert excerpt
  _table_show _table_show nopanel true

   to open the repository showing all the tables. From the repository, drag a form view from the table into this field.

Values entered in the form view are referenced in expressions in the table-action with the form.

_prompt.<form field name>

For example, if there is a field on the form with the label Name, then the value entered in that field by the user can be referenced in subsequent expressions as

_prompt.Name

If this is an update table-action, then the form will be pre-populated with the values from the selected record. Where multiple records are selected, then only those values which are common to all the selected records will be displayed. For insert table-action, when the form pops up all fields will be blank.

Maximum Items Expr.

This field appears if the update table-action selected is Update or Delete. The expressions entered here must evaluate to a positive whole number. The expression can reference any fields entered on the form view associated with this table-action, any attributes of any records selected on the view or screen from which the table-action was initiated and any of the context parameters configured for this table-action.

If the number of items selected on the view from which this table-action is initiated, or retrieved by the filter configured on this table-action, is greater than this number then an error message will be generated and no updates or deletes will take place.

Minimum Items Expr.

This field appears if the update table-action selected is Update or Delete. The expression entered here must evaluate to a positive whole number. The expression can reference any fields entered on the Form View associated with this table-action, any attributes of any records selected on the view or screen from which the table-action was initiated and any of the Context Parameters configured for this table-action.

If the number of items selected on the view from which this table-action is initiated, or retrieved by the filter configured on this table-action, is less than this number then an error message will be generated and no updates or deletes will take place.

_form   acts on the record

currently selected in the view

currently displayed on the form

currently displayed on the form

currently displayed on the card

backing the card

_grid  acts on the record

currently selected in the view

currently selected in the view

_gridRow  acts on the record

current record