Jump to content

client-side action and UUID identifier

Recommended Posts

Reading this example action:


There are many example actions in the Ftrack documentation with varying structures, but this is the only one that I've seen that sets the action identifier with an uuid, making the identifier unique to each action instance, which is helpful in avoiding crosstalk between users using the same Ftrack-connect plugins.

Another example like this uses an internal register function inside the class to filter the action by user.


Which of these methods would be considered best practice to safely configure a client-side action?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...