Skip to content

Commit 85b2904

Browse files
committed
screenshot and doc changes
1 parent b3a6280 commit 85b2904

10 files changed

+3
-4
lines changed

README.md

+3-4
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ To configure the URL buttons, you must supply a JSON array of URLs with `title`
6666

6767
This will yield the following display:
6868

69-
![social_media_sites](./assets/screenshot-0.png)
69+
![social_media_sites](./src/images/screenshot-0.png)
7070

7171
### Using Zendesk Object Properties
7272

@@ -104,7 +104,7 @@ This generates the following button:
104104

105105
We can highlight this button and see the following URL:
106106

107-
![screenshot](./assets/screenshot-1.png)
107+
![screenshot](./src/images/screenshot-1.png)
108108

109109
### Using Custom Fields in URLs
110110

@@ -123,8 +123,7 @@ For example, let's say we use the custom field for the customer like `Issue Topi
123123

124124
Given an issue type of "new feature", this would generate a URL with the values set:
125125

126-
![customer_related_issues](./assets/screenshot-2.png)
127-
![customer_related_issues_url](./assets/screenshot-3.png)
126+
![customer_related_issues](./src/images/screenshot-2.png)
128127

129128
An important note here is that URLs generated by custom fields are not updated dynamically. If the custom field is on the Agent side for example and is updated, the page will need to be refreshed to update the URLs.
130129

assets/screenshot-0.png

-40.5 KB
Binary file not shown.

assets/screenshot-1.png

-20.4 KB
Binary file not shown.

assets/screenshot-2.png

-24.4 KB
Binary file not shown.

assets/screenshot-3.png

-19.5 KB
Binary file not shown.

src/images/dots.gif

-35.7 KB
Binary file not shown.

src/images/screenshot-0.png

81.4 KB
Loading

src/images/screenshot-1.png

92.9 KB
Loading

src/images/screenshot-2.png

120 KB
Loading

src/images/warning.png

-18.6 KB
Binary file not shown.

0 commit comments

Comments
 (0)