Follow

How to customize the FSM with screen configurations?

Issue Description

You want to hide certain fields displayed on a screen on a mobile app or make certain fields read-only or mandatory so as to suit your needs.

Solution

We are continually expanding the possibility to customize screens in the Coresystems Field Service Management (FSM) Solution so that you can customize the following field properties:

  • Hiding or displaying fields
  • Making fields read-only or editable
  • Making fields mandatory (required) or optional
  • Define the default value for fields when creating new records
  • Validate field values when editing a record
  • Renaming labels incl. custom translation
  • Change the screen layout by changing the position of the fields

Currently supported screens

Release 5.40 provides the option to configure the following screens:

Screen Code

UI in Configurator

iOS Mobile

Windows Client

Android Mobile

Web

Activity

X

(without Web)

X

X

X

X

(CSActivitySidebar)

Business Partner

 

X

-

X

 

Effort

 

X

X

X

-

Expense

 

X

X

X

-

ItemsAndStock

 

X

-

X

 

Material

X

X

X

X

-

Mileage

X

X

X

X

-

SalesOpportunity

 

X

X

X

-

SalesOrder

 

-

-

-

-

SalesQuotation

  - - - -

ServiceCall

 

X

X

X

X (CSServiceCallDetail)

ServiceCheckout

 

X

-

-

-

ServiceContract

 

X

-

X

-

 

How to add screen customization

For the screen configurations that are supported to be configured via UI see the Online Documentation - Screen Configuration in Admin

Further details on how to adjust a screen based on the technical file without UI can be found in the documentation linked below which is aimed at consultants and partners: Documentation - FSM Customization

Default Screen Configurations for the supported screen can be downloaded from this blog: Package with all default screen configurations

 

What has changed?

- From Version 5.25 the TranslationKey is used with a different fallback logic. If no translation is defined as custom translation

BEFORE(Version 5.25): If no translation is defined as custom translation the TranslationKey entered in the screen configuration is displayed as Label

AFTER (Version 5.25): If no translation is defined as custom translation the default translation of the app is displayed as Label

- IMPORTANT: From Version 5.26 the correct Screen Code has to be entered to use the screen configuration in addition to defining the correct Object Type. See above table with corresponding codes.

- Version 5.30 add support for expressions in the Android app

- 5.40 & 5.50 support more screen

Attachments:

Was this article helpful?
1 out of 2 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.