Category | Requirement
-- | --
Must have | the owner will be able to define the name of the mandatory label
Must have | the user can assign whatever value to the mandatory label
Must have | the owner will be able to define multiple mandatory parameters
Must have | the owner will be able assign the policy system-wide
Nice to have | the owner will be able to assign a policy to a specific team
Nice to have | the user can only choose from a set of possible values for a certain mandatory label
Nice to have | the owner can assign conditions to certain mandatory labels (no clear functional requirements given on what these conditions could be)
Nice to have | Naming convention (no clear functional analysis of what should be included in the naming convention)
ID 1dff037
<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
At the moment, the only property that should be enforced by a policy are labels. The owner of IESI wants to ensure that all scripts have a certain label assigned, this means that those labels could be mandatory if they are defined in the script-policy configuration.
Category | Requirement -- | -- Must have | the owner will be able to define the name of the mandatory label Must have | the user can assign whatever value to the mandatory label Must have | the owner will be able to define multiple mandatory parameters Must have | the owner will be able assign the policy system-wide Nice to have | the owner will be able to assign a policy to a specific team Nice to have | the user can only choose from a set of possible values for a certain mandatory label Nice to have | the owner can assign conditions to certain mandatory labels (no clear functional requirements given on what these conditions could be) Nice to have | Naming convention (no clear functional analysis of what should be included in the naming convention)