Autodesk adds ability to script classifications in Fusion Lifecycle

I’ve been waiting for this update to Autodesk Fusion Lifecycle for awhile. You can now programmatically interact with item classifications via scripting.  

Classifications in FLC allows for different form fields to apply to different classes of items in a  single workspace. So in this context, if you apply classifications for example to a part workspace, you can have different types of information saved for different types of parts. A mechanical component would have different attributes than an electrical component. 

Prior to this update, manipulation of classifications was all a manual process. You had to choose the classification when creating or editing the item and you couldn’t easily retrieve that information for use.

You can now write and read to an item classification after the item has been created. In the first scenario this would make FLC more useful is a workspace I use for task management. We have different types of tasks for different kinds of actions that need to happen as part of the process FLC manages. Now instead of just the simple comment field from the task’s workflow actions menu, you can add any type of field to gather input for the specific task type. 

This would also allow you to script changes in the classification as the task progresses through the process:

  • User 1 needs to enter ABC information. Classification set to allow ABC fields for entry.
  • User 2 needs to read ABC information and enter XYZ information. Classification set to hide ABC entry fields and show ABC read-only fields. XYZ fields are shown to gather input.


I’m really looking forward to getting creative with this new update. I believe this is a good situation where the new functionality can definitely be exploited for other uses beyond what the original intent was by Autodesk.

Follow the updated help documentation for how to implement.


VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Permanent link to this article:

My Very 1st AU Class Proposal

A long time overdue, but I finally submitted my first ever Autodesk University class proposal. Check it out and vote if you think it’s worthy. Visit the voting site and look up “Hack the Vault Job Processor”. 

“Out of the box, the Vault job processor is a great way to keep your data updated. The job processor can update visualization files, create PDF files or synchronize properties. The job processor also has lots of limitations. This course will show you how to hack your job processor through custom jobs to allow more granular control of your design automation tools. Learn how to create a custom job processor job, learn how to interact with the jobs by setting priorities for different job types, query the job queue, add or remove jobs to the queue. With this additional functionality you’ll be able handle different types of files separately and learn how to take control of your Vault.”

Key Learnings:

• Understand the out-of-the-box limitations of the job processor
• Create a custom job and configure it to run
• Employ the extended capabilities available with the Job Processor API
• Develop your processes further using the design automation capabilities of the Vault job processor.


VN:F [1.9.22_1171]
Rating: 5.0/5 (1 vote cast)

Permanent link to this article:

Swift Prints for Inventor 2021

Swift Prints for the all new Inventor 2021 is now available from the Autodesk Apps Store. This version doesn’t bring any new and exciting features but it does provide and all new additional method for licensing.

If you already own a license of Swift Prints, you can still sign into the Autodesk account you used to purchase Swift Prints. This method allows for a single license of Swift Prints to be active for the signed in user. You can use Swift Prints on any computer you use while signed in.

New for 2021: You can also now purchase a license or multiple licenses of Swift Prints for your entire organization which does not require you to be signed into an Autodesk account. Using the App Store, you can purchase a license and enable the application using a license key. You can also disable Swift Prints and reauthorize it on additional computers when needed.

Buy now from the Autodesk Apps Store | App Store


VN:F [1.9.22_1171]
Rating: 5.0/5 (1 vote cast)

Permanent link to this article:

maxReceivedMessageSize error in Vault

Here’s something interesting I learned today in regards to Vault when it comes to checking in large files. While debugging issues with large 30+mb drawing files that kept failing on the Job Processor I did some digging. The Job Processor error coincided with the Vault FileStore log error stating:

Exception(Inner): The maximum message size quota for incoming messages (52428800) has been exceeded.
To increase the quota, use the MaxReceivedMessageSize property on the appropriate binding element.

After doing some digging on Google, I discovered if you change the setting maxReceivedMessageSize in the web.config file on the Vault Server from the default value of “52428800” to at least “92428800” the issue is resolved. You should replace every matching value in the web.config.

This helps with large file check-in and should reduce the number of issues your clients experience as well as issues with the Job Processor.

VN:F [1.9.22_1171]
Rating: 4.0/5 (1 vote cast)

Permanent link to this article: