Not much left to add from my side. As David said, it is in fact a kind of text version of the model tree (or better the model info) and you can insert conditional statements to skip (suppress) features based on parameters and relations in the model.
Speaking of relations, the usual model relations show in their own section within the Program.
Finally you can use the INPUT section of Program to prompt the user to enter variables for parameters (normally to drive the design as described above).
Whenever a model with INPUT is regenerated, it prompts the user.
However, when using such models in an assembly, you can force their regeneration and feed in the input programmatically from assembly level by using an EXECUTE statement inside the Program.
That's the short summary about what Program does. Details are in the PTC/Help.
How you want to use it for your models instead of family tables, is something you need to test with your own use cases - difficult to make any recommendations:
- For Program you always have to enter the appropriate values to get the desired design, which is more flexible as you just change the input parameters.
- For a family table all settings are predefined for each instance, but if you want a different design, you have to either modify an instance or create a new one.
