This page is for application designers. It explains how to set up a rule to determine whether or not an action will run an associated task plan.

Overview

When working with data, applications and IT systems, there are routine processes that you need to run. PhixFlow makes it easy for you to set up and manage these processes using task plans, to which you add tasks. For details of tasks and task plans, see:

Using Tasks and Task Plans
Task
Training module 14 Creating Tasks and Task Plans

You can also use the action/table-action property → Run Task Plan section to configure an application action to run a task plan. Use the task plan rule properties tab to define a rule (expression) that determines the conditions under which the action runs the task plan.

This properties tab is not available from the repository. It opens from the Action → Run Task Plan section → Task Plan Rules table.

Property Pane Toolbar

For information about the toolbar options, see the Common Properties page, Toolbars and Controls section.

Properties Tab

Parent Details

If this item is within or belongs to another, its parent name is shown here. See the Parent Details section on the Common Properties page for more details.

Basic Settings

Field Description

Task Plan

PhixFlow displays the name of the selected task plan. You can:

select a different task plan from the drop-down list.
Create New a new task plan
Show Task Plans.

Expression

Enter a PhixFlow expression that evaluates to:

either 1 which means /wiki/spaces/HELPTRUNK/pages/47218879. PhixFlow runs the first task plan that evaluates to true, and ignores subsequent task plan rules.
or 0 which means false. PhixFlow does not run the task plan.

The values that represent true are:

any number other than 0
for a list: all items in the list are true
the following case-insensitive strings
- true
- t
- yes
- y

The values that represent false are:

0 (zero)
any string not listed as true above including false

See Expressions and PhixScripts.

Order If there are multiple Task Plan Rules in the action, specify the order in which PhixFlow evaluates their expression. The order is important, as PhixFlow only runs the first task plan whose expression evaluates to true.

Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.

Sections on this page

Learn More

For links to all pages in this topic, see Using Table Actions.

Terminology changes in progress

As part of the redesign of PhixFlow, we are changing the following terms:

dashboard → screen
stream → table
stream attributes → attributes
stream item → record
stream set → recordset
stream view → view
stream item action → record-action
stream action → table-action
driver class → database driver