How to treat a Web Service-based Reference Event when moving a process definition from one environment to another

  • 24 February 2022
  • 0 replies
  • 7 views

Badge +3
 

How to treat a Web Service-based Reference Event when moving a process definition from one environment to another

KB001190

PRODUCT
K2 blackpearl
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.

 

Introduction

 

 

Issue:

When moving a process containing a Web Service-based Reference Event from one environment to another, the Reference Event still points to the source environment. This KB article shows how to treat the web-based Reference Event in order to ensure that the process definition can be deployed in the destination environment without any errors.

Solution:

The following steps show how to treat the Web-based Reference Event in order to ensure that the process definition can be successfully deployed in the destination environment:

    1. Create an Environment Field containing the URL to the Web Service. 
Note: The Environment Field should also exist in the destination environment with the Web Service URL for that environment.

In the Constructor step of the Reference Event, do the following:

    1. Set the URL property with the Environment Field. This will ensure that the source Web Service is used in the source environment and the destination Web Service is used in the destination environment.
    2. Set the UseDefaultCredentials property with the Inline Function - Logical > True
Note: The steps above should be performed for every Reference Event of the workflow process.

Below is an example of how to set the Inline Function:

 


0 replies

Be the first to reply!

Reply