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: resources/integration_cards_guidelines.md
+10-1Lines changed: 10 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,7 +65,16 @@ The following roles/personas are supported:
65
65
- Page/Content Administrator
66
66
- Translator
67
67
68
-
Configuration Editor is usually defined in the "dt/Configuration.js" file and referenced in the manifest file under `sap.card/configuration/editor` property.
68
+
The Configuration Editor is implemented through two key components:
69
+
70
+
1.**Definition file**: Create a `dt/Configuration.js` file that exports a Designtime definition object
71
+
2.**Manifest reference**: Reference this definition in the `manifest.json` under the `sap.card/configuration/editor` property
72
+
73
+
The `dt/Configuration.js` file defines the Configuration Editor's structure by specifying:
74
+
- Form layout and field definitions
75
+
- Input controls and visualizations
76
+
- Validation rules and field relationships
77
+
- Grouping and organization of configuration options
69
78
70
79
When creating or modifying Integration Cards, follow these guidelines for Configuration Editors:
71
80
- Assume the role of Administrator persona when designing the Configuration Editor.
0 commit comments