mirror of
https://github.com/ynput/ayon-core.git
synced 2025-12-24 21:04:40 +01:00
some text correction
This commit is contained in:
parent
3627c91b8a
commit
5af4b16828
3 changed files with 8 additions and 14 deletions
|
|
@ -115,7 +115,6 @@ sidebar_label: Artist
|
|||
**2. possibility - Ftrack URL is not set or is not right**
|
||||
- Check **Ftrack URL** value in *Ftrack login* window
|
||||
- Inform your administrator if URL is incorrect and launch OpenPype again when administrator fix it
|
||||
- The Ftrack URL can be changed in OpenPype Settings → System → Modules → Ftrack
|
||||
|
||||
**3. possibility - Ftrack Web app can't be reached the way OpenPype use it**
|
||||
- Enter your **Username** and [API key](#where-to-find-api-key) in *Ftrack login* window and press **Login** button
|
||||
|
|
|
|||
|
|
@ -28,8 +28,9 @@ In most cases actions filtered by entity type:
|
|||
|
||||
So if you do not see action you need to use check if action is available for selected *entity type* or ask *administrator* to check if you have permissions to use it.
|
||||
|
||||
|
||||
Actions can be highly customized according to specific client's requests.
|
||||
:::note
|
||||
Actions can be heavily customised by your studio, so this guide might not fit 100 %.
|
||||
:::
|
||||
|
||||
:::important
|
||||
Filtering can be more complicated for example a lot of actions can be shown only when one particular entity is selected.
|
||||
|
|
@ -65,12 +66,6 @@ Project Manager or Supervisor must set project's applications during project pre
|
|||
|
||||
#### A group of actions that are used for OpenPype Administration.
|
||||
|
||||
### Create Update Avalon Attributes
|
||||
* Entity types: All
|
||||
* User roles: Pypeclub, Administrator
|
||||
|
||||
Action creates and updates Ftrack's Custom Attributes that are needed to manage and run OpenPype within Ftrack. Most of custom attribute configurations are stored in OpenPype settings (*click on the systray OpenPype icon → Settings → Project → Anatomy → Attributes*). It is not recommended to modify values stored in the file unless your studio used completely custom configuration.
|
||||
|
||||
### Sync to Avalon
|
||||
* Entity types: Project, Typed Context
|
||||
* User roles: Pypeclub, Administrator, Project manager
|
||||
|
|
@ -126,7 +121,7 @@ With this action it's possible to delete up to 15 entities at once from active p
|
|||
* Entity types: Project
|
||||
* User roles: Pypeclub, Administrator, Project manager
|
||||
|
||||
Allows project managers and coordinator to *set basic project attributes* needed for OpenPype to operate, *Create project folders* if you want and especially prepare project specific [anatomy](admin_settings_project_anatomy) or [settings](admin_settings_project).
|
||||
Allows project managers and coordinator to *set basic project attributes* needed for OpenPype to operate, *Create project folders* if you want and especially prepare project specific [settings](admin_settings_project).
|
||||
|
||||
:::tip
|
||||
It is possible to use this action during the lifetime of a project but we recommend using it only once at the start of the project.
|
||||
|
|
@ -217,7 +212,7 @@ Please keep in mind this action is meant to make your project setup faster at th
|
|||
* Entity types: Task
|
||||
* User roles: Pypeclub, Project manager, Administrator
|
||||
|
||||
Collects approved hires files and copy them into a folder. It usually creates h.264 files for preview and mov for editorial. All files are then copied according to predefined naming convention to a specific folder.
|
||||
Collects approved hires files and copy them into a folder. It takes any components of any versions and copies and renames them correctly.
|
||||
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ You can only use our Ftrack Actions and publish to Ftrack if each artist is logg
|
|||
|
||||
|
||||
### Custom Attributes
|
||||
After successfully connecting OpenPype with you Ftrack, you can right on any project in Ftrack and you should see a bunch of actions available. The most important one is called `OpenPype Admin` and contains multiple options inside.
|
||||
After successfully connecting OpenPype with you Ftrack, you can right click on any project in Ftrack and you should see a bunch of actions available. The most important one is called `OpenPype Admin` and contains multiple options inside.
|
||||
|
||||
To prepare Ftrack for working with OpenPype you'll need to run [OpenPype Admin - Create/Update Avalon Attributes](manager_ftrack_actions#create-update-avalon-attributes), which creates and sets the Custom Attributes necessary for OpenPype to function.
|
||||
|
||||
|
|
@ -56,7 +56,7 @@ There are specific launch arguments for event server. With `openpype eventserver
|
|||
- `--ftrack-url "https://yourdomain.ftrackapp.com/"` : Ftrack server URL _(it is not needed to enter if you have set `FTRACK_SERVER` in OpenPype' environments)_
|
||||
- `--ftrack-events-path "//Paths/To/Events/"` : Paths to events folder. May contain multiple paths separated by `;`. _(it is not needed to enter if you have set `FTRACK_EVENTS_PATH` in OpenPype' environments)_
|
||||
|
||||
So if you want to use OpenPype's environments then you can launch event server for first time with these arguments `$OPENPYPE_SETUP/openpype eventserver --ftrack-user "my.username" --ftrack-api-key "00000aaa-11bb-22cc-33dd-444444eeeee" --store-credentials`. Since that time, if everything was entered correctly, you can launch event server with `$OPENPYPE_SETUP/openpype eventserver`.
|
||||
So if you want to use OpenPype's environments then you can launch event server for first time with these arguments `openpype.exe eventserver --ftrack-user "my.username" --ftrack-api-key "00000aaa-11bb-22cc-33dd-444444eeeee" --store-credentials`. Since that time, if everything was entered correctly, you can launch event server with `openpype.exe eventserver`.
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="env">
|
||||
|
|
@ -186,7 +186,7 @@ Push thumbnails from version, up through multiple hierarchy levels
|
|||
|
||||
Change status of next task from `Not started` to `Ready` when previous task is approved.
|
||||
|
||||
Multiple detailed rules for next task update can be configured in the presets.
|
||||
Multiple detailed rules for next task update can be configured in the settings.
|
||||
|
||||
### Delete Avalon ID from new entity
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue