Lucas Correia

Very cool! Thank you for sharing this! Regards, Lucas

The documentation could be a bit more clear about this. The JS API doesn't support targeted expressions when subscribing to events. That is, the following will trigger the callback if the topic matches regardless of what the data is: session.eventHub.subscribe('topic=my-company.some-topic and data.foo=bar', callback); It should however support publishing events that target specific clients. Try the following: const event = new Event( 'ftrack.action.trigger-user-interface', eventData, { target: 'applicationId=ftrack.client.web and user.id="SOME-USER-ID"' } ); Regards, Lucas

Hi Jen, For your use case are you looking at obtaining the file path or uploading the file to the server location / storage? For showing the actions interface, have you tried using the ftrack.action.trigger-user-interface event instead of ftrack.actions.launch? https://help.ftrack.com/en/articles/1040479-events#ftrackactiontrigger-user-interface I believe the Web UI listens for the trigger-user-interface event, but not for the launch one. Regards, Lucas

The Python API Client often uses relationships (e.g. status) to update entities, but when using the raw API backend or the JS API client I recommend that you instead the relationship key attributes instead. In this case, that would be `status_id`. A more complete example of a request body would be: [ { "action": "update", "entity_type": "Task", "entity_key": [ "12bd29be-72b0-11e7-96a7-0a580ae40a16" ], "entity_data": { "status_id": "44dd9fb2-4164-11df-9218-0019bb4983d8", "__entity_type__": "Task" } } ] Regards, Lucas

Hi Konstantin, Thanks for the feedback. I have reported this as a bug. Regards, Lucas

Hi Mike, We have a helper method for obtaining the available statuses in the project schema, but it doesn't seem to be one for returning the available types at the moment. It is a bit complicated to follow the entity structure for the project/workflow schemas, so I did a first pass at a similar method which you can find here: https://bitbucket.org/snippets/ftrack/n79e8B It might need some more polish before it is read for general use, but I believe it should be enough for your use case. You can use it like so: getAvailableTypes( session, 'AssetBuild', 'caddd816-acb5-11e1-8668-f23c91df1211' ).then( types => console.info('Types', types) ); Regards, Lucas

Thanks for reporting the issue. I have pushed a commit which replaces the git+ssh dependencies with git+https. This should fix the permission error you are seeing. Regards, Lucas

Invited! / Lucas

Hi Remus, Thanks for reaching out. There is currently no support for formatting version description/comments. We plan to move to markdown for task and version descriptions in the future. Regards, Lucas

Hi Margot, For the next iteration of the client review interface, we will make it possible to add previous invitees by searching for them by name. Further down the line, we may also introduce a way to view and manage all external collaborators/clients. Thanks for the feedback! Regards, Lucas

Hi Chris, You should have received an invite now. Regards, Lucas

Hi Emi, Thanks for the feedback! Currently it is only possible to mark new note as completable, but not a note written by a client when transferring it. I agree that this would be a very useful feature and will bring it forward to the team. Thanks, Lucas

Hi Remus, I don't believe there is any workaround for this. You can group the custom attributes to make it less confusing for users, but will still show up for other asset types. Regards, Lucas

Invited. Regards, Lucas

Hi, Thanks for reaching out. If you call "AssetVersion.encode_media(component, keep_original=False)" the original component will automatically be removed from the cloud storage (ftrack server location) and deleted when the encoding process completes. There is no need to remove it manually. Regards, Lucas