Upchain enables you to add important product data as well as current and historical revision information directly within the title block of a drawing. When you add specific Upchain attribute codes to the title block or other tables, the drawing is updated to show to corresponding information upon the release of the item.
drawing.create.dwg and drawing.create.pdf to create these translations, and drawing.populate.title.block.codes to ensure the codes are converted during release. If you want to generate the released PDF from the original PDF and convert the codes directly in the PDF, you must enable the tenant property drawing.populate.original.pdf.| Attribute name | Upchain attribute code | Description |
|---|---|---|
| Item name | {%01%} |
Value entered into Item Name field. |
| Item number | {%02%} |
Number assigned to the item based on your item numbering rules. |
| Major revision | {%03%} |
Major revision based on your item numbering rules. |
| Minor revision | {%04%} |
Minor revision based on your item numbering rules. |
| Revision Description | {%05%} |
Value entered into the Revision Note field. |
| Created by | {%06%} |
User who created the item version being released. |
| Creation date | {%07%} |
Date of creation of the item version. Format: YYYY-DD-MM. |
| Approved by | {%08%} |
The user who makes the decision to release the items during the CR workflow. If no task exists to approve the CR, then this field is blank. |
| Approved date | {%09%} |
Date at the time the user decides to release the items during the CR workflow. If no task exists to approve the CR, then this field is blank. |
| Material | {%10%} |
Value entered into the Material field. |
| Finish | {%11%} |
Value entered into the Revision Note field. |
| Heat treat | {%12%} |
Value entered into the Revision Note field. |
| Weight | {%13%} |
Value entered into the Revision Note field. |
| Company | {%14%} |
Value entered into the Revision Note field. |
| Mass | {%33%} |
Value entered into the Mass field. |
| Drawn by | {%34%} |
Drawing file version creator. |
| Drawing date | {%35%} |
Drawing file version creation date. |
| Checked by | {%36%} |
Change Request creator. |
| Checked date | {%37%} |
Change Request creation date. |
| Major revision-Minor revision | {%38%} |
Combination of the major and minor revision in one code (eg. AA-00) to avoid spacing between the two. |
These codes are useful to include a Revision History table on the drawing and refer to the previous three revisions of the item:
| Attribute name | Upchain attribute code | Description |
|---|---|---|
| Revised date 1 | {%15%} |
Date of creation of the second most recent item version that was released. Format: YYYY-DD-MM. |
| Revised date 2 | {%16%} |
Date of creation of the third most recent item version that was released. Format: YYYY-DD-MM. |
| Revised date 3 | {%17%} |
Date of creation of the fourth most recent item version that was released. Format: YYYY-DD-MM. |
| Revised by 1 | {%18%} |
User who created the second most recent item version that was released. |
| Revised by 2 | {%19%} |
User who created the third most recent item version that was released. |
| Revised by 3 | {%20%} |
User who created the fourth most recent item version that was released. |
| Revision description 1 | {%21%} |
Value entered into the Revision Note field for the second most recent item version released. |
| Revision description 2 | {%22%} |
Value entered into the Revision Note field for the third most recent item version released. |
| Revision description 3 | {%23%} |
Value entered into the Revision Note field for the fourth most recent item version released. |
| Revision 1 | {%24%} |
Revision level for the second most recent item version released. Format: Major Revision-Minor Revision |
| Revision 2 | {%25%} |
Revision level for the third most recent item version released. Format: Major Revision-Minor Revision |
| Revision 3 | {%26%} |
Revision level for the fourth most recent item version released. Format: Major Revision-Minor Revision |
| Approved by 1 | {%27%} |
The user who made the decision to release the Revision 1 item during the CR workflow. If no task exists to approve the CR, then this field is blank. |
| Approved date 1 | {%28%} |
Date at the time the user decided to release the Revision 1 item during the CR workflow. If no task exists to approve the CR, then this field is blank. |
| Approved by 2 | {%29%} |
The user who made the decision to release the Revision 2 item during the CR workflow. If no task exists to approve the CR, then this field is blank. |
| Approved by date 2 | {%30%} |
Date at the time the user decided to release the Revision 2 item during the CR workflow. If no task exists to approve the CR, then this field is blank. |
| Approved by 3 | {%31%} |
The user who made the decision to release the Revision 3 item during the CR workflow. If no task exists to approve the CR, then this field is blank. |
| Approved date 3 | {%32%} |
Date at the time the user decided to release the Revision 3 item during the CR workflow. If no task exists to approve the CR, then this field is blank. |