Here at Simego we have started 2018 busy updating Ouvvi's user interface system to have a more modern look and feel. We believe, and we hope that you do to, that this new face lift makes the software faster and more intuitive to use. Ouvvi V4 is now available here.
Whilst we have been doing the UI update we have also been adding new features as requested by you, our customers. Below you will find a quick overview of the new features available.
Dashboards now enable you to group together vital projects so that you can quickly see what is successful and what is failing. This will help maintain a smooth running of all of your projects and is one of the great reasons why Ouvvi makes a fantastic management tool.
You can use the dashboard feature to create a monitoring system, to have a quick overview of your major systems. At a glance you can see if these have been running successfully or if they have failed, and you can see the time it took for the last request vs the overall average time it takes to run a request for that project. If the project monitoring your system has a Data Sync project adding, updating or deleting then you will also have a total data change number added to the project view. As this all feeds back into the logs you can have an auditable record of when your server was on and offline and for how long this was for.
We have created a monitoring dashboard to watch our Azure platform which holds our website, database and helpdesk system. We have also split this down further to observe each SQL Server contained within the Azure platform. So if any of these go offline, we can see when and where this happened to investigate further. This also watches our CRM, Salesforce and Podio API's to make sure they are running, as well as a project to let us know how many new users have signed up that day.
You can see a quick snapshot of this below:
Groups are similar to dashboards however we have envisaged these being a simpler way to group projects by type. For instance, we have collated all the projects we have that connect to a CRM instance under the CRM group. This makes it easier to locate the project you are after rather than scrolling through hundreds of projects. You can use these however you wish to.
As well as having the grouping and dashboards to make it easier to find the project you are looking for, we have also included a search bar at the top of the page. Use this to look for key words, and Ouvvi will return to you all projects, steps and triggers that contain those key words. Just type in the word or words and press return.
We have now added a new Ouvvi step handler for SSIS, that will allow you to run packages on your SSIS servers without installing an Agent on those machines. You can even pass Ouvvi user settings to those packages. The SSIS log gets imported into the Ouvvi log, meaning you can keep all logging information together in the same system. It's a great way to mix SSIS with Data Sync and other tasks.
For more information on the configuration of these steps please visit our documentation site.
You can install Ouvvi onto your Azure portal using Azure Web Apps. This can create a really cost-effective method of running Ouvvi rather than using a windows server license. You can run the web components through Azure and install the agents on any on premise machine or use a WebJob in Azure for Cloud only.
These agents can be stored wherever they are needed tucked safely behind your company's firewalls. This could then use Microsoft's scaling feature to scale up the system requirements as required, and return them back once the operation is complete.
We have been running our production systems on Azure with the basic SQL DB and S1 hosting package which has been great.
Azure can be used to make Ouvvi available on mobile devices and tablets, so now you can check up on those important projects wherever you may be. Just log into your azure hosted Ouvvi site such as
https://ouvvi.azurewebsites.net, and you can have full functionality of Ouvvi on the go.
We have updated the look of the status reports you will receive from Ouvvi if you use the 'Ouvvi Project Status Report' or the 'Ouvvi Status Report' step. These now include a more detailed log report on projects that have failed, so then you can better determine why something has failed before you log into your Ouvvi system. And an improved layout so that they are in a more readable format on your devices.
You can now add encryption to your Ouvvi and Data Sync Projects to help ensure you are GDPR compliant and to ensure the security of your project files. The new encryption will protect connection secrets, such as passwords and security keys, so if you need to export your project to an external user or to another colleague they cannot obtain those secrets. This will also cover Ouvvi user settings containing connection secrets and passwords, meaning that the password fields contained within connection strings will be encrypted. You will be able to maintain an encryption key per environment, and can generate your encryption keys from within Data Sync. The new encryption setup in Data Sync will contain a store of your encryption keys, however you will need to retain a copy of your encryption key as you will not be able to reveal this after the key has been generated. We recommend using a secure password store to do so, for example OnePassword.
If you run Data Sync projects with Success Data Changes enabled then you can now apply run conditions that can prevent subsequent steps from running if the first step had no changes but was still returned as a success. This is a great feature for scheduled synchronisation operations where there may not have been any changes made. One great way this can be useful is if you have a reporting step in the project, and you only wish for the report to be sent when changes have been made.
We have also updated the .opr files, so now when you import and export projects the project data remains in an XML format rather than being encoded. This makes it easier to read and edit if necessary.
The Import will now merge the meta data rather than delete the project and re-create it. This means that is a project exists then the project settings are not affected i.e. the triggers remain. Steps are also included in the merge, if a step does not exist in the import file then it is deleted. The step history is written during the import and audit events are created, meaning that when the merge occurs the run time history is not lost. The import will match projects and steps based on their name, so changing either of these will create new projects and steps.
If you ever think that there is a feature missing from our products, that would help you and other people out, then let us know by sending a message to email@example.com. We love to hear feedback from our customers and will keep striving to add more functionality to our software.