To turn a screen into a user interface, you must configure the operations that PhixFlow will run. Usually, these operations will change:
- either data, for example to update or delete records.
- or the application interface, for example to close one screen and open another.
For example, you can:
- Design a form with editable fields and buttons.
- Connect the form to a stream, to populate the fields with data.
- Make changes to data in the fields.
- Click the "Save" button.
At this point there will be no change to the data in the stream until you have configured the button to perform the operation of updating the data in the stream.
To configure an operation using an action, you can:
- Add an action directly to the repository. Actions that are not associated with a stream can do things like open dashboards.
- For specific stream, you can create an action to operate on the stream data. Action on a stream can:
- create, update or delete data
- run a task
- run analysis on a model
- open or close a screen/dashboard
- show prompts or messages to communicate with the user
You can connect the output of one action to the input of the next action, and specify rules to determine the conditions under which the action will run.
You can optionally configure
- the contexts in which the action will or will not run using context parameters
- a prompt to confirm the user wants to run the action
- something about uploading a file
- that PhixFlow checks the conditions to allow the action to run are met (validation)
- a task plan that will run after the micro-actions
- any dashboards to open or close when the action completes
- a message to display after the action completes, for example with errors and warnings.
The pages in this topic are: