Leaderboard

Thanks Lorenzo, it works after launching ftrack connect(don't know it has to be with connect before). Is there anyway I can get it work without ftrack-connect? We've wrapped all the publish/actions launcher entrace so except for this we don't need ftrack-connect. It would be great if there's a way we can do it without ftrack-connect. Cheers.

Hi @John Su, the path is resolved through an event available in ftrack_connect itself and called resolve.py If the path is red is possible that your structure cannot be properly initialised and hence not be resolved. You can try adding more logs into the resolve.py and see if anything is off. Please send us , either here or through support (depending on how sensible the information are) and we'll look further into it. Hope it helps. Cheers. L.

Hi Remus, Filtering on the Overview tab has been enhanced in latest version, 4.2: Add support for filtering out events, tasks and milestones on Users and Projects timeline views. More information on latest versions: https://help.ftrack.com/release-and-migration-notes/release-notes Regards, Johan

Hi @mark.fin , we have the same issue. What we need is a lock system for the Ftrack entities and attributes. Please have a look at this discussion http://forum.ftrack.com/index.php?/topic/788-lock-system-for-entity-attribute/ . Until this is implemented, we are using an Ftrack action which works pretty nice for us. How the action works: - it listen for all the events - ones an event match the conditions, we process it. Example: we allow production to create an asset and update the name as long as the status is not changed. Ones the status is changed, we mark it (set a key in metadata). If the production renames it now, the action detects that the asset is marked and rename it back to the previous name and let the user know why he/she can't do it.

Being able to change the time log for other people as a supervisor or coordinator would be good.