Object that represents a post configuration.
| Name | Description |
| classType |
Static function that all classes support that returns the type of the class as a string. The returned string matches the string returned by the objectType property. For example if you have a reference to an object and you want to check if it's a SketchLine you can use myObject.objectType == fusion.SketchLine.classType(). |
| Name | Description |
| capability | Gets the capabilities supported by the post. Capabilities define what types of operations can be post processed using this configuration. |
| description | Gets the description of the post. |
| extension | Gets the extension of the output file created by the post. |
| isValid | Indicates if this object is still valid, i.e. hasn't been deleted or some other action done to invalidate the reference. |
| objectType | This property is supported by all objects in the API and returns a string that contains the full name (namespace::objecttype) describing the type of the object. It's often useful to use this in combination with the classType method to see if an object is a certain type. For example: if obj.objectType == adsk.core.Point3D.classType(): |
| vendor | Gets the name of the vendor of the machine tool or controller this post configuration supports. |
| version | Gets the version of the post. |
| Name | Description |
| Manufacturing Workflow API Sample | Manufacturing Workflow API Sample. This sample script starts by creating a simple component, which is then used to describe a milling workflow. It creates a setup and a few operations, picks tools from a Fusion sample tool library using loops and queries, and post-processes the operations using an NC program. |
| Post Toolpaths API Sample | Demonstrates posting toolpaths in the active document using an NC program: import a post configuration from the post library, choose which setups or operations to include, set NC program and post parameters, and run Before running: Run from Scripts and Add-Ins with a design that contains at least one CAM setup with toolpaths. The script prompts for what to post (all setups, first setup, or first operation) and optionally opens the NC file when complete. It may offer to switch to the MANUFACTURE workspace. |
| Turning Workflow API Sample | Turning Workflow API Sample. This sample script starts by opening a simple component, which is then used to describe a basic turning workflow. It creates a setup and a few operations, picks tools from a Fusion sample tool library using loops and queries, and post-processes the operations using an NC program. |