Scheduler
- Change – Moved Security related details to new tab called Security
- New – Support for creating Webhook URLs with Client Secrets so that external applications can call-back to Scheduler tasks and gain access without a sign in. The Client Secrets can be revoked or have an expiry date time. Many Client Secrets can be assigned to any account but only admin users may manage and create Client Secrets.
- Add – Better support for incoming Webhook POSTs with JSON or XML data. Created new REST API endpoint called SchedulerWebhookPost which external applications can POST data to. This is automatically saved as a Task Parameter called Post which can then be accessed with a reference {_Task.Param.Post}. The idea is that applications POST data and the Task is triggered and then tasks the JSON or XML data and executes actions like a Writeback into a database table or some other action like grooming the data and sending an Email or Teams Message.
- New – Microsoft Teams – Send Message Action. Based on a Teams Channel Link or Channel – Incoming Webhook URL Link create messages. There is a basic mode for sending simple messages with a subject, priority and message and an advanced most for POSTing JSON so that the full functionally of ‘Message Cards’ can be used for things like Questionnaires and Feedback.
Site Setup
- Change – Revised Client Secret / Feed Key logic as Power BI has a bug that meant that some character sequences would not work, so now very simple characters are used. Previously generated Client Secrets / Feed Keys will need to be refreshed. Also, it is possible to have more than one Client Secret associated with a user name. Only users with admin permissions can maintain and create Client Secrets. As before it is possible to revoke or have a Client Secret expire at a defined date and time. Client Secrets allow external applications to access the Sharperlight REST API without going through a complex sign in procedure. For example, Power BI and Webhooks. The Client Secret can be on the URL but in most cases, it is used in the Header over https using Basic Authentication with a username of FeedKey. For example, Basic FeedKey:Client_Secret
- Add – Azure AD sync for the Web Channel can now support syncing via Web sign in form other Applications. Two new REST endpoints have been create called AzureLogon and AzureLogoff. When setting up Azure Application there two end point can be used to ensure that Sharperlight auto signs in with the same user and also auto signs out when the main web apps signs out.