This page is for application designers who want to create screens for application users.

Overview

This page explains the screen properties. For  For information on how to divide a screen into different panes, and how to add components to it, see Splitting a Screen.

Insert excerpt
_property_tabs _property_tabs name basic-h nopanel true

Basic Settings

Field	Description
Name	The name of the screen.
Open Maximised	Insert excerpt _check_box_tick _check_box_tick nopanel true  to open the screen maximised. Insert excerpt _check_box_untick _check_box_untick nopanel true  to open the screen as a popup window.
Allow User to Resize	Insert excerpt _check_box_tick _check_box_tick nopanel true  to enable the application user, when running in  Insert excerpt _app_mode _app_mode nopanel true , to resize the screen. Insert excerpt _check_box_untick _check_box_untick nopanel true  to keep the screen size fixed when running in in  Insert excerpt _app_mode _app_mode nopanel true . This option does not affect resizing the screen in  Insert excerpt _design_mode _design_mode nopanel true .
Show Toolbar	Insert excerpt _design_mode _design_mode nopanel true

 always

always has a toolbar with the screen name on the left and toolbar icons on the right.  Insert excerpt _check_box_tick _check_box_tick nopanel true  to also display the toolbar in  Insert excerpt _app_mode _app_mode nopanel true . The screen name is displayed. Toolbar icons are not displayed. Insert excerpt _check_box_untick _check_box_untick nopanel true  is the default as the toolbar is usually not required in  Insert excerpt _app_mode _app_mode nopanel true .

Show Window Button Bar

Insert excerpt _check_box_tick _check_box_tick nopanel true  to display a Windows-style bar at the top of the screen. This has a maximise/restore button and a close button.

Image Removed

Image Added Insert excerpt _check_box_untick _check_box_untick nopanel true  to have no Windows-style bar at the top of the screen.
Always On Top	Insert excerpt _check_box_tick _check_box_tick nopanel true  to keep the screen on top of other screens. This is useful for a popup window that you want a user to complete before returning to another screen. Insert excerpt _check_box_untick _check_box_untick nopanel true  to allow other screens to be displayed in front.
Keep Data	Insert excerpt _check_box_tick _check_box_tick nopanel true  to allow screen data to be referenced even after the screen is closed. This is useful if an application user needs access to global data available in the system. Insert excerpt _check_box_untick _check_box_untick nopanel true  is the default. The screen data is not required once the screen is closed.
Preload	screens , especially complex screens, can take some time to open, which can feel slow to the application user. Use this option when you need a screen to open quickly. Preloading screens adds to the time it takes PhixFlow to initially start up.  For this reason we recommend you only preload screens that an application user will always want to open. Insert excerpt _check_box_tick _check_box_tick nopanel true  to preload the screen when PhixFlow first starts.  When the user then opens the screen , it displays immediately. The data itself may still take time to load. Insert excerpt _check_box_untick _check_box_untick nopanel true  is the default. The screen does not need to be preloaded. Preloading relates to the screen itself. Any data backing the screen is only loaded when the screen opens, and this may also take time to load.
Cache Locally	If an application user is likely to require the same screen in different stages of a task. Use this option so that, when the user closes and reopens the screen, it loads immediately.  Insert excerpt _check_box_tick _check_box_tick nopanel true  to cache the screen on the application user's client computer when the screen first opens. Insert excerpt _check_box_untick _check_box_untick nopanel true  is the default. The screen does not need to be cached. Caching relates to the screen itself. Any data backing the screen will be reload each time the screen is opened.
Position	By default, new screens are set to Floating. If you want a screen to open with a fixed position, select one of the Pinned drop-down options: Pinned to top Pinned to bottom Pinned to left Pinned to right Floating Use the Pinned options to create a permanently visible screen. This is useful for a navigation area or toolbar that you want to be visible for all other screens. Floating screens do not overlap with pinned screens. When the user maximises a Floating screen, it expands only to the remaining space.
Width	For screens that are not set to Open maximised, specify a screen width in pixels, for example 500px for a small confirmation window. The default size for a popup screen approximately 800px.
Height	For screens that are not set to Open maximised, specify a screen height in pixels, for example 150px for a small confirmation window. The default size of a popup screen is approximately 500px.
Top	Available when Position is Floating. For screens that are not set to Open maximised, set an offset value in pixels to position the screen where it is required. For example, to display a screen as a popup window towards the top left of the screen, set: Top: 60px Left: 60px
Left
Right
Bottom

Screen Elements

Screen elements are specific sections on a screen that posses their own properties, specifically each element can be backed by a different table.

To view a list of the elements for a specific screen, open the 

Menu Items

This section has a toolbar with standard buttons and:

•  Image Modified Show Table-actions

• Insert excerpt
  _filter _filter nopanel true

The grid contains a list of menu items. To add a menu item to the list, click 

1. Click 

   Insert excerpt
   _add _add nopanel true

2. Select 
   • either Add a new sub-menu
   • or Add a new menu item; see Startup Actions
3. PhixFlow opens a new properties tab for a menu item or sub-menu; see Startup Actions for details.

To remove a menu, use the toolbar button 

Mappings

This section has a toolbar with standard buttons. 

Components on the screen, such as buttons or data-components, can  can have actionflows or record-actions. Record Record-actions can take data from attributes in different tables  or views. Where the attributes have different names, you must map the attribute, so that the recordthe record-action recognises action recognises the data. This grid contains grid contains a list of mappings for the components on this screen. 

To configure a mapping, in the screen, right-click a component and select 

Unreachable Actions

This section has a toolbar with standard buttons. The grid displays a list of actionflows that are linked to components on the screen, but do not exist yet.

Actions

This section has a toolbar with standard buttons. The grid displays a list of actions and recordand record-actions that are linked to the screen.

Menus and Toolbars

Screen Toolbar

There is a toolbar above the screen canvas. This provides the following options:

Screen Popup Menu

Right-click on a screen to display its popup menu. The options available depend on where you click. If there are many options, some are moved onto the sub-menu