ProcessBook "Under the Hood"

Blog Post created by dhollebeek on Jan 27, 2017

Hi all!


If you've been following along with the PI ProcessBook news, you know that the latest version (2015 R2) uses .Net 4.  If you haven't been following along, now you know .  But, this won't be about .Net 4 specifically.  I recently gave a short presentation internally and there was one plot that I thought I would share so that you can see what's been happening with PI ProcessBook that isn't obvious just by looking at it.  I do apologize that the plot is somewhat vague (I did this intentionally when I created it for this blog because of security concerns).  Just trust me, there really are detailed statistics behind this to back this up .  As you can see we started updating the technology underlying PI ProcessBook in 2015 R2 and we have plans to continue to do so.  The last point is a rough guess of where the next release will be.  The release date and name haven't been finalized yet, but at least you can get some idea of how this will continue in the future.  So, why are we doing this?  The biggest benefit is security.  Windows security has advance considerably over the lifetime of PI ProcessBook, but is only used if the application is updated as well.  There are other advantages as well such as PI ProcessBook is faster and more stable on modern computers.  Going forward, security will continue to be one of the areas we will be focusing on with PI ProcessBook (allowing more control of VBA is next on the list).  So, without further ado, here's the pretty picture :