Lucas Correia

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

It looks like it is an issue with the eslint loader. As it is not needed for building the project, you could try replacing these lines, with an empty array: const rules = [];

I see. Thanks for the feedback on the documentation! It does seem like node-sass depends on node-gyp which in turn requires windows-build-tools. I wasn't aware of that. Regards, Lucas

Hi, The Adobe extension consists of two parts: ftrack-connect-spark-adobe (adobe specific logic) and ftrack-connect-spark (shared UI). When building the extension, it copies the UI distribution (`node_modules/ftrack-connect-spark/dist/`) to build/staging/ftrack_connect_spark/. I don't actually think the distribution files are checked in into ftrack-connect-spark, which means that you either have to build those files locally or copy the files over from the extension if you are not making any changes to the UI. To build the extension with changes to the UI, you will need to: Clone the ftrack-connect-spark repository Build it (yarn install && yarn dist) Configure ftrack-connect-spark-adobe to use the local package In ftrack-connect-spark: yarn link In ftrack-connect-spark-adobe: yarn link ftrack-connect-spark Rebuild ftrack-connect-spark-adobe using grunt 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

Just heard from a colleague that this might be related to an issue with cached templates that can occur on local installations prior to version 4.1.3. If you are running a previous version, either upgrade to 4.1.3+ or contact support for help with purging the cache. Regards, Lucas

Hi Remus, Firefox and Chrome of recent versions (including the ones mentioned) should be both supported. Do you by chance have configured ftrack to override the default create project behaviour? If not, can you check if you see any errors in the browser console and open a support case with any information from the logs? We'll be able to help you more easily there. Regards, Lucas

Hi, I doesn't look like the user account type is exposed via the API. I think this is an oversight on our end and have added a request to remedy this. Regards, Lucas

Hi Remus, We store an Event entity when some entities (e.g. Task, Note) are created. Examples of how to query these are available in this snippet. Currently, we do not track changes to AssetVersionLink and no create Event will be available. I've added a request to add this. Regards, Lucas

Hi, A Component entity can be either a Component, FileComponent, ContainerComponent or SequenceComponent. Typically, FileComponent or SequenceComponent. A file component represents a single file, while a sequence component represents multiple files in an image sequence. To publish a sequence component, you can use the connect publisher and a select a sequence of files which share a common base name and have an incremental number suffix. A sequence component is a type of a container component. A container component will contain members, which is a collection of components which make up the component. Regards, Lucas

Invited! / Lucas