Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Obtaining the Google API key

Updated on April 5, 2022

You add the Map control (the pyTrackingMap rule) to a section, dynamic layout or harness, to enable users to interact with location points, and view user tracks on a map from within a desktop or mobile app. You must obtain the Google API key, because the control uses the Google Maps service.

Before you begin: Make sure that you have a Google Developer account and are familiar with any region-based or usage restrictions. View the Get API Key tutorial from Google for additional assistance with this process.
  1. Access the Google Developer Console and log in to your account.

  2. Create a project or select your existing project.

  3. Enable the Maps JavaScript and Geocoding APIs.

  4. Create a browser key to use for the Public API access.

    Note: Make note of the browser key, because you need it to configure a dynamic system setting.

  • Adding the Map control

    Add a Map control (the pyTrackingMap rule) to a cell to view markers, static user locations, and case-related markers that can represent job locations and tracks of users of offline-enabled mobile apps.

  • Configuring a dynamic system setting for the Map control

    Add the Map control (the pyTrackingMap rule) to a section, dynamic layout, or harness to enable users to interact with location points, and view user tracks on a map from within a desktop or mobile app. You must configure a dynamic system setting that stores the Google API key, because the control uses the Google Maps service.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us