{"id":394,"date":"2021-06-23T10:32:30","date_gmt":"2021-06-23T14:32:30","guid":{"rendered":"https:\/\/www.tks-designs.com\/blog\/?p=394"},"modified":"2021-06-23T10:34:19","modified_gmt":"2021-06-23T14:34:19","slug":"shotgun-action-menu-item-ami-server","status":"publish","type":"post","link":"https:\/\/www.tks-designs.com\/blog\/?p=394","title":{"rendered":"Shotgun Action Menu Item (AMI) Server"},"content":{"rendered":"\n
\"\"<\/a><\/figure>\n\n\n\n

The #1 request every studio wants is the ability to run actions on their pipeline through the Shotgun web interface. Luckily SG allows this through the use of Action Menu Items<\/strong> (AMIs). The jist is: choose an Entity type in the web interface (ie Version<\/strong>), name your new Item (say Render Slates…<\/em>), and setup an IP address to receive this information. SG then encapsulates the users’ selection of that entity type (either one or multiple entities) and sends the data to the receving machine, re-directing the users’ web browser in the process. With that data & connection, the machine at the other end can perform any action (say, submit all selected shots to the farm) and provide the end user with visual feedback (success, failure).<\/p>\n\n\n\n

I developed a plugin-based AMI Server (philosophically similar to the Shotgun Event Server<\/a>) for just this purpose, and I’m very happy with the result. The key is not only to perform the action, but to provide feedback to the user in a friendly and readable way; the user should be able to tell clearly whether the action has succeeded or failed. I even had a friend in CSS design whip me up a nice-looking CRT-style output because, why not \ud83d\ude09<\/p>\n\n\n\n

Check out the video below to see it in action!<\/p>\n\n\n\n

\n