Matriks Doc 3 Document Management Installation Guide

Transcription

1 Matriks Doc 3 Management Installation Guide MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON ID: NA-4.00-MATDOC-3.24-English - v.1.01 Disclaimer: This material is for informational purposes only. Matriks A/S disclaims all warranties and conditions with regard to use of the material for other purposes. Matriks A/S shall not, at any time, be liable for any special, direct, indirect or consequential damages, whether in an action of contract, negligence or other action arising out of or in connection with the use or performance of the material. Nothing herein should be construed as constituting any kind of warranty. The example companies, organizations, products, domain names, addresses, logos, people and events depicted herein are fictitious. No association with any real company, organization, product, domain name, address, logo, person, or event is intended or should be inferred. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Copyright Notice: Copyright 2005 Matriks A/S, Denmark. All rights reserved. Trademark Notice: Microsoft, Navision, are either registered trademarks or trademarks of Microsoft Corporation or Microsoft Business Solutions ApS or their affiliates in the United States and/or other countries.

2 Contents This guide will outline the steps necessary to install, configure, uninstall and optionally manual implement the Matriks Doc software. The guide is divided into the following topics: Matriks Doc Configuration...3 Prerequisites... 3 Installing... 3 Step 1: Backup objects... 3 Step 2: Get Matriks Doc files... 3 Option 1: Using the Matriks Doc CD... 3 Option 2: Accessing the Internet... 4 Step 3: Import Matriks Doc objects... 4 Step 4: Install Matriks Doc help files... 4 Configuration... 5 Setting up Matriks Doc... 5 Setting up Security... 5 Role: MD-SETUP... 5 Role: MD-USE... 5 Uninstalling... 6 Step 1: Restore Navision objects... 6 Step 2: Remove basic objects... 6 Step 3: Remove the Matriks Doc security roles... 6 Step 4: Remove Matriks Doc help files... 6 Matriks Doc Technical Notes...7 Footprint... 7 Basic objects... 7 Interface objects... 8 Modifications...11 Normal Forms...11 Special Forms...14 Codeunits...15 MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 2/17

3 Matriks Doc Configuration Matriks Doc Configuration The Matriks Doc document management product consists of a range of Navision database objects that are installed, configured or uninstalled with the Navision client. In order to perform these tasks successfully, Matriks Doc requires that the Navision client is properly installed and connected to a valid Navision Database. Prerequisites Matriks Doc 3 files Navision 4 Office 2000, Office XP or Office 2003 Installing The installation procedure is divided into the following steps: 1. Backup Navision objects for uninstall purposes 2. Get the Matriks Doc files 3. Import the Matriks Doc objects 4. Install the Matriks Doc help files Step 1: Backup objects In order to be able to uninstall the Matriks Doc software it is necessary to backup the Navision objects before installing the Matriks Doc objects. Please perform the following tasks: Open the Navision client and connect to/open the Navision database Open the Object Designer (Tool->Object Designer) Click on All button in the designer menu Select All objects (CTRL + A) Select Export Objects in file menu (File->Export) Export objects to a before_md3.fob file Keep the before_md3.fob in a safe place Step 2: Get Matriks Doc files In order to retrieve the Matriks Doc software you need a Matriks Doc CD or access to the internet. The internet access download option is primarily intended for MBS professionals and will require a partner login. The CD option is recommended for all other users. Option 1: Using the Matriks Doc CD Insert the Matriks Doc product CD Get the help files from the CD menu. Click on Navision Objects in the CD menu. Get the basic objects FOB file from the CD menu. Get the proper interface objects FOB file from the CD menu. Have these files ready for step 3 MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 3/17

4 Matriks Doc Configuration Option 2: Accessing the Internet Go to Click on Products in the left menu bar Click on Matriks Doc 3 in the left menu bar Click on Download in the left menu bar Enter your Partner password and click on Login Select the Navision version Download and unzip the basic objects FOB file that match the Navision executables Download and unzip the interface objects FOB file that match the Navision version Download and unzip the help files that matches your language Have these files ready for step 3 Step 3: Import Matriks Doc objects Open the Navision client and connect to/open the Navision database Open the Object Designer (Tool->Object Designer) Select Import Objects from the file menu (File->Import) Find and select the basic objects FOB file Choose Yes to import all objects (No conflicts should be found!) Select Import Objects from the file menu (File->Import) Find and select the interface objects FOB file Choose Yes to import all objects (No conflicts should be found!) Select Codeunit in the object designer Find and mark all 60089xx codeunits, EXCEPT for codeunits that refers to Office versions not installed on machine that will do the compile. Compile all marked codeunits (Tools->Compile) Step 4: Install Matriks Doc help files Close the Navision Client Go to the Navision client installation folder Copy the 2 help files (addin_a.chm, addin_a.hh) to: o folder ENU if United States o folder ENG if United Kingdom o folder ENA if Australia Open the Navision client and connect to/open the Navision database MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 4/17

5 Matriks Doc Configuration Configuration Setting up Matriks Doc Before you can use Matriks Doc you must assign a number series. Please perform the following tasks: Refresh the Navigation Pane to see the new s Menu Click on the s Menu Select Setup-> Setup Select the Numbering Tab Click on the Nos. lookup Create No. Series with checked Default Nos and Manual Nos Click OK to return to Setup Close Setup Setting up Security In order to secure Matriks Doc everyday usage and ensure that ordinary users do not inadvertently alter the Matriks Doc configuration we recommend that you define the following Navision roles and apply them to users. Perform the following tasks: Open the Roles window (Tools->Security->Roles Menu) 1. Insert a new Role (press F3) and call it MD-SETUP with description setup 2. Select Role->Permissions. 3. Insert permissions from the MD-SETUP table below. 4. Close Permissions. Repeat 1 to 4 with MD-USE and description use instead Remember your users will HAVE TO have access to the subsystem for which the user should be able to define a template. This typically depends on other roles you have assigned to your users. Close Roles window Open Database Logins window (Tools->Security->Database Logins) Assign the MD-SETUP and MD-USE roles to users as you see fit Role: MD-SETUP Table Data Setup Yes Yes Yes Yes Yes Role: MD-USE Table Data Yes Yes Yes Yes Yes Table Data Template Field Yes Yes Yes Yes Yes Table Data Category Yes Yes Yes Yes Yes Table Data Setup Yes Yes Table Data Journal Line Yes Yes Yes Yes Yes Table Data Table Information Yes Yes MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 5/17

6 Matriks Doc Configuration Uninstalling The installation procedure is divided into the following steps: 1. Restore Navision objects 2. Remove Matriks Doc basic objects 3. Remove Matriks Doc security roles. 4. Remove the Matriks Doc help files Step 1: Restore Navision objects Open the Navision client and connect to/open the Navision database Open the Object Designer (Tool->Object Designer) Select Import Objects in file menu (File->Import) Find and select the before_md3.fob file Choose Yes to import all objects Click No to open Import Worksheet Put a *MATDOC* filter on column Existing Object Version List Click on Replace All Click on Ok Step 2: Remove basic objects Click on All button in the Object Designer menu Put a MATDOC* filter on column Version List Select table ( ) a: Click Run b: Select all lines (CTRL + A) c: Click on Delete in the Toolbar (F4) d: Click Yes to delete selected lines e: Close Table Run (Esc) Repeat a-d for all Matriks Doc tables Select all Matriks Doc objects (CTRL+ A) Click on Delete in the Toolbar (F4) Click Yes to delete selected lines Step 3: Remove the Matriks Doc security roles Open the Roles window (Tools->Security->Roles Menu) Find and remove MD-SETUP and MD-USE. Find and remove other Matriks Doc rules that you may have defined yourself. Step 4: Remove Matriks Doc help files Close the Navision Client Go to the Navision client installation folder Remove the 2 help files (addin_a.chm, addin_a.hh) from: o folder ENU if United States o folder ENG if United Kingdom o folder ENA if Australia Open the Navision client and connect to/open the Navision database Verify that the Management and the corresponding help files have been removed. MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 6/17

7 Matriks Doc Technical Notes The following topics has been supplied in order to give the Navision professional a more thorough understanding of the scope of the Matriks Doc software and how a Navision professional can manually implement Matriks Doc into installations in scenarios where the general purpose installation cannot be used. Footprint The Matriks Doc software is delivered in 2 FOB files called basic objects and interface objects. The basic objects contain objects in the 60089xx object range that make up the core of the Matriks Doc application. The interface objects contain Navision objects from various application modules that have been altered to integrate with the basic objects. Basic objects The basic objects consist of the following 26 tables, forms, codeunits and menu objects: ID Table Table Table Table Table Form Form Form Form Form Form Form Codeunit Codeunit Codeunit Codeunit Codeunit Codeunit Codeunit Name Template Field Category Setup Journal Line s Templates Categories Setup Table List Journal Template Fields Management Access Management Flow Management OS Interface Routines Appl. Management Proxy Word Management (XP) Excel Management (XP) Codeunit Word Management (2000) Codeunit Excel Management (2000) Codeunit Word Management (2003) Codeunit Excel Management (2003) Codeunit Codeunit Menu 51 Special Template Management Session Variables MatriksDoc AddOn MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 7/17

8 Interface objects Matriks Doc has been integrated into the following 83 Navision objects: ID Form 14 Form 16 Form 17 Form 18 Form 21 Form 22 Form 26 Form 27 Form 30 Form 31 Form 41 Form 42 Form 43 Form 44 Form 49 Form 50 Form 51 Form 52 Form 76 Form 77 Form 88 Form 89 Form 104 Form 344 Form 370 Form 371 Form 434 Form 446 Form 507 Form 509 Form 5050 Form 5052 Form 5086 Form 5087 Form 5091 Name Salespeople/Purchasers Chart of Accounts G/L Account Card G/L Account List Customer Card Customer List Vendor Card Vendor List Item Card Item List Sales Quote Sales Order Sales Invoice Sales Credit Memo Purchase Quote Purchase Order Purchase Invoice Purchase Credit Memo Resource Card Resource List Job Card Job List Account Schedule Navigate Bank Account Card Bank Account List Reminder Finance Charge Memo Blanket Sales Order Blanket Purchase Order Contact Card Contact List Campaign Card Campaign List Segment MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 8/17

9 Form 5093 Form 5116 Form 5200 Form 5201 Form 5600 Form 5601 Form 5644 Form 5645 Form 5700 Form 5701 Form 5725 Form 5726 Form 5740 Form 5900 Form 5964 Form 5980 Form 5981 Form 6050 Form 6053 Form 6256 Form 6257 Form 6630 Form 6640 Form Form Form Form Form Form Form Form Form Form Form Form Form Form Codeunit 80 Codeunit 83 Segment List Salesperson/Purchaser Card Employee Card Employee List Fixed Asset Fixed Asset List Insurance Card Insurance List Stockkeeping Unit Card Stockkeeping Unit List Nonstock Item Card Nonstock Item List Transfer Order Service Order Service Quote Service Item Card Service Item List Service Contract Service Contract Quote Reverse Auction List Reverse Auction Sales Return Order Purchase Return Order Work Center Card Work Center List Routing List Routing Production BOM Production BOM List Prod. BOM Version List Routing Version List Production BOM Version Routing Version Planned Production Order Firm Planned Prod. Order Released Production Order Simulated Production Order Sales-Post Sales-Quote to Order (Yes/No) MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 9/17

10 Codeunit 84 Codeunit 90 Codeunit 93 Codeunit 94 Codeunit 393 Codeunit 395 Codeunit 5407 Codeunit 5922 Codeunit 5944 Blnkt Sales Ord. to Ord. (Y/N) Purch.-Post Purch.-Quote to Order (Yes/No) Blnkt Purch Ord. to Ord. (Y/N) Reminder-Issue FinChrgMemo-Issue Prod. Order Status Management Serv-Quote to Order (Yes/No) SignServContractDoc MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 10/17

11 Modifications When a customer database has been modified by other add-ons or one needs Matriks Doc interface objects for a Navision version that is not currently supplied by Matriks A/S, it may be required of the MBS professional to build the interface objects manually. By following the modification instructions below, it is possible for any with a little C/AL experience to add Matriks Doc functionality to Navision objects. It is the same recipe used internally by Matriks A/S. Normal Forms Most of the changes to Navision forms are about adding a new menu item called s to the forms leftmost Menu Button. Place the new menu item under Comments or if Comments is not present, then make a menu separator in the bottom of the menu item list and place the s menu item last in list. The s menu item should have a formlink to "Form documents" Below are the RunFormLinks with OnUpdate instead of the default OnOpen as property: ID Form 14 Form 16 Form 17 Form 18 Form 21 Form 22 Form 26 Form 27 Form 30 Form 31 Form 41 Form 42 Form 43 Form 44 Form 49 Form 50 Form 51 Form 52 Form 76 Form 77 Form 88 Form 89 Form 104 RunFormLink Table No.=CONST(13),Reference No. 1=FIELD(Code) Table No.=CONST(15),Reference No. 1=FIELD(No.) Table No.=CONST(15),Reference No. 1=FIELD(No.) Table No.=CONST(15),Reference No. 1=FIELD(No.) Table No.=CONST(18),Reference No. 1=FIELD(No.) Table No.=CONST(18),Reference No. 1=FIELD(No.) Table No.=CONST(23),Reference No. 1=FIELD(No.) Table No.=CONST(23),Reference No. 1=FIELD(No.) Table No.=CONST(27),Reference No. 1=FIELD(No.) Table No.=CONST(27),Reference No. 1=FIELD(No.) Table No.=CONST(36),Reference No. 1=CONST(0),Reference No. 2=FIELD(No.) Table No.=CONST(36),Reference No. 1=CONST(1),Reference No. 2=FIELD(No.) Table No.=CONST(36),Reference No. 1=CONST(2),Reference No. 2=FIELD(No.) Table No.=CONST(36),Reference No. 1=CONST(3),Reference No. 2=FIELD(No.) Table No.=CONST(38),Reference No. 1=CONST(0),Reference No. 2=FIELD(No.) Table No.=CONST(38),Reference No. 1=CONST(1),Reference No. 2=FIELD(No.) Table No.=CONST(38),Reference No. 1=CONST(2),Reference No. 2=FIELD(No.) Table No.=CONST(38),Reference No. 1=CONST(3),Reference No. 2=FIELD(No.) Table No.=CONST(156),Reference No. 1=FIELD(No.) Table No.=CONST(156),Reference No. 1=FIELD(No.) Table No.=CONST(167),Reference No. 1=FIELD(No.) Table No.=CONST(167),Reference No. 1=FIELD(No.) Table No.=CONST(84),Reference No. 1=FIELD(Schedule Name) MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 11/17

12 Form 370 Form 371 Form 434 Form 446 Form 507 Form 509 Form 5050 Form 5052 Form 5086 Form 5087 Form 5091 Form 5093 Form 5116 Form 5200 Form 5201 Form 5600 Form 5601 Form 5644 Form 5645 Form 5700 Form 5701 Form 5725 Form 5726 Form 5740 Form 5900 Form 5964 Form 5980 Form 5981 Form 6050 Form 6053 Form 6256 Form 6257 Form 6630 Form 6640 Form Form Form Table No.=CONST(270),Reference No. 1=FIELD(No.) Table No.=CONST(270),Reference No. 1=FIELD(No.) Table No.=CONST(295),Reference No. 1=FIELD(No.) Table No.=CONST(302),Reference No. 1=FIELD(No.) Table No.=CONST(36),Reference No. 1=CONST(4),Reference No. 2=FIELD(No.) Table No.=CONST(38),Reference No. 1=CONST(4),Reference No. 2=FIELD(No.) Table No.=CONST(5050),Reference No. 1=FIELD(No.) Table No.=CONST(5050),Reference No. 1=FIELD(No.) Table No.=CONST(5071),Reference No. 1=FIELD(No.) Table No.=CONST(5071),Reference No. 1=FIELD(No.) Table No.=CONST(5076),Reference No. 1=FIELD(No.) Table No.=CONST(5076),Reference No. 1=FIELD(No.) Table No.=CONST(13),Reference No. 1=FIELD(Code) Table No.=CONST(5200),Reference No. 1=FIELD(No.) Table No.=CONST(5200),Reference No. 1=FIELD(No.) Table No.=CONST(5600),Reference No. 1=FIELD(No.) Table No.=CONST(5600),Reference No. 1=FIELD(No.) Table No.=CONST(5628),Reference No. 1=FIELD(No.) Table No.=CONST(5628),Reference No. 1=FIELD(No.) Table No.=CONST(5700),Reference No. 1=FIELD(Item No.),Reference No. 2=FIELD(Variant Code),Reference No. 3=FIELD(Location Code) Table No.=CONST(5700),Reference No. 1=FIELD(Item No.),Reference No. 2=FIELD(Variant Code),Reference No. 3=FIELD(Location Code) Table No.=CONST(5718),Reference No. 1=FIELD(Entry No.) Table No.=CONST(5718),Reference No. 1=FIELD(Entry No.) Table No.=CONST(5740),Reference No. 1=FIELD(No.) Table No.=CONST(5900),Reference No. 1=CONST(1),Reference No. 2=FIELD(No.) Table No.=CONST(5900),Reference No. 1=CONST(0),Reference No. 2=FIELD(No.) Table No.=CONST(5940),Reference No. 1=FIELD(No.) Table No.=CONST(5940),Reference No. 1=FIELD(No.) Table No.=CONST(5965),Reference No. 1=CONST(1),Reference No. 2=FIELD(Contract No.) Table No.=CONST(5965),Reference No. 1=CONST(0),Reference No. 2=FIELD(Contract No.) Table No.=CONST(6241),Reference No. 1=FIELD(No.) Table No.=CONST(6241),Reference No. 1=FIELD(No.) Table No.=CONST(36),Reference No. 1=CONST(5),Reference No. 2=FIELD(No.) Table No.=CONST(38),Reference No. 1=CONST(5),Reference No. 2=FIELD(No.) Table No.=CONST( ),Reference No. 1=FIELD(No.) Table No.=CONST( ),Reference No. 1=FIELD(No.) Table No.=CONST( ),Reference No. 1=FIELD(No.) MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 12/17

13 Form Form Form Form Form Form Form Form Form Form Form Table No.=CONST( ),Reference No. 1=FIELD(No.) Table No.=CONST( ),Reference No. 1=FIELD(No.) Table No.=CONST( ),Reference No. 1=FIELD(No.) Table No.=CONST( ),Reference No. 1=FIELD(Production BOM No.),Reference No. 2=FIELD(Version Code) Table No.=CONST( ),Reference No. 1=FIELD(Routing No.),Reference No. 2=FIELD(Version Code) Table No.=CONST( ),Reference No. 1=FIELD(Production BOM No.),Reference No. 2=FIELD(Version Code) Table No.=CONST( ),Reference No. 1=FIELD(Routing No.),Reference No. 2=FIELD(Version Code) Table No.=CONST(5405),Reference No. 1=CONST(1),Reference No. 2=FIELD(No.) Table No.=CONST(5405),Reference No. 1=CONST(2),Reference No. 2=FIELD(No.) Table No.=CONST(5405),Reference No. 1=CONST(3),Reference No. 2=FIELD(No.) Table No.=CONST(5405),Reference No. 1=CONST(0),Reference No. 2=FIELD(No.) MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 13/17

14 Special Forms Form 344 (Navigate) :Record [New Code 1] Where to place: DocExists := FIND('-'); in FindRecords() //Matriks Doc Begin IF.READPERMISSION THEN BEGIN.RESET;.SETCURRENTKEY(" No.");.SETFILTER(" No.", DocNoFilter); InsertIntoDocEntry( DATABASE::,0,.TABLECAPTION,.COUNT); END; //Matriks Doc End [New Code 2] Where to place: Last case (before end) in ShowRecords() //Matriks Doc Begin DATABASE::: FORM.RUN(0,); //Matriks Doc End MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 14/17

15 Codeunits Codeunit 80 (Sales-Post) :Record :Codeunit Flow Management [New Code ] Where to place: Last lines of OnRun //MatriksDoc Begin IF.READPERMISSION THEN.DocNoOnPostedSale(SalesHeader); //MatriksDoc End Codeunit 83 (Sales-Quote to Order (Yes/No)) :Record :Codeunit Flow Management Where to place: Before commit of OnRun // MatriksDoc Begin IF.READPERMISSION THEN.SalesQuotetoOrder("No.",SalesHeader2."No."); // MatriksDoc End Codeunit 84 (Blnkt Sales Ord. to Ord. (Y/N)) :Record :Codeunit Flow Management Where to place: Before last message of OnRun // MatriksDoc Begin IF.READPERMISSION THEN.BlanketSalesOrdertoOrder("No.",SalesHeader2."No."); // MatriksDoc End Codeunit 90 (Purch.-Post) :Record :Codeunit Flow Management Where to place: Last lines of OnRun //MatriksDoc Begin IF.READPERMISSION THEN.DocNoOnPostedPurchase(PurchHeader); //MatriksDoc End MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 15/17

16 Codeunit 93 (Purch.-Quote to Order (Yes/No)) :Record :Codeunit Flow Management Where to place: Before last message of OnRun // MatriksDoc Begin IF.READPERMISSION THEN.PurchQuotetoOrder("No.",PurchOrderHeader."No."); // MatriksDoc End Codeunit 94 (Blnkt Purch Ord. to Ord. (Y/N)) :Record :Codeunit Flow Management Where to place: Before last message of OnRun // MatriksDoc Begin IF.READPERMISSION THEN.BlanketPurchOrdertoOrder("No.",PurchOrderHeader."No."); // MatriksDoc End Codeunit 393 (Reminder-Issue) :Record :Codeunit Flow Management Where to place: Last lines of OnRun //MatriksDoc Begin IF.READPERMISSION THEN.DocNoOnIssuedReminder(ReminderHeader."No.", DocNo); //MatriksDoc End Codeunit 395 (FinChrgMemo-Issue) :Record :Codeunit Flow Management Where to place: Last lines of OnRun //MatriksDoc Begin IF.READPERMISSION THEN.DocNoOnIssuedFinanceCharge(FinChrgMemoHeader."No.", DocNo); //MatriksDoc End MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 16/17

17 Codeunit 5407 (Prod. Order Status Management) :Record :Codeunit Flow Management Where to place: Last lines of OnRun //MatriksDoc Begin IF.READPERMISSION THEN.DocNoOnProductionOrders(Rec,NewStatus); //MatriksDoc End Codeunit 5908 (ServOrder-Post) :Record :Codeunit Flow Management Where to place: Last lines of OnRun // MatriksDoc Begin IF.READPERMISSION THEN.DocNoOnServiceOrders(ServHeader."No.",PostedServHeader."No."); // MatriksDoc End Codeunit 5922 (Serv-Quote to Order (Yes/No)) :Record :Codeunit Flow Management Where to place: Before last message of OnRun // MatriksDoc Begin IF.READPERMISSION THEN.ServiceQuotetoOrder("No.",ServQuoteToOrder.ReturnOrderNo); // MatriksDoc End Codeunit 5944 (SignServContractDoc) :Record :Codeunit Flow Management Where to place: Last lines of SignContractQuote //MatriksDoc Begin IF.READPERMISSION THEN.ContractQuotetoContract(FromServContractHeader."Contract No.", SalesHeader."No."); //MatriksDoc End MICROSOFT BUSINESS SOLUTIONS NAVISION ADDON 17/17