Treatment of unsupported literals in browser based SFMs

Treatment of unsupported literals in browser based SFMs


When viewing SFMs on the Browser that have an unsupported literal mapped as part of them then they fail with an error message. This idea is to request that the doesn't happen but instead the mapping line for the literal is ignored if the literal is not recognised.

Examples are the three new literal for Latitude, longitude and accuracy.

We would not want to maintain two different versions of each SFM that uses these literals but would just want them to be ignored when on the browser.

What is the underlying problem do you intend to solve with this idea?
Error message shown when literal is unsupported
How is the problem being addressed today, if at all?
We have created two different SFMs
Product Area?
ServiceMax Literals
What version of ServiceMax are you on?
1 Comment
Product Team
Product Team
Status changed to: On The Roadmap

Hi @richard_lewis  This is on our roadmap. Web delivery will be handling these literals in 19.2 release.