For the complete documentation index, see llms.txt. This page is also available as Markdown.

Manage service versions and effective dates

After an Excel file has been uploaded to Spark and the logic is converted to code, it is referred to as a service. Multiple versions of a service can be added to an existing service, called service versions.

In Spark, each service version has effective start and effective end dates. Spark can serve the different service versions of one service based upon a transaction date input.

Define effective from and effective until dates for a service version

  • In any action that leads to a new service version, you can set the Effective from and Effective until dates for the service version.

  • By default, Effective from is set to the upload date and time. Effective until date is set 100 years into the future.

  • Dates and times are defined in your local time. Check the detected time zone in the User menu.

  • You can also change the dates for an existing service version inEdit a service property.

Resolve service versions

Execute API (v3) uses the request_meta transaction_date.

  • If a specific version or version_id is being called, the API will ignore the transaction_date.

  • If the transaction_date is specified and no version is specified, it will use the latest version that applies at the time of the transaction_date.

  • The Execute API always resolves the version_id parameter first, service_id parameter second, and the service_uri last. It is possible that within an API request, these three parameters may refer to different services, however Spark will resolve the reference in the same order.

  • This functionality cannot be tested within the API Tester as it is service version specific. You must use an external application to make the API request.

Invocation method
transaction_date
Version resolution

version_id

has no impact on version resolution

Version specified by the API call.

service_id or service_uri

none provided

Latest version that applies where the transaction_date equals the current time.

service_id or service_uri

included in the API request

Latest version that applies at the transaction_date. If the transaction_date is outside of the effective from or effective until dates for any service versions, then no calculation will be returned.

Last updated