Table of Contents

How To Implement Directed Web Access

About Directed Web Access

Directed Web Access (DWA) allows anyone with Internet Explorer and email access to perform a Process Commander assignment, even if they do not have a Process Commander operator ID.  Assignments sent to such outside parties are called external assignments.

When Process Commander creates an external assignment , it sends an email message to the assignment recipient. The email contains a link to a specially formatted URL, as shown in the red circle.

DWA Email

When the recipient clicks this link, a browser session opens and submits a one-time-only signature token to the Process Commander server. Process Commander evaluates the token to authenticate the external user and displays the assignment in her browser window. The user completes and submits the requested information, which ends the requestor connection. The link can be used only once.

How to Implement Basic Directed Web Access

Complete these steps to implement basic DWA in your application:

  1. Verify Prerequisites for DWA
  2. Create an Operator ID for the External User
  3. Configure the URL for your Process Commander System
  4. Create a Correspondence Rule
  5. Call a DWA Flow

The following sections describe these steps in detail.

1: Verify Prerequisites for DWA

Before you implement DWA on your system, verify that the following prerequisites are in place:

  • Process Commander is configured to send outgoing e-mail.
  • Process Commander is configured for SSL (optional).
  • The flow that will use DWA already exists.
  • The external user you want to send the assignment to is a party in the flow's work object.

2: Create an Operator ID for the External User

Complete the following steps to create an operator ID for the external user:

  1. Create a new Operator ID that starts with the reserved word External.
  2. On the Operator tab, specify an access group, organization, and division that provides the external operator with the ability to complete the external assignment. For security reasons, reference an access group that provides only the minimal RuleSet Versions that the external user needs to complete the assignment.

 

  1. Click the Security tab. Set the License Type field to Invocation. Leave the Use external authentication? check box blank.

3: Configure the base URL

Complete the following steps to configure your system's base URL:

  1. Locate the Data-Admin-System-Settings instance named Pega-ProCom.PublicLinkURL. This instance contain a URL that identifies your Process Commander system.
  2. Set the Value field to the URL that you want to appear to external users. (For example, the URL may reference a proxy server rather than your actual Process Commander server.)

 

The ExternalInstructions HTML fragment rule, referenced in the correspondence rule that you create in the next step, contains code that uses this value as part of the DWA URL.

4: Create a Correspondence Rule

Complete the following steps to create a correspondence rule that contains the DWA URL:

  1. Create a correspondence rule (Rule-Obj-Corr type).
  2. Set the Correspondence Type field to email.
  3. Choose a name for the correspondence rule that begins with the word "External".
  4. In the HTML Source field, use an include JSP tag or directive to copy in the standard correspondence fragment named ExternalInstructions.Emailat the point where you want the DWA URL to appear.:

     

 

5: Call a DWA Flow

V5.2 includes two standard flow rules that support DWA:

  • Work-.EngageExternalQuick
  • Work-.EngageExternalInformation

The flow that your application calls determines the type of processing used for the external assignment:

  • For synchronous processing, where flow execution waits until processing on the external assignment is complete before continuing, use the standard Work-.EngageExternal flow action, which starts the EngageExternalQuick flow.
  • For asynchronous processing, where the calling flow continues execution while the external assignment is pending, add a spin-off shape in the flow that starts the Work-.EngageExternalForInformation flow.

For a detailed description of these standard flows, see How to extend and tailor basic Directed Web Access.

Calling the Work-.EngageExternalQuick Flow

To call the Work-.EngageExternalQuick flow, add the EngageExternal local flow action to an existing assignment. Complete the following steps to call the flow.

Note that if you plan to copy and modify this flow action, the URL for the external assignment must be static — not a URL that is generated or altered by JavaScript or other runtime processing. Because of this restriction, the flow action cannot use AJAX, dynamic select controls, or SmartPrompt.

  1. Include the standard local flow action EngageExternal (or another you have based on that one) as a local flow action in an assignment. When selected, this starts a flow execution of the standard flow Work-.EngageExternalQuick.

 

  1. Test the flow. At runtime, the operator uses the EngageExternal flow action to identify the party (or email-addressee) to receive the email correspondence, enter a subject line, and select the correspondence rule.

Adding a Spin-Off Shape That Calls the Work-.EngageExternalForInformation Flow

Complete the following steps to call the Work-.EngageExternalForInformation flow:

  1. Open a flow for editing.
  2. Add a Spin-Off shape in the appropriate location.
  3. Set the value of the Flow Rule field, located in the Spinoff Properties form, to .EngageExternalForInformation.
    The Flow Rule Field
  4. Test the flow.
Suggest Edit

58% found this useful

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.