Submission Info Isn't Following BMLT Server Auto-Calculations

[tempsaint]

We have the ability in the BMLT Server to configure certain fields, like Zip/Postal Code, County/Sub-Province, or Longitude and Latitude so that they are automatically calculated based on the the Street, City/Town, and State/Province data filled. When someone submits meeting information with the bmlt-workflow plugin, this data is not automatically calculated. Not being a software engineer, I'm guessing this is because there's no "Save" action taking place in the BMLT Server which performs that auto-calculation.

If a person submits a meeting with the bmlt-workflow plugin and doesn't include the County/Sub-Province or Zip/Postal Code (these are not commonly known points of data for many people in the U.S.) then the fields remain empty until someone manually saves the meeting information in the BMLT Server.

[nigel-bmlt]

Could you clarify that the desired behaviour would be:

• that the county/sub-province or zip/postal code are optional to be provided in the submission form and we automatically calculate them inside the submission UI if they aren't provided?

This seems sort-of in line with the BMLT behaviour, but I'm concerned that this leaves the user in a situation where they have no real idea what is actually being created for them until after the meeting shows up in the meeting list via crouton etc. It might make sense when the admin is actively editing the meeting inside the BMLT UI, but if they're just pressing approve in the plugin you could end up with any random meeting output depending on how accurate the original submission was or our auto calculation logic.