service portal can't select the next button for order guide.

[P_8]

Hi Everyone,

I am facing this issue in Madrid release.

When the order guide form loaded from portal i can see the warning message in console as ""UI Script does not return an object: Conditional Focus".

Again after filling all the details, the next button is not getting redirected to further steps. Everytime i click the next button i can see the warning in console as "(g_form) [NOACTION] Could not find UI Action: submit".

As part other community discussions i changed the g_form.setValue('description', desc.toString());  but still the same issue persists.

could you please suggest any workaround for this issue.

[Mike Patel]

Make sure request method is set, like I showed on my post.

[Manikandan T]

I set to submit in catalog item in requested method ,then also it is not moving to checkout

[stuartgriffiths]

Also experiencing issues with Service Portal Order Guides since upgrade from NewYork to Orlando.

Order Guide widget has been cloned from the OOB widget with minor cosmetic customisation, but same behaviour with OOB widget.

Troubleshooting suggests it is related to UI Policies being used to hide variables leading to the <Next> button becoming unresponsive.

Multiple scenarios.

1. Button unresponsive on 'Choose Options' step.
 > UI Policy on item hides cascading variable sets.
 > Issue triggered when a variable is hidden on the Describes Needs step.

Workaround - amended UI Policy that hides the cascading variables, replacing single UI Policy Action set to act on the variable set with multiple actions, one for each variable in the set.

2. Button becomes unresponsive on 'Describe Needs' step.
 > Issue triggered when a variable that was made mandatory/visible TRUE via UI Policy is then set mandatory/visible FALSE by a separate UI Policy (use requires some complex form logic).

Workaround - changing the UI Policy Action such that variable was kept visible but not mandatory prevented the issue from manifesting. This is not an acceptable workaround for my use case so am continuing my investigations.

Am attempting recreate on a PDI with a view to raising a HI case.

[stuartgriffiths]

Update...

Have isolated the problem down to a new validation script - sys_script_validator.do?sys_id=c43ccb2c77170010e46abe41a91061cb.

The validation script interacts with the 'sp.validation.executor' UI scipt (sys_ui_script.do?sys_id=df652d52e7b21300b2888f49c2f6a9f6).

What I believe is happening:

• When the Order Guide form loads, a count of Date/Time fields fields is established in the widget scope data
• UI Policies then hide a previously visible Date/Time field, or vice versa.
• Click on the <Next> button.
• $scope.goNext() runs.
• Check (with console logging script lines added) the number of validation executions.
• The number of executions doesn't match the initial Date/Time field count.
• The process stops.

My workaround is to make the validation script inactive.

I'll raise a HI case.

[choff]

Thanks for this, Stuart. This didn't quite get me over the finish line, but I found & deactivated a second validation script for Date fields on the Service Portal (sys_id=2a7b4f2c77170010e46abe41a910618e) and that seems to have done the trick.

Can I ask how you were able to narrow it down to the validation script? It would be helpful for me to troubleshoot similar issues in the future. Thanks!