How Do I Generalize SharePoint URLs in a Process Model to Migrate from One Environment to Another?

Symptoms

The AgileParts in a SharePoint process model are designed to use hard-coded URL values. Thus, every time a process model is moved from one environment to another, the AgilePart’s configuration has to be opened, modified, and published to AgilePoint Server again.

Cause

The columns of the SharePoint libraries remains the same. However, the URL must be changed with the change of the environment: Development, Test, and Production.

The following example displays a list of URLs created for different environments:

• http://demo3Dev:8000/TimeOffRequest
• http://demo3Test:8888/TimeOffRequest
• http://demo3Prod:8080/TimeOffRequest

Resolution

1. In each of your environments, in Enterprise Manager, create a shared custom attribute with the same name, and a value that reflects the SharePoint URL you want to use for that environment.

   For example:

   Environment	Attribute Name	Attribute Value
   Development	SPServer	demo3Dev:8000
   Test	SPServer	demo3Test:8888
   Production	SPServer	demo3Prod:8080

   For more information, see Create a Shared Custom Attribute

2. While configuring the a SharePoint AgileShape in your development environment, wherever a SharePoint URL is required, enter the literal URL.

   The literal URL is required for AgilePoint to connect to and retrieve data from SharePoint at design time.

3. Finish setting up the SharePoint AgileShape using the literal URL.
4. Once the configuration is complete, then modify the SharePoint URL to use the shared custom attribute you created.

   Example:

   http://${SPServer}/TimeOffRequest

   • Do not change the settings for any other configuration fields. If you do this with a URL that includes a shared custom attribute, you could invalidate the configuration.
   • Do not click the Connect button. You cannot connect from Envision to a URL that uses a shared custom attribute.

At runtime, AgilePoint Server replaces the value of the shared custom attribute ${SPServer} in the URL. Once the appropriate values are set for the custom attribute in each environment, AgilePoint can generate the correct, environment-appropriate URL.