Lucas Correia

Administrators
  • Content Count

    199
  • Joined

  • Last visited

  • Days Won

    39

Everything posted by Lucas Correia

  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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
  8. Hi, The image_encoder.py 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 image_encoder.py 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
  9. 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
  10. Hi Chris, You should have received an invite now. Regards, Lucas
  11. 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
  12. 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 ftrack.com/actions. Regards, Lucas
  13. 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
  14. 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
  15. Hi Kariem, Are you launching actions for a task in ftrack? Could you send your ftrack Connect logs to support@ftrack.com? 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
  16. Hi, Can you reach out to us at support@ftrack.com and let us know which account / organization you are with and refer to this post and we'll investigate your issues. Regards, Lucas
  17. Thank you for the feedback! We will take your feedback into consideration as we improve the review interface in the future. Regards, Lucas
  18. Hi Christian, Thanks for the feedback. To display some information from an external system in ftrack, I would recommend writing either an action or a custom widget. You can read more about actions and custom widgets in the following blog post: https://www.ftrack.com/en/2016/08/actions-custom-widgets-javascript-api-making-ftrack-better.html Another way to display external data is with a dynamic enumerator. The dynamic enumerator custom attribute can be used to be able to select information available in external systems. Read more about dynamic enumerators in the documentation: https://help.ftrack.com/administering-ftrack/advanced/using-custom-attributes#dynamic-enumerator-attribute. Regards, Lucas
  19. Hi, The permission "Can change status of a task" controls the ability to change statuses of both tasks and other objects, such as shots. I'll bring this up with the team to clarify the situation and see if we can expose seperate permissions for other objects. The ability to assign tasks is controlled by the permission "Update objects". It is currently not possible to allow users to assign tasks, without giving them permission to update other object attributes. Read more in the documentation: https://help.ftrack.com/administering-ftrack/users/managing-permissions-and-roles Regards, Lucas
  20. Hi, Thanks for reaching out. The JavaScript API does not automatically connect to the event hub. You can either call Session.eventHub.connect() or specify autoConnectEventHub when creating the session. Read more in the documentation: http://ftrack-javascript-api.rtd.ftrack.com/en/stable/handling_events.html Yep! Both are connected to the same event server and events will be available to either client. Regards, Lucas
  21. Hi Denis, The logic to extract the version number from the file name in the web interface is unfortunatly not available in ftrack Connect. It is also possible to set or change the version number if publishing via the API. It is exposed as the `version` attribute on `AssetVersion` entities. Regards, Lucas
  22. 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
  23. Hi Tim, The API (both JS and Python clients) always requires a valid user, even when using "Global" API keys. Where are you using the JavaScript API? As a widget in ftrack, another web page or from Node? In a web widget, we inject the users credentials (assuming the option has been set in the dashboard options). See the ftrack.widget.load event. If you are using ftrack-web-widget or ftrack-spark-base (see resources and examples) you can call ftrackWidget.getCredentials() at any time to get the users credentials). In NodeJS, you can replicate the behaviour of the Python API in the following way: const session = new ftrack.Session( process.env.FTRACK_SERVER, process.env.FTRACK_API_USER, process.env.FTRACK_API_KEY ); Regards, Lucas