Old Actions

[jonathan-v]

Lately we have been digging deep into ftrack connect and the new actions implementation.  

We are finding that we don't like actions being so tightly connected to "connect".  It's quite cumbersome to get working correctly and really doesn't fit into our workflow.

 

I would love to just run an action without having connect running.  There are some instances where it's not even possible for us to run connect thus not allowing us to use actions at all.

We miss being able to run one listener from a server that activates all of our actions.  This even leaves us with the flexibility of writing a custom user listener that fits our facility.  As well as, managing permissions on who can run what action.   

 

In addition I miss the one click functionality of an action.  Rather than launching a menu, finding the action and then executing.  Just an unnecessary extra step.  

 

Is there any way to continue with the development of connect, but still allow for the old actions implementation?  Actions really were what I found to be the most powerful aspect of ftrack and not being able to take advantage of that has been sad. 

 

Really appreciate the help,

Jonathan

[Mattias Lagergren]

Hi Jonathan,

 

Lately we have been digging deep into ftrack connect and the new actions implementation.  

We are finding that we don't like actions being so tightly connected to "connect".  It's quite cumbersome to get working correctly and really doesn't fit into our workflow.

 

I would love to just run an action without having connect running.  There are some instances where it's not even possible for us to run connect thus not allowing us to use actions at all.

We miss being able to run one listener from a server that activates all of our actions.  This even leaves us with the flexibility of writing a custom user listener that fits our facility.  As well as, managing permissions on who can run what action. 

 

 

This is still completely possible and you don't have to have connect running to have custom actions. Connect leverages the same technology but you can still have standalone scripts running with actions outside Connect.

 

Here is information on how to develop custom actions:

http://ftrack.rtd.ftrack.com/en/latest/developing/actions.html#developing-actions

 

This is general information on actions:

http://ftrack.rtd.ftrack.com/en/latest/using/actions.html#using-actions

 

 

We will have look and see how we can clarify the documentation.

 

Also, thank you for the feedback on the actions menu vs popup dialog. It is still quite new so we're evaluating and gathering feedback.

[jonathan-v]

Excellent!  Thanks for the help.   We we're actually using the old way with the topics function and found that it was deprecated which is why we we're hitting a brick wall.  

This is working much better, but definitely look into the old pop up dialog, as we find it is much faster to execute an action. 

 

Thanks again for your help.