shotgunsoftware/tk-multi-workfiles2

Flow Production Tracking Toolkit File Manager helps you safely manage your Work Files

Documentation

This repository is a part of the Flow Production Tracking Toolkit.

• For more information about this app and for release notes, see the wiki section.
• For general information and documentation, click here: https://help.autodesk.com/view/SGDEV/ENU/?contextId=SA_INTEGRATIONS_USER_GUIDE
• For information about Flow Production Tracking in general, click here: https://help.autodesk.com/view/SGSUB/ENU/

Using this app in your Setup

All the apps that are part of our standard app suite are pushed to our App Store. This is where you typically go if you want to install an app into a project you are working on. For an overview of all the Apps and Engines in the Toolkit App Store, click here: https://help.autodesk.com/view/SGDEV/ENU/?contextId=PC_TOOLKIT_APPS

Have a Question?

Don't hesitate to contact us at https://knowledge.autodesk.com/contact-support

tk-multi-workfiles2's Issues

Decouple File Action Logic From UI

Hello!

Are there any plans to decouple the file action logic from the UI so that the actions could be called from other code paths?

My current use case is I am adding much deeper Perforce support and need to call the open and save actions from within hooks. In the future I am going to want to do this from other apps/frameworks.

I would love to have this so that all open, save, and new file logic would be available to call by the pipeline and located in one place as part of the tk-multi-workfiles2 app instance.

My apologies if this is already possible and I'm not seeing how by reading through the source.

BUG - Houdini - v14.1: UI styling white on white cards

The latest release of workfiles will style the cards in the workfiles app white with white text which makes it unusable.

Disable Publish Support

Hello!

I am looking to disable published workfile support in the workfiles2 tool. The reason is that our publishing model decouples the published files from the workfiles that generated them other than metadata and connections stored in Shotgun. Due to this, the publish template contains keys that can not be expanded from a Context.

Would an option to disable published workfile aspects of the tool be something that would be supported if I went ahead and added it? As far as I can tell there is no option to do this currently and so we are unable to use the tool.

Also, please let me know if I've missed something and there is an alternative way to deal with a scenario like this.

Best,

Tony