cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Configration Management Global policy

ptc-6083798
1-Newbie

Configration Management Global policy

How to set Global Policy for Change Packages?

Can we set the Change Package Reviewers to multiple users and anyone can approve/accept the change package (No need to accepted by all the members listed .) we don’t want group.

Requirement is the out list of reviewers any one can accept the change package

1 ACCEPTED SOLUTION

Accepted Solutions
mrump
14-Alexandrite
(To:ptc-6083798)

Hi overcautious anonymous community member A A,

well IMHO (based on personal experience and reading the manual ) the only way to achieve the behavior you want (only one reviewer out of a group of reviewers need to accept the CP) is using groups.

The property setup is quite straight forward:

Every "principal" (being a user or group) that is listed in the "Change Package Reviewers" property must accept the CP.

This means:

  • if you specify a list of users, each of these users has to accept.
  • if you specify a single group (e.g. "review team"), at least one member of this group has to accept the CP.
  • if you specify a list of groups (e.g. "QA team", "development team" and "test team"), each of the groups has to accept, meaning that at least one member of each group has to accept the CP.

and of course you can mix this


  • if you specify a list of groups (e.g. "development team" and "test team") and a single User (e.g. your system architect), each of the groups (meaning that at least one member of each group) and the system architect user have to accept the CP. That is minimum 3 accepts in total.

The "append" checkbox indicates that in a hierarchical setup the reviewer property can be inherited from the upper level and is only extended by the current entries.

HTH Matthias

View solution in original post

1 REPLY 1
mrump
14-Alexandrite
(To:ptc-6083798)

Hi overcautious anonymous community member A A,

well IMHO (based on personal experience and reading the manual ) the only way to achieve the behavior you want (only one reviewer out of a group of reviewers need to accept the CP) is using groups.

The property setup is quite straight forward:

Every "principal" (being a user or group) that is listed in the "Change Package Reviewers" property must accept the CP.

This means:

  • if you specify a list of users, each of these users has to accept.
  • if you specify a single group (e.g. "review team"), at least one member of this group has to accept the CP.
  • if you specify a list of groups (e.g. "QA team", "development team" and "test team"), each of the groups has to accept, meaning that at least one member of each group has to accept the CP.

and of course you can mix this


  • if you specify a list of groups (e.g. "development team" and "test team") and a single User (e.g. your system architect), each of the groups (meaning that at least one member of each group) and the system architect user have to accept the CP. That is minimum 3 accepts in total.

The "append" checkbox indicates that in a hierarchical setup the reviewer property can be inherited from the upper level and is only extended by the current entries.

HTH Matthias

View solution in original post

Announcements