Below is the existing behavior of the MOBILE_INITIAL_SCREEN application parameter in FSM.

Scenario 01: When the baseline design revision is in use (i.e. always a baseline screen, without any customization will be set as the initial screen)

• Valid values are Home and JobList. These work as expected and appears as the initial screen when the user logs in
• Baseline WF screens (ex: DebriefLabor, ScheduleRequestContact) cannot be considered as valid, since they are connected to a Task or a Quote. In such cases, the Home screen appears by default as the initial screen
• Non-WF baseline screens (ex: CustomerList, ReceivingList, TimeReporting) can be used and they appear as the initial screen when the user logs in. However, this cannot be considered as a reasonable value.

Scenario 02: Usage of custom screens (i.e. when a custom design revision is set as the default design for mobile)

• Home, JobList screens work as expected and open with relevant customizations
• Non-WF baseline screens with customizations, (ex: CustomerList, ReceivingList) can be used and they appear as the initial screen with relevant customizations. However, using such screens as the initial screen doesn’t make much sense
• When a newly added custom screen is used, the app could fail to login. Thus, cannot be recommended to be used as the initial screen