We are excited to have our 3E MatterSphere products and services listed in the new Thomson Reuters Marketplace.

This Marketplace provides an easy way for TR customers globally to find accredited service providers (like us) and seamlessly integrated products (like ours).

Artificial Lawyer published an article on how this new Marketplace will operate.

The beta version of the Marketplace is available here.

Stay tuned for further offerings from MOSMAR appearing in this online Portal.

We are so excited to announce our partnership with Templafy. Read the full Press Release here.

Templafy is a global market leader in template management and document automation. It has sold over 3 million licences worldwide, and includes KPMG, IKEA and Pandora in it’s client base. The Templafy cloud based solution provides seamless distribution and application of branded material and documents to it’s enterprise customers.

Our passion at Mosmar has always been to help our clients implement user friendly and efficient systems that ultimately save them time and money. In teaming up with Templafy, we can offer our clients complex document automation with seamless branding, secure integration and distribution.

Helping leading brands in the legal sector to implement efficient and user-friendly solutions that save time and money is our top priority at Mosmar,” said CEO of Mosmar, Rebecca Painter. “Partnering with Templafy marks the next step on our path to providing our customers with the broadest and best possible product experience.” 

Our DocAssist automation solution provides the best in legal process automation, allowing lawyers to work the way they do when drafting documents. DocAssist as well as a number of our solutions and services, integrate perfectly with Templafy via it’s sophisticated and secure cloud based distribution model.

About Templafy 

Templafy helps many of the largest companies in the world drive workforce alignment, reduce their liability and increase their productivity through the market leading document creation and document automation platform. 

Founded in Copenhagen, Denmark in 2014, Templafy’s team leveraged more than 15 years of experience in template management and document automation to develop an enterprise cloud service solution, which is now a global market leader within its category, validated by blue-chip enterprise customers on every continent. 

For more information on Templafy’s product and company, visit www.templafy.com, or follow us on LinkedIn: www.linkedin.com/company/templafy/ or Twitter: @templafy 

I’ll be honest – the 3E MatterSphere Client Portal isn’t the prettiest face straight out of the box.

But that’s not what you’re buying – the value is in the real-time and secure connection to the powerhouse of data that is your MatterSphere repository.

Here are some before and after ‘glamour’ shots of what we (and you!) can do with the Client Portal.

Want more info? Get us a shout – info@mosmar.com.au

3E MatterSphere version 9 is here.  As a certified 3E MatterSphere partner, Mosmar was fortunate enough to be included in the pilot program, so we had an early look at this new release.

Here are our key takeaways:

1. Navigation

In V9, this is more accentuated from a visual aspect, providing breadcrumb navigation from a consistent toolbar.

Improved navigation is a big theme in this release.  Navigation hasn’t been terrible in MS in the past, actually I feel it’s one of the better features.  Forward/back buttons like a browser, enabled users to remain the same window and drill through from a command centre view into clients, then down into matters.

2. Visuals

Upgrading from 6.3 to 7, we all experienced the ‘white wash’ and the loss of the beloved icons.  V9 brings iconography back, but in a stylish way, not to the overused degree of 6.3. 

The Visual indicators are also help with navigation so it’s more obvious which 3E MatterSphere object you’re looking at.  This is really important given that the same feature (such as search lists) are used across multiple levels – be it client, matter, associate etc. Previously it was easy to get lost in the interface, and accidentally exit out of a screen you wanted to be in.

Here’s another visual biggie – screen scaling is fixed! For those that dock and undock laptops, you likely would have experienced the controls that suddenly disappear – not cool. Problem now solved!

And for those that find the wizards that pop up, on top of another wizard, on top of another wizard, on top of (ok you get the point) – these multi layered wizards have gone with the Dodo.

3. Dashboards

3E MatterSphere was always flexible via it’s Search List function, providing visibility of data (any data – whether in 3E MatterSphere or another database) at any level of the 3E MatterSphere object mode (client, matter, associate, contact etc). 

Dashboards take this concept further by grouping related information together on the one screen.

Think – all custom data relating to a Client available on the one dashboard – matters, tasks, appointments, contacts, key dates, financial information, KPIs, SLAs, XYZs (ok I made the last one up, but you catch my drift).

4. Elastic Search

Elastic search arrived in an earlier version, but v9 brings access to it via the Microsoft Office ribbons. 

Natural language searching makes it super easy to find what you’re after, and it searches across everything 3E MatterSphere knows about.  Pretty cool I must say.  Navigation is improved (see point 1 above), and ironically perhaps not so important now with elastic search so easily accessible.

Summary

These are just the primary changes in this release, there are other more subtle changes that might really tickle your fancy. Or solve a bugbear that has annoyed you for years.

As fans of 3E MatterSphere, we are pleased to see focus being given to an interface which is used heavily by so many legal professionals.

However, we must give our prize to ITEM 3 above – Dashboards. 3E MatterSphere stores a comprehensive amount of information, and being infinitely extensible (which we LOVE), means some sites have access to an invaluable bank of collected information.

Leveraging that information and presenting it (pivoting it even) via a dashboard for a partner/supervisor/manager to oversee – invaluable in our opinion.

Want to know more?

Give us a shout – info@mosmar.com.au

Is this you? A documents needs to be drafted and you’re pretty sure you created a similar document recently for another case. Surely it’ll be faster to create that new document based on that previous one….right?

Many professionals have faced this dilemma at some point in their career – the temptation of the Save As button. You tell yourself you’ll carefully check the data, you’ll diligently proofread and any residual information from the previous case will be eradicated. Until …. the moment when it isn’t. 

The most common and critical mistakes made are:

  1. Incorrect Party/Contact details
  2. Key dates
  3. Inappropriate clauses

This article (ironically) by the Legal Practitioners’ Liability Committee nails the risks. “Previous matter documents are not precedents”, “Every matter is different and no matter how good your precedent, you need to proofread the document.” And the holy grail of mistakes – “Unfortunately, the practitioner failed to replace the names of the parties in the copied agreement with the new parties”. Ouch. 

One of the LPLC tips states it simply – “do not copy over documents from other files”

Document automation vendors (like myself) know the temptation is hard to resist, despite a firm’s best intentions, automation tools and policies. So we work on ways to ensure the Save As journey is as safe as possible. 

Mosmar’s DocAssist, and TR’s 3E MatterSphere are two products we know intimately and resolve the Save As dilemma in their own ways.

DocAssist – how’s it work?

After “Saving As” to a new iManage workspace, DocAssist will automatically pick up the new matter number and apply it to the document. 

All content controls containing the previous matter data will be cleared, and data applicable to the new matter will be loaded. Such content controls include:

  • Party/Contact lookups
  • Key Dates
  • Financial data
  • Text controls
  • Clause controls

MatterSphere – how’s it work?

After “Saving As” to a new iManage workspace or MatterSphere folder, the user is prompted to “Refresh the data”. 

All fields will be refreshed, loading all the information from the new MatterSphere matter.

What’s the benefit?

Content specific to the document itself is retained, so doesn’t have to be retyped into a new document

  • Scenario: A subpoena needs to be drafted for similar information (the core content of the document), but the parties need to be changed (the merging information via the automation tool).

Naturally the risk is reduced, as the sensitive data from the previous matter is removed and current information from the new matter is introduced.

Does it actually work in practice?

This data “merging” process is only as good as the data being captured. If you’re not storing critical contact data and key dates in a database but instead typing manually into documents, no automation tool is going to save you. 

It may seem like the fastest way to create a document, but in the long run it will burn. Both from inefficiency in creating future documents, and from the Save As risk (see above). 

What to know more? 

We have a whole raft of horror stories we could share. Or if you’d like to talk to us about making your documenting journey not a scary one, get in touch

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.

© Copyright - Mosmar