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

Invited! / 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

Invited. Regards, Lucas

Hi Chris, It should be possible to use an event listener to automate starting a timer for a user when a task's status is set in progress. The reason that we don't do this automatically is that there can be several situations where you do not want the timer started automatically, and it is hard to know when this is. An event listener is a small python script that can be used to subscribe to changes in ftrack and perform custom logic such as updating a status, starting a external process or triggering a user interface. Here are some useful resources for setting up an event listener: * Developer hub with introduction to the API * How to subscribe with the API * Information about the update event * Example event listeners If you are not interested in logging time, but rather want to see how long a particular task has been in a certain state you can look at querying `Event` objects using the API. There is a snippet with some examples here. You probably want to query for action=change.status.task and parent_id=the task's id. Regards, Lucas

Hi, We have just added a new "Clone review session" feature to client reviews in ftrack 3.3.17. Cloning review session will allow you to carry over the collaborators from one review session to the next, making it a lot easier to work with reoccurring review sessions with the same collaborators. Hosted sites will be upgraded to this version during the next week. More information is available in the release notes for 3.3.17. We still have more plans to further improve the workflow when inviting collaborators to review sessions going forward. Please let me know what you think; does the new feature implemented work for your use cases, or do you need anything more? Regards, Lucas

Thank you for the feedback. This was actually planned for the initial implementation, but fell through due to time constraints. I'll bump it up and see if it something we have time to tackle again. Regards, Lucas