Quirky one here, most of the time when we use child configurators, when adding a new child configurator to the parent the new child is automatically active.
We have one particularly complex parent/child CPQ, when you add a child configurator the new child tab is not automatically focused.
I am sure this is the result of the complex code we have in this particular CPQ which has been developed by three different people. However if someone maybe has some ideas, please throw them out there.
As I mentioned this particular CPQ has been through three people. The first person turned off the Auto-navigate to new option
This is understandable as they created some amazing Snap Code to auto populate several children based on a selection at the parent. With this feature turned on it is very disorienting as that rules runs to add several children all at once as the nested scrolls through the children as they are added.
I recently added some functionality to this CPQ so that items can be added manually one at a time. I have now added a Value rule to re-enable this feature when in the manual entry mode. So I have found a happy answer
1 Like