The Developers Blog just reached 50 000 views

Today we reached 50 000 views. There is an upgoing trend and the number of views continues to grow each month. Last month we had around 7 000 views. The audience is kind of narrow, it is a blog for Smart Office developers. That is people who are building Mashups, creating JScripts and developing Smart Office features with the Smart Office SDK. There might also be one or a few System Administrators who find some good articles here.

I hope you enjoy our examples and blog posts. It requires a lot of hard work and we welcome more bloggers from the User Experience team, here at Infor.

Infor is a product company and we love our product.

Karin & Peter

9 thoughts on “The Developers Blog just reached 50 000 views

  1. Daniel Henningsver

    Congratulations, It is nice to see the community is growing. I have a question, is there a public Smart Office SDK that can be used when developing script for Smart Office. Currently it is a bit complicated to try to understand the possibilities for scripting and the only scource of information is the blog like this.

    Reply
    1. karinpb Post author

      The Smart Office SDK is only available for partners and Infor Consultants. But the SDK is more for feature and mashup control development, or converters that you might use in Mashups. The SDK also contains an API documentation of all classes that you are allowed to use, which means that the JScript developers guide is a good place to get the class names and then you can check this API documentation. But this compiled html help is only delivered with the SDK. There is another “SDK” documentaion under the help menu in the Mashup Designer but the content there is a subset for Mashups and does not contain as much as the full set.

      I do recommend reading blogs but also to have a look at specific classes in the MForms.dll using a free decompiler like Jetbrains dotPeek. For example all arguments that you get in your script. Apart from that we have the JScript developers guide. Only what is officially documented is allowed to be used. Which means that you can do a lot more than we acctually support.

      You could contact support and ask for Lawson Smart Office SDK / SDK documentation. I’m not sure what they would say but it is worth a try.

      Reply
      1. Daniel Henningsver

        Thank you for you feedback. I will look into a compiler and might contact support for a try.

  2. Amit

    Hi,
    I am trying to write a test feature that it purpose is to show the company logo, depend on the company that currently used.
    I couldn’t find a way to inform my app when a company change occurs and I know that this is possible (the widget profile information does that).
    Can someone please help me how to figure it out?
    Thanks.

    Reply
    1. karinpb Post author

      Hi,
      I’m on vacation so I can’t really check the code. But check if the UserContext class in the mforms dll implement INotifyPropertyChanged. If it does subscribe to it.

      Reply
    2. karinpb Post author

      Hi Amit,
      Sorry for the late reply. I was on vacation. You need to get the M3 user context object and subscribe to the property changed event.
      You also must unsubscribe to that event if you for example attach to the context from you XAML code behind.

      var m3UserContext = ApplicationServices.UserContext.GetApplication("M3") as MForms.ApplicationUserContext;
      if (m3UserContext != null)
      {
      m3UserContext.PropertyChanged += OnPropertyChangedUserContext;
      }

      Then in the property changed you check what property has been changed. The UserContext below with constants are in MForms.UserContext.

      private void OnPropertyChangedUserContext(object sender, PropertyChangedEventArgs e)
      {
      if (e.PropertyName == UserContext.CURRENT_COMPANY_KEY || e.PropertyName == UserContext.CURRENT_DIVISION_KEY)
      {
      // When the current company or division is changed update what you need to update
      }
      }

      Don’t forget to unsubscribe to the event if this is from for example a XAML code behind (or something else that is not a singleton). If you fail to unregister you will leak memory.
      m3UserContext.PropertyChanged -= OnPropertyChangedUserContext;

      Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s