Infor Smart Office 10.1 is GA

Smart Office, the Infor product with the best looking implementation of the new SoHo design was released in May. GA date for Lawson applications was the 16: th of May and GA date for M3 was the 23: th. In Stockholm we celebrated the new major release of M3, 13.1 with cake and a mini Inforum with sessions.

So what’s new in 10.1?

login

First of all it’s the new SoHo design! I know there will be lots of discussions about this design just as we had with the jade green when we selected the canvas background for Smart Client. The new design is modern and clean and I like it.

appearance

 

Canvas

Before I’ll give you a highlight from the release notes I would like to clarify a few things about 10.1 and 10.0.5 and give you some information on coming service packs / fix packs.

1. There is no upgrade path to 10.1 from 10.0.5. 10.1 is a new install.

There is no upgrade path from previous versions. Migration support will be added in 10.0.5.2 and 10.1.1 so I would recommend you to wait until those versions are delivered before installing 10.1 in a production environment unless you are OK with a new install. There are always files/data that you can manually move if you as an administrator has a lot of knowledge about the different data that we store on the server, but for example user files such as settings will be lost.

2. 10.1 runs on .Net 4.5

This means that you cannot install 10.1 on Windows XP (or equivalent). For those customers that still have clients on XP we recommend 10.0.5.2. Note that this version does not have as much new functionality as 10.1, but we have pushed down some enhancements because we expect that version to be around for at least as long as Microsoft has extended support for Windows XP. But it is not the same as 10.1 so for all the news you need to be on 10.1.

3. 10.1 is a 32-bit installation.

We have changed to only building only 32 bit installations. If you develop features and use 3rd party components you need to verify that they still work. If you have had issues with web plugins that requires 32 bits you will be happy for this change.

4. Support for SQL server

One of the changes we did for 10.1 was to change the database design so that we can run on MS SQL server and not only the H2 database. The data we have is still mostly file based but the files are stored in that database and in the coming service pack 10.1.1 we will move some of the remaining files (like the profile.xml) to the database as well.

Note! We tested this on a specific version of the GDBC application in the grid, as it turns out version 2.0.5 has an issue so you cannot connect to an SQL server so you would need to get a fix on GDBC 2.0.5 before installing on an SQL server. Unless you run grid version 10.1.9.6 and GDBC 2.0.3, because that version has been verified. So watch out for the correction on the grid extensions /GDBC component.

5. Support for the GRID 10.1.11.0 and 11.1.11.0 and LCM 10.

For M3 13.1 we support LCM 10. We also support the new grid version but we found out that upgrade via LCM does not work in the released version so don’t update Smart Office to 10.1.1 until you know that you have applied a fix for the grid if you are on grid 10.1.11.0 (The fix is available via CCSS, with the ID: Lawson_Grid_10.1.11.0_2.)

5. Don’t install 10.1 on a grid that already has Smart Office
Even though it might be possible to select and install 10.1 on a grid that already has Smart Office (10.0.5) this is not supported and will lead to very strange results. There can only be one Smart Office per Grid.

All applications

  • Support for SoHo Design with the possibility to choose theme accent color
  • Added support for MS SQL server
  • Added support for Atom feeds in News reader widget
  • Added support (controlled via a setting) for pushing mashup files to the server without using LCM.

M3

  • Added support for a user to import/export excel templates from within the Templates Manager
  • Support for bookmark parameters from Mashup
  • Field help display in modal windows and generic positioning fields
  • Addition of dropdown menu to positioning fields in B-panel
  • Support for check boxes in lists that have editable columns
  • Mashups are now included in the M3 Transactions menu

Lawson Applications

  • A new File Transfer Wizard is available in the Navigator under Lawson Applications -> Other. Note: for a Windows FTP server, the directory list output format must be set to Unix style.
  • An API Builder utility is available to aid scripting and is available either from the Help menu of the Script Tool or in the Navigator under Lawson Applications -> Other.
  • Most list boxes which present a list of data field names now default to database definition order (typically the most used fields are first) with an option to sort on field name.
  • New user setting (on Advanced tab) to highlight key and required fields with red border when empty.
  • A report navigation button has been added to the Report Viewer to easily move to the Parameters page.
  • Multiple List View visualizations. Previously you could only create one Chart Visualization per List View screen. Now multiple Chart and Related Info visualizations are possible.

What does this new style mean for me as a developers?

We will probably write more posts on this topic but what you need to do is test your applications and mashups in the new style to see how they look. If you have keept to standard you should be more or less fine. But there is a line here between 10.0.5 and this new version becuase in 10.1 there are a bunch of new classes and stuff that you will start to use and those buttons etc will not be available in 10.0.5. There is also no way to get margins exactly right in both versions. But I have so far never seen an application or Mashup (developed outside or our team) where I couldn’t spot an issue with incorrect margins or alignment.

For mashups there is a compability resource dictionary that you can add to your mashup if you want the old implicit margins. We probably need another posts just on Mashups, and then another on SDK applications. The goal was that as much as possible should just look more or less the same, but you need to verify that by testing your application in the new version.

Becuase of this style change there are considerations you need to do in your development when developing for multiple versions of Smart Office. You can still develop for 10.0.5 and previous version and install on 10.1 but you cannot reference image resources contained in Smart Office or hard code brushes/colors.

Other information

The S3 Tech blog has a video about the 10.1 and they also have some information from the Inforum sessions.

2 thoughts on “Infor Smart Office 10.1 is GA

  1. Jimmy Ehrnström

    Is there, or will there be, a new version of the SDK for the 10.1.x versions of SmartOffice?

    I’ve been working with the SDK for the 10.0.5 version and successfully implemented a few different features. After packing them as apps I have often been able to run them under 10.1. But today I ran into problems with a custom built mashup control that threw an error when being added to a mashup under 10.1. It had previously worked fine in 10.0.5. The error was: ‘Control must be a FrameworkElement’, or something simliar. Could it perhaps be a .NET framework difference?

    My Visual Studio is currently linked to our 10.0.5 SmartOffice using the necessary registry keys from your guide. I tried to relink it to our 10.1 environment but got a ‘Communcation failed’ error.
    I suspect I should be using a new version of the SDK but haven’t found any information about if this is available?
    And finally, thank you for a great blog!

    1. norpe

      New SDK builds are usually made available when a new Smart Office version is GA, or shortly thereafter. There should be SDK downloads available for 10.1.x and now 10.2.x as well.

      The registry keys are different for 10.0.5.x and 10.1.x and later. This is documented in the SDK documentation and there are also registry files that contains the correct registry paths.

      Regarding the error with the Mashup we would need some more information. I don’t think it is an issue with .NET versions but there could be something that has changed in Smart Office or one of the features in Smart Office.

Comments are closed.