Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

This page provides details of the properties for the open screen node and associated expressions. These are part of actionflows.

Sections on this page

Overview

Use an  Open Screen action node to open new screens within PhixFlow. To set the actionflow to close the active dashboard on completion, on the top right of the canvas, tick Close Parent Dashboard.

Example

The above video shows a basic actionflow to open a screen from a button. To open a screen:

  1. Right click on the button and click Add Actionflow
  2. Name the action
  3. Drag the screen you want to open onto the main body of the actionflow. You have just created an open screen node.
  4. Now we need to wire up an input to initiate the actionflow
  5. Click Add next to the inputs
  6. Name the new input connection point and select driving.
  7. Click create connection point
  8. Click on the on click input. This will start the actionflow when a user clicks on the button.
  9. Click connect input to finish setting up the actionflow
  10. Go back to the first screen to test to see if it works.

 Properties Tab

Parent Details

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

Basic Settings

FieldDescription
NameEnter the name for the action node.
Show in the Repository

An application can have many actionflows, and an individual actionflow can have many nodes. This can lead to many items being listed under Actionflow in the repository. Use this option to omit the node from the repository.

 Tick to display this node in the repository.

 Untick to omit this node from the repository.

Screen

Select a dashboard that the action will open. The dashboard can be selected using the drop down or  List Screens.

If the screen has not been created yet, create one using  Add New.

A warning symbol appears on the node if a screen has not been selected.

Model Validation StatusWhen you save changes to the properties of a table or view attribute, PhixFlow validates that the properties are set correctly. If there is an issue with the properties, PhixFlow indicates the status of the validation check:
  • UNKNOWN - PhixFlow has not run the validation check yet. Save the properties to run the check.
  • SUCCESS - the properties are set correctly
  • ERROR - PhixFlow has found issues that need attention. Scroll down the properties to the Errors section where you will find the list of properties that need correcting.

When a table or view attribute has validation errors, PhixFlow also reports that the parent application and package have errors.

PhixFlow can process data from tables or view attributes that have validation errors. The validation checks help you to configure tables and view attributes so that PhixFlow can continue to run efficiently.  For example, PhixFlow reports an error if a table has no Data Retention option set because it can affect performance when all old tablesets are retained, 

To run validation checks on all tables, view attributes, applications and packages,  use Administration Menu → More → Validate Model Objects

Input Connection Points

Each open screen node has 1 primary input connection point by default called 'screen'. Connecting to this connection point opens the screen and allows the user to optionally map the following screen properties. (may not happen for v9)

PropertyTypeDefault Values if not setDescription
heightNumberfind outSets the height of the screen
widthNumberfind outSets the width of the screen
topNumberfind outSets the top position of the screen relative to the window
leftNumberfind outSets the left position of the screen relative to the window
maximisedBooleanwhatever is set on the screen properties
  • True will open the dashboard in its maximised state.
  • False will open the dashboard in its minimised state and will use the above properties.

Once a screen has been attached to the open dashboard node an input connection point for each form on the screen is created with a role of component. Each input connection point automatically has any data fields on the form (dynamic text or form fields) added as attributes. These attributes can be mapped to and supplied with data.

Each input connection point has the following properties:

FieldDescription
NameThe name of the input connection point
Role
  • Primary
    Simply opens the dashboard regardless of data. Has optional mapping fields to set screen properties.
  • Component
    Opens the dashboard and can provide forms with data
Open Mode
  • Update
    opens form fields with the latest data
  • Insert
    opens the screen with form fields empty
  • Change fields
    opens form fields with data
Attributes

A list of attributes available on the input connection point. These directly link to the fields available on the form.

Component connection points display attributes available on the associated form.

Primary connection points display the screen properties as attributes.

Output Connection Points

If the screen attached to the node contains start phase buttons (buttons with the action type 'Start Phase') the output connection point section will appear.


Properties - to do


Description

We recommend that you always enter a description to explain the purpose of this item.

 Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.

Learn More

For links to all pages in this topic, see Understanding Actionflows


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







  • No labels