Content guidelines

Guidelines for relevance nodes in .bes files.

When creating content in your Git source repository, you must comply with the following guideline:

  • Always use standard <Relevance> nodes in your .bes files to define relevance conditions.
Correct example:
<Relevance>exists (operating system) whose (it as string as lowercase contains "Win" as 
lowercase)</Relevance>

Note: GroupRelevance Clauses are not supported.

You cannot use <GroupRelevance> clauses in your source repository .bes files. If your files contain these nodes, repository synchronization will fail during the site validation and export phase.

Incorrect example (Unsupported):
<GroupRelevance JoinByIntersection="false">
    <SearchComponentPropertyReference PropertyName="OS" Comparison="Contains">
        <SearchText>Win</SearchText>
        <Relevance>exists (operating system) whose (it as string as lowercase contains "Win" as lowercase)</Relevance>
    </SearchComponentPropertyReference>
</GroupRelevance>
If you use the unsupported <GroupRelevance> structure, you will encounter an error in your synchronization logs similar to the following:
Failed to sync repository site git@github.com:repo-owner/repo-name.git: Site validation and export failed: 
C:\Program Files\BigFix Enterprise\BES Server\RepositorySiteGather\Sites\repo-name\Source\Fixlets\Analyses\12345-Some Analysis.bes:
GroupRelevance clauses in .bes files not supported. Use standard <Relevance> nodes instead.

To fix this issue, extract the core relevance statement from the <SearchComponentPropertyReference> block and place it directly inside a standard <Relevance> tag, as shown in the correct example above.