Question
Last activity: 18 Dec 2015 1:53 EST
"Please correct flagged fields” when selecting another flow action. How to avoid?
Hello!
I have a big form on a flow action. If user wants to select another flow action, then Pega does not allow for this and asks to fill all the fields marked as Required.
Are there any solutions for this?
Thanks.
Hi!
Pega version is 7.1.8. Yes, this is a client-side validation when you have ‘Required’ flag for property on a section.
Alexey Titorenko
Lead System Architect
SYMPHONY BUSINESS INTEGRATOR S.R.O.
FraÅa Kráľa 35 | 811 05 Bratislava | Slovakia
<http://www.symphony.eu.com/> <http://www.symphony.eu.com/>Website <http://www.symphony.eu.com/> | email <mailto:[email protected]> | Facebook <https://facebook.com/symphony.eu> | Skype <http://www.symphony.eu.com/Signatures/Alexey%20Titorenko>
Tel: 7 926 218 22 17 <tel:7 926 218 22 17>
Hi!
Pega version is 7.1.8. Yes, this is a client-side validation when you have ‘Required’ flag for property on a section.
Alexey Titorenko
Lead System Architect
SYMPHONY BUSINESS INTEGRATOR S.R.O.
FraÅa Kráľa 35 | 811 05 Bratislava | Slovakia
<http://www.symphony.eu.com/> <http://www.symphony.eu.com/>Website <http://www.symphony.eu.com/> | email <mailto:[email protected]> | Facebook <https://facebook.com/symphony.eu> | Skype <http://www.symphony.eu.com/Signatures/Alexey%20Titorenko>
Tel: 7 926 218 22 17 <tel:7 926 218 22 17>
This email may contain confidential and/or private information.
If you received this email in error please delete and notify sender.
JPMC
IN
Hi Alexey,
I did a quick test in Pega 7.1.8 by loggin in as [email protected] and creating an OOB WO (General Task) and changing the floaction from other actions menu, but do not see the above mentioned erros. Instead am able to easily switch between flowactions.
Could you please try this with OOB operator id ?
I found one interesting thing….
In the same application one form allows to change flow action without any problems, but on another screen the problem appears.
Harnesses are different, but configurations a the same (the same chechboxes are checked and not custom scripts on both).
So, there is not need to use OOTB user as event under current user one form works fine.
One noticeable difference between forms is presence of tabs on the problematic one.
Alexey Titorenko
Lead System Architect
SYMPHONY BUSINESS INTEGRATOR S.R.O.
FraÅa Kráľa 35 | 811 05 Bratislava | Slovakia
I found one interesting thing….
In the same application one form allows to change flow action without any problems, but on another screen the problem appears.
Harnesses are different, but configurations a the same (the same chechboxes are checked and not custom scripts on both).
So, there is not need to use OOTB user as event under current user one form works fine.
One noticeable difference between forms is presence of tabs on the problematic one.
Alexey Titorenko
Lead System Architect
SYMPHONY BUSINESS INTEGRATOR S.R.O.
FraÅa Kráľa 35 | 811 05 Bratislava | Slovakia
<http://www.symphony.eu.com/> <http://www.symphony.eu.com/>Website <http://www.symphony.eu.com/> | email <mailto:[email protected]> | Facebook <https://facebook.com/symphony.eu> | Skype <http://www.symphony.eu.com/Signatures/Alexey%20Titorenko>
Tel: 7 926 218 22 17 <tel:7 926 218 22 17>
This email may contain confidential and/or private information.
If you received this email in error please delete and notify sender.
JPMC
IN
ok, thats interesting. It proofs its not a bug at your end and not got that behavior through some hotfix as well, as we have few usecases working fine.
Few test which we can do:
1) Use the OOB Work-Perform harness (present in Pega-EndUserUI:07-10-13) and test the behavior
2) Remove the tabbed structure (just for testing), though i feel it should not be because of tabbed layout for sure... but better to cross check...
Is this an upgraded system or a fresh Pega 7.1.8 ?
Hello all!
We have found a reason for such behaviour. The fact, that the problem appears only on some flow steps, not all, allowed us to find it.
The problem was caused by the fact, that we put FlowActionHTML_Simple section into a layout in harness. This is needed to split work area as we need. Those steps, which work fine, do not have such modificaiton.
We changed harness configuration in a way, when both pyCaseHeader and FlowActionHTML_Simple are within the same layout. Actually, we put both into a section and put a section into layout.
This workaround may not be applicable for all situation, but it works in our case. At lease for now.