Wiki

Case Status
Log In

Wiki

 
Kappris for SysAdmins  Kappris Co-Operators
  
Page Collections
Attributes
Hierarchy
  • RSS Feed

Last modified on 31/03/2022 16:57 by User.

Tags:
cooperator, imanage, sos, liberate, practiceevolve

Kappris Co-Operators

Configuration and prerequisites

Proclaim

Proclaim Server Prerequisites:

The Proclaim server is required to have the following features:

  • Task Server active and running, where we can run the automated tasks.
  • Incoming Mail Directory Monitoring V2, it will check a designated folder to find any documents to upload.
  • SOAP API, it’s required to have the SOAP API installed so we can get the latest matters for the user. We will require the address of the SOAP API to be added to Kappris Configuration.
  • Incoming Mail Phrases, it will be necessary to create a 2 letter Incoming Mail Phrase with the ‘autoprocess’ check marked for every matter type that we like to use. The default value is ‘KU’.

Proclaim Client Requisites:

The client should provide us with the following information:

  • Proclaim User and Password, we will require a user and password to log into the Proclaim Server. The password needs to be encrypted with our Encryption Tool.
  • Incoming Mail Directory Monitoring v2 Watch folder path, we will need the full path of the folder that the IMDMv2 process is watching, so we can add our own documents to it.

Configuration:

  • Edit Config.ini adding the location of Kappris.ini
  • Edit Kappris.ini with the server (address of SOAP API), user, password, destination folder, destination path and csv file path detail

Check the server is correct by browsing to it and you should see the WSA Web Services page.

SOS

Prerequisites:

  • A script to create a csv file containing the last used matters
  • A script to pick up the finished document and add it to history

Configuration:

  • Edit Config.ini adding the location of Kappris.ini.
  • Edit Kappris.ini with the path to the csv file - the path expects %AppData% first.
  • Edit kappris.ini with the destination path for the final document

iManage10

iManage10 Server Prerequisites:

  • Kutana Kappris Spine iManage Application to be installed. Kutana Kappris Spine IManage Application.zip
  • Login to imanage.kutana.co.uk (substitute for client's server address) with an admin user. Click User - Control Centre - Applications and upload the zip file above.

Client configuration:

  • Make sure the Client ID and secret for the server application match the entries in KappConf.xml
  • Edit Config.ini adding the location of Kappris.ini
  • Edit Kappris.ini with the iManage server address 

Practice Evolve

Configuration

  • Edit Config.ini adding the location of Kappris.ini
  • Edit Kappris.ini with the server, VendorKey and UserKey details

TLS/SSL error - add these keys to the registry:

'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord
'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord

Liberate

Prerequisites:

  • A script to pick up the finished document and add it to history

Configuration:

  • Edit Config.ini adding the location of Kappris.ini
  • Edit Kappris.ini with the server, database and destination path

Kappris

Prerequisites:

  • Kappris version 2.5.2.18227 or above.
  • The SignSaveViaCooperator workflow installed and configured.
  • A Print Mode configured to use the above workflow.
  • Configuration of Kappris.ini settings file.

All cooperators configuration settings.