| Name | Description |
| add | Create a new Operation. |
| 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(). |
| createInput | Creates a new OperationInput object, which is used to define the operation you want to create. Use properties and methods on the returned OperationInput object to define the desired operation and then pass it into the add method to create the operation. |
| item | Function that returns the specified operation using an index into the collection. |
| itemByName | Returns the operation with the specified name (as appears in the browser). |
| itemByOperationId | Returns the operation with the specified operation id. |
| Name | Description |
| compatibleStrategies | Gets a list of the strategies that are compatible with the parent setup. This only returns strategies that are allowed to be added based on the active Setup or CAMFolder. Note: There may be cases where a compatible strategy might not be allowed to be created due to licensing or other issues like disabled preview features. |
| count | The number of items in the collection. |
| 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(): |
| Name | Description |
| Generate Setup Sheets API Sample | Demonstrates generating the setup sheets for an existing toolpath.. |
| Generate Toolpaths API Sample | Demonstrates generating the toolpaths in the active document. |
| Hole and Pocket Recognition API Sample | This sample script demonstrates three different methods for feature recognition: one for holes and two for pockets. The script starts by creating a simple component which is then used to demonstrate the three methods. After the features are recognised they are coloured and milling and drilling operations are created for each feature. RecognizedHoleGroup returns a list of BRepFaces that can be used as selections for the drilling operation. RecognizedPocket and PocketRecognitionSelection do not return BRepFaces, and their output needs additional processing before the output can be used for creating machining operations. The sample script demonstrates a couple of different methods, including finding the pocket BRepFaces and creating sketches from the recognized pockets. This script works only if the Manufacturing Extension is active. |
| 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, a few operations, pick some tools from a Fusion sample tool library using loops and queries and ends up post-processing the operations out using an NC Program. |
| Post Toolpaths API Sample | Demonstrates posting toolpaths in the active document. |