I used to read mom_cycle_text and execute some custom cycles, moves or whatever...
Note for Post Builder (I assume the same for Post Configurator) A "standard text" cycle calls the proc MOM_drill_text_move.
Rather than depend on what a user enters in the "TEXT" field in NX, in (my over-ride of) that procedure I check for UDE variables, and handle the "cycle" appropriately.
If no UDE variables are found, user gets an error.
1) Requires a UDE for every "text" cycle you want to implement
2) Requires you to clear (unset) all the UDE variables at "end of path" (so next, possibly different, text cycle doesn't do the wrong cycle)
3) If you are using the CLS file for external posts, this may not work.
Production: NX10.0.3.5 MP16/TC11.2
I'd rather be e-steamed than e-diseaseled