Page Comparison

...

Default principle sets can be defined per team type via Settings / Org Structure type config. Select a team type, then choose a preferred principle set for that team type.

...

JSON parameters for Principles:

...

^title Count of people that have matching values for a specifid specified field by number or by ratio

...

      {
        "type": "FIELD_MATCH",
        "args": {
          "field": "country",
          "min": 8,
          "max": 10,
          "argsmetric": { "count"
        }
      "field": "country",
          "min": 8,
          "max": 10,  }

In the above, if there are any values for the country field where less than 8 or more than 10 people have a matching value the principle evaluation fails.

Also supports signal overrides.

See Role Tag Parameters for details on the roleTagType and roleTagAttribute parameters.

Demand Allocation Ratio

^parameter minAllocationRatio,maxAllocationRatio,includedTags,excludedTags,fteThreshold,includeVacancies,useFteRatio

^title <%- actualAllocationRatio %>%</strong> members are allocated to demand structure.

{
            "metric"type: "countDEMAND_ALLOCATION_RATIO",
        }    args:   }

In the above, if there are any values for the country field where less than 8 or more than 10 people have a matching value the principle evaluation fails.

Also supports signal overrides.

See Role Tag Parameters for details on the roleTagType and roleTagAttribute parameters.

Demand Allocation Ratio

^parameter minAllocationRatio,maxAllocationRatio,includedTags,excludedTags,fteThreshold,includeVacancies

^title <%- actualAllocationRatio %>%</strong> members are allocated to demand structure.

{{
              fteThreshold: 0,
              includeVacancies: false,
              typeincludedTags: "DEMAND_ALLOCATION_RATIO",[],
              argsexcludedTags: {
              fteThreshold  NON_PACE_ALLOCATION: 0[],
              includeVacancies  RESOURCEAVAILABILITY: false[],
                includedTagsNON_PACE_ALLOCATION_DEFAULT: [],
              excludedTags:},
{                 NON_PACE_ALLOCATIONincludedTeamTypes: [],
                RESOURCEAVAILABILITYexcludedTeamTypes: [],
                 NON_PACE_ALLOCATION_DEFAULT: []"Working With Agile"
              }],
              maxAllocationRatio: 100,
              minAllocationRatio: 90
            }
          }

Notes:

• useFteRatio - default is false. When set to true the ratio is calculated from the sum of allocated FTE (with over allocation ignored) as a percentage of total available FTE. When set to false the ratio is the number of members that have any demand allocation at all as a percentage of the total number of members.

Line Manager Count

^parameter maxManagers

...

Note: needs verifying by a dev (update this is only used by 1 customer so might not be something we use more broadly with a common set of needs()

      {
          "type": "ROLE_CONFORMITY",
          "args": {
              "requiredTags": [
                  "tag", "tag", "tag"
                ]
          }
      }

...

    { 
          "type": "TIMEZONE_OVERLAP",
          "args": {
                "goodOverlap": 3
          }
    }

Signal Overrides

By defaults default the are three signals for principles they are:

...

For principles that support the roleTagType parameter this can be a string with a specific tag type (e.g. SPEICALIST SPECIALIST) or it can be a list of tag types like:

...