Card View FastTab Actions
- How do I modify the field order within the Card View FastTab?
- How do I add or remove unbound functions for customization?
- How do I set related pages to fields using different relation types (e.g., Simple Lookup, Drill Down)?
- How do I apply relation filters and conditions to refine content in related pages?
- How do I create a line link between headers and lines using Drill Down relations?
- How do I configure multiple actions or functions for a Field or Function type field?
- How do I arrange a page into sequential subpages for data insertion?
- How do I define fields for complex barcode scanning?
- How do I toggle visibility of objects or customize hidden fields in the mobile application?
Tip
Summary: This topic outlines actions for configuring the Card View FastTab in COSMO Mobile Solution. It includes steps for field order modification, adding unbound functions, setting related pages, applying relation filters, and organizing pages into subpages.
Unless otherwise specified, the actions described in this topic are accessible from the Manage menu on the Card View FastTab.
Field Order Modification
Choose the Move Up and Move Down actions to modify the field order by moving a line higher or lower. Moving fields between sections (Field List, Function List, Filter List) is not possible.
Add or Remove Unbound Functions
Choose the Add Unbound Function or Remove Unbound Function action to open a list that contains predefined and developed unbound functions to add or remove.
Set Related Page to a Field
The Related action opens the Relations page where related page(s) can be set to the selected field in the Card View FastTab.
The supported Relation Types are:
- Simple Lookup and Conditional Lookup are for scenarios in which you would like to choose a value from a related list. In the mobile application, an icon marks these kind of fields.
- Drill Down, Conditional Drill Down types are used for opening a related page.
Tip
For custom development, it is recommended to create a field with an empty source expression in order to use it as a (conditional) drill-down.
The defined relations are shown in the Relation Type field in the line in the Card View FastTab.
In the Relations page, specify the linked page in the Related Service Name field. To use a Lookup type relation, the Related Field Name field must be filled; otherwise, the relation will function as a Drill Down.
Multiple Lookup and Drill Down type lines can be defined.
Important
If you specify a Drill Down Relation Type, the object will not be available in the mobile application as a field, but it will be shown on the function bar if the field is set to Visible.
To initialize default values for a Card type page, which is opened via a Drill Down or a Conditional Drill Down, select the Fill Default Value checkbox in the Relations page.
Relation Filters
On the Actions menu, choose the Relation Filters action to open the Relation Filters setup page where filters can be specified for all type of relations for the selected Relations record. Using filters, the content of the appearing page will be reduced.
| Field | Description |
|---|---|
| Related Field Name | Specifies the field that will be filtered. |
| Filter Type / Filter Value | Specifies what the filter does. The options are: - Filter: specifies a filter expression. Filter expressions commonly used in Business Central are also available in COSMO Mobile Solution, except for parentheses: ( ). For intervals, use '=<*filter value*' and '=>*filter value*' instead of '..*filter value*' and '*filter value*..'. All filter expressions apply together to the content of the linked page. - Field or Variable: a field name or a variable code can be selected from the drop-down list in the Filter Value field. |
Defined relation filters are indicated in the Filters field in the Relations page.
Relation Conditions
Conditional Lookup and Conditional Drill Down entries are created if a relation condition is defined.
On the Actions menu, choose the Relation Conditions action to open the Relation Conditions setup page where conditions can be specified for Drill Down and Simple Lookup type relations for the selected Relations record. Conditions allow you to predetermine in what cases a related page should be opened.
| Field | Description |
|---|---|
| Field Name | Specifies the field that will be filtered. |
| Filter Type / Filter Value | Specifies what the filter does. The options are: - Filter: specifies a filter expression (e.g. >0, false, 100..200, etc.). - Variable: a variable code can be selected from the drop-down list in the Filter Value field. The usual filter operators (=, <, >, <=, >=, <>, ..) can be used with both filter types. Multiple filter expressions can be defined. In this case, all filter expressions apply together to the content of the linked page. |
Defined conditional lookups are indicated in the Conditional field in the Relations page.
Create Line Link to Header with Drill Down Relations
When using Headerline page types, there is a header section and a lines section. The lines are linked to the header using a Drill Down relation (Drill Down or Conditional Drill Down) via a specific dummy field that is specified as Lines. Once this relation is made, select the Lines checkbox in the Card View FastTab. Note that this checkbox can only be selected on one line.
A defined line is indicated in the Lines field in the Relations page.
Multi-Level Lookup
To be able to use multi-level lookups, see Multi-Level Lookup.
Add Further Actions or Functions to a Field
Field Actions allow you to define and manage custom actions for individual fields in the Card View FastTab of COSMO Mobile Solution. These actions can automate processes or perform other logic when interacting with a specific field in the mobile application.
With field actions, you can define what should happen:
- before the field interaction is processed,
- after it succeeds,
- after it fails, or
- after it is cancelled.
Typical uses include showing a message, asking for confirmation, refreshing page data, closing the page, closing ancestor pages, or running another function or drill-down target.
Structure of Field Actions
Field actions are organized in three levels:
| Element | Purpose |
|---|---|
| Action Group | A container for one field action scenario. It belongs to one field and contains the conditions and actions that define that scenario. Action groups are evaluated in a defined order. |
| Action Condition | A condition inside an action group that restricts when the group is applicable. Conditions refer to a field and compare it by a filter, another field, or a variable. |
| Action | The executable instruction inside an action group. Each action defines when it runs, what it does, and optionally which parameter it uses. Actions run in the order defined inside the group. |
Action Groups
The Action Groups page is the entry point for field action setup.
Each action group contains:
- Description: identifies the purpose of the group.
- Enabled: determines whether the group is active. Action groups are enabled by default.
- Action Conditions: define when the group is relevant.
- Actions: define what the system should do.
Choose the Move Up and Move Down actions to modify the evaluation order of the action groups.
Note
Field action groups are maintained on the global configuration. User-specific copies are inherited, but user-specific action groups and their nested records cannot be inserted or deleted from this setup page.
Action Conditions
The Action Conditions part defines the criteria for an action group. If no action conditions are defined, the action group is applicable for every validation.
Each condition consists of the following fields:
| Field | Description |
|---|---|
| Field Name | Specifies the page field or related flow field that is checked by the condition. |
| Condition Type | Specifies how the comparison value is resolved. The supported options are Filter, Field, and Variable. |
| Condition | Specifies the actual filter expression, field name, or variable code, depending on the selected Condition Type. |
The supported condition types are:
- Filter: compares the selected field against a filter expression.
- Field: compares the selected field against another field.
- Variable: compares the selected field against a user variable.
Actions
The Actions part defines the behavior that is executed by the action group.
Each action consists of the following fields:
| Field | Description |
|---|---|
| Run Time | Specifies when the action is triggered. The supported options are On Before, On Success, On Failed, and On Cancelled. |
| Action Type | Specifies the action to execute. The available options depend on the selected Run Time. |
| Action Parameter | Specifies the parameter for the selected action type, if required. Depending on the action type, this can be a message template, a target function or drill-down object, or a service name. |
Choose the Move Up and Move Down actions to modify the execution order of the actions inside the current action group.
Supported Run Time and Action Type Combinations
The following combinations are supported for field actions:
| Run Time | Action Type | Action Parameter | Description |
|---|---|---|---|
| On Before | Confirmation Message | Select a message template. | Shows a confirmation message before the field action continues. This is the only action type allowed for On Before. |
| On Success | Run Function | Select a function, Drill Down, or Conditional Drill Down target from the same service. | Runs another target after the field action succeeds. The target must exist and must be a function or a drill-down-capable field. |
| On Success | Message | Select a message template. | Shows a message after the field action succeeds. |
| On Success | Refresh Data | Leave empty. | Refreshes the current page data after successful execution. |
| On Success | Close Page | Leave empty. | Closes the current page after successful execution. |
| On Success | Close Ancestor Page | Select a global page customization service name. | Closes previous pages in the stack until the specified page is reached. If the specified service is not in the stack, all open pages are closed. |
| On Failed | Run Function | Select a function, Drill Down, or Conditional Drill Down target from the same service. | Runs another target after the field action fails. |
| On Failed | Message | Select a message template. | Shows a message after the field action fails. |
| On Failed | Refresh Data | Leave empty. | Refreshes the current page data after failed execution. |
| On Cancelled | Run Function | Select a function, Drill Down, or Conditional Drill Down target from the same service. | Runs another target after cancellation. This is meaningful only when cancellation can actually happen. |
| On Cancelled | Message | Select a message template. | Shows a message after cancellation. This is meaningful only when cancellation can actually happen. |
| On Cancelled | Refresh Data | Leave empty. | Refreshes the current page data after cancellation. This is meaningful only when cancellation can actually happen. |
Note
For Confirmation Message and Message actions, the Action Parameter is optional. If no message template is configured, the mobile application shows a default confirmation or default message.
Important
If an action group contains On Cancelled actions, cancellation can only occur when a confirmation is shown before execution. This confirmation can come from an On Before action with Confirmation Message in the same group, or from another applicable action group (including one from a different field).
Order of Execution
Field actions use ordering on two levels:
- Action Group order controls the evaluation order of the groups on the field.
- Action order controls the execution order inside one group, but only among actions with the same Run Time.
The Run Time values already define a fixed execution sequence that cannot be changed by reordering lines. For example, an On Before action is always executed before any On Success, On Failed, or On Cancelled action, even if one of those actions is moved above it in the list.
Choose the Move Up and Move Down actions on the corresponding page or part to modify these orders.
Add Further Actions or Functions to a Function
Multiple actions or functions can be triggered by a Function type field.
Select a Function type field and then choose the Function Action action to define when and which actions or functions should be triggered in a predefined order.
| Run Time Option | Function Action / Action Caption / Action Parameter Description |
|---|---|
| Before Action | - Skip Confirmation: Default value of a Function Action. This line gets automatically created for every Function type field. - Refresh Data: Refreshes all data of the current page. - Custom Confirmation Message: Custom message will be shown in the mobile application. Choose an Action Parameter from the Message and Title Template page. - Parameter Page: It is possible to open a parameter page and pass certain parameters. The Action Parameter field should contain the Drill-Down type field that points to the parameter page. Check the relation of CCSMSSerialNoCreationWS and CCSMSItemTrackingListWS pages for more information. Correct order of Function Actions: start with confirmation-related, follow with refresh-related, then end with a single "Parameter Page" action, if necessary. |
| After Action Succesful | - Close Page: Closes the current page. - Refresh Data: Refreshes all data of the current page. - Open New Page: Opens a new page. - Open Next Record: Opens the next record. - Refresh Parent: Refreshes the page the where the current page was opened from. - Confirm Message: Custom message will be shown in the mobile application. Choose an Action Parameter from the Message and Title Template page. - Close Ancestor Page: Closes all pages of the current stack until it reaches the page that was set as a value in the Action Parameter field. If that page is not in the stack, all open pages are closed. Multiple pages can be set using a separator. - Clear List Search: If a List and Card type page's Card part was opened as a result of a Quicksearch, and you close the page, the search field will be emptied; therefore, the complete list will be shown instead of the results of the previous search. - Print Document: Prints a report that was set in the Action Parameter field and was previously defined in the Custom Report Settings in the current page. If the Action Parameter field is empty, the default report will be printed. - Print Label: Prints a label that was set in the Action Parameter field and was previously defined in the Custom Report Settings in the current page. Correct Order of Function Actions: start with other function actions (any actions not related to refresh, drill-downs, new pages, or next records), then place refresh-related actions in the middle to update the necessary data or state, and finally end with drill-downs, new page actions, and next record actions to finalize the process. |
| After Action Failed | - Refresh Data: Refreshes all data of the current page. - Close Page: Closes the current page. - Confirm Message: Custom message will be shown in the mobile application. Choose an Action Parameter from the Message and Title Template page. - Close Ancestor Page: Closes all pages of the current stack until it reaches the page was set as a value in the Action Parameter field. If that page is not in the stack, all open pages are closed. Multiple pages can be set using a separator. Correct order of Function Actions: start with refresh-related function actions, follow with close-related actions, then end with confirmation-related actions. |
| Next Function | Triggers the chosen Function, Drill Down, or Conditional Drill Down. |
| After Cancelled | This function can only be utilized with a confirmation. If the confirmation message has been canceled, invoking this function action type allows for the triggering of another function. In this scenario, the Function Action should be set to Run Function, and the Target Object should specify the function to be triggered. |
Choose the Move Up and Move Down actions to modify the action order.
Note
If the Skip Confirmation option is set, the Custom Confirmation Message will not be shown in the mobile application.
The same Run Time options can be set multiple times.
The Close Page and Close Ancestor Page options should be set at the end of the order but should be defined before Next Function's function actions.
Multiple Sided View
You can arrange a page into sequential subpages in the mobile application to determine the order of data insertion and create a comprehensible page structure.
Note
The Multiple Sided Page toggle must be turned on in the General FastTab to use this feature.
To define the subpage, field, and function order choose the Multiple Sided Settings action.
The Multiple Sided Settings page contains all objects of the Card View FastTab, although upon opening the page you will see only those which are set as visible. To change this view option, choose the Show All action.
A subpage section represents a separate page within the current page in the mobile application. To add a Subpage, choose the Insert New Subpage action. You can remove the last one by choosing the Delete Last Subpage action.
Every Subpage contains Field List and Function List parts according to the Card View FastTab. You can move fields and functions/actions across subpages by choosing the Move Up and Move Down actions.
The Field Type, Visible, and Editable fields are non-editable and are inherited from the Card View FastTab.
In the mobile application, starting from the second subpage, previously provided field values can be shown at the top of the screen. If you want to remove a field from this part of the page, select the Hide From Summary checkbox for that field.
Define Fields for Complex Barcode Scanning
It is possible to populate multiple fields by a single scan on a complex barcode. For more information, see Complex Barcode Function.
Show Visible Objects Only
If you would like to see object that are currently visible in the mobile application, choose the Show the Visibles action
Show or Hide Fields
For better user experience, uncommonly used customization fields like Function Button Picture, Auto Focus Mode, Variable Default Value, Default Value, and Default Value Caption are hidden by default. Choose the Show More action to reveal them.
Properties Menu
The Properties menu contains actions for clearing the Visible, Editable, Filterable, and Searchable checkboxes for all objects in the Card View FastTab.
Feedback
Submit feedback for this page .