Remote Data

---

title: “Remote Data” description: "" lead: "" date: 2023-06-12T13:21:11-06:00 lastmod: 2023-06-12T13:21:11-06:00 draft: false images: [] menu: docs: parent: “how-to” identifier: “remote-data-26ec0f140f23e021a0b6f7126ccd02f4” weight: 205 toc: true

Remote data can be retrieved from any system that uses Trimble Identity JWT as an authentication mechanism.

Rego Methods

We provide as part of the appliance methods that can be used to retrieve remote data documented as part of the Rego SDK. There are also Rego commands that will not be available. At this time http.send is disabled.

Caching

When registering a package, you specify remote data sources and cache information in order to provide the most accurate data to appliances. Currently, only caching by a hard expiration time span is supported. Caching time for each remote data source is specified in a hh:mm:ss format. A cache time of 00:00:00 will not cache remote data from the specified source, but is not recommended for performance of evaluation decisions.

Note

If a redis cache is not supplied for appliances by specifying CACHE_TYPE, an in-memory cache will be used for each appliance which could potentially increase memory needed by each appliance.

GET API calls to remote data sources are cached by the identity used for the call as well as the URL provided to the remote data source. POST API calls to remote data sources calls are cached by the identity used for the call as well as the URL and request body hash.