cancel
Showing results for 
Search instead for 
Did you mean: 

Linked SFM to the return the originating or base SFM to show the updates from SFDC updated fields in

Linked SFM to the return the originating or base SFM to show the updates from SFDC updated fields in

Linked SFM to the return the originating or base SFM to show the updates from SFDC updated fields in

0 Likes

Enhancement:

We would like the linked SFM to the return the originating or base SFM to show the updates from SFDC updated fields in the layout.  IE, from save, Workflow updates fields based on what was done in linked SFM.  This would then render in base SFM.

 

Current Behaviour

When user saves linked SFM:

1) FSA reloads the parent SFM process (i.e. Debrief Work Order edit process to reflect the newly added line) - sync is not completed yet, we have a flag that indicates that code has run, it will be empty at this stage

2) Triggers aggressive sync - custom code runs and updates the flag 

 

But, even after having the code run in client DB, user will still see "" (blank) value in the UI because, FSA doesn't refresh the UI after sync is completed while in the edit process. So, in the Debrief Work Order edit process, the fields populated by code will still be blank after the sync (even when the DB has the updated value). When user clicks save on the Debrief Work Order edit process, we save the UI values in the DB. This overrides the code-populated information (obtained from server) to a blank value and we send this information in PUTUPDATE request in the sync which resets the value to blank in the server.

What is the underlying problem do you intend to solve with this idea?
Fields being blanked out when user debriefs from FSA
How is the problem being addressed today, if at all?
Time-consuming manual population by admin team
What version of ServiceMax are you on?
18.2