Maps & location

Application address: /integrations/maps · Product baseline: 0.4.0

Reference status

Screen inventory extracted from the implementation. Labels and explicitly declared input constraints are recorded below. This is not a claim that every control, calculation, or business workflow has been verified in a running system.

Open this screen

Use OSERP navigation to find Maps & location, or open /integrations/maps on your OSERP application after signing in. Confirm the active company before reading or changing records.

Menu access: settings:manage

Menu access only determines whether the screen is offered. Saving, posting, deleting, exporting, and approving can require additional server permissions.

Fields and input controls

Limits in this section are interface declarations. A missing maximum is not a promise of unlimited storage. Read how field limits work. Labels may differ with language and configuration.

Google Maps API key

Property	Reference
Reference key	google-maps-api-key
Location	Screen / contextual panel
Input control	Field
Required in interface	not declared on control
Maximum characters	Not explicitly declared on this control
Editing	No disabled/read-only condition declared directly on this control.

Use Google to fill addresses from a shopper's location

Property	Reference
Reference key	use-google-to-fill-addresses-from-a-shopper-s-location
Location	Screen / contextual panel
Input control	checkbox
Required in interface	not declared on control
Maximum characters	Not explicitly declared on this control
Editing	No disabled/read-only condition declared directly on this control.

Named actions

These are labels found in screen components; availability and consequences depend on record state. Confirm the operation before executing it.

• Save
• Test the key

Help text and messages

The following wording is embedded in this screen. It describes interface guidance, rather than independently verified system guarantees.

• In Google Cloud, enable the Geocoding API for a project and create an API key. Restrict the key to the Geocoding API (and to this server's address if you can). The key is stored encrypted and is never shown again.

Verification still required

Business purpose for each control, dynamically generated fields, backend limits, saved defaults, permission combinations, audit effects, and complete workflow outcomes require manual review against the published application.

See the operating manual, coverage register, and troubleshooting guide.