Do any one have any resource about creo parametric customization

https://youtu.be/H9MzRCDQ_fY?si=rHd7W2ssUsbmasgP

Depends on what you are trying to accomplish for customization objectives.

Something “in” Creo as a module or “outside” that interacts with Creo; that can impact your path to implementation.

I would also ask yourself IF a user is required to be in the loop for usage or is it just a process that analyzes or manipulates data.  The various end user experience paths are important to understand, if it is a simple thing, you can get by with simpler approaches and tools, deeper things require access to lower level capabilities.

Generally speaking, a best practice, I would focus on the flow of data and then what customizations enable that.  Then the question of user involved or not involved and what APis would be best suited help bring things to focus pretty quickly.

Data flow first, then user experience, then pick the tools to enable.

If you are looking to streamline the generation of variations or configurations, it might be better to look at Pro/PROGRAM as a mechanism for part and assembly customizations.  Pro/PROGRAM specifically is a hidden gem that is not obvious, but very powerful when applied in a limited/focused fashion (turn on/or features and components via parameters as an example).  If you are thinking that customization of parts and assemblies is a priority, I would look at Pro/PROGRAM first to see what is possible.  However, I would avoid EXEC statements to pass parameters around if you are going to have item reuse concerns for those scenarios - instead find a way to target the models with data and “trust” they models will regenerate properly.   If you are looking into Drawing Automations, I would not try to automate there (except for some basic things) -- instead I would suggest “trusting” the parametric show/hide of dimensions, notes, driven from the models vs drawing level decisions whenever possible.

If you install ObjectToolkit - I think there are working examples in the distribution you can look at and reference.  ObjectTookit is likely a heavier lift for simple things (e.g. open models, pass parameters, regen models, export, etc.)

If your customization objectives are more focused on batch processing or one-off generation of derived models and drawings - this is likely easier to get rocking with CREOSON and the python interface CREOPYSON (BOTH free / open source, just requires JLINK to be installed with your Creo installation.

if you still need ObjectToolkit - the open source libraries are useful to understand some of the core semantics of how Creo interacts and works (at a lower level)

Hope this helps!

Dave