Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

MobileMap (and InventoryManager) are built upon the ArcGIS system and require ArcGIS user ‘named user’ accounts for authentication and all data access. All users, therefore, must have an ArcGIS account, therefore. ArcGIS These named user accounts can be AGOL accounts (including AGOL access provided with ArcGIS GIS Professional Basic/StandarStandard/Advanced licenceslicenses), ArcGIS Enterprise (AKA Portal) accounts, or limited ArcGIS user accounts that can be purchased from WSG as a part of our Inventory Management Solution. This third option is only relevant for clients that want to use MobileMap but are not Esri customers and are do not interested in need broader access to the ArcGIS system (e.g., access to other applications like ArcGIS Field Maps or Survey123).

ArcGIS Online (AGOL)

AGOL User Types and Roles

...

The discussion below this image makes recommendations for appropriate combinations for different testing and deployment scenarios.

...

...

Scenarios

  1. Test in which Feature Service is published in WSG's AGOL organizational account. External tester needs to be invited to join a group, thus needs

  2. Test in which Feature Service is published in WSG's AGOL organizational account and WSG provides a temporary user account for tester (preferred)

  3. Test in which client will publish Feature Service in their AGOL account and WSG staff are invited to join the client-created AGOL Group

  4. Test in which client publishes Feature Service in Portal. Typically, WSG staff are given domain or Portal user account

  5. Production use for MobileMap/IM only (no need for other Esri mobile apps)

  6. Production use for MobileMap and other Esri apps (e.g., Field Maps, Survey123)

Most MobileMap users will create or edit data, thus they need editing capabilities. Therefore, they will typically need Data Editor, User or Publisher roles.

...

When evaluating MobileMap within your organization, there are three possible scenarios for gaining access to a demo feature service.

  1. WSG publishes a service, creates a new AGOL group, and invites client AGOL users to join this group

  2. WSG publishes a service, creates a new AGOL group, and provides client with temporary WSG AGOL user account(s) for a short evaluation period

  3. WSG provides the materials needed to publish a service (data model, file geodatabase, map document/project file, documentation) and supports client in publishing a service, creating a new AGOL group, and inviting at least one WSG user to join this group.

Production

The pattern for deployment into production with ArcGIS Online is very similar to testing scenario 3 above, where WSG provides the materials needed to publish a service (data model, file geodatabase, map document/project file, documentation) and supports client in publishing a service, creating a new AGOL group, and inviting at least one WSG user to join this group. The only difference is that this may follow testing scenario 1 or 2 in which the data model was developed and tested within WSG’s AGOL organizational account. WSG cannot host production feature services for our clients unless we are also providing ArcGIS user accounts.

...