Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
270 views

Exclude RFC from Time Period based on value of a field

Jump to solution

Goal: Exclude any RFC where IMC is the business area

Desired results: When creating any RFC where IMC is the business area we need to exclude this from being included in the Change Freeze (Time Period).

Process to date:

If there is a Change Freeze that includes 06/30/17 to 07/04/17 and the RFC’s scheduled start and schedule end time is within this time, this conflicts with the freeze window.

When this happens the RFC will have a popup letting you know that the RFC is scheduled within the Change Freeze and there is an additional approval required (CIO).

Process change desired:

The change that we would like to see is that when a RFC has a business are of “IMC” we would like to exclude the RFC from the Change Freeze and exclude the RFC from the additional approval (CIO).

Proposed solutions: Here are some of the solutions that I have tried but may have something wrong.

  1. Rule Set to set field to value- Set the Time Period conflict to a value of 0

 Rule setRule setApproval DefinitionApproval Definition

 2. Change the Approval Definition- Wanted to see if there needs to be a change to the approval definition

0 Likes
1 Solution

Accepted Solutions
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

If the business goal is to avoid the CIO approval, you could simply change the condition for SSC-CIO approval to be:

tpconflict in $L.file>0 and business.area in $L.file~="IMC"

View solution in original post

0 Likes
2 Replies
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

If the business goal is to avoid the CIO approval, you could simply change the condition for SSC-CIO approval to be:

tpconflict in $L.file>0 and business.area in $L.file~="IMC"

View solution in original post

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
 
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.