You are here: Reference > Data classes > License data instances > License Compliance form - Completing the Summary tab

  License Compliance form
Completing the Summary tab
  1. About 
  2. New 
  3. Summary 
  4. License 
  5. Import 
  6. History 

Caution: The License Compliance system operates automatically using default parameters that are appropriate in many cases. This facility does not restrict your use of the system, and does not affect system performance. Do not create or update the Data-Admin-License or Data-Admin-System facilities, except as advised by Pegasystems Global Support.

For an overview of this facility, see Working with the License Compliance facility. For official documentation, contact Global Customer Support.

The Summary tab presents a summary of current parameters for the License Compliance facility. Fields in the Contract Terms group are read-only, derived from license text on the License tab.

Complete fields in the Customer Options and Additional Properties group to set or update reporting parameters. Changes you make to these fields take effect the next time the server is restarted.

Field

Description
Contract Terms  
Issued to

Your organization name, decoded from information in the License tab. Read-only.
Measurement period

Length of the measurement period for which license compliance is to be monitored, such as monthly or quarterly. Read-only, decoded from information in the License tab.
Authenticated services charged to user

Consult official documentation.
Rule checkout or update forces Regular user

Consult official documentation.
Usage Type

Indicates a time interval that affect how named users are categorized as regular or occasional.
Sporadic user: Max hours per period

Consult official documentation.
Occasional user: Max hours per day

Consult official documentation.
Occasional user: Max hours per period

Consult official documentation.
Customer Options
First day of week

Select which day of the week is to be considered the first day, for reports based on weeks. The default is Sunday.
Service Reporting granularity

Select to control how service requests appear in reports from this facility:

  • As "Services" — Presents the least detail. A single report line summarizes usage by services.
  • By Service Type — Summarizes counts by service type, so that (for example), invocations by rules of type Rule-Service-SQL appear separately from invocations by rules of type Rule-Service-SOAP.
  • By Service Package — Summarizes counts by service type, and by service package (the initial key part) within service type.
  • By Service Method — Presents the most detail, records the entire visible key of service rule.
Retention period for hourly data

If not zero, specifies a number of days after the end of a day that hourly data are retained. If zero, hourly data are purged for yesterday shortly after midnight GMT, following the roll-up to daily data.
Retention period for daily data

If not zero, specifies a number of days after the end of a measurement period that daily data are retained. If zero, daily data are purged for all days in a period shortly after the end of that period, following the roll-up to period summary data.
Additional properties to identify user

Optional. To further identify or classify requestors, you can include additional facts in the first usage record from the values of properties available at login time. For example, you can save the operator's organization unit (property pxRequestor.pxOrgUnit), or the operator's work group.

The additional properties are included in the hourly and daily data, but not in the period summary data. You can update the schema for the hourly and daily data to expose these properties as columns, and then define reports that utilize these additional properties.
(no label)

Optional. Enter a property reference to be evaluated and included in the first hourly usage record for each requestor session.

About License Compliance data instances

Open topic with navigation