What are they and why would we use them?
...
New in Qube
...
! 6.5
We've added 10 new fields to the Qube job. These will allow you to "tag" your job with any combination of a Show, Shot, Sequence, or Department name, a client code, or 5 other "generic" fields for easier search, sorting, and cost reporting. These tags will be available in the WranglerView job submission UI's, and in the "Job" and "Running Instances" panes.
...
5 more are 'generic' names for those customers whose needs are not met by 1 or more of the 5 "stock" fields. These will appear in the Qube Wrangle and ArtistView the WranglerView and QubeArtistView as:
- Custom1
- Custom2
- Custom3
- Custom4
- Custom5
| Note |
|---|
If your site elects to use the generic fields, you should ensure that you use them consistently. If, for example, you have a "category" value, and you decide you want your Custom1 field to store your Category values, do not use the Custom1 field for anything else. Also do not store the Category values in any other of the custom fields. If you do erroneously enter a value into an incorrect field, you can always "modify" the job at a later date to fix this. |
Future versions of Qube! will allow for an alternate name to be displayed for these "generic" fields; ArtistView QubeArtistView currently provides for a way to do this in the user preferences, but the design goal is to define these on the supervisor, and not have to define them for each user.
...