Creating the Custom Component Based on Its Project or Forge URL
Use the following method to create the custom component based on its known project or forge URL.
To create a custom component based on its URL:
|
2.
|
In the URL field, enter URL for the component. As you enter the URL, it is checked for an acceptable format (such as http://example.com), but not for validity. |
[
|
3.
|
Click Create New Component. |
|
•
|
If Code Insight recognizes the URL you entered as belonging to one of the forge-URL domains currently supported for custom component creation, the New Custom Component window opens, showing component fields—including Name, Title, URL, and Forge—automatically populated with values based on domain conventions. (For the list of supported domains, see Supported Forge-URL Domains for Custom Components.) |
|
•
|
If Code Insight does not recognize the URL as belonging to a supported domain (that is, it is unable to parse the URL), the New Custom Component window opens showing the URL only. You must click Get Details to complete the component fields manually in Free Form mode. (Click OK on the “Unable to parse URL...” message box to proceed to Free Form mode.) |
|
4.
|
Update the component fields as necessary, noting that the Name, Title, and URL fields are required. For more information about these fields, see Custom Component Properties. |
|
•
|
If the URL you initially entered (at the top of the window) belongs to a supported domain and you edit that URL, click Get Details to update the remaining field values according to forge-URL domain conventions. |
|
•
|
If you must manually provide field values because the URL you initially entered does not belong to a supported domain, click  in the upper part of the window for examples of the standard name, title, and URL conventions used by the Forge value you select. |
|
•
|
If the component is successfully created, it is immediately saved to the Code Insight database and listed in the Lookup Component window or on the Components tab on the Global Component & License Lookup tab. (The Components tab automatically filters to the new component by its component ID.) |
|
•
|
The process of indexing the component in the Code Insight Data Library begins immediately in the background. Once indexed, the custom component is made available for global component searches that users can perform against the Code Insight Data Library. For important information about the indexing process and these searches, see Note About the Indexing Process for Custom Components. |
|
•
|
If the component name and title combination already exists in the Data Library, an error message is displayed. You can edit the custom component details to provide a unique name or title; or (through the Lookup Component window) locate the already-existing component and associate it with the inventory item. |