Showing results for 
Search instead for 
Did you mean: 

SFM App Permissions - Migration tool

SFM App Permissions - Migration tool

SFM App Permissions - Migration tool

SFM App Permissions can't be migrated through Migration tool. Every time a new SFM Transactions, Wizard, we need to manually give SFM App permission on new and existing SFMs. 


When new Sandbox is created and during PROD configuration migration to thisSandbox, SFM App permissions are not migrated. We need to do this manually for each object. Most of the standard SFM Transaction and Wizards are disabled or access revoked in our PROD org. These will be visible in new Sandbox after Seed data downloaded and we can't migrate SFM App permissions but manually align to disable them.

What is the underlying problem do you intend to solve with this idea?
Migration inconsistencies and manual work for Admin
How is the problem being addressed today, if at all?
Manually migrated
Product Area?
Migration Tool
What version of ServiceMax are you on?
Tags (1)
Product Team
Product Team
Status changed to: Under Consideration
Product Team
Product Team
Status changed to: Delivered

Hi @smusku ,

19.3 Migration tool release will support migration of 'SFM App Permissions' 

In the source tree you will find option 'SFW SFM App Permissions'. Source tree will also list the application types. You can choose to select all or specific form factor for which app permissions needs to be migrated. Screenshot for source tree

Screen Shot 2019-10-09 at 4.37.53 PM.png

Screenshot showing validation result, Android tablet is selected for migrating 'App Permissions'

Screen Shot 2019-10-09 at 3.32.26 PM.png

As part of migration, visibility status will be set similar to source org for SFM transaction, SFM Wizard and SFM Custom actions. 

Note: 1. As part of 'SFM App permission' migration, Only flag status will be migrated and not the processes. 

2.  Visibility status will be set only for those processes found in the target org i.e. if source org has extra processes it will be ignored.

Use this feature and share your feedback. 

3. Visibility status of extra processes found in target org will not be altered.