Usage System Settings

Usage system settings define how usage functions in the tenant.

NOTE: The value in the Tenant Editable column indicates whether or not the system setting can be edited by a user.

  • Yes — A user (with the appropriate role and security authorities) can edit the system setting value in the Admin application, as well as return it to the default value. Refer to Edit System Settings.

  • No — The system setting can only be edited by a Gotransverse representative. Contact Gotransverse Technical Support before editing the system setting to ensure the change will not cause issues within the tenant.

Usage System Settings
Name Description Data Type Possible Values Default Value Tenant Editable

Batch size

Number of records to be processed per batch in Tenant Charge File.

Integer

NULL

100

No

Copied usage event id is written to the following additional usage event field.

Defines which text field of a usage event is populated with the original usage event ID when it is copied.

List

TEXT01

TEXT02

TEXT03

TEXT04

TEXT05

TEXT06

TEXT06

No

Enable currency conversion as part of the rating process

Enables users to create complex rating rules which can perform currency conversion as part of the rating process.

  • If set to FALSE, the application will not calculate currency conversion while rating.

  • If set to TRUE, the application allows for currency conversion during rate and adds an additional worksheet to the usage rule spreadsheet.

Boolean

TRUE

FALSE

FALSE

No

Enable currency conversion offset processing for rating

Enables users to when processing currency conversion as part of rating to offset the currency conversion rate utilized by the number of days to the start date of the usage event.

List

0 — 5

1

No

Enable retention of voided usage events

Enables retention of voided usage event records and their charges so you can view and take action on those usage records. Details on voided usage event records can be retrieved with API 2.0. Refer to the API 2.0 help site for more information.

  • If set to FALSE, the application does not retain voided usage event records. They are removed from the application allowing for no traceability on the details of the voided records.

  • If set to TRUE, the application retains all the details on the voided usage event records including the charges that are returned to the user.

Boolean

TRUE

FALSE

FALSE

No

Enable upload of updated global usage rule files

Enables users with the ability to upload updated global usage rule files and trigger asynchronous service period updates based on the new file.

Boolean

TRUE

FALSE

FALSE

Yes

Lookup Table Processing Mode

Defines the processing of multi-value lookup tables by API 2.0:

  • MULTI — API manages multiple values for the lookup table entry.

  • SINGLE — API manages single or multiple values for the lookup table entry. This option is deprecated and is available for backwards compatibility only. Gotransverse recommends switching to the MULTI option. Contact GTV Support for details.

For more information and examples, refer to the API 2.0 guide on Usage Lookup Tablesexternal link.

List

SINGLE

MULTI

MULTI

No

Maximum number of events to void

Maximum number of events to void.

Integer

NULL

100

No

Maximum usage events records

Maximum number of records allowed in a usage event file.

Integer

NULL

1000

No

Maximum size of usage event file

Maximum size, in megabytes, for a usage event file to be uploaded.

Integer

NULL

10

No

Maximum size of usage event zip file

Maximum size, in megabytes, for a usage event ZIP file to be uploaded.

Integer

NULL

1

No

Partition UsageEventFile Job

Partitions ProcessUsageEventFileQuartzJob job per Service Resource and Service Resource Type.

 —

TRUE

FALSE

TRUE

Yes

Rerate Strategy

Defines strategies when a rerate can happen.

Refer to Usage Rerating Strategies.

List

EDIT

VOID

OUT_OF_ORDER

ROLLOVER

OVERWRITE

ADDON

SPREAD_SHEET_RULE_DIRTY

NEW_SPREAD_SHEET_VERSION

PERIOD_REBUILD

VOID_UNEXPECTED

EDIT

VOID

OUT_OF_ORDER

ROLLOVER

OVERWRITE

ADDON

PERIOD_REBUILD

VOID_UNEXPECTED

Yes

Set the currency conversion date field for use by complex usage rules in rating

When processing currency conversion, enables users to specify the date field of a usage event used by a complex usage rule in the process of looking up a currency conversion rate.

List

Start_Date

Date 1

Date 2

Date 3

Date 4

Date 5

Start_Date

Yes

Usage rating decimal precision

Defines the level of decimal precision for usage rates and rate calculations. For existing and new tenants, the default value is 5. The precision can be configured starting from 5 to 20 decimal points. Usage rating decimal precision cannot be lower than the previously set value.

Integer

5 - 20

5

Yes

Usage rating decimal precision

Defines the level of decimal precision for usage rates and rat6*9999+++*999999999999999999999999999999999999999999999999999999999999999-e calculations. For existing and new tenants, the default value is 5. The precision can be configured starting from 5 to 20 decimal points. Usage rating decimal precision cannot be lower than the previously set value.

Integer

5 - 20

5

Yes

 

 

Usage rule creation mode

Controls the timing of when usage rules are created.

EAGER - rules created with service period creation.

LAZY_NON_ROLLOVER - rules that are not configured with rollover are created when the first usage event is submitted to the period.

These rules do not support usage pooling. Refer to the Usage Rerating Strategies Knowledge Base article for more information about usage pooling.

List

EAGER

LAZY_NON_ROLLOVER

EAGER

No

 

 

 

Topic updated: 09/2024.