Understanding the BigFix Software Distribution Software Entity

In the BigFix UI, a Software entity is a logical, version-agnostic grouping of one or more Packages that represent different versions, flavors, architectures, or operating systems of the same application — providing a unified view of all deployment options for a given software title.

The Software entity is a concept introduced in the BigFix UI that has no direct equivalent in the legacy BigFix Console or WebUI. It acts as a higher-level organizational container above the Package, allowing administrators to manage multiple deployment variants of the same application from a single location.

A single Software entry can contain multiple Packages to accommodate:

  • Different versions of the same application — for example, version 2.3 and version 2.4 of the same product.
  • Different editions or flavors — for example, Standard and Enterprise editions.
  • Different operating systems — for example, a Windows package and a macOS package for the same application title.
  • Different processor architectures — for example, x64 and ARM builds.

Software as a Virtual Container

Unlike a Package, there is no discrete platform object in the BigFix Platform that represents a Software entity. Software exists exclusively as a conceptual grouping within the BigFix UI. The attributes and characteristics of a Software entry are entirely defined by the Packages it contains.

Warning:
Deleting a Software entry is a cascade operation. It permanently deletes all Packages contained within it, including all associated Files and Tasks. This action cannot be undone. Use the Delete Software action with care.

Software-to-Package Relationship Example

The following example illustrates how a single Software entry can span multiple Packages:

  • Software: NewsPaperCreator
    • Package: NewsPaperCreator v2.3 — Windows x64
    • Package: NewsPaperCreator v2.4 — Windows x64
    • Package: NewsPaperCreator v2.4 — macOS

Each Package is independent and contains its own set of Files and Tasks. Administrators can deploy any individual Package from within the shared Software entry.