my app has a scheduled agent that checks for new mails and updates the tile if new mails received, i'd also like to play a notification sound from the background agent to notify the user about new mails like the google mail app does, however I haven't found anything except to the SoundEffect which seems not usable from scheduled task.
is there a way to play such notification sound?
thanks
There is no way to play a sound from a background agent. (see the list of Unsupported APIs for Background Agents)
If you want to notify the user of a change you could raise a ShellToast instead. (depending on the users settings this may play a sound.)
Related
Is there a way to activate an event Alexa without speaking?
For instance, I am working on a project involving a pill box, and once it is set up, I want Alexa to remind me to take my medication without requiring a vocal command from me
Have you looked into Routines? This would let you schedule time-based actions like Alexa-spoken reminders.
If you're building a custom skill, the Reminders API would give you a way to programmatically setup spoken reminders as well.
There's also the Alexa Routines Kit skills can use to create Routines by voice, but this is in developer preview, so you would need to apply for access.
I was going through the integration documents available for snowflake & service now. But, all documents are oddly focussed on sf consuming snow data for analytics. Didn't find anything related to creating tickets for failures at snowflake. Is it possible?
It's not about the monitoring & notification aspect of snowflake but connecting with service now and raise a ticket for query failures (tasks,sp etc.)
Any ideas?
There's no functionality like that as of now. I can recommend you open an Idea for it and if enough customers want it our Product Management will review it.
For the Snowpipe, we found a way to use it. We send the error message to SNS and then we can do a Lambda function to call the Rest API of ServiceNow to create a ticket.
For Task, we find that it is possible to use External Functions to notify to AWS whenever the Task fails, but we haven’t implemented it.
Email is a simple way. You need to determine how your ServiceNow instance is processing emails. We implemented incident creation from Azure App Insights based on emails.
In ServiceNow find the Inbound Action you need to process the email or make one.
ServiceNow provides every instance with an email account
Refer to enter link description here
The instance email is usually xxxx#service-now.com.
If your instance url is "audi.service-now.com", the email would be "audi#service-now.com".
For a PDI dev#servicenowdevelopers.com, e.g.; dev12345#servicenowdevelopers.com
I'm just getting started with Watson Dialog service and I'm trying to ensure that I don't allow my users to attempt to resume a conversation with the bot if their conversation session is no longer valid. Is there an expiration on Dialog conversations at all? Or does IBM simply store conversations forever?
EDIT:
If there is a method to determine whether a Dialog Conversation has expired, please provide a link to documentation, or an example, of said method.
If a user returns and starts a new session, then that is a new conversation. Conversations do time out. I've only worked on enterprise engagements, so the time out varies. I believe default is 30 minutes, but that may change for Bluemix.
A better solution however is to have your application on determining it's time out, to dump the users profile variables to storage. When they return you can rebuild the relevant part of the conversation.
I want to send a message from a windows phone to other windows phone via web services.
How can I do that?
Make use of Push Notifications. They are used to initiate an activity on a phone from a third party. There are three types of them: Tile Notification, Toast Notification and Raw Notification.
Toast Notifications (Example: SMS alert) are received when the application is not running. If for some reason sending from one phone to another implies that both of them run at the same time, consider using Raw Notifications. However, I suppose you should use both of them: if a Raw Notification is dropped (this usually means that the application is not running in the foreground), send Toast Notification.
As far as I undestand your requirements, you should do the following:
Once the application is started (or a user is logged in), establish Push channel and request PushUri for the phone from Microsoft Push Notification Server
Send the PushUri to your service, associate it with the user and save it.
To send a message to a phone application, just pass appropriate parameters to its PushUri. You can do this either from your web service or directly from another phone.
You may find the documentation useful. There are examples of how to establish, send and receive them.
P.S. Take into account that the second Toast Notification may fail as well because during the timespan between two Notifications the user may launch your application. Don't forget to handle this.
I need to develop a windows application with .NET 3.5 that needs to have a calendar and user can schedule appointments.
I want (not with a windows-service) that while the application is on, all the reminders that are set up for this user + reminders that admins set them up, should trigger an event in the application so I can handle it (showing the user a message, notify icon or whatever), once its datetime becomes now.
The data is saved in SQL Server and accessible from many computers, the admin should be able to externally create reminders for users.
Any approaches?
Locally, you could trigger the events using a timer that check the current time e.g. every 10 seconds or more often. The clients should regularily synchronize with the database server, querying all data for the current day or (on user demand) later events. This allows the clients to run and to remind the user even when the network fails for some time.
Another very interesting option is a server side reminder tool next to the database. It generates reminders and sends them via XMPP to the clients. The client machines don't need a special software anymore - any Jabber client would be sufficient, although a special software acting as an XMPP client would be possible, too.
You should really avoid popups. Popups are generally considered not user friendly. They interrupt the user's work flow. Even worse, they steal the keyboard input. What if the users was typing an important email right now?
Instead you might provide a nice, pleasant sound and a task bar bubble or similar.