This content has been marked as final. Show 2 replies
did you mark both parameters as required ? If so then a missing parameter will lead to this error. What I would do in this situation is to use two parameters as follows
- task flow type : values are jobType and jobGroup
- the second parameter then would be the valueId: Here you either pass the value of the jobType and jobGroup
This way you can always pass the parameters to the task flow so that a required parameter doesn't hurt.
Frank thanks for your reply.
I tried your idea. I first tried passing in the Job or JobGroup selected as the second parameter. However that doesn't work because setMainContent requires a Map as the second argument.
I then tried putting the Job or JobGroup into a Map. If the user selects a Job I put that Job into the Map with key value of "selectedValue". Likewise, when user selected a JobGroup, I put the JobGroup into a Map with key value of "selectedValue". The error no longer occurred. However, the value in the pageFlowScope.selectedValue inside the task flow is always set to the first item selected. For example if a user starts out by selecting a job named "Jobxyz", the correct "Jobxyz" object was in the pageFlowScope.selectedValue. Subsequently, when the user selects a job named "Job123", the value in the pageFlowScope.selectedValue is the "Jobxyz" object. This also happens when I move between job groups and jobs. It's always the first value selected that makes its way to the pageFlowScope.selectedValue.
Do I need to somehow reset the Map that the UI shell uses for passing in task flow parms?