Then in the template we can reference the geometry service url as {{organization.helperServices.geometry.url}}
Geocoding as an array would be something like this for the default locator {{organization.helperServices.geocode[0].url}}
We we construct the template replacement dictionary prior to deployment we should pull all properties from portal/self into this object. This will give us more flexibility to expand and take advantage different properties from the organization/portal in the templates.
In the template replacement dictionary we should reserve the "organization" object for all the properties returned from the target portal/self call. https://developers.arcgis.com/rest/users-groups-and-items/portal-self.htm
This will allow us to support any property defined by the portal during template replacement. For example today we have something like:
instead we the helper urls should be reference like:
Then in the template we can reference the geometry service url as {{organization.helperServices.geometry.url}}
Geocoding as an array would be something like this for the default locator {{organization.helperServices.geocode[0].url}}
We we construct the template replacement dictionary prior to deployment we should pull all properties from portal/self into this object. This will give us more flexibility to expand and take advantage different properties from the organization/portal in the templates.
We should also pull all the properties form the logged in user under the "user" object: https://developers.arcgis.com/rest/users-groups-and-items/user.htm