Hello All,
I was reading through the configurator technical reference guide and I came across a section about the On Load event for the configurator and in that section it says that we can, “set the configuration as complete, [which causes] the application to skip pages and instead execute the On Leave event of each page….”
So… my question is, how do we “set the configuration as complete?”
Please see the attached excerpt from the 10.2.300 configurator tech ref guide on this.
Respectfully,
Utah
Are you trying to programmatically finish the configuration, so the user doesn’t need to got to the last page and click save?
I don’t even want to see the configurator.
There is misleading phrasing in the Configurator documentation that implies you can have a smart string as in input. But this doesn’t really exist.
I would not like to use a smart string. I just don’t want to see the sub configurator in one of our methods.
It should just skip over the whole thing as there is nothing to select.
Have you looked at a “No Inputs” configurator. I’ve never tried it as a sub configurator. Details in the Techref guide.
No inputs configurators cannot be used as subconfigurators. Such a beautiful restriction.
Can you give us an overview of what’s going on within the parent configurator? For example, is it dropping the part in question, or are there options that are applied in the parent that then mean that the part can be standard rather than configured?
We are swapping out a subassembly in the parent configurator with another configurable part. The only reason that we have that part as configurable is becuase it will not launch the subconfigurator inside of it. So since it HAS to be configurable, we just created a dummy configurator with a blank page that the user clicks through. after they click through it, the subconfigurator launches for the part inside of it.
What about treating it like a hybrid template/super BOM? Have both subassemblies listed as materials, making sure the configurable one is pulled as an assembly, with Keep When rules in place so that only one is ever kept. That might allow the configurator to detect the configurable part within the subassembly (when kept) without having to make the subassembly configurable because the configurable part shows up directly on the BOM.
Super boms are not maintainable for our organization. Way too many keep when rules to write and keep track of. To clarify, the assembly that we are configuring is 2 levels down. It is a child of a child to the parent part which also poses a problem when rev and mom structure changes occur. All the method rules get messed up if you change assembly sequences or mtl sequences.The way we are attempting to create our configurators eliminates the need for many keep when rules and the problems of having child method rules, but in order to do it, we have to use subconfigurators and these dummy subconfigurators that I do not want to see.
How many “inputs” determine the sub-sub-assembly?
Are these sub-assemblies phatoms by chance?
One Input determines the sub sub assembly. The subassemblies are not phantom right now.