What's changed

What's Changed

What's changed with the new out-of-the-box Shotgun Integrations.

With Shotgun 7.2, we introduced the concept of Shotgun Integrations: a set of basic tools, available in commonly used software packages, available without having to set up any configuration files. Now, when you select a Project in Desktop, you have the option to jump right in without any configuration at all. It will autodetect the software you have on disk, and inside each, you'll have access to the Panel, Publisher, and Loader apps.

And if you want to go deeper, all the existing Toolkit configuration functionality is still available.

In addition to this simpler setup, we've done a lot of cleaning up and revamping throughout the Toolkit codebase.

Here are some of the things that are part of the out-of-the-box Shotgun Integrations:

  • Every project will have a default set of integrations – both via Desktop and in Shotgun context menus – available off the bat, with no extra setup.
  • Out of the box, Shotgun Integrations no longer deal with folder structure and filenaming for your work files and publishes. There are no templates to maintain, and there is no filesystem schema.
  • Instead: For work files, you can use your host app’s native Project setup. For example, if you set up a Maya Project, you’ll just use Maya’s File Open/File Save commands, and your files will be saved according to your Project settings. Publishes can be discovered in Project locations, or dragged in from arbitrary locations.
  • No Workfiles app. Because you're not dealing with filesystem schemas and templates, you can just use your host application’s native File Open/File Save commands for file management. (Of course, you can choose to bring the Workfiles app, and templates and schemas, back into your workflow with the classic full setup.)
  • Set work area in the Shotgun Panel: In the absence of Workfiles, there's no way for Shotgun to know what entity to associate Publishes and Loads with, unless you've launched from an entity's context menu in Shotgun. We've added a button within the Panel where you can set your work area.
  • The Software entity: With no Pipeline Configuration, there’s no paths.yml or app_launchers.yml. With the new Software entity, you can manage paths to software packages, restrict visibility to specific users, groups, or projects, manage versions, and group applications within the Desktop app, all from within Shotgun itself.
  • We’ve added a descriptor field to our Pipeline Configurations entity. So if you are using a full Toolkit setup, you can manage Pipeline Configurations right in Shotgun, even for remote workers.
  • A new and improved Publisher! We’ve redesigned the Publisher from the ground up. In addition to running it from host apps, you can now run it standalone, straight from Desktop, and drag in arbitrary files to publish. And you can use the new publisher in classic Toolkit setups, too.
  • We’ve revamped Desktop’s websockets setup, which means lots of improvements for browser integration. We've got better menu organization in the web app, general speed enhancements due to a more robust caching mechanism, and we've added a browser_integration core hook, which allows for customization of some portions of the workflow. Note that as a byproduct of this revamp, you will need to be logged into a site in Desktop in order for browser integration to work.

If you'd like to customize your Toolkit pipeline, all of the classic configuration and extension tools are still there. Just choose "Advanced Project Setup" in Desktop to move a project from these basic integrations to a full configuration.

Tell the doc gen system that we don't want a table of contents by adding this special markup: TANK_NO_TOC



Article is closed for comments.