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: Documentation/Architecture.md
+15-1Lines changed: 15 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,6 +47,12 @@ The app can be customized if you wish, though it's worth noting that customizati
47
47
48
48
Integration with Prompt Buddy is provided through a single flow (details can be found below) which adds Prompt Buddy prompts to the **Prompts** list and Prompt Pulse prompts to the relevant dataverse tables used by Prompt Buddy. This keeps both solutions in sync and ensures prompts can be accessed from both apps.
49
49
50
+
## Reporting
51
+
52
+
Basic reporting can be found in the **Reporting** list in the form of a single list item. This list item is created automatically if it does not exist by the app and flows.
53
+
54
+
If multiple list items exist in this list, only the first item is updated in terms of the numeric data.
55
+
50
56
# Flows
51
57
52
58
Detailed information about the flows used in the solution can be found below:
@@ -125,7 +131,7 @@ This flow is triggered on a recurrent scheduled inside the Dataverse for Teams e
125
131
126
132
## Data Source
127
133
128
-
As detailed in the [Overview](Overview.md) documentation, there are 3 SharePoint lists used in prompt pulse. Please see the details of each list below and what each column is used for:
134
+
As detailed in the [Overview](Overview.md) documentation, there are 4 SharePoint lists used in prompt pulse. Please see the details of each list below and what each column is used for:
129
135
130
136
### Prompts list
131
137
@@ -162,4 +168,12 @@ As detailed in the [Overview](Overview.md) documentation, there are 3 SharePoint
162
168
| -------- | ------- | ------- |
163
169
| Value | Single line of text | The configuration value.
164
170
171
+
### Reporting list
172
+
173
+
| Column Name | Type | Used for |
174
+
| -------- | ------- | ------- |
175
+
| PromptsSent | Number | The number of prompts sent in Prompt Pulse either directly or via scheduling.
176
+
| AppLaunches | Number | The number of times the app has been launched/opened.
177
+
| PromptsCopied | Number | The number of times prompts have been copied (clicking the prompt card) in the app.
178
+
| PromptsLiked | Number | The total of prompts that have been liked by users.
Copy file name to clipboardExpand all lines: Documentation/Deployment-guide.md
+28-6Lines changed: 28 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,6 @@ Note - You must create ALL of the columns below even if you are not deploying th
43
43
| ChannelIds | Multiple lines of text |
44
44
| GroupChatIds | Multiple lines of text |
45
45
| CommunityIds | Multiple lines of text |
46
-
| MessageId | Single line of text |
47
46
| Scheduled | Yes/No | Default value = No |
48
47
| ScheduledDateTime | Date and time | Include time |
49
48
| Status | Choice | Not Sent, Send, Sent, Failed | Default value = Not Sent
@@ -61,31 +60,53 @@ Note - You must create ALL of the columns below even if you are not deploying th
61
60
| LikedPrompts | Lookup | Source list = 'Prompts', Select a column = 'ID' |
62
61
| TutorialComplete | Yes/No | Default value = No |
63
62
64
-
6. Create a list name 'Configuration'.
63
+
6. Create a list named 'Reporting'.
65
64
7. Create the following columns:
66
65
67
66
| Column Name | Type |
68
67
| -------- | ------- |
69
-
| Value | Single line of text
68
+
| PromptsSent | Number
69
+
| AppLaunches | Number
70
+
| PromptsCopied | Number
71
+
| PromptsLiked | Number
70
72
71
-
8. Create a list item in the above list with the following details:
73
+
8. Create a list named 'Configuration'.
74
+
9. Create the following columns:
75
+
76
+
| Column Name | Type |
77
+
| -------- | ------- |
78
+
| Value | Single line of text
79
+
80
+
10. Create a list item in the above list with the following details:
72
81
73
82
Title: AppId
74
83
75
84
Value: Leave empty
76
85
77
-
9. Create a second list item in the above list with the following details:
86
+
11. Create a second list item in the above list with the following details:
78
87
79
88
Title: ServiceAccountUPN
80
89
81
90
Value: UPN (Email) of your service account
82
91
83
-
9. Create a third list item in the above list with the following details:
92
+
12. Create a third list item in the above list with the following details:
84
93
85
94
Title: PromptBuddyInstalled
86
95
87
96
Value: 'true' (if you wish to integrate with Prompt Buddy) or 'false'.
88
97
98
+
13. Create a fourth list item in the above list with the following details:
99
+
100
+
Title: ShowShareEngage
101
+
102
+
Value: 'true' (if you wish to allow sharing to Viva Engage) or 'false'.
103
+
104
+
14. Create a fifth list item in the above list with the following details:
105
+
106
+
Title: ShowShareUsers
107
+
108
+
Value: 'true' (if you wish to allow sharing to users) or 'false'.
109
+
89
110
## Step 2: Deploy Power Apps solution
90
111
91
112
1. Navigate to **Power Apps** as the service account.
@@ -129,6 +150,7 @@ Before rolling out Prompt Pulse, it is neccessary to configure the permisions on
129
150
1. Amend the permissions on the **Prompts** list (Advanced Settings) to **Create items and edit items that were created by the user**.
130
151
2. Amend the permissions on the **Users** list (Advanced Settings) to **Read items that were created by the user** and **Create items and edit items that were created by the user**.
131
152
3. Break permission inheritance on the **Prompts** and **Users** lists and add only users/groups that will use Prompt Pulse.
153
+
4. Break permission inheritance on the **Configuration** and **Reporting** lists and ensure that only admins have write access to these lists, users should have read access.
132
154
4. Ensure that admins who may need to read, edit and delete all list items have **Full Control**/**Owner** permissions on the SharePoint site.
**Note - Viva Engage and Users radio buttons are only enabled if the 'ShowShareEngage' and 'ShowShareUsers' list items in the Configuration list are set to true.**
51
+
50
52
### Viewing/using prompts
51
53
52
54
From the main screen, users can view the latest 20 prompts. To use a prompt simply click the prompt **'tile'** and the prompt text will be copied to your clipboard.
@@ -119,6 +121,21 @@ To import prompts from Prompt Buddy, follow the steps below:
Basic reporting to showcase the adoption of Prompt Pulse is now available in the form of a SharePoint list. A single list item will be created in this list by the app and flows if it does not exist.
127
+
128
+
The 'Reporting' list shows the following information:
129
+
130
+
- PromptsSent - The number of prompts sent in Prompt Pulse either directly or via scheduling.
131
+
- AppLaunches - The number of times the app has been launched/opened.
132
+
- PromptsCopied - The number of times prompts have been copied (clicking the prompt card) in the app.
133
+
- PromptsLiked - The total of prompts that have been liked by users.
134
+
135
+
You may wish to create your own reports using tools such as Excel or PowerBI to visualize this data.
136
+
137
+
<imgsrc="https://github.com/pnp/prompt-pulse/blob/main/Documentation/Images/reporting-list-screenshot?raw=true"alt="Prompt Pulse Reporting List Screenshot"><br/>
138
+
122
139
### Tips
123
140
124
141
- Use a dedicated service account/M365 user when deploying Prompt Pulse (adaptive cards will be sent from this account).
@@ -143,7 +160,7 @@ There are 6 flows that are part of the Prompt Pulse solution, these are listed b
143
160
144
161
As mentioned earlier there is an additional flow for the Prompt Buddy integration.
145
162
146
-
- Send Prompt: This flow executes when a list item is created or modified in the 'Prompts' list and sends the prompt to the specified location using adaptive cards or in the case of Viva Engage, a message.
163
+
- Send Prompt: This flow executes when a list item is created or modified in the 'Prompts' list and sends the prompt to the specified location using adaptive cards or in the case of Viva Engage, a message.
147
164
- Send Scheduled Prompt: This flow runs on a recurrent schedule (5 minutes by default) and is responsible for checking for scheduled prompts in the list and sending these.
148
165
- Like Prompt: This flow runs when a user clicks the **Like Prompt** button in the adaptive cards and adds the prompt to the users' liked prompts.
149
166
- Get Group Chats: This flow is used in the Power App and retrieves a list of group chats that the current user is a member of where the Prompt Pulse account is a member of the chat.
@@ -160,6 +177,7 @@ There are 3 SharePoint lists used in the solution:
160
177
- Prompts: Stores the prompts shared/scheduled in the app.
161
178
- Users: Stores the users who have opened/used Prompt Pulse and their liked prompts.
162
179
- Configuration: Stores configuration settings for Prompt Pulse.
180
+
- Reporting: Stores basic reporting data for Prompt Pulse.
163
181
164
182
These lists can be easily extended or changed should you wish to modify/customize Prompt Pulse. You can of course edit and delete prompts directly from the list if required. Avoid modifying the values of the GroupId, GroupChatId, TeamId, ChannelId and MessageId columns as these are used heavily in the Power Automate flows.
0 commit comments