Audit Log for ServiceMax Changes

There is currently no easy way to see audit history of ServiceMax configuration changes. Modifying an SFM for example. This should be similar to the Salesforce Audit log.

Also our experience is that when a user modifies one thing in the org, which we think is using translation workbench, then all the last modified stamps get updated. This erases the little audit info of last modified that we do have.

Due to the way that ServiceMax manage SFM updates turning on field history tracking for the relevant ServiceMax configuration objects would not be enough for auditors.

This is the feedback from the Product team in a ServiceMax Knowledge article:

However, in regard to SFM changes, there is no OOTB UI to track changes to SFM settings.

ServiceMax uses record data to create the SFM transactions, mapping, filter criteria etc. You can use field history tracking on the ServiceMax Process and ServiceMax Config Data objects. However, when changes are made to a mapping or page layout within an SFM, the existing record data is deleted and new records are created.

It is technically possible to track SFM changes in the database, but would require technical expertise from SVMX to make sense of the underlying databases that track the SFM changes.

Use of Salesforce Audit Trails Feature to Track Changes

idea 1467

What is the underlying problem do you intend to solve with this idea?
Unable to meet audit requirements to track changes using ServiceMax Setup.
How is the problem being addressed today, if at all?
Not addressed
Product Area?
What version of ServiceMax are you on?
Summer 16
Product Team
Product Team

@richard_lewis @lisa_mercer @martski @kevinpayne @mmajerus6 

Starting 191, we have started tracking changes to ServiceMax configuration by Migration tool.

We are tracking Who ,When, Which ServiceMax entity record and What action details in a log file (excel) which will be emailed to user who has initiated the migration.

This log file will detail out list of items selected for migration, it will also list of dependent items that get migrated along with selected items, time taken to migrate each item, status and additional info for each entity that is being migrated.

If case of partial migration due to unknown errors user has to manually go and check for configurations that didn't get migrated. Now this file can be referred to identify the list of items that got migrated and list of items that didn't get migrated due to unknown errors.Screen Shot 2019-03-07 at 11.30.36 AM.png Attaching a sample of the file for reference

Also we have introduced a new custom object in target org which will capture high level details about changes to ServiceMax configurations. Again for now it will capture migration tool changes.

In coming releases we will extend this to capture changes at designer level.

For now recommend to try migration tool for moving configurations between environment and share your feedback.

@anita_dsouza  CC


Staff Chef richard_lewis
Staff Chef

Thanks for the update @shivaranjini_g 

Customer Success Team

@mmajerus6   Can you please let me know if this meets Bio-Rad's needs?



Pastry Chef mmajerus6
Pastry Chef

Hello @lisa_mercer. For us, the migration tool has been pretty solid for the past couple years, so this will provide some value. The real value is when we get the history tracking for the Designer changes.

Hoping we can also report on the new custom object so that anytime someone updates a component via the designer, we will know immediately.

Thank you for keeping us in the loop!