Microsoft Dynamics AX Connector. Implementation Guide

Transcription

1 Microsoft Dynamics AX Connector Implementation Guide

2

3 Microsoft Dynamics AX Connector Implementation Guide Version 3.0 Copyright Bottomline Technologies, Inc All Rights Reserved Information in this document is subject to change without notice and does not represent a commitment on the part of Bottomline Technologies. Bottomline Technologies makes no warranties with respect to this documentation and disclaims any implied warranties of merchantability or fitness for a particular purpose. Bottomline Technologies 325 Corporate Drive Portsmouth, NH Telephone: (603) Fax: (603) btinfo@bottomline.com Internet: SWR-CFIMDAX30-REF

4

5 T ABLE OF CONTENTS v Chapter 1: Introduction... 7 Chapter 2: Configuration.. 9 Document Processes.. 10 Setting up a Document Process. 10 Specifying Default Values.. 13 Delivery Destinations. 15 Setting up Delivery Destinations 15 Enabling Reports Specifying the XML Path.. 24 Folder Monitor Mapping Directly to a Queue.. 26 Printing Batch Jobs.. 29 Chapter 3: Enhanced Features. 35 Print Management Document Process. 36 Fax Print.. 39 Screen Preview Enterprise Portal Multi-select Preview Support Appendix A.. 45 XML File Naming Convention Processing Parameters 47 Security Keys.. 51 Glossary.. 52 Index Microsoft Dynamics AX Connector Implementation Guide v

6 vi vi Microsoft Dynamics AX Connector Implementation Guide

7 Chapter 1: Introduction C HAPTER INTRODUCTION Note The information contained in this guide applies to both Microsoft Dynamics AX 2009, and Microsoft Dynamics AX, version 4.0, unless specifically stated otherwise. Create!form processes output from multiple source systems for either packaged software solutions or custom legacy applications. This guide describes the specific configuration process developed by Bottomline Technologies to ensure seamless document process automation with Microsoft Dynamics AX. Required Create!form components include: Create!form Designer Create!form Designer is used to design form projects, which Create!form Server merges with the output of your enterprise server. The form project allows you to reformat and enhance the output of your enterprise, incorporating logos, images and drawing objects as well as formatted text. Create!form Director Create!form Director is used to design projects that Create!form Server splits and processes for the enterprise server which then merges, transforms, e- mails, faxes or archives, as necessary. The types of action that Create!form Director performs include: Splitting the spool file into multiple spool files Sending particular parts of the spool file to particular directories or queues Extracting data for use in reports Creating backup copies of the spool file Microsoft Dynamics AX Connector Implementation Guide 7

8 8 CHAPTER 1: INTRODUCTION Adding job ticket templates (JTTs) that determine various parameters used in processing by other Create!form products Create!form Server Create!form Server is the central processor which handles the output from the enterprise server, and applies the appropriate project designed with either Create!form Designer, Create!form Transform or Create!form Director. The output from Create!form Server can be printed, faxed, ed or archived using other Create!form products. Note For a list of optional Create!form products contact a Bottomline Technologies customer service representative. Steps for Configuration Following, as outlined in succeeding sections, are the steps for configuration: Set up a document process for each Create!form Director project used in processing Dynamics AX output Specify default values Specify delivery destinations for Dynamics AX output Enable Reports Specify the XML Path for the Microsoft AX Connector Components. All of the Microsoft Dynamics AX administration functions for the integration can be accessed via the Setup section of the Administration pane. Refer to Chapter 2, Configuration, for more information on completing the first step: setting up a document process. 8 Microsoft Dynamics AX Connector Implementation Guide

9 Chapter 2: Configuration C HAPTER CONFIGURATION This section outlines the steps necessary for configuring Microsoft Dynamics AX for use with Create!form software. The following topics are discussed: Document Processes Specifying Default Values Delivery Destinations Enabling Reports Specifying the XML Path Printing Batch Jobs Microsoft Dynamics AX Connector Implementation Guide 9

10 10 CHAPTER 2: CONFIGURATION Document Processes Document Processes Note Users with AOS Service require full access to the directory where the XML output path is mapped, as well as access to the printer queue. This means that the AOS Service user must be granted all permissions to complete the required tasks. Document processes represent the distribution logic that is defined in a Create!form Director project. Before a Create!form Director project is used for processing Microsoft Dynamics AX reports, it is mapped to a document process, as described in the following section. First there must be at least one document process established as a default for reports that do not require a specific Director project. For a report that specifies the distribution logic, or document composition logic, then a unique Director project is used. For example, an invoice may have delivery rules based on customer type. Setting up a Document Process Each document process is created with a user-friendly name and description so that the appropriate report is selected for the Create!form Director project. To set up a document process 1 In the Administration pane, expand Setup and then Create!form. 2 Click Document Processes. 10 Microsoft Dynamics AX Connector Implementation Guide

11 CHAPTER 2: CONFIGURATION Document Processes 11 3 On the Setup tab, enter the following details: Process Name Process Description Process Project A user-friendly name for the process A meaningful description of the process The name of the Create!form Director project running on the Create!form server Microsoft Dynamics AX Connector Implementation Guide 11

12 12 CHAPTER 2: CONFIGURATION Specifying Default Values Specifying Default Values Default Values must be specified when they have not already been established as required values in a form. To specify default values 1 In the Administration pane, expand Setup and then Create!form. 2 Click Defaults. 12 Microsoft Dynamics AX Connector Implementation Guide

13 CHAPTER 2: CONFIGURATION Specifying Default Values 13 3 Enter details for the following default values: XML Output Location The path to the folder, or queue, in which the Dynamics AX XML output is placed. This is the folder from which the Create!form Director project takes files for processing. Specify the location as a UNC path in the form \\server\volume\directory or as a network file share (optional). Screen Preview Temp Location Default Document Process Default Screen Preview Timeout The path to the folder where temporary PDF files are created when the user requests a screen preview of a report. Specify the location as a UNC path in the form \\server\volume\ directory or as a network file share. Users requiring access to this folder will need the proper permissions. The user-friendly name of the document process to use for processing output when no other process is selected. The maximum time, in seconds, to allow for loading a formatted report for display in a preview screen. If the report cannot be displayed within this time, the preview screen closes with an appropriate message to the user. Microsoft Dynamics AX Connector Implementation Guide 13

14 14 CHAPTER 2: CONFIGURATION Delivery Destinations Delivery Destinations Note Cheque reports will be restricted to printer destinations only. Other destination types will be filtered out when selecting delivery destinations for the report. Delivery destinations define how output can be delivered to particular users or groups. The table below shows the methods of delivery currently supported. Table 2.1 Destination Screen Printer Fax Document Process Delivery Methods Description Writes the PDF to a temporary file and displays it on the user's screen. Sends the output to a printer. Sends the output as an attachment. Sends the output as a fax message. Processes the output by means of a Create!form Director project. Each delivery destination is associated with a method, and with specific users and groups. This means that users can see and select only those destinations that are appropriate for their role. The attributes of a delivery method define the physical routing of the output so that, for example, the XML output file can be directed to a particular network location, according to which user or group requests the output. Delivery Method Code Note In Microsoft Dynamics AX Connector, since labels are now localized, Field_DeliveryMethod_Code has been added to the BT prolog in order to support Director projects which may service AX clients using multiple languages. Each delivery method type will be consistently represented with an assigned code. 14 Microsoft Dynamics AX Connector Implementation Guide

15 CHAPTER 2: CONFIGURATION Delivery Destinations 15 The BT prolog was modified in the following way: Prolog Parameter Form Field Field_Path Defaults or Delivery Destinations XML output path Field_ScrenTempPath Defaults or Delivery Destinations Screen Preview Temp Location Field_Testing Enabled Reports Testing Parameters Field_ProcessName Defaults or Delivery Destinations (process) or Enabled Reports Document Process Field_DeliveryMethod and Field_DeliveryMethod_Code Printer Setup Form Each of the delivery methods is coded as follows: Delivery destination chosen in the Send to list Field_ReportParameters Enabled Reports Report Parameters Field_Destination Parameters Delivery Destinations Destination Parameters Field_PrinterNetworkId Delivery Destinations Printer Network ID Field_PrinterCopies Printer Setup Form Number of Copies Field_ NetworkId Delivery Destinations (E_mail) Network ID Delivery Method Screen 0 Printer 1 2 Fax 3 Document Process 4 Code Each delivery method s code corresponds to its enumeration values from the BT_DPA_Dest_Type base enum. Within Director_Generic_v3 these values are used to direct the output to the desired destinations. Setting up Delivery Destinations To define a delivery destination 1 In the Administration pane, expand Setup and then Create!form. 2 Click Delivery Destinations. Microsoft Dynamics AX Connector Implementation Guide 15

16 16 CHAPTER 2: CONFIGURATION Delivery Destinations 3 On the Destinations tab, click in the Delivery Method field, and select a delivery method. 4 In the Destination Name field, beside the chosen Delivery Method, enter a descriptive name for the delivery destination. 5 In the XML Output Location field, enter the XML Output Location ONLY if it is a different location than the one specified during Default setup. 6 In the User Restrictions field, select the check boxes for the Delivery Methods where the User will not need access. 7 On the Setup tab, specify the following: * Fields containing an asterisk are displayed only when the appropriate delivery method is selected. 16 Microsoft Dynamics AX Connector Implementation Guide

17 CHAPTER 2: CONFIGURATION Delivery Destinations 17 XML Output Location Restricted use Destination description Destination Parameters Screen Preview Temp Location *Printer Network ID This field is used to over-ride the default locations that is set in the Defaults form. It is the path to the folder, or queue, in which the Dynamics AX XML output is placed. Leave this field blank to use the default. Select this if the destination is to be restricted for use by particular users or groups. Clear this setting to allow all users to use the destination. A description of the destination. Specify additional parameters to the destination. If the selected delivery method is Screen, the path to the folder where temporary PDF files are created when the user requests a screen preview of a report. If the selected delivery method is Printer, the network name of a shared printer on which the output is printed, or a printer queue that is used to trigger a Create!form project. * Network ID If the selected delivery method is , the e- mail server to use for routing the output. *Fax Network ID If the selected delivery method is Fax, the fax server to use for routing the output. Microsoft Dynamics AX Connector Implementation Guide 17

18 18 CHAPTER 2: CONFIGURATION Delivery Destinations 8 On the Groups tab, if use of the delivery destination is to be restricted to particular groups, click the left arrow to list those groups in the Restrict to groups area. If more than one group requires restrictions use the double arrow button. 18 Microsoft Dynamics AX Connector Implementation Guide

19 CHAPTER 2: CONFIGURATION Delivery Destinations 19 9 On the Users tab, if use of the delivery destination is to be restricted to particular users, click the left arrow to list those groups in the Restrict to Users area. If more than one group requires restrictions use the double arrow button. Microsoft Dynamics AX Connector Implementation Guide 19

20 20 CHAPTER 2: CONFIGURATION Delivery Destinations 20 Microsoft Dynamics AX Connector Implementation Guide

21 CHAPTER 2: CONFIGURATION Enabling Reports 21 Enabling Reports To enable a Microsoft Dynamics AX report for processing by a Create!form Director project, you must associate the Application Object Tree (AOT) report object with the project. Use the Enabled Reports feature to do this. Note Reports enabled through the Enabled Reports form are enabled in the conventional client and the Enterprise portal. To associate a report object with a project 1 In the Administration pane, expand Setup and then Create!form. 2 Click Enabled Reports. Note AOT Reports do not automatically display when navigating to the Enabled Reports window for the first time. The AOT report will need to be chosen from the drop down list and then associated with a project. 3 On the Enabled Reports tab, select the check boxes in the Create!form Enabled field that need to be enabled. Microsoft Dynamics AX Connector Implementation Guide 21

22 22 CHAPTER 2: CONFIGURATION Enabling Reports 4 On the Setup tab complete the following fields: Create!form Enabled: Select this field to enable the report for processing by the Create!form Director project, or clear it to disable such processing. Testing Parameters: The names of any trigger parameters in the Create!form Director project which cause processing to change to a path defined for testing purposes. For example, when using the example Director_Generic_v3 project, entering SAMPLE causes output to be created in the form of an XML file that can be used for forms design, rather than being sent to a printer. Screen Preview Timeout Is when a preview screen attempts to display a formatted report, the maximum time to allow for loading the report. If the report cannot be displayed within this time, the preview screen closes. It is sometimes 22 Microsoft Dynamics AX Connector Implementation Guide

23 CHAPTER 2: CONFIGURATION Enabling Reports 23 necessary to increase the timeout period for complex projects that take a long time to process reports. Document Process The user-friendly name of the document process to use for processing the selected report object. Report Parameters Specify additional non-testing parameters for the report. Director_Generic_v3 allows designers to use the first line of the Reporting Parameters field to specify the name of the Designer project that merges the enabled report. If there is no parameter, then the AOT Report name is used to find the Designer project. When a report is first enabled, but no Designer project has been created, the test report project AXTestReport can be used to test Create!form while samples are gathered. Note The ability to specify an explicit Create!form report name in the Reporting Parameters allows designers to select different report designs for the same report by AX Company without modifying Director_Generic_v3. Only the first lines of the Testing Parameters and Reporting Parameters fields are used to drive logic in Director_Generic_v3. This allows the designer to add additional parameters on subsequent lines if their DPA application requires it. Microsoft Dynamics AX Connector Implementation Guide 23

24 24 CHAPTER 2: CONFIGURATION Enabling Reports 24 Microsoft Dynamics AX Connector Implementation Guide

25 CHAPTER 2: CONFIGURATION Enabling Reports 25 5 On the Deployment Schedule tab, specify which report design should be issued on the selected dates. (The date and time is based on the AOS Server time) Dynamics AX allows the user to create multiple designs per report. You can select a specific design to be enabled at a defined date and time. Note If the deployment date is left blank then the design becomes immediately available. If the design is left blank then the default AOT, or first design, is chosen. 6 On the Delivery Destinations tabs, list the delivery destinations to be assigned to the report object. Microsoft Dynamics AX Connector Implementation Guide 25

26 26 CHAPTER 2: CONFIGURATION Enabling Reports 26 Microsoft Dynamics AX Connector Implementation Guide

27 CHAPTER 2: CONFIGURATION Specifying the XML Path 27 Specifying the XML Path Create!form Server retrieves XML files that are written directly to a shared queue. There are two places to specify XML paths within Microsoft Dynamics Connector: from the Defaults form, and from the Setup tab in the Delivery Destinations form (Refer to Delivery Destinations for more information regarding the Defaults form and the setup tab.). Mapping Directly to a Queue To establish an XML path mapped directly to a queue On the Start menu, in the Printers and Faxes screen, right click the CF Director printer and select Sharing. On the CF_Director Properties screen, in the Sharing tab, Click the OK button. Note If the queue is pointed to a local port, then the folder that contains the file for the port must be enabled to allow any user access. For example, if the computer that hosted the CF Director queue is named Server, then the XML output location would be \\Server\CF Director as shown. Microsoft Dynamics AX Connector Implementation Guide 27

28 28 CHAPTER 2: CONFIGURATION Printing Batch Jobs Printing Batch Jobs Before printing batch jobs using Microsoft Dynamics AX Connector, the server must be configured for printing. For example: To print a report in batch mode 1 On the Posting Invoice screen, click Batch (d) on the bottom right hand corner of the screen. The Batch Processing form is displayed. 2 Select the Batch processing check box and click OK. The Infolog dialog box displays with a confirmation that the Order invoice job is added to the batch queue. 28 Microsoft Dynamics AX Connector Implementation Guide

29 CHAPTER 2: CONFIGURATION Printing Batch Jobs 29 3 Click Close. Now the batch printers need to be configured on the Microsoft Dynamics AX Server. 4 On the AX Server navigate to Control Panel >Administrative Tools > Microsoft Dynamics AX Server Configuration. The Microsoft Dynamics AX Server Configuration Utility screen appears. 5 On the Utility screen select the Allow clients to connect to printers on this server checkbox, and click OK. Microsoft Dynamics AX Connector Implementation Guide 29

30 30 CHAPTER 2: CONFIGURATION Printing Batch Jobs 6 If the Utility screen appears grayed-out like the one below, then a new configuration will need to be created. 30 Microsoft Dynamics AX Connector Implementation Guide

31 CHAPTER 2: CONFIGURATION Printing Batch Jobs 31 To create a new configuration 1 Next to the Configuration field, click Manage > Create Configuration. The Create Configuration pop up appears. 2 On the Configuration name field, Type a configuration name (any name will do) and select OK. The Utility screen re-appears. Microsoft Dynamics AX Connector Implementation Guide 31

32 32 CHAPTER 2: CONFIGURATION Printing Batch Jobs 3 Select the Allow clients to connect to printers on this server checkbox and click OK. The Configuration Utility dialog box appears. 4 Click Yes and wait for the service to restart. 32 Microsoft Dynamics AX Connector Implementation Guide

33 Chapter 3: Enhanced Features C HAPTER ENHANCED FEATURES There are several features that Create!form s Dynamics AX Integration enhances in Microsoft Dynamics AX: Print Management Enterprise Portal Multi-select Preview Support Microsoft Dynamics AX Connector Implementation Guide 33

34 34 CHAPTER 3: ENHANCED FEATURES Print Management Print Management Microsoft Dynamics AX Print Management is a robust feature that provides many options for printing. Create!form s Dynamics AX Integration enhances the existing print management feature by offering the following Create!form specific print mediums: document process fax printer screen preview capabilities These modifications allow direct integration with Create!form Server for Dynamics AX reports that are Create!form enabled. Refer to the Microsoft Dynamics AX Help for more information on Print Management/Print Mediums. Document Process Select the document process delivery destination by clicking on the Name drop down menu. 34 Microsoft Dynamics AX Connector Implementation Guide

35 CHAPTER 3: ENHANCED FEATURES Print Management 35 Fax The Print Management form for Create!form Fax maps to fax delivery destinations. Select the fax delivery destination by clicking on the Name drop down menu. Type the Fax number in the Fax number field. Type any text to be included on the cover sheet in the Cover sheet text field. Microsoft Dynamics AX Connector Implementation Guide 35

36 36 CHAPTER 3: ENHANCED FEATURES Print Management The Print Management form for Create!form maps to delivery destinations. Select the delivery destination from the drop down menu. Type who the is from in the From field. Type who the is to in the To field. If sending a copy of the to other parties, type their names into the CD field. If sending a blind copy of the to another party, type their names into the Bcc field. Type the Subject of the into the Subject field. Type the text of the into the Body field. 36 Microsoft Dynamics AX Connector Implementation Guide

37 CHAPTER 3: ENHANCED FEATURES Print Management 37 Print The Print Management form for Create!form Printer maps to printer delivery destinations. Select the printer delivery destination by clicking on the Name drop down menu. Microsoft Dynamics AX Connector Implementation Guide 37

38 38 CHAPTER 3: ENHANCED FEATURES Print Management Screen Preview Note The user must be granted Read access in Folder Security Permissions and Shares to view screens. The Print Management form for Create!form Screen maps to screen preview delivery destinations. Select the screen preview delivery destination by clicking on the Name drop down menu. 38 Microsoft Dynamics AX Connector Implementation Guide

39 CHAPTER 3: ENHANCED FEATURES Print Management 39 Microsoft Dynamics AX Connector Implementation Guide 39

40 40 CHAPTER 3: ENHANCED FEATURES Enterprise Portal Enterprise Portal Dynamics AX's Enterprise Portal client is supported in the Create!form Dynamics AX Connector. Enterprise Portal support is limited to legacy reports, i.e. reports that are also accessible in the standard AX Client. The Enterprise Portal also uses special reports called Web Reports which are NOT supported. Enterprise Portal reports are enabled in the same manner as regular reports via the Create!form Enabled Reports form. 40 Microsoft Dynamics AX Connector Implementation Guide

41 CHAPTER 3: ENHANCED FEATURES Multi-select Preview Support 41 Multi-select Preview Support Create!form Dynamics AX Connector allows multiple documents to be viewed in a single preview PDF when performing a multi-select. To enable the multi-select feature select the Combine into one Report checkbox. Note Microsoft Dynamics AX Connector supports combining for the following reports: SalesQuotationConfirmation WMSPickingList_OrderPick Invent PickingListJournal or InventPickingList (depending on which sales order is chosen) ProjInvoice PurchInvoice PurchPackingSlip PurchReceiptsList PurchPurchaseOrder PurchRFQSend SalesQuotation FreeTextInvoice SalesConfirm SalesInvoice SalesPackingSlip Microsoft Dynamics AX Connector Implementation Guide 41

42 42 CHAPTER 3: ENHANCED FEATURES Multi-select Preview Support 42 Microsoft Dynamics AX Connector Implementation Guide

43 Appendix A A PPENDIX APPENDIX In this Appendix we will discuss the following: XML File Naming Convention Processing Parameters Security Keys Glossary The following table describes the categories of components that are installed by the integration installers. Microsoft Dynamics AX Connector Implementation Guide 43

44 44 APPENDIX A XML File Naming Convention XML File Naming Convention The filename of the XML files created by the integration are derived at run time based on the following: Value Source Notes Report Name Enable Reports Table Separator Semicolon used as separator User ID Derived at runtime Data-Time Stamp Derived at Runtime Semicolon as a separator Output Scenario Indicator If print medium is screen, then _P If print medium is not screen, then _D If via an ad hoc request, then _A _P = Preview _D = Default _A = Ad hoc File Extension.xml 44 Microsoft Dynamics AX Connector Implementation Guide

45 APPENDIX A Processing Parameters 45 Processing Parameters Before a report is written to an XML file, a header section is added to the file. The purpose of the header is to pass parameters for the enabled report attributes to CF that will allow the proper process to be selected and to provide parameters that will be used for determining the presentation and delivery attributes of the output. For example, if the end-user selects a "Send to" option of printer, then the header contain a parameter indicating which printer the user selected. CF would then use this parameter to route the output to the correct printer. XML Tag Source Notes Field_BT_AX_ConnectorVersion Internal The version of DAXI installed when generated Field_AXVersion Internal The version of AX installed when generated Field_AX_AOSId Internal The server name and the port that the AOS is running on Field_AX_Instance_Name Internal The name of the AOS Instance Field_Object Enable Reports setting Field_ReportDesign Derived at runtime from report instance Field_Path Derived from Delivery Destination logic Folder where XML file was created Field_Filename Derived at runtime Name of the XML file created by AX Field_UserId Derived at runtime Logged on AX user Field_UserName Lookup in user table Full name AX user Field_GroupIds User s groups All group ids for which the user has memberships Field_GroupNames User s groups All group names for which the user has membership Field_User Lookup in user table If available Field_CompanyId Derived at runtime The company account for the current logged on AX user Microsoft Dynamics AX Connector Implementation Guide 45

46 46 APPENDIX A Processing Parameters XML Tag Source Notes Field_TestIndicator Enable Reports Table This is an indicator passed to trigger conditional logic for testing the BT-PDA process Field_RequestType Derived at runtime based on how the output scenario that initiated the request Values: Preview Default Adhoc Field_DeliveryMethod Derived at runtime based on the delivery method selected from the Printer Setup dialog OR if the report was invoked via a preview or default scenario the delivery method is determined by the logic for the scenario Values: Screen Printer Fax Process Field_DeliveryMethod_Code The delivery method Contains the code for the delivery method of the report. Screen: 0, Printer: 1, 2, Fax: 3, Document Process: 4 Field_DestinationName Derived at runtime from selected Delivery Destination Field_ProcessName If Delivery Method is Screen then this is the Screen Preview Process from the Enable Reports table or Defaults table. If Delivery Method is Process then this is the process selected in the Printer setup dialog Otherwise this is the Default Process from the Enable Reports table or the Defaults table 46 Microsoft Dynamics AX Connector Implementation Guide

47 APPENDIX A Processing Parameters 47 XML Tag Source Notes Field_ProcessProject Field_ScreenTempPath Field_ScreenTempFileName Field_PrinterNetworkId Field_PrinterCopies Field_ NetworkId Field_ AddressForm Field_ AddressesTo Field_ AddressesCC Field_ AddressesBCC Field_ Subject Field_ Body Field_FaxNetworkId Corresponding Process Project for the selected process. Lookup form the processes table. Derived at runtime from selected Delivery Destination. If Delivery Destination field is null, then use setting from Default table Derived at runtime from XML file name Derived at runtime from selected Delivery Destination If Request Type = Adhoc, then entered in Printer setup dialog else null Derived at runtime from selected Delivery Destination If Request Type = Adhoc, then entered in Printer setup dialog else null If Request Type = Adhoc, then entered in Printer setup dialog else null If RequestType = Adhoc, then entered in Printer setup dialog else null. If Request Type = Adhoc, then entered in Printer setup dialog else null If Request Type = Adhoc, then entered in Printer setup dialog else null If Request Type = Adhoc, then entered in Printer setup dialog else null. Derived at runtime from selected Delivery Destination Has data when Delivery Method = Screen Has data when Delivery Method = Screen Has data when Delivery Method = Printer Has data when Delivery Method = Printer Has data when Delivery Method = Has data when Delivery Method = Has data when Delivery Method = Has data when Delivery Method = Has data when Delivery Method = Has data when Delivery Method = Has data when Delivery Method = Has data when Delivery Method = Fax Microsoft Dynamics AX Connector Implementation Guide 47

48 48 APPENDIX A Processing Parameters XML Tag Source Notes Field_FaxNumber Field_FaxCoverSheetText If Request Type = Adhoc, then entered in Printer setup dialog else null If Request Type = Adhoc, then entered in Printer setup dialog else null Has data when Delivery Method = Fax Has data when Delivery Method = Fax Field_DesintationParameters Delivery Destinations Specify destination parameters Field_ReportParameters Enabled Reports Specify report parameters Field_TotalNumberInBatch Batch Processing Total number of documents in the batch Field_CurrentNumberInBatch Batch Processing Document s Order in the batch 48 Microsoft Dynamics AX Connector Implementation Guide

49 APPENDIX A Security Keys 49 Security Keys Security Keys are automatically installed during the Microsoft Dynamics AX Installation when the project XPO is imported. The Application Object Tree or the project can be inspected to verify that the Security Key is installed. To verify the Security Keys were installed 1 Click the Project icon on the top of the screen. 2 Expand the Shared folder. 3 Scroll down to BT_DPA _AX2009_Ver_3_0_15 and click to open the Project icon. 4 Once the Project is open, if the Security Keys are successfully installed, they appear on the Project s Application Object Tree. The Microsoft Dynamics AX components of the Integration include 5 security keys (1 parent key and 4 child keys). Microsoft Dynamics AX Connector Implementation Guide 49

50 50 APPENDIX A Security Keys The "Create!form, Setup" key can be used to restrict access to Create!form menu items on the Administration navigation pane. The "Create!form, Tables" key can be used to restrict access to Create!form tables. At a minimum, all users need "View" level access to the tables, but only administrators of the Create!form configuration settings need "Create" level access. The remaining keys ("Daily" and "Periodic") are not presently used. Refer to the Microsoft Dynamics AX Help for more information on Security Keys. 50 Microsoft Dynamics AX Connector Implementation Guide

51 APPENDIX A Glossary 51 Glossary AX: acronym for Dynamics AX as well as Axapta. AOT: acronym for Application Object Tree. BT-DPA: This is the generic acronym which stands for "Bottomline Technologies - Document Process Automation". This is used in the integration as a label prefix for components of the solution. form: the AX AOT objects representing UI windows integration: the short name for referring to delivered solution that is installed into an existing AX implementation. report: the AX AOT objects representing AX output intended to be printed Microsoft Dynamics AX Connector Implementation Guide 51

52 52 APPENDIX A Glossary 52 Microsoft Dynamics AX Connector Implementation Guide

53 Index INDEX I NDEX 53 A Appendix 45 C Chapter 2 Configuration 9 Create!form Designer 7 Create!form Director 7 Create!form Server 8 D Delivery Destinations 15 setting up 15 Document Process 36 Document Processes 10 setting up 10 E Enabling Reports 19 Enhanced Features 35 Enterprise Portal 42 F Folder Monitor 24 G Glossary 52 I Introduction 7 M Multi-select Preview Support 43 Microsoft Dynamics AX Connector Implementation Guide 53

54 54 INDEX P Print Management 36 Printing Batch Jobs 29 Processing Parameters 47 S Security Keys 51 Specifying Default Values 13 Specifying the XML Path 24 mapping directly to a Queue 26 Steps for Configuration 8 T To associate a report object with a project 19 To define a delivery destination 15 X XML File Naming Convention Microsoft Dynamics AX Connector Implementation Guide