Entersoft Business Suite^® | Entersoft CRM^® | Entersoft Mobile Suite^®

Technical manual

Identity

Document version 4.0

Software version ESMobile 5.2

Last update December 2022

Copyright

No part of this work may be reproduced, transmitted, stored, or used in any form or by any means, without the prior written permission by Entersoft S.A. Regarding the content of the present document…

It may be altered at any time.
It serves exclusively informative goals.
No guarantee whatsoever is handed out for the possibility of existing mistakes, or the wrongful use or unwanted results, produced by the use of processes hereby followed and recommended.

Περιεχόμενα

1 Introduction
2 Overview screen (ListForm)
3 Photo gallery screen (SFListForm)
- 3.1 Display format / Special settings
4 Selection list screens
5 Data entry screens
6 Informative screens
7 Special screens
8 Business rules
- 8.1 BR syntax
- 8.2 BRs Wizard
9 App customization
10 Ideas & Solutions
11 Appendix

Introduction

The purpose of this document is to provide all the necessary technical information to experienced users who wish to modify the default functionalities of the iOS Entersoft Mobile Suite (ESMobile) application. In brief, the individual objectives are:

To provide detailed implementation instructions for the individual screens of the ESMobile application. Note that the screens, that are either modified or fully implemented at an ESMobile application customization level, are considered custom and are automatically marked with an asterisk.
To provide information about the extension possibilities concerning the functionality schema of the ESMobile application.

Requirements for using the ESMobile application and the present manual include:

being familiar with the interface & use method for each mobile device.
the knowledge of all the necessary actions to install and setup the IIS & Application server
proper set-up of the required equipment

Note that

The present manual applies to all ESMobile platforms (iOS, UWP, Android). The parts that, by way of exception, relate to a specific ESMobile platform, are marked accordingly.
The individual examples of this manual are available for download at the mPortal tool.

Symbols

	iOS platform
	Universal Windows (UWP) platform
	Android platform

Overview screen (ListForm)

The overview screen (ListForm) in its simplest form is used to display data in the form of a list. However, by means of a case-by-case “appendix”, it is possible to extend the ListForm screen with the following features:

Display of the list's numeric data in the form of a Graph.
Redirection, by focusing a list entry, to the Dashboard screen. The Dashboard screen allows the user to expand the ListForm screen information and to directly perform a series of actions.

The elements required to implement a ListForm screen are:

Element	Comment
Command	Using a ListFormCreatorCommand command is required.
Form	In order to implement the display format in its simple form it is necessary to use an AdvancedList.xml file. The Graph screen appendix is implemented in a ChartParams.xml file, while the dashboard screen appendix in an ExtraLayoutParams.xml file.

Next up in this section, you will be provided with detailed implementation instructions for “ListForm” screens, using a specific example.

Screen Data

Example SampleListForm

Defining the ListForm screen data and the command-form link is possible by appropriately configuring the sub-properties of the command file. The command file should be in the Commands sub-folder of the ESConfig or CSConfig area. Attention: the command file name should match the name of the command in the file.

Example

Suppose that we wish to create a screen that displays customer addresses in the form of a list. This list must fulfill the following basic specifications:

Include only active customers.
Display information from the customer & their addresses.
Be sorted alphabetically based on the “Name” column of a person.

Suppose also that the form of this screen is SampleListForm

Property	Comment
FormID	The folder in ESForms or CSForms where the relevant AdvancedList file of the form can be found, namely SampleListform folder for this example.
Title	The label that appears as a screen ListForm title, in this example, the label "Points of Sales".
Filter	The “static” filtering criterion for the data, in this example, the ta.Inactive column.
BaseSelect	The “select query” that specifies the data to be displayed.
ESQueryID	The name of the independent definition file for the base select query. It is automatically filled-in only in the case where, for the purpose of re-using the select query, it’s meant to be defined in an independent file. In such a case, the BaseSelect property must be empty. Note that the independent select query file should be located in the Queries sub-folder of the ESConfig or CSConfig area.
SearchPanelFilter	The alternative search criteria.
SearchPanelID	The name of the independent definition file for the alternative search criteria. It is automatically filled-in only in the case where, for the purpose of re-using the search criteria, they’re meant to be defined in an independent file. In such a case, the SearchPanelFilter property must be empty. Note that the independent select criteria file should be located in the SearchPanels sub-folder of the ESConfig or CSConfig area.
LoadDataOnOpenForm	Right after the screen is called, it displays the data (true), or displays-updates the data after the user fills in the search criteria (false). In cases of a list with a big number of entries, it is recommended to set this property as False. This way, data will appear only after editing the filter criteria, while at the same time clearing the filter criteria will not cause the list to update.
CacheSearchPanel	Maintains the content of entry search criteria (true), or clears them the screen is closed (false).
OrderBy	The “static” sorting criterion for the data, in this example, the p.Name column.

Sorting

Example SampleListForm

Specifying the alternative sorting criteria for an entry list is possible in the command file and by appropriately configuring the SortBy property. If there are alternative sorting criteria specified in the command, the -Sort button appears on the top right part of the screen. By pressing this button it is possible to switch between the available criteria. It is recommended that, in case the user has opted for implementing alternative sorting criteria, the static sorting criterion is also defined as one of them.

Regarding the definition method and the available properties for the alternative sorting criteria, the following apply:

Property	Comment
Caption	The label displayed as the criterion title.
ESCaptionID	Exclusively refers to the product translation process (Translation key).
Expression	The fields – sorting direction of the entries list.
Default	The criterion that has value True is the default sorting criterion of the entry list. This value overrides a possible OrderBy property of the command.

Example

Suppose that we wish to extend our ListForm screen so that, in addition to the person’s “Name” column sorting , there is also the possibility of ascending or descending sorting based on the “ABC class” customer column, while also maintaining the person’s Name as a default criterion.

Search

Example SampleSearchPanel

Specifying alternative criteria for searching an entry list is possible in the command file and by appropriately configuring the SearchPanelFilter property or the SearchPanelID property.

The definition method and search criterion characteristics vary depending on the column type to which the criterion will apply. The available criteria types are: ColumnNames, FieldChooser, DateField, DropDown, Autocomplete & Boolean. Note here that the “Remove filters” button is automatically added to the bottom-right of the alternative criteria screen. Pressing this button directly resets the content of the individual search criteria to their original value.

ColumnNames

Refers to a string-type column and the content is typed in by the user. Regarding the definition method and the available criteria properties, the following apply:

Property	Comment
ID	The criterion SEQ.NO should be unique.
minimumInput	The number of characters we wish to be required in order to directly refresh the entries list. By keeping this property empty, pressing the -Search button is also needed to refresh the entries list
title	The label displayed as the criterion title.
column	The command column on which the criterion is applied. The * character is used to indicate, on a case-by-case basis, the following: xxx, starting with xxx, contains xxx, ends with
default	The default criterion value.
keyboard	For the alphanumeric keypad to appear focused on numbers, set value “num”. Concerns the iOS platform only
soundex	Specifically, for the person’s fields name-address code-item description & catalogue item, it is possible for the search result to be the same, regardless of whether the criteria is typed in uppercase-lowercase or Greek-Latin characters. To activate this feature, it is necessary to: in the column property, specify the column that has undergone the Soundex conversion in the soundex property, specify the SoundexEQUC value lastly, in the SoundexMappingsID property of the ListForm command, specify the SoundexConversion value

Example

Suppose that we wish to implement a search criterion for list entries, based on the person's "Name" column.

FieldChooser

Refers to a string-type column and the content is typed in by the user. Used to aggregate multiple ColumnNames-type criteria into one criterion. Regarding the definition method and the available criteria properties, the following apply:

Property	Comment
ID	The criterion SEQ.NO should be unique.
minimumInput	The same applies as for the ColumnNames criterion. The property is relevant to all individual criteria.
title	The label displayed as the criterion title.
column	The same applies as for the ColumnNames criterion.
soundex	The same applies as for the ColumnNames criterion.

Example

Suppose that we wish to implement a search criterion for list entries, by selecting one of the person's “Address” or “Telephone” columns.

DateField

Refers to a date-type column, which allows the user to select a time period. Regarding the definition method and the available criteria properties, the following apply:

Property	Comment
ID	The criterion SEQ.NO should be unique.
title	The label displayed as the criterion title.
column	The command column on which the criterion is applied.
defaultselection	The default criterion value. The available options are:
	* 3-Today 4-Yesterday 5-Tomorrow	* 6-Current week 7-Previous week 8-Next week

Example

Suppose that we wish to implement a search criterion for list entries, based on the task's "Start date" column. The criterion is set to 3-Today by default.

Boolean

Refers to an integer-type column that always refers to two values (true / false). Regarding the definition method and the available criteria properties, the following apply:

Property	Comment
ID	The criterion SEQ.NO should be unique.
title	The label displayed as the criterion title.
column	The command column on which the criterion is applied. Note that, if the column to which we wish the criterion to be applied is not by nature of the integer type, it must be converted accordingly into an integer.
truetext	The label that appears when the criterion condition is met.
truevalue	The column value when the criterion condition is met.
falsetext	The label that appears when the criterion condition is not being met.
falsevalue	The column value when the criterion condition is not being met.
nonetext	The label that appears if there is no specific value selected.
the room was a one-off room	The default criterion value.

Example-1

Suppose that we wish to implement a search criterion for list entries, based on the "Person type" column. We also want the criterion to allow the user to switch between Legal and Physical person and have value 0-Legal person as the default.

Example-2

Suppose that we wish to implement a search criterion for list entries, based on the task's "Related campaign" column. We also want the criterion to allow the user to switch between tasks within and without the campaign and have no default value. Provided that the “related campaign” column is of GID type, the ViaCampaign column must be used, which has the following definition: cast ( case when t.fCampaignGID is null then 0 else 1 end as Int ) ViaCampaign

DropDown

Refers to a string-type column, which allows the user to select from list of values. Regarding the definition method and the available criteria properties, the following apply:

Property	Comment
ID	The criterion SEQ.NO should be unique.
title	The label displayed as the criterion title.
column	The command column on which the criterion is applied.
default	The label that appears if there is no specific value selected from the list.
query	The “select query” that specifies the data to be displayed in the value selection list. The syntax should be of form: <query>select ValueMember, DisplayMember1, DisplayMemder2 from...</query> where ValueMember is the value based on which the entries will be filtered. DisplayMember1 & DisplayMember2 are the columns that will appear in the DropDown criterion. Filling them in is optional.
selectedvalue	The default criterion value. A fixed value can be specified, or alternatively, a select query. In this case, the syntax should look like this: <selectedvalue>query: select ValueMember from...</selectedvalue>
binding	Restrict the list of values of a criterion, based on the value selected in another criterion. The syntax should be of form: <binding bindelement="" filter=""/> where bindelement, is the id of the criterion based on which the list of values will be restricted. filter is the column based on which the list of values will be restricted.

Example-1

Suppose that we wish to implement a search criterion for list entries, based on the customer's "ABS class" column. We also want the criterion to display a selection list and have category B as its default value.

Example-2

Suppose that we wish to implement a search criterion for list entries, based on the "Task type" column. We also want the criterion to display a selection list and have task type ES.SAP as its default value.

Example-3

Suppose that we wish to implement a search criterion for list entries, based on columns "Area & “Zip code” of the person’s address. We also want the criteria to display a selection list and be able to restrict the list of values of criterion Zip code, based on the value selected for Area.

AutoComplete

Refers to a string-type column that allows the user to find a value by typing and select multiple values. Regarding the definition method and the available criteria properties, the following apply:

Property	Comment
ID	The criterion SEQ.NO should be unique.
title	The label displayed as the criterion title.
column	The command column on which the criterion is applied.
query	The “select query” that specifies the data to be displayed in the value selection list. The syntax should be of form: <query>select ValueMember from...</query> where ValueMember is the value based on which the entries will be filtered.
binding	The same applies as for the DropDown criterion.
multiselect	Multiple selection of values (true) or not (false).

Example

Suppose that we wish to implement a search criterion for list entries, based on the "Task type" column. We also want the criterion to display a selection list and allow the selection of multiple values.

Display Format / List

Example SampleListForm

The displayed elements of the ListForm screen as a list can be set by appropriately configuring the individual properties of the form's AdvancedList file. Note that the ListForm screen consists of two main areas (RowTemplates), the data area (Normal RowTemplate) and the header area (Header RowTemplate). The design specifications differ per area.

Next up in this section, you will be provided with detailed design instructions for the ListForm areas.

Data area

Setting the data range (normal RowTemplate) is mandatory and always refers to the first RowTemplate of the form’s AdvancedList file. Regarding the definition method and the properties available at an area level (RowTemplate) and element level (Cell), the following applies:

Property	Comment
RowTemplate
Height	The area height.
Cell-Required
Type	The ListForm in its simple form only supports TextCell-type elements.
Bounds	The display location of the element. The 4 sizes of this property determine x, y, width & height respectively, with 240 as the maximum screen width.
CellSource	The command column that corresponds to the element.
Cell-Optional
Name	A name for informative purposes.
Visible	Display (true) or hide (false) the element.
Alignment	The alignment of the element’s content with the following values available: Left, Right & Center.
FontSize	The font size.
FontStyle	The font style, with the following values available: Regular, Bold & Italic.
ForeColor	The font color, with the following values available: Black, Blue, Brown, Cyan, Gray, Darkgray, Green, Lightgray, Magenta, Orange, Purple, Red, White & Yellow.
BackColor	The background color, with the following values available: Black, Blue, Brown, Gray, Green, Orange, Red, White & Yellow.
FormatString	The display format of a numeric element. Some typical options are:
	Definition	Result
	{0:G}	16325.62
	{0:C}	16,325.62 €
	{0:N} ή {0:#,#.00}	16,325.62
	{0:P} ή {0:0.00\%}	163.26 %
	{0:#.0}	16326

Example

Suppose that we wish to implement a ListForm screen that displays the following elements in the data area: Name, Address, Telephone & ABC class of the customer. Suppose also that we wish to implement a different display format for the Name element than that of the rest.

Note that

Specifically for an iOS platform and for the ListForm screen to function properly, the form's AdvancedList file must have property SelectedTemplateIndex assigned. In this property should indicate the Normal RowTemplate SEQ.NO, namely SEQ.NO 0.
Specifically for an iOS platform, it is possible to differentiate the elements and display format between Normal and Selected entry. The settings required are:
- Define a second RowTemplate (Selected RowTemplate) in the form's AdvancedList file. The definition method and available properties are exactly the same as described for Normal RowTemplate.
- Specify the Selected RowTemplate SEQ.NO in property SelectedTemplateIndex.

Header area

Defining the header area (Header RowTemplate) is optional and is done by indicating the RowTemplate SEQ.NO in the TemplateIndex property of section HeaderRow and by assigning property true to the ShowHeader property. Regarding the definition method and the properties available at an area level (RowTemplate) and element level (Cell) of the area, the following applies:

Property	Comment
RowTemplate
Height	The area height.
BackColor	It must be specified by using an RGB color code and should be in format #0,0,0. Concerns UWP & Android platforms only.
Cell-Required
Type	Header RowTemplate only supports TextCell-type items.
Bounds	The display location of the element. The 4 sizes of this property determine x, y, width & height respectively, with 240 as the maximum screen width.
CellSource	The label displayed as the title. It should be specified in format ""Title"" where label quot; indicates the quotation marks.
Name	Exclusively refers to the product translation process (Translation key).
Cell-Optional
Visible	Display (true) or hide (false) the element.
Alignment	The alignment of the element’s content with the following values available: Left, Right & Center.
FontSize	The font size
FontStyle	The font style, with the following values available: Regular, Bold & Italic.
ForeColor	The font color, with the following values available: Black, Blue, Brown, Cyan, Gray, Darkgray, Green, Lightgray, Magenta, Orange, Purple, Red, White & Yellow.
BackColor	The background color, with the following values available: Black, Blue, Brown, Gray, Green, Orange, Red, White & Yellow.

Example

Suppose that we want the ListForm screen of our example to also display the header area.

Display Format / Graph

Example SampleListFormChart

As mentioned above, adding a ChartParams.xml file to the ListForm screen as an “appendix” also enables the ability to display the data of a list as a graph. The available graph types are: Column, Bar, Pie, HalfPie & Doughnut.

Example

Suppose that we wish to implement a ListForm screen that displays the top 10 customers based on turnover. Suppose also that we want it to display them as a list, as well as a Bar-type graph.

In order to do this, a ChartParams.xml file must be added to the folder where the form's AdvancedList file is also located. In our example, that folder is SampleListFormChart.

Dashboard screen

Example SampleDashboardForm

As mentioned above, the Dashboard screen is an “appendix” to the ListForm screen, which allows the user, by focusing on a list entry, to expand the information of the ListForm screen, as well as directly perform a series of actions. Next up in this section, you will be provided with detailed implementation instructions for the Dashboard screen, using a specific example.

Example

Let say that we wish to implement a ListForm screen which, in addition to displaying customer addresses in a list, also provides direct access to the customer's additional information: VAT number, Occupation, Family, basic contact Information & basic Financial data.

In order to do this, an ExtraLayoutParams.xml file must be added to the folder where the form's AdvancedList file is also located. In our example, that folder is SampleDashboardForm.

Entries list

The display format of the entries list follows a default template consisting of 1 image column and 2 data columns-rows. Therefore, the display format of the entries list is "redefined" and this can be done via the following properties of the form's ExtraLayoutParams file:

Property	Comment
imagecolumn	The command column that corresponds to the image file name.
imagefolder	The folder where the image file is located.
title	The command column that corresponds to element Column-1 & Row-1. This element displays in Bold.
formtitle	The command column that corresponds to the Dashboard screen title. Note that, if this property is empty or does not exist, the title of the Dashboard screen uses the title property.
titlewidth	The width of the title element (%).
subtitle	The command column that corresponds to element Column-1 & Row-2.
subtitlewidth	The width of the subtitle element (%).
info1	The command column that corresponds to element Column-2 & Row-1.
info1width	The width of the info1 element (%).
Info2	The command column that corresponds to element Column-2 & Row-2.
Info2width	The width of the info2 element (%).

Main area

The additional elements that our example requires are defined in section extraparamsof the form's ExtraLayoutParams file. For the ergonomic display of the elements, defining multiple extraparams sections is also possible. Regarding the definition method and the available area properties, the following apply:

Property	Comment
Area
title	The label displayed as the area title.
ID	The area’s SEQ.NO, which should be unique.
Element
name	The command column that corresponds to the element.
caption	The label displayed as the element’s caption.
type	The element type. Values email, facebook, location, mobile, skype, telephone, twitter & web automatically give the item the corresponding functionality (e.g. by assigning the location type to an element, pressing it redirects the user to the map).

Other areas

The other areas that make up a Dashboard screen are its pages-segments and menu buttons. The information displayed in these areas require the appropriate definition, on a case-by-case basis, of the actions button.

Action buttons (ButtonCell)

The action buttons always refer to a command to be executed. The action buttons can be defined in the form's AdvancedList file and by using a ButtonCell-type element. Elements of this type can be defined in the RowTemplate of the data area.

Note that

Specifically for an iOS Platform, it is mandatory to specify ButtonCell-type elements in RowTemplate for the selected entry, i.e. The RowTemplate specified in property SelectedTemplateIndex.

Regarding the definition method and the available properties of a ButtonCell-type element, the following apply:

Property	Comment
Required
Type	The element must be of type ButtonCell.
Text	The label displayed as the button title.
CellSource	The select query column of the ListForm screen with which the variable [CURRENT] or [PARENT] of the command to which the button refers.
Name	The command and the “specifications” of its execution. The required property configuration varies considerably, depending on the command type (prefix) of the button.
	* A button for a view-type command of an entry or entries list, Edit#Command, is combined with variable [CURRENT]
	* A button for adding a new entry type of command, New#Command, is combined with variable [PARENT] Note that, in special cases where there is a need for a second variable, it can also be combined with variable [CURRENT]. The column of variable [CURRENT] is specified as the button’s suffix.
		For a button of adding a new plan-based measurement (PARENT=CellSource) at a selected point of sales (CURRENT=suffix)

	* A button for adding a new document-type of command, Doc#Command#DocType, is combined with the [PARENT] variable, but also requires the document type to be specified as suffix.
		To enter a new order (suffix=1) on a selected job (PARENT=Cellsource)

	* A button to switch commands based on a condition, CASE#Column#Value1#Command1#Column#Value2#Command2 is combined with variable [CURRENT]. Note that the Column should always refer to a column of the select query of the ListForm screen.
		For a button where the screen to be displayed varies according to the type of selected, (CURRENT=CellSource)

	* A button to switch command types based on a condition, ESCASE[#]Column[#]Value1[#]Button1[#]Column[#]Value2[#]Button2 is dynamically combined, depending on the button type, with variable [CURRENT] (Edit-type command) or variable [PARENT] (New-type command). Note that the Column should always refer to a column of the select query of the ListForm screen.
		In order to toggle between the new appointment button at a selected point (PARENT=CellSource) or a button to view an existing one (CURRENT=Cellsource), depending on the asTask column value.

		Note here that, in special cases where there is a need for more than one variable, the variables and their columns are specified as the button's suffix. In this case, the CellSource property must be empty.

DesignName	The button's show or hide “specifications”. It consists of the following two parts: The button’s hide conditions (Not Applicable). The syntax should be of form: [NA]Column1=Value1;Column2=Value2[NA]. Note that the Column should always refer to a column of the select query of the ListForm screen. The applications-platforms where the button is available. The syntax should be of form: #AppIDPlatforfID1#AppIDPlatforfID2 where:
	Application			Platform
	8		Merchandising	2	iOS
	22		Field Service	3	Android
	322		xVan	4	UWP
	1024		Medical Representative	9	UWP & Android
		To (a) hide the button for an C customer of ABC class and to (b) show the button on all platforms, but only in the Merchandising application.
		<Property Name="DesignName" Value="[NA]ABCClass=C[NA]#82#89" />
Optional
ImageDefault	The image used as the button’s icon. Note that in the case of the Dashboard screen the property is inactive and therefore specifying an icon is unnecessary.
Visible	Show (true) or hide (false) the button. Specified only in case the user wants to hide the button, for all applications-platforms, from the Dashboard screen menu buttons -Actions, -Online, or -Information.

Pages-Segments

It is recommended that the ButtonCell-type elements related to information display should be included in the pages-sections area of the Dashboard screen, namely the Segments section of the form’s ExtraLayoutparams file. Regarding the definition method and the available area properties, the following apply:

Property	Comment
Title	The label displayed as the tab title.
Position	The page’s SEQ.NO, which should be unique.
Command	The ButtonCell that corresponds to the information to be displayed. This property’s content should match the Name property content of the ButtonCell. Note that the maximum number of commands per page is 4, with the exception of the first page (Position 0) where it's 3 commands.
IsMainSegment	The first page (Position 0) has value true, while the other pages have value false.

Example

Suppose we wish to expand the Dashboard screen to have direct access to customer-related local database information, such as: Contacts, Open tasks, History of Appointments & Sales. Suppose also that we wish this information to appear in distinct segments of the Dashboard screen pages.

Note that

In case the design needs of the Dashboard screen are quite specialized, the specific elements that related to pages-segments can be defined using section ESTabs. Note here that, if the user chooses to use section ESTabs, section Segments is automatically rendered inactive. The configuration setup instructions for section ESTabs are provided below, in section Pages-Segments/ESTabs.

Menu buttons

It is recommended that ButtonCell-type elements that relate to direct execution of an action are included in the default buttons of the Dashboard screens. This is possible by using section negotiations of the form's ExtraLayoutParams file. Configuring section newactions is not mandatory, but is strongly recommended to facilitate user navigation around the Dashboard. The Dashboard default menu buttons and the settings required to add them, on a case-by-case basis, are:

	Setting	Comment
Actions		Adding buttons related to adding a new entry is recommended.
Online		It is recommended to add buttons that concern displays information at a direct connection with the server.
View		It is recommended to add a button that redirects the user to the Data entry screen of the current entry.
Attachments		It is recommended to add a button that redirects the user to the attachments management screen.
Dropbox		It is recommended to add a button that redirects the user to the Dropbox application. Concerns the iOS platform only.
Information	It is automatically configured, by collecting all the buttons, from the form's AdvancedList file, that have not been added to another Dashboard segment or button. The order in which these actions are displayed depends on the order set in the form's AdvancedList file.

Example

Suppose that we wish to expand the Dashboard screen to meet the following needs:

Allows the user to directly call actions for new Order & new Collection.
Make it possible to display - in direct connection with the server- reports Customer tab & Customer aging of accounts.

Note that, specifically for menu button -Actions, it is possible to configure options displayed so that only the "popular" ones are displayed initially and, when pressing "…", all of them display. To enable this feature, the following settings are required:

Add, to the form’s AdvancedList file, a ButtonCell-type element, with value More in property Name.

<Cell Type="Resco.Controls.AdvancedList.ButtonCell">
<Property Name="Text" Value="..." />
<Property Name="Name" Value="More" />
<Property Name="DesignName" Value="#82#89" />
</Cell>

Add, to section newactions of the form’s ExtraLayoutParams file an element with the following definition and activate the subcommon property in all the not popular options of the -Actions button

<newaction>
<command>xxx</command>
<online>false</online>
<subcommand>true</subcommand>
</newaction>
<newaction>
<command>More</command>
</newaction>

Special settings

This section shall briefly, as well as by means of a specific example, present the form's ExtraLayoutParams file properties, that allow for further configuration of the behavior of a Dashboard screen.

Property	Comment
onclickcommand	By filling in this property, an action button allows the user, by focusing on a list entry, to override the display of the Dashboard screen and to directly display the screen that corresponds to the button. In case this functionality is selected, it is recommended to include the action button concerning the transition to the Data entry screen of the current entry.
AlertCommand	By filling in this property an action button allows the user, by focusing on a list entry, to display a notification message under conditions. Note here that the display condition and message content are set at the special type command Alert Command and by using the ShowMessage property of the command. Note also that, as with all action buttons, this one must also be specified in the AdvancedList file of the ListForm screen. Concerns the iOS platform only.
		To display a message when focusing on a “Competitors” list entry:

action1command	By filling in an action button in this property, this button is automatically added to the top-right of the screen Dashboard as an icon. Up to 3 buttons of this format can be set (properties: action1command, action2command & action3command). A classic example of using this functionality is the Calendar Dashboard screen that displays the Start, End, and Cancel appointment actions in icon format. Note here that each icon can be defined in the AdvancedList file of the form, in particular in the ImageDefault property of the action button.
		For the start appointment button of the Calendar Dashboard screen

primarykeycolumn	It is possible to automatically refresh, when running an SQLCommand-type of command, the data displayed on the Dashboard screen. To make use of this feature, it is necessary to: Specify, in the primarykeykolumn property of the column that constitutes the unique identification key of an entry. Specify, in the primarykeyquerycolumn property of the table.field that constitutes the unique identification key of an entry. In case the unique identification key is composed by more than one field, their “composition” (e.g. c.GID \|\| p.GID) should be specified. Special attention should be paid, in order to include both the specified column and the table.field to the select query of the ListForm command. Note here that enabling the auto-refresh functionality requires you to specify “true” in the RefreshParent property of command order to be executed.
		To refresh the Calendar Dashboard screen after executing the “Finish” appointment action (command SQLAppComplete)

Advanced functionality

Configure a selected entry

Example SampleListForm

Especially on an iOS platform, and if, for any reason, we wish the ListForm screen not to be expanded with the Dashboard appendix, it is also possible to display a action button (ButtonCell) type of element, by simply focusing on a list entry. The following settings are required to enable this feature:

Specify a ButtonCell-type of element in the AdvancedList file of the form. The way in which this type of element is defined and its available properties are exactly the same as those described in the corresponding section of the Dashboard screen, except that here it is also recommended to specify the icon with which the button becomes visible, in property ImageDefault.
Do not add the ExtraLayoutParams.xml file to the ListForm folder.

Example

Suppose that we wish to enable the ListForm screen to directly call the New order action.

Data bulk update

Example SampleListFormBulkUPD

A ListForm screen can be used as a data bulk update tool for all the selected entries in a list. The following settings are required to enable this feature:

Button configuration. The button that calls the action to be performed is configured using the special type of command InvPopCommand. The distinctive feature of this type of command is that it allows an update query to be called (BaseUpdate property).
Button activation. Activating the button is possible by indicating the InPopCommand file in the RightButtonDefinition property of the ListForm command. The syntax of the property should be [POP]InvPopCommand. Filling in this property expands the ListForm screen with the default menu button -Actions. Please note here that for the screen to function properly, it is required that:

The first column of the ListForm command select query refers to the unique identification key of a list entry.
In the ListForm folder there is the ExtraLayoutParams.xml file.

Example

Suppose that we wish to implement a ListForm screen that will be used as a bulk update tool for the site’s “Flag-1” field. Suppose also that the bulk update action has been implemented through the SampleListForBulkUPDAction command.

Pages-Segments / ESTabs

Example SampleESTabs

As mentioned above, the definition of the elements related to the pages-segments of a Dashboard screen (Segments section of the ExtraLayoutParams file) is subject to specific limitations in terms of the number-size and display location of the segments per page. If we wish to design a Dashboard that overrides these limitations, the tabs-segments can be defined in the ESTabs section of the ExtraLayoutParams file. At the same time, using the ESTabs section, it is possible to display the data either as a graph or as a percentage index.

Regarding the definition method and the properties available at a page level (ESTab) and a segment level (ESTabItem), the following applies:

Property	Comment
ESTab
Caption	The label displayed as the tab title.
ESCaptionID	Exclusively refers to the product translation process (Translation key).
RowDefinitions	The number of rows on the page. At this stage, the Height property is inactive.
ColumnDefinitions	The number of columns on the page. At this stage, the Width property is inactive.
ESTabItem
Command	The ButtonCell that corresponds to the information to be displayed. This property’s content should match the Name property content of the ButtonCell.
Row, Column, RowSpan, ColumnSpan	These 4 sizes determine the segment’s position-height-width, respectively.
IsMain	On the page that contains the main area of the Dashboard screen, value “true” is indicated, while “false” is indicated on the other pages.

Example

Suppose, that we wish to implement a Dashboard screen on the Point-of-sales list, where the “General” page has the format shown in the image, meaning 4 unequal segments, in one of which a Graph-type element has been placed.

Photo gallery screen (SFListForm)

Example SampleSFListForm

The photo gallery screen (SFListForm) is typically used to display data as an image, while simultaneously providing, by focusing on an entry, the following features:

Redirection to another screen for additional information.
Immediate execution a series of actions.

The elements required to implement a SFListForm-type screen are:

Element	Comment
Command	The user is required to use a ListFormCreatorCommand-type of command: Regarding the elements defined at a command level (data, sorting & searching), the exact same apply as described for a ListForm screen.
Form	In order to implement the screen's display format, it is necessary to use an AdvancedList.xml file. Regarding the definition method of the elements area and title area display, the same apply generally as described for a ListForm screen This section shall briefly, as well as by means of a specific example, present both of the points that differ and those that are distinctive features of a SFListForm-type screen.

Example

Suppose that we wish to implement a screen that displays our customer list but, instead of displaying it as a list, displays it as a photo gallery, using the company logo as a picture. Suppose also that we wish to display, apart from the logo, the customer name and the company's headquarters address-phone number.