ch implementation guide -...

Microsoft Dynamics AX Connector

Ch Implementation Guide

Microsoft Dynamics AX Connector Implementation GuideVersion 3.0Copyright Bottomline Technologies, Inc. 2008.All Rights ReservedInformation in this document is subject to change without notice and does notrepresent a commitment on the part of Bottomline Technologies. BottomlineTechnologies makes no warranties with respect to this documentation anddisclaims any implied warranties of merchantability or fitness for a particularpurpose.

Bottomline Technologies325 Corporate DrivePortsmouth, NH 03801Telephone: (603) 436-0700Fax: (603) 436-0300Email: [email protected]: www.bottomline.comSWR-CFIMDAX30-REF

v

. . . . .

T A B L E O F C O N T E N T S

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Document Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Setting up a Document Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Specifying Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Delivery Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Setting up Delivery Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Enabling Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Specifying the XML Path . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Folder Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Mapping Directly to a Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Printing Batch Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 3: Enhanced Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Print Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Document Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Fax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37E-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Screen Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Enterprise Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Multi-select Preview Support . . . . . . . . . . . . . . . . . . . . . . . . 43

Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

XML File Naming Convention . . . . . . . . . . . . . . . . . . . . . . . 46Processing Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Security Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Microsoft Dynamics AX Connector Implementation Guide v

vi. . .

. .

vi
Microsoft Dynamics AX Connector Implementation Guide

C H A P T E R

INTRODUCTION

NoteThe 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 eitherpackaged software solutions or custom legacy applications. This guidedescribes the specific configuration process developed by BottomlineTechnologies to ensure seamless document process automation withMicrosoft Dynamics AX.Required Create!form components include:

Create!form DesignerCreate!form Designer is used to design form projects, which Create!formServer merges with the output of your enterprise server. The form projectallows you to reformat and enhance the output of your enterprise,incorporating logos, images and drawing objects as well as formatted text.

Create!form DirectorCreate!form Director is used to design projects that Create!form Server splitsand 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

Chapter 1:Introduction

Microsoft Dynamics AX Connector Implementation Guide 7

. . . . .8 C H A P T E R 1 : I N T R O D U C T I O N

8

• Adding job ticket templates (JTTs) that determine various parameters used in processing by other Create!form products

Create!form ServerCreate!form Server is the central processor which handles the output from theenterprise server, and applies the appropriate project designed with eitherCreate!form Designer, Create!form Transform or Create!form Director. Theoutput from Create!form Server can be printed, faxed, e-mailed or archivedusing other Create!form products.

NoteFor a list of optional Create!form products contact a Bottomline Technologies customer service representative.

Steps for ConfigurationFollowing, 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 integrationcan be accessed via the Setup section of the Administration pane. Refer toChapter 2, Configuration, for more information on completing the first step:setting up a document process.


C H A P T E R

CONFIGURATION

This section outlines the steps necessary for configuring Microsoft DynamicsAX 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

Chapter 2:Configuration


. . . . .10 C H A P T E R 2 : C O N F I G U R A T I O N

Document Processes

10

Document ProcessesNoteUsers 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 aCreate!form Director project. Before a Create!form Director project is usedfor processing Microsoft Dynamics AX reports, it is mapped to a documentprocess, as described in the following section. First there must be at least one document process established as a default forreports that do not require a specific Director project. For a report thatspecifies the distribution logic, or document composition logic, then a uniqueDirector project is used. For example, an invoice may have delivery rulesbased on customer type.

Setting up a Document Process

Each document process is created with a user-friendly name and description sothat 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.


11

. . . . .C H A P T E R 2 : C O N F I G U R A T I O N

Document Processes

3 On the Setup tab, enter the following details:

Process Name A user-friendly name for the process

Process Description A meaningful description of the process

Process Project The name of the Create!form Director project running on the Create!form server



Specifying Default Values

12

Specifying Default ValuesDefault Values must be specified when they have not already been establishedas required values in a form.

To specify default values

1 In the Administration pane, expand Setup and then Create!form. 2 Click Defaults.


13


Specifying Default Values

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

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.

Default Document Process

The user-friendly name of the document process to use for processing output when no other process is selected.

Default Screen Preview Timeout

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.



Delivery Destinations

14

Delivery DestinationsNoteCheque 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 orgroups. The table below shows the methods of delivery currently supported.

Each delivery destination is associated with a method, and with specific usersand groups. This means that users can see and select only those destinationsthat are appropriate for their role. The attributes of a delivery method define the physical routing of the output sothat, for example, the XML output file can be directed to a particular networklocation, according to which user or group requests the output.

Delivery Method CodeNote 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.

Table 2.1 Delivery Methods

Destination DescriptionScreen Writes the PDF to a temporary file and displays it on the user's screen. Printer Sends the output to a printer. E-Mail Sends the output as an e-mail attachment. Fax Sends the output as a fax message. Document Process Processes the output by means of a Create!form Director project.


15



The BT prolog was modified in the following way:

Each of the delivery methods is coded as follows:

Each delivery method’s code corresponds to its enumeration values from theBT_DPA_Dest_Type base enum. Within Director_Generic_v3 these valuesare 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.

Prolog Parameter Form FieldField_Path Defaults or Delivery Destinations XML output pathField_ScrenTempPath Defaults or Delivery Destinations Screen Preview Temp

LocationField_Testing Enabled Reports Testing ParametersField_ProcessName Defaults or Delivery Destinations

(process) or Enabled ReportsDocument Process

Field_DeliveryMethod and Field_DeliveryMethod_Code

Printer Setup Form Delivery destination chosen in the Send to list

Field_ReportParameters Enabled Reports Report ParametersField_Destination Parameters Delivery Destinations Destination ParametersField_PrinterNetworkId Delivery Destinations Printer Network IDField_PrinterCopies Printer Setup Form Number of CopiesField_EmailNetworkId Delivery Destinations (E_mail) E-Mail Network ID

Delivery Method CodeScreen 0Printer 1Email 2Fax 3Document Process 4




16

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.


17



XML Output Location

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.

Restricted use 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.

Destination description

A description of the destination.

Destination Parameters

Specify additional parameters to the destination.

Screen Preview Temp Location

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.

*Printer Network ID

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.

*E-mail Network ID If the selected delivery method is E-mail, 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.




18

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.


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.




20

21


Enabling Reports

Enabling ReportsTo enable a Microsoft Dynamics AX report for processing by a Create!formDirector project, you must associate the Application Object Tree (AOT)report object with the project. Use the Enabled Reports feature to do this.

NoteReports 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.

NoteAOT 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.



Enabling Reports

22

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 TimeoutIs 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


23


Enabling Reports

necessary to increase the timeout period for complex projects that take a long time to process reports.

• Document ProcessThe user-friendly name of the document process to use for processing the selected report object.

• Report ParametersSpecify 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.

NoteThe 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.



Enabling Reports

24

25


Enabling Reports

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.

NoteIf 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.



Enabling Reports

26

27


Specifying the XML Path

Specifying the XML PathCreate!form Server retrieves XML files that are written directly to a sharedqueue.There are two places to specify XML paths within Microsoft DynamicsConnector: • 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 QueueTo establish an XML path mapped directly to a queueOn the Start menu, in the Printers and Faxes screen, right click the CFDirector printer and select Sharing.On the CF_Director Properties screen, in the Sharing tab, Click the OKbutton.

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 asshown.



Printing Batch Jobs

28

Printing Batch Jobs Before printing batch jobs using Microsoft Dynamics AX Connector, theserver 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.


29


Printing Batch Jobs

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.



Printing Batch Jobs

30

6 If the Utility screen appears grayed-out like the one below, then a new configuration will need to be created.


31


Printing Batch Jobs

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.



Printing Batch Jobs

32

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.


C H A P T E R

ENHANCED FEATURES

There are several features that Create!form’s Dynamics AX Integrationenhances in Microsoft Dynamics AX:• Print Management• Enterprise Portal• Multi-select Preview Support

Chapter 3:EnhancedFeatures


. . . . .34 C H A P T E R 3 : E N H A N C E D F E A T U R E S

Print Management

34

Print ManagementMicrosoft Dynamics AX Print Management is a robust feature that providesmany options for printing. Create!form’s Dynamics AX Integration enhancesthe existing print management feature by offering the following Create!formspecific print mediums:• document process • fax• e-mail • printer• screen preview capabilitiesThese modifications allow direct integration with Create!form Server forDynamics AX reports that are Create!form enabled. Refer to the MicrosoftDynamics AX Help for more information on Print Management/PrintMediums.

Document Process

Select the document process delivery destination by clicking on the Namedrop down menu.


35

. . . . .C H A P T E R 3 : E N H A N C E D F E A T U R E S

Print Management

FaxThe Print Management form for Create!form Fax maps to fax deliverydestinations.• 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.



Print Management

36

E-mailThe Print Management form for Create!form E-mail maps to e-mail deliverydestinations.• Select the e-mail delivery destination from the drop down menu.• Type who the e-mail is from in the From field.• Type who the e-mail is to in the To field.• If sending a copy of the e-mail to other parties, type their names into the CD

field.• If sending a blind copy of the e-mail to another party, type their names into

the Bcc field.• Type the Subject of the e-mail into the Subject field.• Type the text of the e-mail into the Body field.


37


Print Management

PrintThe Print Management form for Create!form Printer maps to printer deliverydestinations. Select the printer delivery destination by clicking on the Name drop downmenu.



Print Management

38

Screen PreviewNoteThe 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 previewdelivery destinations.Select the screen preview delivery destination by clicking on the Name dropdown menu.


39


Print Management



Enterprise Portal

40

Enterprise PortalDynamics AX's Enterprise Portal client is supported in the Create!formDynamics AX Connector. Enterprise Portal support is limited to legacyreports, i.e. reports that are also accessible in the standard AX Client. TheEnterprise Portal also uses special reports called Web Reports which are NOTsupported. Enterprise Portal reports are enabled in the same manner as regularreports via the Create!form Enabled Reports form.


41


Multi-select Preview Support

Multi-select Preview SupportCreate!form Dynamics AX Connector allows multiple documents to beviewed in a single preview PDF when performing a multi-select. To enablethe multi-select feature select the Combine into one Report checkbox.

NoteMicrosoft 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



Multi-select Preview Support

42

A P P E N D I X

APPENDIX

In this Appendix we will discuss the following:

• XML File Naming Convention• Processing Parameters• Security Keys• GlossaryThe following table describes the categories of components that are installedby the integration installers.

Appendix A


. . . . .44 A P P E N D I X A

XML File Naming Convention

44

XML File Naming ConventionThe filename of the XML files created by the integration are derived at runtime based on the following:

Value Source NotesReport Name Enable Reports TableSeparator Semicolon used as

separatorUser ID Derived at runtimeData-Time Stamp Derived at Runtime Semicolon as a

separatorOutput 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”


45

. . . . .A P P E N D I X A

Processing Parameters

Processing ParametersBefore 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 reportattributes to CF that will allow the proper process to be selected and toprovide parameters that will be used for determining the presentation anddelivery attributes of the output. For example, if the end-user selects a "Sendto" option of printer, then the header contain a parameter indicating whichprinter the user selected. CF would then use this parameter to route the outputto the correct printer.

XML Tag Source NotesField_BT_AX_ConnectorVersion Internal The version of DAXI

installed when generatedField_AXVersion Internal The version of AX installed

when generatedField_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 settingField_ReportDesign Derived at runtime from

report instanceField_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 userField_UserName Lookup in user table Full name AX userField_GroupIds User’s groups All group ids for which the

user has membershipsField_GroupNames User’s groups All group names for which

the user has membershipField_UserEmail Lookup in user table If availableField_CompanyId Derived at runtime The company account for

the current logged on AX user


. . . . .46 A P P E N D I X A


46

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 E-mail Fax Process

Field_DeliveryMethod_Code The delivery method Contains the code for the delivery method of the report. Screen: 0, Printer: 1, E-mail: 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 dialogOtherwise this is the “Default Process” from the Enable Reports table or the Defaults table

XML Tag Source Notes


47

. . . . .A P P E N D I X A


7
Field_ProcessProject Corresponding “Process Project” for the selected process. Lookup form the processes table.

Field_ScreenTempPath Derived at runtime from selected Delivery Destination.If Delivery Destination field is null, then use setting from Default table

Has data when Delivery Method = Screen

Field_ScreenTempFileName Derived at runtime from XML file name

Has data when Delivery Method = Screen

Field_PrinterNetworkId Derived at runtime from selected Delivery Destination

Has data when Delivery Method = Printer

Field_PrinterCopies If Request Type = Adhoc, then entered in Printer setup dialog else null

Has data when Delivery Method = Printer

Field_EmailNetworkId Derived at runtime from selected Delivery Destination

Has data when Delivery Method = Email

Field_EmailAddressForm If Request Type = Adhoc, then entered in Printer setup dialog else null


Field_EmailAddressesTo If Request Type = Adhoc, then entered in Printer setup dialog else null


Field_EmailAddressesCC If RequestType = Adhoc, then entered in Printer setup dialog else null.


Field_EmailAddressesBCC If Request Type = Adhoc, then entered in Printer setup dialog else null


Field_EmailSubject If Request Type = Adhoc, then entered in Printer setup dialog else null


Field_EmailBody If Request Type = Adhoc, then entered in Printer setup dialog else null.


Field_FaxNetworkId Derived at runtime from selected Delivery Destination

Has data when Delivery Method = Fax


. . . . .48 A P P E N D I X A


48

Field_FaxNumber If Request Type = Adhoc, then entered in Printer setup dialog else null


Field_FaxCoverSheetText If Request Type = Adhoc, then entered in Printer setup dialog else null


Field_DesintationParameters Delivery Destinations Specify destination parameters

Field_ReportParameters Enabled Reports Specify report parametersField_TotalNumberInBatch Batch Processing Total number of documents

in the batchField_CurrentNumberInBatch Batch Processing Document’s Order in the

batch



49

. . . . .A P P E N D I X A

Security Keys

Security KeysSecurity Keys are automatically installed during the Microsoft Dynamics AXInstallation when the project XPO is imported. The Application Object Treeor 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 securitykeys (1 parent key and 4 child keys).


. . . . .50 A P P E N D I X A

Security Keys

50

• 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 SecurityKeys.


51

. . . . .A P P E N D I X A

Glossary

GlossaryAX: acronym for Dynamics AX as well as Axapta.AOT: acronym for Application Object Tree.BT-DPA: This is the generic acronym which stands for "BottomlineTechnologies - Document Process Automation". This is used in theintegration as a label prefix for components of the solution.form: the AX AOT objects representing UI windowsintegration: the short name for referring to delivered solution that is installedinto an existing AX implementation.report: the AX AOT objects representing AX output intended to be printed


. . . . .52 A P P E N D I X A

Glossary

52

53

. . . . .I N D E X

I N D E XIndex

AAppendix 45

CChapter 2

Configuration 9Create!form Designer 7Create!form Director 7Create!form Server 8

DDelivery Destinations 15

setting up 15Document Process 36Document Processes 10

setting up 10

EEnabling Reports 19Enhanced Features 35Enterprise Portal 42

FFolder Monitor 24

GGlossary 52

IIntroduction 7

MMulti-select Preview Support 43


. . . . .54 I N D E X

54

PPrint Management 36Printing Batch Jobs 29Processing Parameters 47

SSecurity Keys 51Specifying Default Values 13Specifying the XML Path 24

mapping directly to a Queue 26Steps for Configuration 8

TTo associate a report object with a project 19To define a delivery destination 15

XXML File Naming Convention 46


ch implementation guide -...

Documents