The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Hidden field was still displayed on preconfigured page

Highlighted
JudyZhu
Regular Collector

Hidden field was still displayed on preconfigured page

For a request type, we designed a rule to hide a field on step A based on the value of another field. On the next step B, the field is set as required.

 

Case 1: on step A, the field is blank and visible. Then going to step B, the preconfigured page showed up to request to fill the field because the field is mandatory for step B. It is as expected.

 

However for Case 2: on step A, the field is blank and the rule is triggered to hide the field. Then going to step B, the preconfigured page still displays to ask for the value of the hidden field.

 

As we understand, once the field was hidden, it should not be in the preconfigured page even it was set as mandatory for step B.

 

Is this an known issue for PPM?

 

Any workaround?

 

Judy

 

 

 

3 REPLIES
TurboMan
Member

Re: Hidden field was still displayed on preconfigured page

Hi Judy,

 

I am just making assumptions, When defining rules make sure you have the Process Subsequent rules "Yes" .

 

 

JudyZhu
Regular Collector

Re: Hidden field was still displayed on preconfigured page

Hi TurboMan,

Yes we set Yes for Process Subsequent. It looks like the ready-only field will not be saved even the value was changed by rule.

Any idea?

Judy
dlinetsk
Member

Re: Hidden field was still displayed on preconfigured page

Hi Judy,

 

this is a known issue - we submitted a case to HP a while ago.

 

Basically, UI rules on forms are not corelated with Status Dependences. 

 

Our case was a bit different, but the issue is the same.

 

We had a Field A that when populated with "YES" sets another Field B as required.  

 

Field A is a required field defined in Status Dependences. When transitioning to next step, the user is asked to populate Field A on the preconfigured page, but Field B does not show up on the preconfigured page at all, so UI rule does not see it and does not set it as required when Field A is set to "YES".  

 

Our work around was to Reconfirm Field B, so it shows on the preconfigured page together with Field A always, then UI rules worked ok on preconfigured page.

 

We belive this is a bug.

 

Thanks,

Dmitry

//Add this to "OnDomLoad" event