Here is a very interesting article on the productivity shift for Inhouse Lawyers. At Mosmar we’ve definitely noticed this trend “More regular communication with key colleagues” – both within our team and with clients.

The time we’re saving in commuting to the office and meetings is being put to good use – we’re able to turn around work faster, and we’re more apt to scheduling the quick ‘video’ check in to ensure projects stay on track. The latter helps keep project focus with the added benefit of building rapport. Sharing a smile or an isolation joke can bond a team.

A win win from our end – a surprise positive during these trying times.

Aakash Mehta, Demi Agraz and Pratik Mehta

Our legendary MatterSphere team attended VANTAGE APAC Regional Conference over 24-25 September at Sydney’s Hilton.  As Thomson Reuters product and implementation partners it is always good to meet clients face to face in an environment where we can demonstrate our latest and greatest customisations and product suites. It’s also a good opportunity for us to get feedback and learn from the ecosystem  of users, developers and other partners.

It was refreshing to confirm that MatterSphere is still going strong in the APAC region. Despite online rumours it was obvious from the sessions and conversations with Thomson Reuters team that there is a significant amount of investment going in to continued development of MatterSphere for the UK and APAC market.

Perhaps the most interesting topic of the two day conference was presented by Shine. Jodie Willey and Kelly Addison presented their innovation project, Claimify. We were proud to be in the room for this presentation as Mosmar was one of handful of partners who collaborated on this project. It was a good opportunity for us to see our hard work come to life and also see firsthand the feedback and commentary from other MatterSphere sites on the innovative way Shine developed the MatterSphere Client Portal and database to enable deep learning tools that give their clients and lawyers better insight into the potential outcome of their cases. It’s the first project of its kind globally and we were excited to have taken part in it.

Jodie Willey and Kelly Addison presenting Claimify

Vantage is always a special conference for us. It brings together like minded clients and partners who use the same tools to do very different things. It’s exciting to see the innovation that goes into the development of 3E MatterSphere in house at firms like Shine. We look forward to catching up with everyone again at the next conference!

Janders Dean makes up an important part of the legal technology and innovation ecosystem in Australia and overseas, and #JDHorizons is a date that most inhabitants of this ecosystem save in their calendar well  in advance year after year.

This was the second time we were invited to sponsor #JDHorizons in Sydney. We were blessed with two days of Spring in the middle of Winter with marvellous views of Sydney Harbour, accompanied by a carefully curated program of speakers.

What we liked about the Conference
  • Curated speakers
  • Promotion of diversity
  • Large number of female speakers
  • SheBreaksTheLaw launch
  • Cocktails at 10am doesn’t hurt anyone except your brain
  • Fantastic opportunity for up and coming university students
Why we’ll be back
  • We like the delegates – a great mix of people with common industry, innovation and a collaborative mindset
  • It’s fun and relaxed
  • The topics are relevant, not just to Delegates but to Sponsors too
  • The values of the conference align with outs (diversity, inclusion, wellbeing)

by Nissy Abraham, Developer, MOSMAR

The previous versions of iManage up to 9.x provided us with the ability to add dll references for iManage which enabled us to customise word in VBA to use iManage functionalities. We could capture iManage events in Word VBA using the corresponding references.  But this is not the case in Work 10, where there is no possibility to get those Worksite events and properties in VBA unless through the plugins and RESTAPI’s.

The iManage Work extensibility framework enables you to create .NET plugins for iManage Work 10 for Office.  Using these plugins, you can extend and customize the functionality of the iManage Work 10 for Office add-in.

iManage Work 10 for Office plugins are .NET assemblies loaded by the iManage Work 10 for Office add-in to extend and customise its functionality.  The plugins are downloaded automatically from the Work 10 application Server for each distribution. They can catch the events when an action is performed on the application or a form is about to load, modify the document metadata, retrieve the Office document object, and so on.

Creating a Sample Plugin for Microsoft Word

Sample: Hello World

This plugin displays a “Hello World” message whenever Microsoft Word starts.

  1. Install iManage Work 10 for Office (version 10.0.1 or later).
  2. In Microsoft Visual Studio, create a new Visual C# project with unique Class Library (.NET Framework) namespace, for example,
  3. Add references to iManage Work 10 for Office libraries iwto.dll and IWInterfaces.dl. These DLLs are available in the install directory of iManage Work 10 for Office.
  4. Add a reference to System.Windows.Form under Work10OfficePlugin by right-clicking
    1. References-> Add Reference ->Assemblies ->Framework ->select System.Windows.Forms.
  5. Rename the default C# file cs to HelloWorld.cs
  6. Create a .NET class for the plugin in cs, for example, WordPlugin1. This class must derive from iManage.Work.Tools.PlugInBase

Include the following in the plugin host event in the Initialize method.

HelloWorld.cs

 using System;

using iManage.Work.Tools;

namespace Work10OfficePlugins

{

public class WordPlugin1 : PlugInBase

{

public override bool Initialize(IPlugInHost host)

{

PlugInHost = host;

PlugInId = “myId”;

host.Startup += this.onStartup;

return true;

}

private void onStartup(object sender, EventArgs args)

{

System.Windows.Forms.MessageBox.Show(“Hello World!”);

}

}

}

Sideload the plugin in the Development environment:

  1. Create a resource file by right-clicking the project txt by right-clicking the project Work10OfficePlugins-> Add -> New Item -> Text File -> Add.
  2. Specify the MAC address of the development machine. Up to 20 MAC addresses can be provided in this config file.
  3. Right-click sideload_config.txt and select ->Properties -> Build Action -> Embedded Resource

sideload_config.txt

{

data: {

“macaddresses” : [ “00-0C-29-D4-BD-92”, “C1-12-83-07-3D-4C” ]

}

}

 

  1. Digitally sign the assembly:
  2. Right click the project Work10OfficePlugins -> Properties -> Signing -> Sign the assembly ->. Choose a strong name key file ->  New
  3. Add a Key file name of your choice, for example, plugin
  4. Protect my key file with a password
  5. Enter a password and select OK
  6. Build the project by right-clicking the Work10OfficePlugins project and selecting Build. Ensure that there are no errors in the build.
  7. Navigate to the project directory where the compiled assembly Work10OfficePlugins.dll is.
  8. Copy Work10OfficePlugins.dll to %localappdata%/iManage/Work/plug_ins.If the plug_ins directory is not available, create it and then copy the assembly into it.
  9. Register the plugin:
  10. Add the wplugins.manifest file by right-clicking Work10OfficePlugins and selecting Add -> New Item-> Application Manifest File -> Add
  11. Add the following assembly details in the wplugins.manifest file

 wplugins.manifest

<?xml version=”1.0″ encoding=”utf-8″ ?>

<configuration>

<word>

<entrypoints>

<entrypoint class=”Work10OfficePlugins.WordPlugin1″ resource=”

Work10OfficePlugins.sideload_config.txt”>

<assemblyIdentity name=”Work10OfficePlugins” version=”1.0.0.0″

publicKeyToken=”” language=”neutral” processorArchitecture=”msil” />

<provider name=”iManage”>iManage Office Plug In #1</provider>

</entrypoint>

</entrypoints>

</word>

</configuration>

  1. Copy the file to wplugins.manifest %localappdata%/iManage/Work/plug_ins.
  2. Start Microsoft Word. The “Hello World ” message is displayed.

Deploying the plugins

In the development environment, plugins are loaded to iManage Work Server using a sideloading mechanism as shown in the above example. Sideloaded plugins are authorized to run on up to twenty computers, identified by the MAC addresses of their network cards

In the production environment, the plugins can be registered and uploaded to iManage Work Server by the administrator using REST APIs or iManage Control Center

Using iManage Control Center

iManage Control Center (iCC) enables the administrators to upload iManage Work for Office plugins to iManage Work Server.

The developer creates a zip file which contains the plugin assembly files and manifest file and sends it to the administrator. Using iCC application, the administrator defines security settings on the plugin, and uploads it to iManage Work Server.

Creating Manifest File

You need to provide the information about your Office plugin to iManage Work server in file manifest.yaml. Identify a unique ID for your plugin and create the following manifest file in the YAML format as

manifest.yaml

# Information about Office plugin

id:           UniqueIDForMyProject

name:         Sample Office plugin

publisher:    XYZ Inc.

version:      ‘1’

# Name of the extensions

desktop_extensions:

– iwtoTestPlugIn.WordPlugin

– iwtoTestPlugIn.ExcelPlugIn

– iwtoTestPlugIn.PowerPointPlugIn

– iwtoTestPlugIn.OutlookPlugI

 

iManage Work REST APIs

The iManage Work REST APIs enable users to perform operations such as viewing documents, browsing workspaces, and searching for documents on the iManage Work server through the HTTP protocol. Several operations that are performed through the iManage Desktop client applications can be performed and/or automated using iManage Work REST APIs.

More information regarding Work 10 upgrade is available from

https://imanage.com/support

 

Need Help?

Please get in touch with MOSMAR should you need any help with your Work 10 upgrade.

We have years of experience with this product and know the intricate details of how to go about your upgrade.

We are very proud to be sponsoring ALTACon today.  Our very own Chris Painter will be presenting his member story which promises to be very entertaining and have you journeying back to the 80s with him #backtothefuture #martymcfly.

Please drop by our booth to say hi to Wendy Dias and Chris and discuss all things document drafting.

https://www.altacon.com.au

It’s nearly that time of year again for the Thomson Reuters Elite VANTAGE conference.  Held on 10-11 October in Sydney, MOSMAR are again silver sponsors and promise to captivate you all at our session on MatterSphere workflows. As always, we will provide a sugar hit to keep you awake and enthralled.

There is always much to learn at VANTAGE while having a great catchup with friends and colleagues in the industry.

Be sure to register, and see you there!

http://www.elite.com/exchange/vantage/auc17/regional-conference/

Have you ever tried to open a .CHM file in Windows, and it shows the index but no content? Not exactly HELPful. It had me stumped when checking out the NetDocuments ndOffice extensibility documentation.

Well it turns out to be such a simple fix. Right click on the .CHM file, select Properties, then select Unblock.

Too easy.

We get a lot of queries about Office 365, and about whether a law firm can use the online version instead of the local applications.

It’s an interesting question, and a very interesting answer.

The first thing to be aware of is the online version of Word is very limited in what it can do. So as long as your needs for editing are basic, then the answer is “possibly”.

A deal breaker for legal is often the fact that the online version has limited support for track changes. If you have a document with track changes turned on already, then yes you can edit it online and your changes will be tracked – but the kicker is you won’t see the tracked changes online. You need to open the document on the desktop version to see your tracked changes. Also, there is no way to turn track changes on or off with the online version, so you need to do that in the desktop version of Word first.

Another commonly used feature in legal documents are cross references. Well you can forget about them in the online version.

We also won’t mention that you can’t insert or update a table of contents, you can’t add or edit styles, or you can’t add shapes, textboxes or WordArt.

There is also only limited support for content controls. The online version only supports rich text content controls – so you can forget about things like date controls and dropdowns.

Law firms tend to have a lot of addins and customisations, most of which are also not supported in the online version.  So forget about all those macros and ribbon customisations your firm uses on a daily basis  – they won’t be available. Most commercial addins are either COM or VSTO addins – which do not work online as they rely heavily on the operating system and the .Net framework so will not be happy in the confines of a browser.

Speaking of addins, that usually includes your document management system. You’ll find most will require the desktop version of Word.

The online version of the Office apps have a long way to go to even get close to the desktop versions. They may be a handy tool to get you across the line with a few basic edits especially when you’re stuck with only your phone, iPad or browser. But I don’t think you’ll be doing any of the real heavy lifting online any time soon.

Hopefully that answers the question for now.

I’ve been having an extremely strange issue with a custom application. Basically the application is a form that displays to the user so they can select some options relating to how they want to print a document in Word. The form then goes off and does a few things with the printer driver and prints the document as required.

For some strange reason the form started playing up recently, and users were reporting that it was locking up sometimes, and the only way you could close it was to end the WinWord process in Task Manager which is a little drastic!

With a bit of debugging (and luckily being able to replicate the issue) I found the problem code was calling the DocumentPropertiesA function from winspool.drv. This was the part of the code that was updating the printer driver with the new settings. All of a sudden the call was not returning in some instances, but in a strange twist execution was returned to the form. No exception was returned. I enabled all the controls on the form to test further, and it turns out the form was indeed active again, and the buttons would work, but you could not close the form.

A bit of research reveals you cannot close a form if there is another event still running. So I guess the code running on the OK button event was considered to be still running.

If I clicked on the OK button again, the same code would run, but at the same line of troublesome code would actually return an AccessViolationException error, and you could not continue the code.

So a bit more research and yes, AccessViolationException is bad, and your code should stop.

But here’s where it gets interesting. In versions of .Net 3.5 and earlier, an AccessViolationException would get passed back to the CLR and you could trap it. As of version 4 it does not. Well thanks for that Microsoft. You can read all about it here. That was like trying to find a needle in a haystack.

Turns out the fix is pretty simple. In the class that was running, I added the following imports statement

Imports System.Runtime.ExceptionServices

Then on the actual sub that was running, I added the following attribute

<HandleProcessCorruptedStateExceptions()>
Public Sub Update()

And voila, the TRY CATCH around the problem line picks up the exception.

I can now catch the problem. Turns out it’s not fatal in this case, and the code can keep running, and even more strangely, it works. I suspect there is still another problem that needs a little more investigation, but I’m now back to a print dialog form that appears to work the same as before which no longer locks up. So happy users, and happy developer.

If you feel like reading more on exceptions, then here’s a little more light reading that you may find interesting, I know I did. http://msdn.microsoft.com/en-us/magazine/dd419661.aspx#id0070035

© Copyright - Mosmar