Lucas Correia

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Lucas Correia

  1. 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', 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"SOME-USER-ID"' } ); Regards, Lucas
  2. 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 = [];
  3. 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
  4. 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
  5. 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? I believe the Web UI listens for the trigger-user-interface event, but not for the launch one. Regards, Lucas
  6. 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
  7. Hi Konstantin, Thanks for the feedback. I have reported this as a bug. Regards, Lucas
  8. 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: 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 =>'Types', types) ); Regards, Lucas
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. Hi, The is what what we refer to as an event listener. 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 An event listener can be deployed centrally on a server (typically separate from the local/on-prem ftrack installation), or the user's machine if it needs access to it. In this case, you will want to have one instance of the listener running centrally. You can run the event listener from the command line: python You can also register the event listener as a plugin. For more information, see the links above. You can use something like Supervisor or Monit to monitor and ensure the event listener is always running. Regards, Lucas
  17. 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
  18. Hi Chris, You should have received an invite now. Regards, Lucas
  19. 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
  20. Hi Patrick, It is unfortnatly not possible to use information in calendar events inn the spreadsheet / custom attribute expressions. More information about expression custom attributes can be found in the documentation here. One possiblibility is to develop a custom action to calculate and show the information you want. More information about actions is available at Regards, Lucas
  21. Hi, Sorry for the delayed response on this. I don't see a reason why changes to `TypedContextLink` shouldn't emit update events. I have added a bug task to look into this. Thanks for the feedback. Regards, Lucas
  22. 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
  23. Hi Kariem, Are you launching actions for a task in ftrack? Could you send your ftrack Connect logs to You can find the logs by following these steps: 1. Open the Connect service menu 2. Click on About 3. Click on Open log directory 4. The name of the log file is ftrack_connect.log Regards, Lucas