cancel
Showing results for 
Search instead for 
Did you mean: 

iPhone App - Remove the requirement to have certain fields in the SFM

iPhone App - Remove the requirement to have certain fields in the SFM

iPhone App - Remove the requirement to have certain fields in the SFM

While testing the iPhone Summer 16 app, we have found that some features and functions just do not work unless we add a certain field to the SFM view or edit SFM.

Examples of this are:

  • SFM Formulas don't work unless the fields they update are on the layout. We would like to set some fields in the background but can't because they have to be shown to the tech
  • Picklist values don't respect the record type unless the record type ID field is on the layout.
  • If an sfm mapping is setting a field but its not on the layout, the layout goes blank until the record is synced
  • Lookup context is only possible if the context field is on the layout
  • A translation of a pick list value will only work on a service report if the field is included on the view layout for that object and is active for the group profile. If the field is not included on the view layout, it just shows the default translation

It would be great to remove these restrictions as it would make the app more flexible, less frustrating to configure and more streamlined/user friendly to the tech.

What is the underlying problem do you intend to solve with this idea?
Ease of configuration and usability for the tech
How is the problem being addressed today, if at all?
n/a
Product Area?
Other
What version of ServiceMax are you on?
Summer 16
19 Comments
Roast Chef
Roast Chef

I can envision either:  1) a checkbox on existing Layout whereby a "technical only" setting can be noted that makes the field invisible or 2) a new tab for technical only fields that are being referenced by formula, mapping, lookup, etc.

Pastry Chef
Pastry Chef

Or even better... no requirement at all to add these fields. It just automatically knows what fields are referenced in formulas, validations etc. and includes them without you needing to do anything extra. All you need to add to the layout is the fields you actually want the user to see.

Roast Chef
Roast Chef

Good point - administrator doesn't need to see them at all. 

Staff Chef
Staff Chef

Hi Michael Majerus​, please share this list when you are provided with it.

Regards, Richard

Sushi Chef
Sushi Chef

I absolutely agree with this - The biggest impact is usability where there are fields that confuse the user, for me this is an absolute must have.

Pastry Chef
Pastry Chef

These are some frustrating limitations we have just come across in testing the FSA, totally agree with the conclusions, especially as we don t need to have these fields in the classic apps.

Roast Chef
Roast Chef

The FSA is especially impacted due the touch-centric UI - having a bunch of fields there for background purposes only really makes for excessive scrolling.  This would help immensely for online SFM as well of course!

Roast Chef
Roast Chef

Hi all - just checking if any new information has come in this area during Maximize.  This is probably at the top of our list at this point due to usability concerns.

Pastry Chef
Pastry Chef

I was at Maximize and didn't hear anything about this mentioned