Now starting the session on Push Notifications in Acumatica #AcumaticaDevSummit pic.twitter.com/uuyFibsWKZ
— Tim Rodman (@TimRodman) June 20, 2018
What we will cover in this session #AcumaticaDevSummit pic.twitter.com/0NTGvAF0zN
— Tim Rodman (@TimRodman) June 20, 2018
Nice interactive touch with the video camera #AcumaticaDevSummit pic.twitter.com/YXplNjRsMe
— Tim Rodman (@TimRodman) June 20, 2018
Simple JSON example using Acumatica notifications #AcumaticaDevSummit pic.twitter.com/8C5dyi0gAv
— Tim Rodman (@TimRodman) June 20, 2018
Anatomy of an Acumatica notification #AcumaticaDevSummit pic.twitter.com/R4mzb4gYpo
— Tim Rodman (@TimRodman) June 20, 2018
MSMQ (Microsoft Message Queuing) will be required in Acumatica 2018 R2 because it's used by some internal Acumatica stuff #AcumaticaDevSummit
— Tim Rodman (@TimRodman) June 20, 2018
What happens when Acumatica sends a notification #AcumaticaDevSummit pic.twitter.com/rrAFlTic9z
— Tim Rodman (@TimRodman) June 20, 2018
Some recommendations for your Acumatica notification data queries, mostly surrounding performance #AcumaticaDevSummit pic.twitter.com/HVBIIcaj0I
— Tim Rodman (@TimRodman) June 20, 2018
Now we're building a push notification from a generic inquiry #AcumaticaDevSummit pic.twitter.com/2Tb6KqiDaZ
— Tim Rodman (@TimRodman) June 20, 2018
Notice, no formulas in this generic inquiry #AcumaticaDevSummit pic.twitter.com/D0apqp1DBj
— Tim Rodman (@TimRodman) June 20, 2018
A built-in notification definition #AcumaticaDevSummit pic.twitter.com/TqnIrH2AUm
— Tim Rodman (@TimRodman) June 20, 2018
More about the built-in definition #AcumaticaDevSummit pic.twitter.com/OuQbwEMcaL
— Tim Rodman (@TimRodman) June 20, 2018
Verifying the built-in notification #AcumaticaDevSummit pic.twitter.com/3Fxoy5hnff
— Tim Rodman (@TimRodman) June 20, 2018
Dropping them onto the screen in Acumatica #AcumaticaDevSummit pic.twitter.com/TUPnGdPFnq
— Tim Rodman (@TimRodman) June 20, 2018
Notice that only the PRODUCT vendor class is returned #AcumaticaDevSummit pic.twitter.com/odJFGGtzlV
— Tim Rodman (@TimRodman) June 20, 2018
Acumatica supports OData 3.0 #AcumaticaDevSummit pic.twitter.com/WPjjxjiKei
— Tim Rodman (@TimRodman) June 20, 2018
Now onto the built-in notification destinations #AcumaticaDevSummit pic.twitter.com/g5gKUnVZqz
— Tim Rodman (@TimRodman) June 20, 2018
Option #1: Webhook. You can add custom headers. Failed notifications are stored for 2 days. #AcumaticaDevSummit pic.twitter.com/l5brQnu8VB
— Tim Rodman (@TimRodman) June 20, 2018
An example using Webhookinbox #AcumaticaDevSummit pic.twitter.com/amlLs71d1C
— Tim Rodman (@TimRodman) June 20, 2018
Changing the currency on a Vendor to CAD (even though GBP shown in the screenshot) #AcumaticaDevSummit pic.twitter.com/G0pz7LcfDd
— Tim Rodman (@TimRodman) June 20, 2018
What it looks like when it lands in Webhookinbox #AcumaticaDevSummit pic.twitter.com/YT1vSNWzDA
— Tim Rodman (@TimRodman) June 20, 2018
Updating Terms on the vendor also sends the notification. The reason is that LastModifiedDateTime is included in the result set #AcumaticaDevSummit pic.twitter.com/0m1LHZmBUp
— Tim Rodman (@TimRodman) June 20, 2018
Option #2: SignalR (not as reliable) #AcumaticaDevSummit pic.twitter.com/Lg4EhShWSU
— Tim Rodman (@TimRodman) June 20, 2018
Option #3: MSMQ (most reliable) #AcumaticaDevSummit pic.twitter.com/g9zPv4W4C9
— Tim Rodman (@TimRodman) June 20, 2018
Recap of the three destination types #AcumaticaDevSummit pic.twitter.com/DTn8HHUBhr
— Tim Rodman (@TimRodman) June 20, 2018
Links to additional resources #AcumaticaDevSummit pic.twitter.com/BkwitOijFh
— Tim Rodman (@TimRodman) June 20, 2018
Thanks for a great session Vladimir #AcumaticaDevSummit pic.twitter.com/zs9ftgLvbN
— Tim Rodman (@TimRodman) June 20, 2018