OpenInsight 10.0.8 and other news


My new OpenInsight 10.0.8 based demo application, coming very soon.

Hi Everyone, I hope that you are all well, staying safe during these Covid-19 days and that the various government measures around the world are not impacting on you, your families and your businesses too much.

Looking back at the blog, I cannot believe how long it has been since I posted anything here. That is not a sign of how busy, or not busy, I have been and I have been keeping very busy over the nine months or so.

Personally, I have been working from home throughout the lockdown period in the UK and nothing much really changed, other than my daughter taking over my office and regular workplace. Thankfully, I can work pretty much anywhere. I hope that you have been as fortunate in your workplace, although I know that some of you have struggled to settle into working from home and you are glad to be getting back t osome level of normality.

On the work side, I was really busy at the beginning of lockdown. This was mostly helping people with setting up remote workers as countless numbers of end users were moved from office to home working. I am pleased to say that pretty much everyone relocated their OpenInsight end users to remote working, regardless of whether this involved an eay O4W move or a slightly more involved OI desktop move.

The process also had one interesting benefit. It flagged up a number of systems that were not necessarily configured for optimal performance and stability and my support colleagues worked with those clients to help them to get the best from their remote access solutions.

Following this floury of suport activity, which also resulted in a number of new licenses, my client side activity settled back to normal levels for the duration of the lockdown and July and August are seasonally slow.

For me, this was the perfect time for RevUS to begin putting the finishing touches to the next OpenInsight release. I was given access to the 10.0.8 alpha and then beta releases and I set to building myself a brand new application. This would be written for the desktop and entirely in version 10.0.8. The development has gone well and, once completed, I hope to make it availble to all of our WORKS subscribers.

… this is THE release when I think that OpenInsight and other Multivalue developers should begin to explore OpenInsight and how it can be used to modernise and benefit their application development.

This project has enabed me to get more and more into application development with OpenInsight 10.0.8 and to learn more and more along the way. I will write more about the application itself nearer to when it is released, but it features commuter modules heavily (whereas the EXAMPLES application in OpenInsight is largely script based), some nice pretty) screens and I hope that it will feature a complex report with charts and more. The is an area that I am working on with my support colleagues at the moment.

I have been amazed at what a junior developer can build using OI10 and this is never moreso that now with the new version. The process of application development using the new version is becoming quicker and more enjoyable with each release. In addition, in my opinion, this is THE release when I think that OpenInsight and other Multivalue developers should begin to explore OpenInsight and how it can be used to modernise and benefit their application development.

Personally, I would have liked for this to be version 10.1, yes I really do think that it is good enough. But, I fully respect Revelation’s decision to hold this as another point release and especially as more and more Revelation developers are currently making the move to version 10 and more developers are reporting on their experiences of running their older applications through the conversion.

Will the next release be that ground breaking 10.1, we will have to wait and see, but I certainly hope that it will.

So, if you are an OpenInsight WORKS subscriber, you can now download both the 10.0.8 upgrade and full install files from the private WORKS area. If you are not yet on WORKS, or your subscription has since expired, you can still get your hands on the usual 30 day evaluation which has just been updated to 10.0.8.

For those of you that sinply want an update on the main changes, I have copied those below for your reading pleasure.

So, I’ll leave this long posting for now and I’ll be back very soon (I hope) with details of my new OI 10.0.8 written demo app.

ttfn,
M.

OpenIsight 10.0.8 Release Notes

Major Changes in the OpenInsight 10.0.8 Release

OpenInsight now provides an option to change the precision of mathematical operations. This can be set by calling the setEPMode stored procedure, passing in 1 to enable and 0 to disable the functionality. By default, the extended precision math will maintain 32 digits of precision, but this can be modified by calling the setEPModePrecision stored procedure, passing in the number of digits of precision desired. Both the enabling of extended precision, and the default number of digits, can also be defined in the application properties. The following operators/functions are affected: +, +=, -, -=, *, /, ==, =, !=, <>, >, <, >=,<=, mod(), int(), abs(), atan(), cos(), exp(), ln(), pwr(), sin(), sqrt(), tan()

OpenInsight’s RLIST functionality and performance have also been improved starting with the 10.0.7 release. A new version of RLIST (RLISTX), which optionally replaces and extends RLIST, is available to enable these enhancements. RLISTX merges the features of RLIST, SELECT_INTO, OLIST/RUN_REPORT, and RTI_XBAND. One obvious change is the ability to pass in multiple select statements to RLIST in a single call, @FM delimited. Using the Record Editor, or the Configuration Record option from the OI Console, you must create a CFG_RTI_RLIST record in SYSENV, with RLISTX in field 1. If this record doesn’t exist, or has anything other than RLISTX in field 1, then normal RLIST behavior (“RLIST 9”) and functionality will remain. (Note that the CFG_RTI_RLIST information is cached by your system; after changing this value, you should exit and re-enter OpenInsight).

The MultiValue BFS (MVBFS) connections for QM, D3 and U2 have been enhanced to submit multiple select lists to the “back end” host for bulk processing whenever possible. This enhancement can result in significant performance improvements when using an MVBFS connection. Note that these changes work in conjunction with the RLISTX changes discussed above; you must enable RLISTX and install a “plugin” stored procedure on the host system to access these changes. There is now a button on the MVBFS connection designer which will install this plugin (a program named RTI_MVBFS_SERVER_PLUGIN_U2, RTI_MVBFS_SERVER_PLUGIN_D3, or RTI_MVBFS_SERVER_PLUGIN_QM).

Starting with OpenInsight 10.0.4, “child” processes launched from OpenInsight can be configured so that they do not consume
additional license seats. In particular, CTO, AREV64, BRW, and O4W calls (using the engine server’s built-in web server)
made from a copy of OpenInsight will not count against the licensed count of users.

For example, a single user copy of OpenInsight can now run the IDE, a CTO session, and generate a BRW report at the same time.

Note that this enhancement requires both OpenInsight 10.0.4 (or above), and the Universal Driver 5.2 (or above).
OpenInsight 10.0.8 will work with the Universal Driver 5.1, but it will not exhibit these license enhancements until it is
“paired” with a UD 5.2.

To take advantage of this license enhancement for O4W and engine server tasks, users/developers must update their eserver.cfg file (either directly or through the Settings dialogs). In particular, any passwords that are currently explicitly embedded in the eserver.cfg can be replaced with an asterisk (“*”); this indicates that the specific connection should use the enhanced licensing. This also has the additional advantage of no longer requiring manual updates to the eserver.cfg file when passwords are changed for the applications or users defined in the connection string. (As an additional enhancement, the username can also be replaced with “*” if you wish to use the ‘default user’ created for an application).

For example, if your eserver.cfg previously contained the following lines:

WebServerConnection_console=SYSPROG,OICONSOLE,OICONSOLE,65,1,RUN_OECGI_REQUEST,,,1,,
SystemMonitor=RTI_OEMONITOR_CLEANUP,SYSPROG,SYSPROG,SYSPROG;RTI_OEMONITOR_INDEX,SYSPROG,SYSPROG,SYSPROG

They can now be replaced with the following lines:

WebServerConnection_console=SYSPROG,OICONSOLE,*,65,1,RUN_OECGI_REQUEST,,,1,,
SystemMonitor=RTI_OEMONITOR_CLEANUP,SYSPROG,*,*;RTI_OEMONITOR_INDEX,SYSPROG,*,*

One Evening = One Application


I was recently asked by someone looking at using OpenInsight for the first time, “How quickly can I really build a small system in OpenInsight 10?”.  Naturally, being a salesperson, the answer was “Very quickly and you’ll be surprised just how quickly.”

This evening I had the opportunity to put this to the test.

As many of my readers will know, I am some months into building a large system that I hope to take to market very soon.  This system uses authorisation keys to set (and update) the user count and the expiry date in the system.  It is nice feature in the application, but it is not overly clever.  However, I find myself having to manually create the authorisation keys from time to time and this was becoming tedious.

I therefore decided to build myself a small application in OpenInsight 10 to help me to generate the authorisation keys and then to keep a history of who has had keys, when, with how many users, etc.

Whilst I did not time this mini- project, all of the following has been achieved by a junior application developer (me) in one evening.  That includes defining the application, building the three data tables, the four forms and all of the popups, messages, etc.  It also involved writing two commuter modules to support the Customers and Key Generation forms.

As is usual for my systems, the application operates from a main MDI Frame window, as shown below.  Granted, I need to tidy a few things up (like the menus), but remember this is an example of what can be achieved in a few short hours and by a junior.

The MDI Frame is used to display all of the application’s windows and these are launched from the three buttons on the toolbar.  The fourth button being the Exit button, which closes down everything.  All of these buttons are operated by CLICK quick-events.  i.e. I did not have to write any code to get anything working in this form.  In fact, it does not even have a commuter module defined for the window.

You could say that the MDI Frame window is a NO CODE form, but that is a private joke which anyone that follows the Google Pick discussion forum will understand ;).

KeyGen-1

The next form is the Customers form, which enables me to capture some basic contact information for my customers.  At the bottom of the screen is a table which uses some symbolic fields, a relational data table and a relational index to display all of the authorisation key records that are linked to the Customer.  This enables me to see when  keys have been generated, the user count and the expiry date for that entry.  It will build into a history of the license over time.

Again, I needed to write very little code to operate this form.  The code is pretty much limited to a Changed and a Clear event to set the toolbar buttons from disabled to enabled (and vice versa), Click events for the Cut, Copy and Paste buttons and a Click event for the Email Address label.  So very little code and what code there is in the commuter module is very basic code.  To be honest, most of the code was pulled in from my commuter module template, which already had the code for the Cut, Copy and Paste buttons and to enable and disable the Save, Clear and Delete buttons accordingly.

KeyGen-3

The Customer ID label will, when clicked, display a standard record lookup window and when the Email Address label is clicked the user’s email client will launch and the system drops in the email address automatically.  Otherwise the buttons all drive the system and the combo boxes are all populated from the System Codes data table.

KeyGen-4The System Codes window is pretty straight forward with (not including the toolbar) only two key controls which use just three dictionary items (fields) in the database.

“Again, this is a no code form where I do not even have a commuter module defined.”

The combo box is populated using the Auto-fill feature in OpenInsight, which means that the pick list will always be up to date as new code categories are added.

The user then simply adds a new code category (COUNTIES in the example) and then in the table, they enter a MultiValued list of code and descriptions.   As soon as the record is saved, those new descriptions are available to the users in the Customer’s data entry form.

KeyGen-2

The last and most complex window is the Authorisation Key Generator window.

The form itself is not at all complicated and it was very easy to build, but the commuter module behind the form took some time for me to build.

The form uses my usual quick event to launch the Popup (record lookup window) and this in turn reads (displays) the record in the form.  A similar popup is used to select the Licensee’s record ID and to write that to the appropriate edit line.  When the Licensee’s ID is chosen the Licensee’s name is displayed.  This is a calculated field (a symbolic) which brings together the customer’s First Name and Last Name from the Customer’s data table.

KGImage-5The system has been designed to cater for 1 to 9,999 users.  A message will display if the user tries to enter 10,000 or more users.  Again, the message (as shown) is created without any code and it is called using only a few very short lines of code.  The code simply checks for the number of users and then it makes a call to display the saved message if the user count is over 9,999. 

The calendar button launches a standard OpenInsight 10 calendar, from which a date can be selected and this is written to the Expiry Date edit line.  The buttons on the toolbar are all Quick Events.

Once the User Count and Expiry Date fields have been completed, the Key button on the toolbar can be clicked and this will format the authorisation key using certain random  characters and formatted with hyphens.  The authorisation key is truly random, with a unique key being generated every time the key button is pressed, even when the user count and expiry date does not change.

Anyway, it is now getting late and I’ll leave the following items for tomorrow evening:

  1. I need to configure all of the menus.  The system is run by the buttons at the moment.
  2. I need to make sure that an expiry date is a date in the future.

It will then be completed and ready for use.  Not too much left to do then, a nice little authorisation key generation application done and a good evenings work.

All thanks to OpenInsight 10 and how easy the tool set makes it
to build systems like this 🙂

Elkie catches up with Mike


1P7A8552

Following our recent announcement of the release of OpenInsight 10.0.7, Elkie Holland from Prospectus IT Recruitment recently caught up with Mike Ruane to talk about this new release.

The new version includes many customer requested features and enhancements for both OpenInsight developers and MultiValue developers more widely.

You can read Elkie’s report of the catch up at https://www.prospectus.co.uk/blog/2019/09/catch-up-with-mike-ruane-and-all-things-revelation

 

 

 

Lots of data to capture in a single form? OpenInsight 10 has the prefect solution.


PropertyGrid1I occasionally have people ask me about user interface design from an end user’s point of view and mostly this is when a developer is tasked with capturing a very large amount of data, needing lots of controls, in one logical place.

Often, it is possible to break up the required data into bite sized chunks, or to categorise it somehow and then present their data controls as a smaller subset on two or more forms.  Sometimes, probably more often than not, it makes sense to break up the form using the tab control and display these subsets of data controls over multiple pages.  This is something that I have done a lot in my demo applications.

However, I am told that this is not always possible and I have seen data entry forms with hundreds of controls, split over countless tabs.  I recently heard of one OpenInsight based system where a control limit had been reached, forcing a rethink of how the data was to be presented to the end users.

Now, I am currently working on a ‘real world’ application that also demands that, on several of the data entry forms, I need to be able to display and capture hundreds of data fields.  For the form that I am currently working on, this means nearly 400 hundred data items and this translates to well over double that number of controls to be maintained on the form.  AND, I can find no logical way to split these controls over multiple forms 😦

A form with this number of controls means that I had a massive tab control and a form running over 20 or more pages.  From a developer’s point of view, this results in a very cumbersome form to manage and maintain at design time.  For example, how would I easily add in new data prompts without having to spend a large amount of time moving controls around to make the new items fit my already crowded forms?   Worse still, it resulted in a very difficult to navigate form for my users.  Yes, they could probably learn where everything is over time, but in the interests of providing my users with an intuitive display from day one and a far easier to navigate user interface, I had to find another method.

So, following a quick prompt from Carl, I took a look at the brand new Property Grid control in OpenInsight 10.  This is not yet data aware (and I’m not sure of any plans to make it data aware), so there is a code to be written behind the scenes for my use of the control, but it was definitely the perfect solution.

So what did I build to get over this large number of controls issue?

PropertyGrid2

As you will see in the data entry form above, I have managed to reduce the tab count to just 12 tabs.  Although this is still quite a lot, they make sense because most of these will be displaying related data from other data tables.  For example, a list of actions to be undertaken or that have been completed with dates, status and notes, or viewing details.  These will be largely edit tables, one on each tab.

The main tab reduction was achieved through the use of the Property Grid, displayed on the right of the form.  When the user is on the Summary tab (shortly to be renamed), the property grid maintains a few hundred property details that were originally split over numerous tabs.  This data is now displayed in a easily navigable, collapsible, categorised list, enabling the user to show and hide data as required.

When designing the Property Grid, the OpenInsight developer is presented with 29 pre-defined control options that are embedded in the new control.  Things like Dialog, Static and colour pickers, right through to combo boxes, file pickers and more.  The user’s choice is then displayed in the grid and it is pretty easy to them pick up those values and save them to the database.  It is also super quick and easy to add in new data items and to have them display under the correct category.

The Property Grid control is fully documented in the ‘OpenInsight 10 Presentation Server Reference Manual’, but writing data to a cell in the grid is just one line of code.  In the example below, valPropertyStatus contains the data to be written and “Property Status” is simply the name that you have defined in the Property Grid row when you built out the various rows.  It really is that easy, no messing around trying to work out in code which cell or row you are in, you simply use an ‘English’ name.

 Call Set_Property_Only ( CtrlEntID, "VALUE", valPropertyStatus, "Property Status" )

Now, as I might have mentioned earlier, the Property Grid is not yet data aware, so you will need to get these data changes and write them to the data record yourself.

However, I have taken a slightly different approach.  I am not a professional OpenInsight application developer, so I in no way suggest that this method is right and proper but it works for me.

As shown in the image below, I wanted to have collector windows for ‘each’ of the data items in the grid.  This enables me to provide my users with a consistent and easy to navigate solution.  It enables me to present my users with all manner of data controls in easily built and maintained collector (dialog) windows.  In the example below, when the user clicks on the Vendor cell (a button displays), the user is presented with a collector window with, not only the vendor’s name, but also their contact information.  This includes the email address and if the user clicks the blue text, OpenInsight will open up the user’s default email client and drop in the vendor’s email address.

PropertyGrid3

You will notice that the orange Record ID box displays the Record ID.  This will be made invisible for the beta, but it is displayed for development purposes at the moment.  This Record ID is passed to the collector window from the calling window and the record is automatically read and displayed for editing.  When the user has made their changes, the data is immediately written to the record.

When the data is saved and the collector window is closed, the Property Grid is updated to display the new value, or values.  In the case of a collector window with multiple data items, I have chosen the best piece of data to display.  In the example above, this is the Vendor’s name.  In some other instances, I have used three dots (. . .) to indicate that there is data to be viewed.  This solution is used when no single data value works.

A nice, easy and good looking solution.  

Now, those of you that are professional developers and observant, will have noticed a flaw in my design.  If I am passing in a record ID, what is to stop the user from saving a value from the Property Grid without a valid Property Record?  This could quickly result in useless data – property characteristic details without a property address and other meaningful data to readily identify the property,

This issue is addressed by simply checking for a valid record on file when the Property Grid is accessed. If there is no record yet saved to file or it does not meet my requirements of having a valid address, access to the Property Grid is blocked, a message is displayed and the message and collector window closes when the user clicks the message’s OK button.  i.e. the user cannot add data to the grid without a valid record being already saved to disk.

PropertyGrid4

Yes, the method that I am using is a little more complicated than just allowing the user to change the data in the Property Grid and have that data saved when the main save button is pressed.  And, I’ll probably allow that as an option further down the line.  However, I’m pretty pleased with this solution and it is definitely making it easier to develop and use my application.

Oh, and for those of you that think creating and maintaining many collector windows is long winded and time consuming, this is actually pretty quick and easy.  I simply:

  1. Use a template window – So, Open and Save As.
  2. Use a template Commuter Module which prompts me for certain bits of information which are dropped into the code automatically and then this is compiled and saved.
  3. Test run the window and add any additional event code that might be needed.

I am not saying that this is the right, recommended or perfect solution but if you would like to see this in more detail please comment below and I’ll look to put a video together with a look at the Property Grid working and the code used behind the forms.

 

How To Deploy OpenInsight 10 To Your Customers


How To Deploy OpenInsight 10 To Your Customers

didyouknowoi

Deployment in OpenInsight 10 is significantly different from prior versions.  Because system information is now encrypted on a per-system basis, you must tell the copy of OpenInsight 10 that you are changing the serial number (which is used in the encryption process) ‘before’ you change it.  Failure to do this will result in a system that cannot be accessed (until you put the original serial number back into the system).

The steps to making a deployment as you want are as follows:

  1. Request, and receive, the new authorisation code from Revelation Software with the new serial number and new number of users.
  2. In your “master” OpenInsight 10 system, in SYSPROG, go to the Settings/Users/Policy Setup menu choice in the IDE.
  3. In the policy configuration window, check the box “System Deployment Preparation” and press the OK button.
  4. In the Serial Number Entry dialog that appears, enter (and re-enter to verify) the new serial number you obtained from Revelation Software and press the OK button.
  5. Remove or change as appropriate the REVPARAM file from the cloned copy of OpenInsight before deployment.
  6. Clone your copy of OpenInsight.

On the client system, your steps will be as follows:

  1. Copy in the cloned copy of OpenInsight.
  2. Update the license information with the new authorisation code/serial number/number of users (see below).
  3. Run the clientsetup.exe routine found in your OpenInsight 10 folder.

At this point, your client’s copy of OpenInsight should be ready to run.

To update the license information, you have two choices.  In the cloned copy of OpenInsight, you can start up the system with your ‘original’ authentication (just by starting up OpenInsight normally), and then go to the Settings/Application Settings menu in the IDE, and choosing “License Renewal”.  You will be prompted to enter the new authorisation code, and (after confirming that the entered information is correct) you can save the new authorisation information, shut down OpenInsight, and restart OpenInsight.  You’ll find that the system is now running with the new serial number/number of users.

Alternatively, if you wish to ship out systems without your authorisation file in it, you can use the (non-GUI) routine to create the new authorisation file.  This step can be done on your ‘master’ copy of OpenInsight, before deployment to the client system.

Open up a DOS command prompt, and “cd” to your OpenInsight 10 folder.  Type in the following:

REVAUTH OI <authcode> CLIENT.LIC

Where <authcode> is replaced with the authentication code you received from Revelation Software (which I believe you can put in quotes).  So for example, you will type something like this:

REVAUTH OI "xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx" CLIENT.LIC

If there are any errors, revauth will respond with “Invalid code entered: <errcode>”. Otherwise, it will create a valid license file named CLIENT.LIC.  Take that CLIENT.LIC file, and copy it into your “cloned” system, RENAMING IT TO REVENGINE.LIC.  This will then become the license/authentication information for the “cloned” copy, and you should then be able to install that copy as outlined above.

Please remember to run the clientsetup.exe after copying in the cloned copy.

First published on www.revelation.com

New Create User Details function


RTI_CREATE_USER_DETAILS function for OpenInsight 10.0.5 and above.

didyouknowoi

OpenInsight 10 provides support for login policies including locking out of users after a definable number of unsuccessful attempts, password construction requirements, etc. Sensitive data for policy and user information is stored in AES encrypted records.  Policies and users are maintained via the OpenInsight 10 IDE.

OpenInsight 10.0.5 and above introduces a new function called RTI_CREATE_USER_DETAILS that allows developers the ability to create a new user or modify information about an existing user in the OpenInsight database.

Description: Creates a new user or modifies information about an existing user in the current database.

Note:  Only Level 1 (Administrator) and Level 2 (System Administrator) users can create users. Level 0 (User) users can only change their own, existing information.

Syntax: RTI_CREATE_USER_DETAILS(userID, currentPwd, userpassword, fullName, validValue, disabledFlag, disabledDate, disabledTime, resetFlag, userType, userLevel, o4wLevel, expirval, expirdate, errDetails)

Return: “1” if the create or edit succeeded
Value: “” or “0” if the create or edit failed, and additional details are returned in the errDetails parameter.

Parameters: The function has the following parameters.

ParameterDescriptionParameterDescription

Parameter Description
userID A user identifier. userID must begin with an alpha character, followed by any combination of characters, digits, and underscores and cannot include spaces.
currentPwd If enhanced authentication is enabled on this OpenInsight system, then a User-level user who wishes to change any user information must pass in the current password in this parameter. This allows the system to verify that they are authorised to make changes to this user information.
userpassword The new password for this user. If enhanced authentication is enabled, then the password must match the specified authentication policy. If legacy authentication is used instead, the password must be a string of characters, 6 to 20 characters in length, and – if not specified – the default is null, and a password is not required to access the database as this user.
fullName The full name of the user.
validValue This is a user-defined parameter that allows the developer to specify additional information that they would like returned if the user’s logged-in state is queried (for example, to implement additional permission levels and groups). By default, this value is “1”.
disabledFlag If enhanced authentication is enabled on this OpenInsight system, then if set (value is “1”), the user will be disabled; if it is reset (value is “0”), the user will no longer be disabled. If the user is disabled, pass in the additional disabledDate and disabledTime parameters.
disabledDate If enhanced authentication is enabled on this OpenInsight system, and the disabledFlag has been set, this parameter specifies the internal date that the user is disabled until.
disabledTime If enhanced authentication is enabled on this OpenInsight system, and the disabledFlag has been set, this parameter specifies the internal time that the user is disabled until.
resetFlag If this parameter is set (“1”), the user must reset their password at the next login.
userType If this user should only be allowed to access the OpenInsight desktop interface, specify “0” for this parameter. If this user should only be allowed to access OpenInsight via O4W, specify “1” for this parameter. If the user should be able to access both desktop and O4W instances, specify “2” for this parameter.
Userlevel If the user is defined as an OI user, or as both an OI and O4W user, specify the OI permissions level here. There are three levels of users. When the user is logged in, the value is stored in the system variable @ADMIN.

There is no default value for Userlevel. If you do not specify a value, execution fails, and an error is generated.

Value Description
0 User
1 Administrator
2 System Administrator
o4wLevel If the user is defined as an O4W user, or both an O4W and OI user, specify the O4W permissions level here. The valid values for O4W permission groups are customisable on a per-site basis.
expirval Expiration parameter for the password. Possible values are:
Value Description
0 Expires at next login
1 Never Expires (default)
2 Expires at the expiry date
expirdate If expirval = 2, the expiration date (passed as a standard output converted date in a format such as mm/dd/yyyy).  Only required if expirval = 2. Note that this value is only relevant when legacy authentication is used on the OpenInsight system; if enhanced authentication is enabled, expiration will be as per policy.
errDetails If any errors are encountered during the execution of this function, they are returned in this parameter.

 

OpenInsight 9.4 “Roll Up” Patch v5.1 released


OpenInsight 9.4

Revelation have recently released a brand new roll up patch for OpenInsight, taking the series to version 9.4.4.

This patch includes additional fixes to RTP16 (xlate), all the patches and fixes from the previous “Roll Up” patches, as well as:

  • An updated datatbl.dll and oinsight.exe to fix changes in how Windows displays forms.
  • A fixed DICT_MFS_BUILD to ensure that associated group names are included when a dictionary’s %FIELDS% record is rebuilt.
  • A fixed RTP16 (XLATE) to restore previous functionality when explicitly passing a null in parameter 5.
  • An enhancement to OIPI (VSPRINTER1) to improve performance.

After installing this patch, your system will report that it is running version 9.4.4.

This zip file contains an updated RevelationDotNetSetup.msi, RevelationDotNetSetup.exe, revjapi.dll, OESocketServer.jar, OInsight.exe and an OpenInsight RDK, for use in OpenInsight 9.4.0 systems.

This patch replaces the original “Roll Up” Patch v1 released on March 3, 2016, the second “Roll Up” Patch v2 released on March 8, 2016, the “Roll Up” Patch v3 released on June 13, 2017, and the “Roll Up” Patch v4 (and v4_1) released on January 5, 2018, and includes all the previous fixes for OpenInsight 9.4.

Works Members can download this patch from the Works Downloads section of our web site.

Increased OpenInsight 10 WORKS User Count


didyouknowoiThose of you that have been watching my initial OpenInsight 10 videos, will not have failed to notice the OI Management Console and the tools that this powerful feature brings to all OpenInsight 10 (OI10) Systems Administrators.

Not only does it expose some really useful information and statistics, as well as much easier remote configuration, but it makes administering a live system so much easier through the brand new Command Channel.  The guys at RevUS touched on this in their recent Introduction to the Features and Benefits of OpenInsight 10 Webinar and I show working it in my video which provides a Quick Overview of OI10.  Jump to around 12 minutes and you’ll see the Management Console running as an O4W application in the built in OI10 browser on screen.

Anyway, interest in the Management Console was high following the Webinar and a thread appeared on www.revelation.com with regards to some people having trouble running the Management Console and needing a 10 user O4W license to run it.  Whilst running it online is super useful and convenient because System Administrators can access the Management Console from anywhere in the world and at any time, some people might just want to run it locally from their desktop using their OI WORKS license.  This is how I ran the system in the videos.

Even in this local based setup, O4W and the Management Console consumes an additional license, or two – it’s the nature of O4W.  Now, I’ve sat in many a presentation for software where the vendor says “Hey, we have this amazing module, it’ll change your life and that of your users.  Ohh, but it’s going to cost you …”.  Heads quickly fall like a child being offered a big bag of colourful sweets, only for the parent demanding a week’s worth of chores to be completed before access is granted to the bag of sweets.

Revelation Software have once again shown its ongoing commitment
to its OI WORKS community.

It looked like Revelation Software were heading down this same route, but, true to form, Bill told me about an OI WORKS discussion forum posting from Bob Catalano over the weekend.  In the posting, Bob confirms that the Management Console will not function with the usual 2 user OI WORKS license and because of this a decision has been made to increase all existing 2 user WORKS licenses to a 3 user license.

This is brilliant news, it shows Revelations commitment to its highly valued OpenInsight WORKS community of professional application developers and it provides yet more value from the, already, invaluable WORKS subscription service/license.  However, those of you opting for the cheaper NUL based license for your developers will need to look at increasing your NUL license accordingly and in the normal license increase manner.

If you are an active WORKS subscriber looking to work with OI10, please log into WORKS and head over to the WORKS forum for further details on claiming your new OI10 authorisation key.

If you are an expired OI WORKS subscriber or wish to get onto OI WORKS to gain access to OpenInsight 10, please contact your local Revelation office and one of us will be more than pleased to discuss your needs.

 

New OpenInsight 10 YouTube Training Video Playlist


YouTubeOI10

Several of you have been chasing me about the OpenInsight 10 (OI10) training videos recently and the need for these was highlighted recently with the news that we have several non-OpenInsight MultiValue developers taking an interest in the tool set.

I have just finished producing the first three videos in the training series and I have published them to my new OI10 YouTube Channel and in a new playlist which will be added to as I get to finish more videos.

These first three videos are fairly light weight:

  1. The first touches on what OpenInsight is, where is came from and there is a quick overview of the OI10 development environment.  The overview is a reproduction of one of my earlier videos but it is included here for people who are new to OpenInsight and it is therefore conveniently placed in the Lesson playlist.
  2. The second video looks at installing the OI10 evaluation software and making some initial configuration changes ready for the training videos to be followed.
  3. The third video looks at how to create your first application and how to add an application level user into the system using the enhanced security.

I have also added a link to my earlier OpenInsight 9.x tutorial video playlist and which is located on a totally separate YouTube channel.

As usual, access to the video series is 100% free and I hope that existing and new OpenInsight developers and users will find the series of videos useful.

If you have not already, please be sure to subscribe to the channel to get notification of when additional videos are uploaded.  I expect this to be fairly frequently initially and then things will slow up as I have to learn more about the massive changes that have been delivered in OpenInsight 10.

As always, please comment below the videos to let me know that they are being watched and whether you find them useful or not.

An Introduction to the Features and Benefits of OpenInsight 10.


didyouknowoi

An Introduction to the Features and Benefits of OpenInsight 10

Thursday, June 7th, 2018
11:00 am PT / 2:00 pm ET / 7:00 pm BST

REGISTER NOW for this complimentary webcast.

As a reader and subscriber of this blog, you will not have failed to notice that in April  2018, Revelation Software proudly announced the long anticipated official release of OpenInsight Development Suite (OI) 10.0.  This ground breaking released has been completely re-engineered for 64-bit and there are a wealth of new features and benefits which make application development in OpenInsight easier and faster than ever.

Nearly every bit of code in the product has been rewritten, from the user’s interface, to the various reporting tools and the speed of the indexing routines.  Revelation Software have listened to their user base and delivered in this release.

If you are a WORKS subscriber, OpenInsight application developer, MultiValue application developer, or simply someone looking for an easier application development tool set – This is a FREE Webinar that you cannot afford to miss.

To just touch the surface, OpenInsight 10 provides the following new and/or improved components:

  • New IDE
    OpenInsight 10 delivers a brand new Integrated Development Environment (IDE) to developers.  It is visually similar to modern application development tools, it is intuitive and yet it is still designed for the MultiValue developer in mind.  Each of the product’s designers, for forms, tables, reports and all others are now contained into a single, cohesive and dynamic work space.
  • Arev64
    The next generation of the Advanced Revelation emulator, utilising the full power and capabilities of modern 64-bit architectures.  Yet again, Revelation have extended the life of their legacy DOS applications.
  • User and Data Security
    With increased concerns about security and privacy, including the current GDPR requirements, a number of enhancements and changes have been made to further   strengthen data security within OpenInsight and to provide system manager (DBA’s) with greater user management controls.
  • Management Console
    The OpenInsight Management Console is a powerful browser-based database management tool for system administrators.  It provides an overview of your system and the ability to send useful and timely messages to workstations.
  • Git Integration
    For small, medium and large development team, managing your code is a must and OpenInsight’s repository based environment is now tightly integrated to the Git   source code management system and thereby giving you access to one of the leading application development management tools for teams.
  • Universal Driver 5.1
  • This latest version of the ever popular Universal Driver supports 64-bit operating systems and Volume Snap Shot (VSS) capability.  Together, these technologies provide the highest levels of reliability and the facility to quickly recover if something should go bad.

In this webinar Mike, Bob and Bryan will provide an overview of these new features and
benefits of OpenInsight 10 and more.

REGISTER NOW for this complimentary webcast.

If you are unable to attend at this time, register today and attend the archived event at your convenience!