Update README.md
This commit is contained in:
parent
47cbbde49f
commit
efd1b0ac0e
1 changed files with 1 additions and 2 deletions
|
|
@ -9,7 +9,6 @@ Toast_Notify.ps1 will read an XML file on a file share so Toast Notifications ca
|
||||||
To create a custom XML, copy CustomMessage.xml and edit the text you want to display in the toast notification. Reference that file using one of the script parameters.
|
To create a custom XML, copy CustomMessage.xml and edit the text you want to display in the toast notification. Reference that file using one of the script parameters.
|
||||||
|
|
||||||
**Points to Consider**
|
**Points to Consider**
|
||||||
|
|
||||||
I am using an existing app in Windows to call the Toasts. This script creates two buttons in the Toast, "Details" and "Dismiss". Cicking details is designed to take the user to an internal Service Desk announcement page. For that reason, **MSEdge** works really well because the Toast Action launches the browser in the foreground. Oh, you will need MSEdge installed on your client computers for this to work.
|
I am using an existing app in Windows to call the Toasts. This script creates two buttons in the Toast, "Details" and "Dismiss". Cicking details is designed to take the user to an internal Service Desk announcement page. For that reason, **MSEdge** works really well because the Toast Action launches the browser in the foreground. Oh, you will need MSEdge installed on your client computers for this to work.
|
||||||
|
|
||||||
The following files should be present in the Script Directory when you create the package in MEMCM:-
|
The following files should be present in the Script Directory when you create the package in MEMCM:-
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue