Evidence Tab: Suite and Member Evidence

FlexNet Manager Suite 2019 R2 (On-Premises Edition)

Application evidence is used for tracking application suites (for example, Microsoft Excel is an application, which may be evidence of the Microsoft Office suite). Suites are a collection of applications that are sold as a combined unit (although sometimes the individual applications are also sold separately).

On this tab, you can specify whether this application is either:

A suite that contains other applications (for example, Adobe Creative Suite)
An application that is (or can be sold as) a member of a suite (for example, Adobe Photoshop).

This corrects your license consumption calculations, and helps clean up your evidence lists (for more details, see Do I Need to Set Up a Suite of Applications?).

From the Application suite type list on the Suite and member tab, you can select any of the following:

Standalone application (default) — means that this application is neither a suite nor a member of any other suite. With this setting, the rest of this tab has no further purpose.
Member of a suite — indicates that the application you are creating or editing can be a member of a suite of applications. To identify its parent suite, click Search, select a record on the list, and click Add suite or application.
Suite containing applications — indicates that the application record you are creating or editing is a suite itself. To link its member applications, click Search, select one or more application records, and click Add evidence.
Remember: If you selected Suite containing applications, you can optionally use the presence of its member applications to detect the installation of the suite (especially for cases where the suite does not leave distinct installer evidence). To do this, use either or both of these controls:
- Enter a value into the Minimum installations for suite recognition field. This indicates the minimum number of applications associated with the suite that must be present for that suite to be recognized as installed. For example, if you add four applications, and type in 3 into the Minimum installations for suite recognition field, then the presence of any three of these four applications causes recognition of the installed suite. However, where only two member applications are found (or any number less than the specified minimum), these consume from their own separate licenses, and not from the suite license.
  Tip: Suites identified by the Application Recognition Library default to requiring all the member applications of the suite for recognition by this method. Adjust the number to suit your circumstances.
- From the Choose columns dialog box, you can add the Required column, and select those member applications that must all be present for the suite to be recognized as installed. When any application marked as required is missing, the suite is not recognized.
You can use these controls in combination: for example, a minimum requirement of three of the four linked applications, with one of these marked as required. The suite is then recognized when the required application and any two of the remaining three applications are present. You can also ignore these settings, and use other kinds of evidence, such as installer evidence, to recognize the suite.

Suite recognition from application evidence is based on the presence of all required applications and the Minimum installations for suite recognition setting (whether Required or not).

The software that is sold as a suite is not very different from a single application in terms of licensing workflows. Therefore in FlexNet Manager Suite, a suite of applications is treated as a special case of an application with additional evidence records where applicable. For more information on bundles and suites, see Multi-Product License.

The following table lists all columns available on the Suite and member tab.

Column name	Details
Added application	This column displays `Yes` if an operator manually associated an application with the evidence. `No` is displayed if the application is provided through the Application Recognition Library.
Added suite	This column displays `Yes` if an operator manually assigned an application to a suite as its member (by selecting Member of a suite on the Evidence tab). `No` displays if it is assigned through Application Recognition Library.
Category	The broad function of the application, by default from the UN Standard Products and Services Code. For local applications, this field is editable in the General tab of the application properties. (Additional custom categories can be created in Enterprise > Categories.)
Classification	The type of software, especially as it relates to licensing (freeware, commercial and so on). Visible on the General tab of the application properties. It is editable only for applications with a Source value of `Local`.
Edition	The edition of an application, as specified by the publisher of this application. Visible on the General tab of the application properties. It is editable only for applications with a Source value of `Local`.
Installed	The count of installations of this application, calculated from evidence matched in the last imported inventory. Not editable. The installed count is recalculated after each inventory import.
Name	The application's name, which may be: Set by the Application Recognition Library (for applications with `Source: Flexera`), and not editable Derived from the evidence values for Product, Version, and Edition properties (when generated by FlexNet Manager Suite), and editable to suit your corporate standards. You can edit this on the General tab of the application properties when `Local` is displayed in the Source column (which means the application was added manually by an operator).
Product	The basic name of the application, excluding the publisher and references to versions or editions. This field displays the value `Multiple products` for multi-product licenses that have multiple primary products. See Multi-Product License. Product names are supplied by the Application Recognition Library and are not editable. New product names created within your enterprise are editable in the General tab of the application properties.
Publisher	The name of the publisher of this software, responsible for its development and distribution. For application records that you create manually, Publisher is editable in the General tab of the application properties. For applications supplied through the Application Recognition Library, the Publisher field is not editable.
Required	From the Choose columns dialog box, you can add the Required column, and select those member applications that must all be present for the suite to be recognized as installed.
Source	The origin of an application record: `Flexera` — Shown when the application is downloaded in Application Recognition Library (if so, you cannot edit any of the application’s properties, but can link it to additional evidence). `Local` — Shown when an operator in your enterprise created the record for this application. `Flexera (Extended)` — Shown when an operator added additional evidence to the original record from Application Recognition Library.
Status	Indicates your assessment and processing of an application. It can have any of the following values: `Authorized` `Deferred` `Ignored` `Inactive` `Unmanaged`. Editable in the General tab of the application's properties, or by selecting the application and using the Change status button in any of the following lists: Installed Applications Unmanaged Applications Managed Applications Deferred Applications Ignored Applications All Applications.
Version	The release number (or release identifier) of an application. Visible in the Version field in General tab of the application properties. Editable for applications with a Source value of `Local`. For applications from the Application Recognition Library, it is not editable.