You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently we met with the Tanks (UST) folks. They are beginning a migration to Salesforce and were expecting to be able to use the same SF component as Spills. I explained to them that Spills had very specific requirements and that it likely wouldn't fit nicely into their solution. Their requirements are fairly simple and I believe overlap with this project:
attempt to geocode address to get the general location, if not fall back to city, county, or state
click on the map to define a location (they plan to continue to store their coordinates in UTM)
I believe that they said that they didn't even want the ability to input coordinates directly but I could be wrong.
I told them that we would likely be able to steal most, if not all, of the functionality from this project for theirs. I wonder if there's a way that we could create a plug-and-play component that any Salesforce person could easily implement. I'm not sure if this would be something that would come from this project or be something separate.
The text was updated successfully, but these errors were encountered:
Recently we met with the Tanks (UST) folks. They are beginning a migration to Salesforce and were expecting to be able to use the same SF component as Spills. I explained to them that Spills had very specific requirements and that it likely wouldn't fit nicely into their solution. Their requirements are fairly simple and I believe overlap with this project:
I believe that they said that they didn't even want the ability to input coordinates directly but I could be wrong.
I told them that we would likely be able to steal most, if not all, of the functionality from this project for theirs. I wonder if there's a way that we could create a plug-and-play component that any Salesforce person could easily implement. I'm not sure if this would be something that would come from this project or be something separate.
The text was updated successfully, but these errors were encountered: