We have a new type of source system, the Custom Assets source system. The Custom Assets source system creates a database in SQL Server and then syncs content from this database every 10 minutes.
You can create your own asset types in Loome Publish and then write your own code to populate this database from line of business applications or products that we don’t have available as first party source systems.
You can optionally also write your own embedding libraries for your custom asset types to get a complete integration experience. We will be providing a complete guide to accomplishing this in the near future.
You can now use a service principal to sync content from Power BI in to Loome Publish.
If you are hosting Loome Publish on-premises, you can enter a Service Principal Client ID and Secret directly via the user interface.
If you are hosting Loome Publish in Azure, you have the option to configure your Azure App Service as a Managed System Identity and then retrieve either a secret or a certificate for the Service Principal from an Azure Key Vault for added security.
Please note that due to limitations implemented by Microsoft, you can only use Service Principals to sync workspace content. Options for app content syncing will be disabled on the source system configuration screen when you select to use a Service Principal.
You can find more information on how to configure a Service Principal for use with Power BI here - https://docs.microsoft.com/en-us/power-bi/developer/embedded/embed-service-principal
As Microsoft are deprecating SMTP usage on Office 365, we have added the ability to send outgoing email via Microsoft Graph API.
If you are hosting Loome Publish on-premises, you can enter a username, password, and Azure AD Application Registration to allow you to send email via Microsoft Graph API.
If you are hosting Loome Publish in Azure, you have the option to configure your Azure App Service as a Managed System Identity and then retrieve the username and password from Azure Key Vault for added security.
In order to make use of this feature, you will need to configure an Azure AD Application Registration with delegated permissions to Microsoft Graph for the Mail.Send permission and Allow public client flows enabled. This can be done to your existing Azure AD Application Registration, or you can create a new Azure AD Application Registration.
If you are hosting Loome Publish in Azure, you now have the ability to use a Managed System Identity to provide access from the Loome Publish Azure App Service to the Loome Publish Azure SQL DB. Simply configure your Azure App Service with a Managed System Identity and provide it access to the Azure SQL DB. Once completed, re-run the Loome Publish installer, removing the user id and password from the connection string, and adding
Authentication=Active Directory Default; to the connection string.
You can find out more information here on how to configure a Managed System Identity and provide it access to an Azure SQL DB here - https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-sql
The asset registration wizard has not been reworked to allow you to optionally publish an asset directly from the wizard. Each step will allow you to either register the asset, or publish the asset where enough information has been provided to do so.
The logging framework has been reworked to provide a better experience for administrators. All logging is now done to file under the /logs folder of the application. Logging is enabled by default now and set at the error level. With this in mind you can wire up your logging systems to retrieve and alert on any issues logged by Loome Publish.
To collect more detailed logs you can edit the web.config of the application and change the serilog:minimum-level app key to either Information or Debug.
Logs create one file per day that is date stamped, files are removed after 30 days.