Configuring the CourtView Web Service in Workflow - Integration for Courtview - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Premier - external - Standard - Essential - Premier - Standard - Essential

Integration for CourtView
Platform
OnBase
Product
Integration for Courtview
Release
Foundation 23.1
License
Premier
Standard
Essential

After creating the CourtViewService virtual directory, the CourtView web service must be mapped to the Call Web Service Workflow action so that the CourtView service knows when documents linked to CourtView have been archived in OnBase.

Tip:

For complete details on mapping actions and configuring Workflow, see the Workflow help files or module reference guide.

In the Call Web Service Workflow action configuration, configure the method exposed by the CourtView web service:

  1. Select Configure in the WSDL section. The WSDL dialog box is displayed.
  2. Select Use the specified WSDL Location from the WSDL drop-down list.
  3. Enter http://YourWebServer/courtviewservice/courtviewservice.asmx?wsdl in the field provided, where YourWebServer is replaced with the name of the actual Web server where the CourtView service is installed.
  4. Click OK.
  5. Select SOAP from the Protocol drop-down list.
  6. Select UpdateCourtView from the Method drop-down list.
  7. Click the Mappings button beneath the method diagram pane. The Mappings dialog box is displayed.
  8. Map the parameters of the Call Web Service action:

    • PropDBType: The CourtView database type (SQL or Oracle).

    • PropServer: The name of the ODBC used to connect to the CourtView server.

    • PropUid: The user name/ID of the account that can be used to access the CourtView database and the initial catalog.

    • PropPwd: The password that corresponds to the account in the uid.

    • PropDocketID: Variable value that contains the specific Docket ID for the specific action during the Workflow.

    • PropRejectReason: The exception reason response from CourtView.

    • PropInitialCatalog: This parameter is not used by the integration and should be left unmapped.

    Tip:

    For complete details on mapping actions and configuring Workflow, see the Workflow help files or module reference guide.