Configuration

COSMO Mobile Solution Page Customizations

Page Types in the Mobile Solution Configuration

Task Link
Customizing page types in COSMO Mobile Solution General FastTab fields

The specification is relevant within the context of the configuration for FDC only for behavior during configuration. In this context, there are several types of pages available:

  • List pages: These pages display records in a list format, with configured fields appearing as columns. They are commonly used for tasks such as selecting lookup values or presenting summary lists.

  • Card pages: These pages present information in a card layout, with fields displayed as labels before the field value. They are typically used for displaying detailed information, such as in detail cards.

  • Journal pages: These pages have a presentation similar to the Card page type but are specifically designed for completing ledger entries. They support multi-page presentation of information, which is useful for processes like FDC processes.

It's worth noting that other page types beyond these three are not supported by FDC.

FDC Page Types

  • FDC Process: This process describes the procedure for factory data capture (FDC). It encompasses several steps:

  • Initializing the record: This step is implemented via Default Values in the Page Customization.

  • Populating mandatory and other fields: For instance, this involves the selection of work order, resource, and entering quantity.

  • Posting the record: This step is implemented via the default action associated with the process. The default action is automatically executed when the conditions are met (e.g., display of the action "Come"). The execution of the action is linked in the processing process of the "Terminal Processor."

  • Actions are displayed at the bottom of the page.

  • Item Journal Process: This process is akin to the FDC process, but it pertains to the item ledger entry. While the functionality is prepared, it has not been implemented yet.

  • Page: This refers to the presentation of a page solely for displaying information. It may include selection lists, overviews, and actions displayed at the bottom of the page.

  • Dashboard: This component delineates a dashboard featuring overview lists (e.g., order backlog, work backlog) and containing possible composite actions to initiate sub-processes such as Come, Leave, Details, etc. The actions are displayed in the right area of the page in the action container.

Functions

Task Link
Customizing page actions in COSMO Mobile Solution Card View FastTab Actions

A function is provided through the underlying Web service page. However, there are prerequisites for accessing this function. Specifically, the function must be declared in the WebService with the [ServiceEnabled] attribute.

Standard functions serve as actions in the terminal page. These actions are responsible for initiating processes within the system. When it comes to actions for processes, they are designed to initiate a classic process. This initiation process requires programming via an event in the codebase. Examples of such processes include Assign Lot and Assign Serial. However, there are exceptions to this rule. Standard actions for a process in the BDE, such as Come, Leave, Register and Deregister, do not require separate programming and are readily available for use.

Actions to open pages are configured as function actions within the system. This configuration involves a sequence of steps. First, the system executes the next function in the defined process. Following this, it selects a drilldown field with a pre-configured relationship, which in turn triggers the opening of the desired page.

Supported Action functions are categorized as follows:

  • Actions before function: These actions are executed before the function is performed. They include refreshing data and displaying a custom confirmation message.

  • Actions after successful function: After the function is successfully executed, certain actions are performed. These actions encompass refreshing data, displaying a confirmation message, clearing the page, and closing the page.

  • Actions after function failure: In case the function encounters an error or failure, specific actions are taken. These actions involve refreshing data, displaying a confirmation message, and closing the page.

  • Next function: Once the current function completes its execution, the system proceeds to the next function in the defined sequence.

Supported Functions for Factory Data Capture

  • Labels / Captions:

    • These are used for pages, where they are displayed as titles on the terminal, as well as for fields and actions.

  • Multi-page cards and processes:

    • This feature allows for the creation of cards and processes spanning multiple pages.

  • Client visibility:

    • Specifies whether certain elements are visible to the client.

  • Relationships in fields:

    • There are two types of relationships:
      • Drilldown:
        • This acts as a dropdown template for an action to call a new page. It is configured via the Relationships action.
      • Lookup:
        • This is used to open a dependent list for selecting a record field. It is also configured via the Relationships action.

  • Filters:

    • Filters can be applied at various levels:
      • Page filters
      • Filters in relationships
    • Additional filters can be added via an event receiver, which is implemented in codeunit 5308658 "CCS FDC Terminal Event Mgt."
      • HandleFilterRelatedRecord:
        • Provides an event for implementing additional filters at the record level. This is necessary if filtering of dependent records in relationship filters is not sufficient or if additional calculations for filtering outside of the underlying record are required.
      • HandleFilterMobilePageCustLineFields:
        • Provides an event for implementing additional filters at the field level. This is necessary if filtering at the table level is not sufficient or if additional calculations for filtering outside of the underlying record are required.
      • HandleOnAfterGetContitionalFilterForControls:
        • Provides an event for implementing additional filters for actions. This is necessary if configuration via "conditional views" is not sufficient or if additional calculations for filtering actions outside of the underlying record are required.
      • HandleOnAfterGetFieldValueForDashboardControl:
        • Provides an event for implementing additional information display in fields. This is necessary if displaying calculated fields beyond the functionality of flow fields is needed. For example, if the value of a field is directly obtained from a page, codeunit, or table function.

  • Conditional Views:

    • These are used to apply filters for the conditional display of fields based on specific criteria or conditions.

  • Actions:

    • Actions allow for the execution of tasks within the BDE (Business Data Entry) process.
    • These actions are defined in the Web service page "CCS FDC WS MS Input Jnl."
    • All actions within a fdc process are predefined. They include standard actions such as
      • Come
      • Leave
      • Break
      • WorkAreaChange
      • Register_WOL
      • Deregister_WOL
      • Register_Output
      • Register_Consumption
      • Register_Scrap

Unsupported Functions for Factory Data Capture

  • Field names (not Captions) in the Web service differing from table field names:
    • Editing of records is enabled only in the BDE capture journal process.
    • Deleting records is not supported.
    • Direct execution of actions outside the BDE process is not allowed.
      • Actions are defined in the Web service page "CCS FDC WS MS Input Jnl."
      • Additional actions can be added via an event receiver, which is implemented in codeunit 5308658 "CCS FDC Terminal Event Mgt."
        • HandleProcessDialogAction:
          • Provides an event for implementing additional actions. This event is necessary if the actions in the Web service page are not sufficient or if additional actions outside the standard Web service pages are required.

Source Code Adjustments

  • Adjustment via event in codeunit 5308657 "CCS FDC Terminal Event Subscr."
  • Filters for presentations, such as columns, are handled through events:
    • OnAfterGetContitionalFilterForControls
    • OnBeforeGetMobilePageCustLineFields
  • Filters for records are managed via events:
    • OnBeforeGetRelatedRecord
    • OnAfterGetRelatedRecord
  • Actions are controlled through events:
    • OnProcessDialogAction
    • OnAfterGetContitionalFilterForControls
    • OnAfterGetFieldValueForDashboardControl

Import and Export of Configurations

Task Link
Import and export configurations in COSMO Mobile Solution Configuration Export and Import

See Also

Setup
Configuring Classic Templates
Configuring Dashboard Templates

Feedback

Submit feedback for this page .