Remus Avram

Members
  • Content Count

    486
  • Joined

  • Last visited

  • Days Won

    12

Everything posted by Remus Avram

  1. Thanks @Mattias Lagergren for your toughts. If there will be an event when a Manager type is added to a user, then we can match the Managers types with the user roles and add the role ones a manager type is added to the user. The issue with the event is described here:
  2. Thanks @Mattias Lagergren for the update. What do you think it would be a quick workaround at the moment?
  3. Hi all, we would like to give production the ability to manage the roles of the user without accessing the Ftrack System settings. From our perspective, one way to do it is to add in the right-click menu a sub-menu "Roles" like the "Managers" one. Or adding the roles to the user from the user Profile. Or to emit an event when a manager type is added to a user. In this way we can match the "Managers" types with the "Roles" types and do it through an action. ( @Luigi already started a discussion abut this here Thanks for your support!
  4. I see. We are doing like this to get the structure: while entity['parent'].entity_type != "Project": entities.append(entity['name']) entity = entity['parent']
  5. Hi @Erik, if I may ask, for what do you use the link attribute? In most of the cases we are getting the project from a task like this: task["project"]["attribute"] Does this work for you?
  6. @Mattias Lagergren can you please write a scenario how it should be set with custom attributes and actions?
  7. Thanks for the idea. This will do the trick for us.
  8. Nobody should be allowed to change the timelogs a week after, but in an exception case, the production would like to allow the specific user to do it. Or Production should be allowed to change their timelogs.
  9. Hi all, is it possible to filter in the Versions Spreadsheet by the component name? I tired with the advanced filter but I was not able to find the right query as the name of the component is not a direct attribute but a key-value in data.
  10. Thanks @Mattias Lagergren for the feedback. We will try to do it like this. But the problem here is that if the production would like to allow only one artist to update his/her time logged, it's not possible.
  11. Thanks @Mattias Lagergren for the feedback. We will try with text type instead of number.
  12. Hi all, production would like to manage the resources in Ftrack. would it be possible: to have more then 2 decimals (e.g. for excange rates EUR-USD 1,196095) to have a dot as punctuation for costs (e.g. 1.000.000,00) and at the same time having long numbers without punctuation (e.g. frame in 1001) Cheers!
  13. Hi all, is it possible to restrict the user to add/update the time logger X days before? A user should be able to add/update the time logger only in the current and last week. Cheers.
  14. And even more. When the real user is added to Ftrack, we need a way to replace the "fake" user with the real user. In this way the real user is already assigned to tasks.
  15. Hi Den, welcome to the forum! Do you want to export from the Ftrack Web interface, or using the ftrack api? I hope this helps: http://ftrack.rtd.ftrack.com/en/stable/using/importing_and_exporting.html
  16. This issue is fixed. Tested with: ftrack server: 3.5.6 ftrack_api: 1.3.1
  17. Let's start with tracking all the changes first. Production get confused when a custom attribute has been changed and it's not tracked in the Activities tab.
  18. Hi Ftrack, we would like to track every change to the ftrack entity in the Activities. It is vital for the production to know who changed what and when. Best, Remus
  19. Remus Avram

    sessions

    If you are using session.get() yes, but if you are using session.query() it will query the DB again. I think the cache makes sens in some cases, for example if only one generic user is allowed to change some data. But in most of the cases you want to query the DB again before changing it to be sure that nobody already updated it. I think the open/close session is not the main problem of having a session per call. Having a session per call it will slow down the process.
  20. Remus Avram

    sessions

    Hi @pawel we are using one session as a global session. why do you want to invalidate the cache? Normally you don't need to do it. If the session is running for a long time, when you want commit a change, first you query the ftrack entity again and then you commit, just to be sure that the entity didn't change in the meantime.
  21. Keeping the id and the type of the entity together works for us pretty nice. But in the event hub, the event['data']['selection'] contains the id and the 'context_type' of the entity instead of the type of the entity. In this case we can't get nice the entity.
  22. Thanks Mattias for your quick answer. Unfortunately, we would like to restrict the permissions for production in order to create new projects in Ftrack or update the other settings.
  23. Hi Ftrack team, production would like to update the start and end date of the project. Is there a role permission for it? Best!
  24. Hi @georgea, we also requested this. Please have a look at https://forum.ftrack.com/topic/939-send-an-existing-note-to-more-recipients/ Best!