You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/partners/siemens/teamcenter-bom-component/customization.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,12 +2,12 @@
2
2
title: "Advanced Customization Options"
3
3
url: /partners/siemens/bom-widget-customization/
4
4
weight: 3
5
-
description: "Describes the customization capabilities that allow developers to add data from external systems, and how these can be combined into the Teamcenter BOM widget."
5
+
description: "Describes the customization capabilities that allow developers to add data from external systems, and how these can be combined into the Teamcenter BOM component."
6
6
---
7
7
8
8
## Augmenting with Mendix Data
9
9
10
-
Client columns allow you to display custom data next to Teamcenter properties in the BOM view. The widget calls the following two microflows:
10
+
Client columns allow you to display custom data next to Teamcenter properties in the BOM view. The component calls the following two microflows:
11
11
12
12
*`CUSTOM_RetrieveClientColumnDefinitions` – Microflow to retrieve the client column definitions: client column name, width, and column order.
13
13
*`CUSTOM_RetrieveClientColumnData` – Microflow to retrieve the additional cell data to display for the BOM lines and client columns.
@@ -16,7 +16,7 @@ As a developer, you are free to implement this according to your own needs. Addi
16
16
17
17
### CUSTOM_RetrieveClientColumnDefinitions
18
18
19
-
This microflow is invoked by the Teamcenter BOM widget to retrieve the definitions of the client columns to display in the widget.
19
+
This microflow is invoked by the Teamcenter BOM component to retrieve the definitions of the client columns to display in the component.
@@ -25,7 +25,7 @@ This microflow is invoked by the Teamcenter BOM widget to retrieve the definitio
25
25
***Object**: `MendixColumnRoot`
26
26
***Attribute**:
27
27
28
-
*`WidgetId` is a unique identifier for the specific Teamcenter BOM widget instance that is making the request. This is useful if your app includes multiple Teamcenter BOM widgets that need to display different columns. You can use this ID to differentiate and return the appropriate data.
28
+
*`WidgetId` is a unique identifier for the specific Teamcenter BOM component instance that is making the request. This is useful if your app includes multiple Teamcenter BOM components that need to display different columns. You can use this ID to differentiate and return the appropriate data.
@@ -34,8 +34,8 @@ This microflow is invoked by the Teamcenter BOM widget to retrieve the definitio
34
34
***Object**: `List of ClientColumn`
35
35
***Attributes**:
36
36
37
-
*`Name` – The name of the client column. This name is used in the UI of the Teamcenter BOM widget as the column title.
38
-
*`ColumnOrder` – The order of the column within the widget, respectively. Teamcenter columns also have their own order, so this needs to be filled in conjunction. If the order is identical, Teamcenter columns take priority.
37
+
*`Name` – The name of the client column. This name is used in the UI of the Teamcenter BOM component as the column title.
38
+
*`ColumnOrder` – The order of the column within the component, respectively. Teamcenter columns also have their own order, so this needs to be filled in conjunction. If the order is identical, Teamcenter columns take priority.
39
39
The first column should be object_string, which is already defined.
40
40
All Mendix client columns must start with `columnOrder 2` and will be displayed before the Teamcenter columns.
41
41
Mendix columns are sorted based on their `columnOrder` parameter.
@@ -46,7 +46,7 @@ This microflow is invoked by the Teamcenter BOM widget to retrieve the definitio
46
46
47
47
### CUSTOM_RetrieveClientColumnData
48
48
49
-
This microflow is invoked by the Teamcenter BOM widget to retrieve the data to be rendered in the BOM tree. It gathers cell data for specific BOM lines and any client columns.
49
+
This microflow is invoked by the Teamcenter BOM component to retrieve the data to be rendered in the BOM tree. It gathers cell data for specific BOM lines and any client columns.
@@ -55,9 +55,9 @@ This microflow is invoked by the Teamcenter BOM widget to retrieve the data to b
55
55
***Object**: `MendixDataRoot`
56
56
***Attributes and associations**:
57
57
58
-
*`WidgetId` – A unique identifier for the specific Teamcenter BOM widget instance that is making the request. This is useful if your app includes multiple Teamcenter BOM widgets that need to display different data. You can use this ID to differentiate and return the appropriate data.
59
-
* Associated `MendixDataColumnName` objects – This list specifies which custom columns the widget is configured to display. Each object has a `Name` attribute, representing the identifier of a custom column.
60
-
* Associated `MendixDataBOMLine` objects – This list contains the specific BOM lines for which the widget requires data. Each object includes attributes such as `ItemId`, `RevisionId`, `RevisionUId`, and `BOMlineUid` to identify the BOM line and its `ItemRevision`.
58
+
*`WidgetId` – A unique identifier for the specific Teamcenter BOM component instance that is making the request. This is useful if your app includes multiple Teamcenter BOM components that need to display different data. You can use this ID to differentiate and return the appropriate data.
59
+
* Associated `MendixDataColumnName` objects – This list specifies which custom columns the component is configured to display. Each object has a `Name` attribute, representing the identifier of a custom column.
60
+
* Associated `MendixDataBOMLine` objects – This list contains the specific BOM lines for which the component requires data. Each object includes attributes such as `ItemId`, `RevisionId`, `RevisionUId`, and `BOMlineUid` to identify the BOM line and its `ItemRevision`.
0 commit comments