|
1 | | -CustomTechDocs |
| 1 | +# CustomTechDocs |
| 2 | + |
| 3 | +Demonstrates how to create a custom content generator for Tech Doc schema elements. |
| 4 | + |
| 5 | +## Project Details |
| 6 | + |
| 7 | +See [TESTSTATUS file](./TESTSTATUS.md) for latest testing information. |
| 8 | + |
| 9 | +#### Built Using: |
| 10 | +Aras 11.0 SP9 |
| 11 | + |
| 12 | +#### Versions Tested: |
| 13 | +Aras 11.0 SP9 (open release) |
| 14 | + |
| 15 | +#### Browsers Tested: |
| 16 | +Firefox 38 ESR |
| 17 | + |
| 18 | +> Though built and tested using Aras 11.0 SP9, this project should function in older releases of Aras 11.0. |
| 19 | +
|
| 20 | +## How It Works |
| 21 | +The project's import package adds a new content generator method for the ItemInfo schema element, replacing the out-of-the-box implementation. The new content generator method, `labs_ItemInfoContentGenerator`, populates every new ItemInfo element with the name, description, cost, major revision/generation, state, and created date for the selected assembly (Part item). The method also adds the assembly's BOM in a tabular layout. |
| 22 | + |
| 23 | +## Installation |
| 24 | + |
| 25 | +#### Important! |
| 26 | +**Always back up your code tree and database before applying an import package or code tree patch!** |
| 27 | + |
| 28 | +### Pre-requisites |
| 29 | + |
| 30 | +1. Aras Innovator installed (version 11.0 SPx preferred) |
| 31 | +2. Aras Technical Documentation is installed |
| 32 | +3. Aras Package Import tool |
| 33 | +4. CustomTechDocs import package |
| 34 | + |
| 35 | +### Install Steps |
| 36 | + |
| 37 | +1. Backup your database and store the BAK file in a safe place. |
| 38 | +2. Open up the Aras Package Import tool. |
| 39 | +3. Enter your login credentials and click **Login** |
| 40 | + * _Note: You must login as root for the package import to succeed!_ |
| 41 | +4. Enter the package name in the TargetRelease field. |
| 42 | + * Optional: Enter a description in the Description field. |
| 43 | +5. Enter the path to your local `..\CustomTechDocs\Import\imports.mf` file in the Manifest File field. |
| 44 | +6. Select the following in the Available for Import field. |
| 45 | + * **aras.labs.CustomTechDocs** |
| 46 | + * **com.aras.innovator.solution.TechDoc** |
| 47 | + * **com.aras.innovator.tdf** |
| 48 | + * **com.aras.innovator.solution.PLM** |
| 49 | +7. Select Type = **Merge** and Mode = **Thorough Mode**. |
| 50 | +8. Click **Import** in the top left corner. |
| 51 | +9. Close the Aras Package Import tool. |
| 52 | + |
| 53 | +You are now ready to login to Aras and try out the CustomTechDocs project. |
| 54 | + |
| 55 | +## Usage |
| 56 | + |
| 57 | +**Pre-requisite:** The Aras instance should include some Parts with BOM relationships. |
| 58 | + |
| 59 | +1. Log in to Aras as admin. |
| 60 | +2. Navigate to **Technical Documentation > Technical Documents**. |
| 61 | +3. Create a new Technical Document with the `Standard` schema. |
| 62 | +4. Add an ItemInfo element to the document, selecting a Part with Part BOM relationships when the search dialog appears. |
| 63 | +5. Save the document. |
| 64 | + |
| 65 | +## Contributing |
| 66 | + |
| 67 | +1. Fork it! |
| 68 | +2. Create your feature branch: `git checkout -b my-new-feature` |
| 69 | +3. Commit your changes: `git commit -am 'Add some feature'` |
| 70 | +4. Push to the branch: `git push origin my-new-feature` |
| 71 | +5. Submit a pull request |
| 72 | + |
| 73 | +For more information on contributing to this project, another Aras Labs project, or any Aras Community project, shoot us an email at [email protected]. |
| 74 | + |
| 75 | +## Credits |
| 76 | + |
| 77 | +Created by Eli Donahue for Aras Labs. @EliJDonahue |
| 78 | + |
| 79 | +## License |
| 80 | + |
| 81 | +Aras Labs projects are published to Github under the MIT license. See the [LICENSE file](./LICENSE.md) for license rights and limitations. |
0 commit comments