Screen Configurations - Limitations



Intro

This topic outlines the limitations associated with the Screen Configurator application and uploaded JSON screen configurations.


JSON Screen Configuration

You can upload JSON-formatted screen configurations directly into the application from Admin > Company > Screen Configurations.

However, support for custom screen configurations that use this approach is not supported, so you are responsible for screen configuration validation and testing.

It is therefore recommended to use the Screen Configurator application for supported screens while noting the limitations.


Limitations

All Platforms

Limitation Description
UDF - order of values in SelectList The order in select lists is not supported. That’s why the sorting order you defined on the UI level of the customization app is not reflected on select lists.
Multiple activate configuration per screen Only one active configuration is supported for a given screen. Multiple active screen configurations are not supported. The application determines active screen configuration by code.
Renaming the configuration The default configuration name (Name-[screenconfigurator]) can’t be modified. When the file name is changed, the screen configuration upload fails.

Mobile Applications

Limitation Affected Client Description
No unified default screen configuration for both mobile and web applications All Different default screen configurations are used for mobile and web applications, which means mobile has its own default screen configuration.
Fields without value don’t appear in display mode. All Only fields with values are shown in display mode, so if you want to check or change the fields without values, please switch to Edit mode.
The currentUser and currentProfile global variables don’t take effect in Windows. All The currentUser and currentProfile global variables are supported in mobile applications, thus the expressions with currentUser or currentProfile can be used in mobile Screen Configuration. However, they only take effect in IOS and Android, but not in Windows.
currentProfile only supports the ${currentProfile.userAccountGroupName} format. All ${currentProfile.userAccountGroupName} is the only supported format of currentProfile, for example, ${currentProfile.userAccountGroupName} === ‘ALL’

Web Applications

Limitation Affected WebApp Description
Reordering cards All Card reordering is not supported.
Renaming cards All Card renaming is not supported.
Adding cards All Adding additional cards to a screen configuration is not supported.
Person object UDF values don’t appear in the screen configuration UnifiedPerson. All UDF defined in the Person object doesn’t appear in the screen configuration UnifiedPerson.
Cards displayed can’t be edited/removed. All Some default cards can’t be removed from web app screen configurations. When groups are added or removed, the changes won’t be displayed in the associated web screen.
The use of currentUser and currentProfile global variables All The expressions with currentUser or currentProfile can’t take effect in web application Screen Configuration as the web application doesn’t support the currentUser and currentProfile global variables.
Screen that can’t be configured TMJ/EMME Web
(Expense, Materials, Milage, and Effort)
TMJ Web app doesn’t support UI based customization using the configurator UI.
Workaround:
It is still possible to adjust the TMJ UI by adding the JSON in this custom format. For more information, see Time & Material Journal Configuration.
Note: CSTimeEffort, CSExpense, CSMileage, CSMaterial, and CSTimeRecordingOverview are supported via custom JSON.
UDFs aren’t always displayed in the assigned card. MDM UDFs are not always displayed in the assigned card.
For example:
* In the Item Details screen, the UDF fields aren’t correctly placed in the assigned cards, instead, they are assigned to the User-defined Fields card.
* In the Unified Person Details screen , the UDF fields assigned to Basic Information and Contact can be placed in the assigned cards. However, the UDF fields assigned to Terroritorries can’t be placed in the assigned card, instead, they are assigned to the User-defined Fields card.
Screen configuration for basic card is not supported if user permission is PartnerAdmin. MDM
(Person screen or Business Partner screen)
The screen configuration (including Business Partner and UnifiedPerson) for basic card is not supported if the user permission is PartnerAdmin (Crowd).
Setting Requiredness to Required in Screen Configuration for the Picture field won’t take effect in MDM . MDM
(Item screen or Equipment screen)
Setting Requiredness to Required in Screen Configuration for the Picture field won’t take effect in MDM, for example, the Picture field in basic card of Item screen or Equipment screen.

Specific Screen

Limitation Affected Apps Description
Using predefined cards such as card_1 and *card_2 is not supported. CSServiceCallDetail (Service Call Web) Renaming the card title and adding fields to the card has no effect. It is not possible to display those cards in the screen.
The Visible expression doesn’t always work for dependent data. CSServiceCallDetail (Service Call Web) In Service Call Web Configuration, the Visible expression doesn’t always work for dependent data.
For examples:
* For serviceCall.problemTypeName.code, the problemTypeName in runtime isn’t the object type, but the string type instead.
* For serviceCall.equipment.code, the equipment is actually the array type in run time, but the array type isn’t acceptable in the Visible expression.
Customization of Editability/Requiredness of Field Territory (ServiceCallTerritory) isn’t supported. CSServiceCallDetail (Service Call Web) Customization of Editability/Requiredness of Field Territory (ServiceCallTerritory) isn’t supported.
Read-only setting isn’t respected/applied by all fields. CSServiceCallDetail (Service Call Web) Read-only setting isn’t respected by all fields. There are some cases where obligatory and read-only fields are rendered as optional and editable.
Some fields can be dragged and dropped into cards in screen configuration UI but it doesn’t work in the application UI. CSServiceCallDetail (Service Call Web) Some fields, such as Service Assignment Activity Code, can be dragged and dropped into cards in screen configuration UI, but these fields won’t appear in the application UI.
The Reserved Material card on the Service Call screen can’t be removed. CSServiceCallDetail (Service Call Web) The Reserved Material card can’t be removed from the Service Call screen.
Setting default value of ServiceCall (Service Call Web) origin isn’t supported. CSServiceCallDetail (Service Call Web) Configuration default value of ServiceCall (Service Call Web) origin in screen configuration isn’t supported.
Setting default value of ServiceCall (Service Call Mobile) origin isn’t supported. ServiceCall (Service Call Mobile) When you create a new service call on mobile, you have to manually choose an origin as setting default value of ServiceCall origin isn’t supported.
The timestamp saved for dueDataTime in Service Call mobile screen configuration isn’t displayed in Service Call mobile app in all clients. ServiceCall (Service Call Mobile) Service Call mobile screen configuration for dueDateTime shows that you can save a date and a timestamp. However in the Service Call mobile app in all clients, only the date is displayed.
Configuration of the Service Call Sidebar isn’t supported. CSServiceCallSidebar (Service Call Web Sidebar) The Service Call Sidebar isn’t configurable.
Removing cards in Activity Sidebar isn’t supported. CSActivitySidebar (Activity Web Sidebar) Removing cards in Activity Sidebar isn’t supported.
Customization of Signal Words in the Activity sidebar isn’t supported . CSActivitySidebar (Activity Web Sidebar) Customization of Signal Words in the Activity sidebar isn’t supported .
activity.responsibles.xx is not supported in expression in Activity Sidebar. CSActivitySidebar (Activity Web Sidebar) You can use activity.responsibles.xx, such as activity.responsibles.id and activity.responsibles.firstname, in expression in Screen Configuration advance setting , but it doesn’t take effect in Activity Sidebar application.
The activity.region.name field isn’t available in CSActivitySidebar using Screen Configurator. It must be added by editing JSON file. CSActivitySidebar (Activity Web Sidebar) In order to use the Planning Scenarios functionality, you must add the activity.region.name field in the JSON screen configuration of the CSActivitySidebar, as this field isn’t available in the Screen Configurator application.
ActivityList only supports maximum 3 fields and the other fields will be ignored. ActivityList (Activity List Mobile) ActivityList goes with the fixed 3 fields approach due to the limited UI space.
Only UDFs of the text type are supported. CSProjectActivitySidebar (Project Activity Web Sidebar) Only UDFs of the text type are supported in screen configuration CSProjectActivitySidebar.
Address in Equipment can’t be edited in Screen Configurator. Equipment (Equipment Mobile) Address in Equipment can’t be edited in Screen Configurator.
The Equipment Mobile screen contains read-only fields that appeared to be editable. Equipment (Equipment Mobile) It is currently possible to modify the equipment mobile screen configuration on the cloud and set the values for non-editable fields serial number and product ID to editable. However, these fields are read-only and can’t be edited in the mobile app.