Lucas Correia

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

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, 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

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 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

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

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