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: source/includes/_internal-methods.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,13 +85,14 @@ Name | Description
85
85
86
86
In addition to inserting static content, you can also add interactive functionality to the menu items by providing `onclick` functions. For example, you can prevent the default link behavior and display an alert message when a menu item is clicked, as demonstrated in the example code.
87
87
88
-
## API.updateLink(intent, setupFunction(meta))
89
-
The `updateLink` method is used to override links on the page where the integration is enabled.
90
-
In order to use this functionality the integration's schema in WISE needs to have a content mapping entry with the content type as `links`.
91
-
The purpose of content needs to be the overriding links functionality (eg, X-Time). Then we just need to select all the PageAlias that we would like to target.
92
-
The PageAlis list can be overriden in the site level to capture any sitebuilder pages as well.
The `updateLink` method is used to override links on the page where the integration is enabled.
93
90
94
-
The WIAPI would deduce the link of the corresponding PageAlias in the site level letting you to modify the link element.
91
+
In order to use this functionality, the integration's schema in WISE needs to have a content mapping entry with the content type as `links`.
92
+
93
+
The purpose of content needs to be the overriding links functionality (e.g., X-Time overriding Service Scheduler pages). Then we need to select all the Page Aliases that we would like to target. The PageAlias list can be overriden in the site level to capture any SITEBUILDER pages as well.
94
+
95
+
The WIAPI will determine the link of the corresponding Page Alias in the sitemap, allowing you to modify the link element.
95
96
96
97
The current supported intent types are:
97
98
@@ -105,7 +106,8 @@ The current supported intent types are:
105
106
106
107
`value-a-trade`
107
108
108
-
And, we only support limited attributes of the link to be modified in order to preserve the look and feel of the link.
109
+
We only support limited attributes of the link to be modified in order to preserve the look and feel of the link.
110
+
109
111
The attributes that can be modified are `href`, `target`, `onclick`, `popover` and `attributes (data-*)`.
110
112
111
113
> Usage:
@@ -124,9 +126,9 @@ The attributes that can be modified are `href`, `target`, `onclick`, `popover` a
124
126
125
127
## Content Modification (deprecated)
126
128
127
-
The `updateLink` method would be replacing this functionality.
129
+
The `updateLink` method replaces this functionality.
128
130
129
-
This method allows you to modify content on a page level. Right now we only support the modification of the `schedule-service` button. So, by using this method you would be able to modify the link attributes of all the schedule service buttons on a page.
131
+
This method allows you to modify content on a page level. Right now we only support the modification of the `schedule-service` button. By using this method you can modify the link attributes of all the schedule service buttons on a page.
0 commit comments