Available from the version:
- Plugin Builder 1.60.0.10 or higher.
- Plugin Builder XML 1.60.0.6 or higher.
Plugin Builder XML integration with Insight is available. Because of this, the Plugin Builder XML received new features such as:
- Tools Collection
With a mill and a saw registered by default, have the possibility of adding new tools and also changing the name or code of them.
- Insight Integration
The milling has a feature that allows to set the Alignment of the tool. To make use of this feature, it is necessary that the integration is realized through Insight.
After configuring the integration with Insight, the tool Alignment option will be available on the mills.
IMPORTANT: Integration with Insight will require a selected tool for all enabled operations or processes.
Integration with insight generate the XML with a new node, Profiles, that contains the information about each profile.
Example:
| Parameter |
Meaning |
| NO | Number |
| SX | Start position in X |
| SY | Start position in Y |
| **MX | Mid position in X |
| **MY | Mid position in Y |
| EX | End position in X |
| EY | End position in Y |
**Appears only when it is an Arc.
- Generation of CNC programs for aluminum components
Available from Plugin Builder versions 1.60.20.3 or higher, and Plugin Builder XML 1.60.20.3 or higher.
It is also possible to generate CNC programs for aluminum components using the Plugin Builder XML + Insight integration system. In these cases, the contour feature is not generated. For the correct generation of files, the registration of aluminum components must have the attribute value ALUMINUM_COMPONENT = Profile or Crossbar.
Integration XML Attributes
View information about the attributes of the Integration XML with the ERP Insight Plugin, by clicking directly on one of them:
NOTES: The TOPSURFACE_GRAIN, BOTTOMSURFACE_GRAIN and BOM_TYPE attributes can be added to the integration XML with the ERP Insight integration plugin. These attributes make it possible to precisely identify the behavior of the materials applied in the project, ensuring correct integration with ERP Insight.
1. TOPSURFACE_GRAIN
The TOPSURFACE_GRAIN attribute defines whether the top face of the item has a vein direction material.
- Type: Boolean 1 (True) or 0 (False)
- The value is obtained from the registration of the material applied to the top face of the item:
- 1 (True): Material with vein direction
- 0 (False): Material without vein direction
The value of this attribute is looked up in the register of the material applied to the top face of the item.
If the material applied to the top face of the item has a direction of vein, the value will be 1. If it does not have a direction of vein, the value will be 0.
Examples:
- • TopSurface_Grain attribute with the value 0:
- TopSurface_Grain attribute with the value 1:
2. BOTTOMSURFACE_GRAIN
The BOTTOMSURFACE_GRAIN attribute defines whether the bottom face of the item has a vein direction material.
- Type: Boolean 1 (True) or 0 (False).
- The value is obtained from the registration of the material applied to the underside of the item:
- 1 (True): Material with vein direction
- 0 (False): Material without vein direction
Examples:
- BOTTOMSURFACE_GRAIN attribute with a value of 0:
- BOTTOMSURFACE_GRAIN attribute with a value of 1:
3. BOM_TYPE
The BOM_TYPE attribute tells you the type of material.
Type: text
This attribute will be displayed in the structure items, if it has a registered value.
Example of BOM_TYPE attribute presentation:
Configuration of the BOM_TYPE attribute
To register the Bom_Type attribute that will be inserted in the XML, of the configuration:
1. Access Registry - Budget - Structures.
2. In Structures - Structure, select the structure that needs to add the information. Access the Builder tab, and enter the desired value in BOM_TYPE.
IMPORTANT: By default, the BOM_TYPE field will be empty.
4. PHANTOM
The PHANTOM attribute shows the information where the items are phantoms, so they will not be presented in XML.
Code example to be inserted:
5. HASHSTRUCTURE
The HASHSTRUCTURE attribute will be displayed on all items that have children.
Code example to be inserted:
6. LINE_TYPE
The LINE_TYPE attribute is used to identify a grouping item, in order to organize the order and/or budget. By definition, this grouping attribute must not be below a product level.
EXAMPLE:
Below, an example of XML with LINE_TYPE attribute applied to the item:
Tags available from Builder version 1.60.20.4:
7. IDCATEGORY
The IDCATEGORY attribute is used to identify the identifier of the category to which the item belongs.
Below is an example of XML with the IDCATEGORY attribute applied to the item:
8. UNIT
The UNIT attribute is used to identify the type of unit of measure the item's quantity is in. Below is an example of XML with the UNIT attribute applied to the item:
9. REDEFINITION
The REDEFINITION attribute is used to identify in items with margin redefinition, the margin redefined in the library.
Below is an example of XML with the REDEFINITION attribute applied to the item:
10. REPETITION
The REPETITION attribute is used to identify the repetition of a particular item in the environment. For libraries with Builder, this value is always 1.
Below is an example of XML with the REPETITION attribute applied to the item:
11. IDPRICEPROVIDER
The IDPRICEPROVIDER attribute is used to identify the identifier of the price provider. It normally has no value when there is only one provider, in this case Price.
Below is an example of XML with the IDPRICEPROVIDER attribute applied to the item:
12. PRICE
The PRICE attribute is used to search for prices online using the reference contained in the attribute (it is usually presented by the COMPLETE reference).
Below is an example of XML with the PRICE attribute applied to the item:
13. QUANTITY
Enter the quantity of the item.
14. FILECREATION
Enter the date and time the file was generated.
15. ASSISTANCEORDER
Tell us if it is a Technical Assistance project.