License data

This page provides the content of the available licenses.

• Valid - A license is valid if both conditions are satisfied:

  1. The current date is between the start and end date of the license validity.
  2. There is a corresponding policy file (with same partner ID, product code, product version, policy code, and policy version) which describes the set of modules, activity codes, and so forth that can be unlocked by licenses.

• Partner ID - This is the ID of the partner who issues the license. Sage has an empty string as Partner ID.

• Product name, product code, product version - The localized name, internal code, and version of the product that should be licensed.

• Serial number - This is the serial number for online help access.

• generation stamp - This is the date and time at which the license has been generated.

• Session control - This can be either "concurrent" (limitation on the maximum number of concurrent badge holders) or "named" (limitation on the maximum number of named badge holders).

• Policy name, policy code, policy version - The localized name, internal code, and version of the policy which belongs to this license.

• Name and address of licensee - This gives the name and the address data of the institution which the license has been issued to.

• Start of validity/end of validity - The first and last day of the license validity period.

• Total session limit - The maximum number of concurrent sessions allowed by this license.

• License type - Either a standard license or a demo license, or a NFR ("not for resale") license for partners.

• Session types The localized names, internal names, maximal number of concurrent sessions for different devices.

• Modules - The localized names, internal names, availability (for example, "always" when it is always allowed by the policy, "licensed" when this has been unlocked by the license, or "not licensed" when it has not been unlocked by the license), and start and end date of the validity and the number of key functions of each module which is always allowed by the policy or can be licensed. A key function can only be used when the corresponding module is licensed or always allowed, and when the user has a badge that allows this function.

• Badges - The localized titles, internal names, maximum numbers of concurrent sessions or named users, and the list of functions which can be used by each badge holder.

• Activity codes - The localized names, internal names, availability (see description under "Modules"), and start and end date of the validity of licensed activity codes.

• Languages - The localized names, internal names, availability (see description under "Modules"), and start and end date of the validity of licensed languages.

• Legislations - The localized titles, internal names, availability (see description under "Modules"), and start and end date of the validity of licensed legislations.

• Parameter kits - The localized titles, internal names, availability (see description under "Modules"), and start and end date of the validity of licensed parameter kits.

• Parameters - The localized titles, internal names, data type and values of certain parameters