Project and Portfolio Management Practitioners Forum
cancel

Status Dependency on OOTB fields

SOLVED
Go to solution
Highlighted
Renju_Babu
Trusted Contributor.

Status Dependency on OOTB fields

I have an issue with setting the Status Dependency for Staffing Profile with the help of UI Rules.

My requirement is based on another field value Staffing Profile field should be required/not required.If we set the Status Dependency for Staffing Profile as required it will always show the Staffing profile as required irrespective of the Rules created and vice versa.

I have created the UI Rules on Page Load,Field Change and also tried before Transition but nothing works out.

The rule is triggering and its making the Staffing Profile as Required (* symbol) but its not prompting or not preventing the users to go forward.

 

Any idea how to resolve this issue?

Is it that for Staffing Profile type component we cannot even set the Status Dependency based on UI Rules?

Please let me know

 

Any help is much appreciated.

 

Regards,

Renju

3 REPLIES
dirkf
Acclaimed Contributor.

Re: Status Dependency on OOTB fields

Hi Renju,

 

sounds similar to the following defect logged:

 

 

QCCR1L46874 UI Rule "setFieldRequired" does not work for "Staffing Profile" validation

 

 

1. Create request type which refer to "PFM - Proposal" request header type.
2. Add UI Rule.
    Event: Apply on before save.
    Dependencies: N/A
    Result Field: Staffing Profile.
    Rule: setFieldRequired(true).
3. Create requests and leave "Staffing Profile" blank.
4. Try to save the request.
5. Observe that request is saved successfully.

The defect was first reported under 9.14 and is currently under investigation.

 

The workaround given in the defect is:

 


As a workaround what you could do is to use status dependencies instead of UI rules

Make the SP required ( not submitted ) for the request status.

Best regards,

Dirk

 

Renju_Babu
Trusted Contributor.
Solution

Re: Status Dependency on OOTB fields

Thank you Dirk for your response.

As a workaround I have made the Staffing Profile mandatory at the status.The issue is even though a Staffing Profile is not needed the users has to create a blank Staffing Profile(no Positions) for all the Proposal created.

Will wait and see what HP responds to the Defect.

 

Regards,

Renju

dirkf
Acclaimed Contributor.

Re: Status Dependency on OOTB fields

Hi Renju,

 

that's good news, thanks for the feedback with the good news.

Yes, I hope  that this will be solved quickly for you too.

 

If you have the info that you need, please consider checking this thread as solved :-)

 

Thanks ahead and have a good time.

 

Best regards,

Dirk

 

 

- kudos always welcome -