This information alert is to advise of the pending release of Velocity365 Version 2.2. This product release contains numerous product enhancements as well as UI improvements and bug fixes. This release will be generally available for deployment to your non-production environment as of Friday March 15, 2019.
Some applications for Dynamics 365, such as Field Service, Portals, and Unified Service Desk store their configuration data as records in Dynamics 365 – alongside your business data.
Microsoft’s Configuration Migration tool allows you to easily move configuration data between Dynamics 365 environments. One limitation of the export function, though, is the inability to separate configuration records from business records of the same type.
The April 19 release of the Power Platform marks a major change in Microsoft’s delivery of updates to customers. With the changes in the updates from last October and the forced upgrade to version 9.x, the platform now will only maintain 1 version and has removed the Customer Driven Update Process. The April 19 release marks the first major release without a customer able to schedule it but the new process ensures everyone is on the latest version and adheres to a consistent update schedule.
It’s common that a single feature update in your portal means modification to multiple components – which can’t be deployed one at a time. Even after proper rehearsal – deploying these changes to a live production environment can be risky business. Any mistakes or delays in your deployment are immediately visible to users.
In these cases it may be decided that the best course of action is to take your portal down and replace it temporarily with a maintenance notice page – informing your users that updates are in progress and the portal will be back up momentarily.
This approach may not be suitable for all situations. Please refer to the Further Consideration section for more details.
An official “maintenance mode” feature is planned for the April 2019 release of Portals. This feature offers the benefits described in this blog post – and also addresses the concerns described below regarding search engine optimization. This blog post offers an interim solution.
Many regulatory organizations still have applicants fill out and submit paper forms at a general collection point, which are then manually sorted and distributed to the appropriate department. With all the licenses and applications that now govern society, how is it that the technology supporting this entire industry has not evolved with the times?
For those who work in regulated fields, the pain of obtaining a license through an agency is all too familiar. The long lines, the endless forms, and the total black hole of information while waiting for approval or rejection make for a difficult, hard to navigate experience for applicants. It’s also a terrible process for those who actually handle license and permit applications – the regulatory employees. On the other side of the counter, employees deal with an application management process that has not advanced much in the last 20 years. Let’s look at three factors that make life more painful for regulatory employees: disparate systems, repetitive tasks, and dealing with complaints from the public.