Lorenzo Angeli

Hi @Nicholas Yue, atm API do not have this ability, but I'll pass on the request to our dev team. Stay tuned ! Cheers. L.

Hi @Gabriel Valderramos a list of the ftrack events can be found in our developer hub. If you want to have some events examples to play with, you can have a look at our recipes repository. Hope this helps. L.

Hi @Pedro Caramelo, the integration for nuke studio target also the hiero executable so you should be able to try to run it and check. For the other integrations (Nuke) is a separate integration and require a different plugin (ftrack-framework-nuke). hope it helps. L.

Hi @Pedro Caramelo hiero integration is part of Nuke Studio one. Could you please try to install that and report back it does show up ? Thanks. L.

Hi @cia_dev sorry to hear you are having issues. if you can share the whole event code through a support ticket we can try to have a closer look where is erroring. Please attach the whole stacktrace and other useful logs when doing so. Thanks ! L.

Hi @dima and @Bruce. let me try to reply inline with your various questions. "So when the user selects the Archive action in a Project we look at the versions and if the client status has Final Approved then it stays all other files will be archived in that project. We dont remove anything else only the media files." This is a custom event listener on the ftrack.update topic, checking if the project status change to Archived. If the event is detected then it shall be fetching all the components attached to asset versions where the status is not "Approved" or state "Done". When these components are found, these should be be then uploaded to an amazon S3 bucket thorugh the S3Accessor, using a custom Location. In order to do that you need the following moving parts. 1) an event listener similar to https://github.com/ftrackhq/ftrack-recipes/tree/main/python/events/cascade-status-changes-0.0.0, just listening to the project changes rather than the task. 2) a custom locatino similar to the https://github.com/ftrackhq/ftrack-user-location as it make use of the s3Accessor. @Lorenzo Angeli Where can we find Ftrack_s3_accessor ready-made plugin for cloud? The plugin is available through pip to install as by repo instructions which boils down to : pip install ftrack-s3-accessor Once the module is available you will be able to make use of it in a custom location as the user-location example does 2. Then we need to delete files from ftrack.server and this should presumably be done by searching for "orphaned" files of this project, right? Yes that's correct, careful only on how you define orphaned components, not being attached to a version is not enough sometimes as notes could be having attachments. 3. How to deploy this action if we use Ftrack Cloud by creating a plugin and placing it through Ftrack Connect in the plugins folder? 4. Or do we need to place the action on our own Python or NodeJS server with a connection through an Ftrack API session? Both way works, I usually prefer using Connect deployment while testing adn using a separate machine (headless) to serve actions when depoying in production. Between python and node, I'd sugges python as we have more examples on the recipes. Hope it helps. L.

hi @dima would you mind opening a ticket with support and provide all the connect logs and stacktrace you are getting. Please include operating system in use and process you are taking to build and deploy the location. Thanks. L.

Hi @dima I see you are trying to run the user-location the code in the repo should be built before installing it. (sorry just noticed the link is dead in the repo, I'll have it fixed) please try the following: create a venv with python >= 3.10 (python -m venv ftrack_env) activate the venv install setuptools with pip (pip install setuptools) run : python setup.py build_plugin This should result in a build folder containing a zip file called ftrack-user-location-0.3.2.zip you can drag and drop this in the connect plugin manager to get it installed, or copy the unzipped ftrack-user-location-0.3.2 folder directly in the connect plugin folders. please remember to setup the environment variables defined in the repo readme The environment strictly required are: FTRACK_USER_SYNC_LOCATION_AWS_ID FTRACK_USER_SYNC_LOCATION_AWS_KEY FTRACK_USER_SYNC_LOCATION_BUCKET_NAME then restart connect and try to publish. Plase feel free to open a ticket with support[at]ftrack.com if you still have errors. Cheers. L.

Hi @Bruce, if you are on cloud and you want to backup data in aws s3, you can use this accessor and use it in conjunction with a recipe like this one to do what you are after. You can also use this other example as base in case, as it uses already the s3 accessor. If you need any further help, feel free to open a support ticket ! hope it helps. L.

@dima the script assume you have an on prem installation of the instance, won't work on cloud instances, could that be the case here ?

@dima to clearify, the typo was actually in the api themselves and we are currently fixing it, so please change it back on the next studio release. > PermissionError(Not allowed to execute operation _validate_entity_keys requires ADMINISTRATOR permissions.) Could you please check if you have Administrator role on the api and user you are using for the script ? Thanks. L.

Hi @dima , it seems there might be a typo in the script. Could you please try to update the script replacing _validate_entity_keys with _validate_entity_key and see if that works for you ? Let us know. Cheers. L.

Hi @Omer If you are using a NAS to store published material, the usual way is to provide an external mount point through SAMBA and/or NFS which then will be mounted in the artists machines. The process and avilable options can differer depending on the NAS in use and its operating system. Once the share is available you can mount it on the user's machine (notes: All users should be mountint it under the same mountpoint, eg: F:/ftrack_storage) and use that during the configuration of the centralised storage scenario. hope it helps. L.

@emlcpfx You can find examples on how to use the ReviewSession in our developer hub, I hope is what you are after. For what concerns Connect plugins, you can find an example in our recipes repository (is a Location, but the plugin structure is similar). And please, feel free to share any error you are having here, or through support tickets if you prefer. Hope it helps. L.

Hi @Nikolay Skolkov , thanks for reaching out. Would you mind opening a ticket with [email protected] and provide connect logs and version information of the integrations, so we can have a closer look ? Thanks ! L.