+6
Rejected

Honor parent/child relationship when required parent field is set to empty or value is changed

Joe Cerep 9 months ago in Productivity Management updated 7 months ago 3

Comcast Aprimo - Monday, December 9, 2019 1....mp4 
Please see attached video. 


We are experiencing a change in functionality that began when the "This field is required. Input Error" messaging was added to the Task Inbox. This issue is regarding cascading DCTs with parent/child relationships. When a required parent field (1) has a value entered, a required child field (2) is triggered. If the required child field (2) has a value entered, another required child field (3) is displayed. At this point, field (2) is unable to be set to empty, even if the value for parent field (1) is updated and field (2) should no longer be displayed.

The request is to have parent/child relationships honored in the task inbox at all times. If the value that triggers a child field is not present in the parent field, the child field would not be displayed. Ticket CS0026742 was closed and we were referred to submit a Voice request.

Rejected

I have discussed this internally with the PM team and we have determined this is how we need these relationships to function.

One point you made is that if EA 2 is hidden its value is still causing EA 3 to be visible.  However, this is definitely functioning as designed because there are plenty of use cases where you DO want to use an EA value that you may never display to the user on a task to drive where other EAs are visible.  You ask a "Yes/No" question on a previous task and want that value to drive different EAs to show in a DCT on another task.  So we have to honor EA values even if the field is not visible.

Your other issue is that once they EA has a value if cannot be set back to empty.  Again this is a configuration decision and it needs to behave this way.  My understanding from my team is that the EA 2 that you are mentioning in your example above is required at the system configuration level.  NOT just at the DCT level.  If this is configured that way then what your seeing is FAE.  Once you set a value into a system level required EA, you can never set it back to "empty/null" again.  This is true on the Activity or Project Edit pages as well.  A required EA must be completed when it is visible and once you complete it, you cannot remove that value again anymore.

The solution to your issue can be solved with configuration.  Change the EA configuration in System Tools to set the EA to NOT be required.  Then in the DCT you can still set the EA to be required for just that DCT.  If you do that then when the EA is visible to the user they would have to set a value but if they clear the field and then also clear the parent field EA 1, then EA 2 will be hidden and if it is required but hidden the user will still be able to close the task and pass validation.

If you feel like we missed something about this or you did not follow my explanation, please reach out and let me know and we can discuss.

Thanks Eric,

I appreciate the detailed response. We weren't able to make the EAs in question not required as they were displayed on Work Request Forms and the only option for required vs optional at the Work Request Form level is the EA configuration in system tools. Regardless, I will be making changes to our main workflow/DCT configuration that should resolve this issue but I did want to clarify one comment you made for my own knowledge.

"Once you set a value into a system level required EA, you can never set it back to "empty/null" again. This is true on the Activity or Project Edit pages as well. A required EA must be completed when it is visible and once you complete it, you cannot remove that value again anymore."

EAs can be required at the system tool level but set to not required in a DCT. Is the description below accurate for the current functionality?

- EA that is required at system level is displayed as not required in a task DCT

- Task can be submitted with no value entered into that EA 
- If a value is entered into that same EA, the value can be removed but the task will not be able to be submitted until that  EA has a value in it

I completely agree this is a major issue and needs to be fixed.