E-AWE: Workflow Parameter Configuration That Include Slash ( / ) In Transaction Name For Generation Of URL Sent By AWE In Email Are Unencoded, (Doc ID 2069915.1)

Last updated on OCTOBER 23, 2015

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.54 and later
Information in this document applies to any platform.

Symptoms

On : HCM 9.2 version, AWE Workflow


When an email gets sent to users by AWE, parameters in the URL are not encoded. For example, the email URL may include &KEY=test/slash, instead of &KEY=test%2Fslash.   ( %2F is the encoding for the / character)   This example is using the HR_TRANSACTIONS category for Delegation of AbesnceManagement transaction as an example,

When an email gets sent to users by AWE, parameters in the URL should be encoded.

The issue can be reproduced at will with the following steps:
1. Navigate to Set Up HCM > Common Definitions > Self Service > Workflow Transactions.
    Insert new row, enter MY#PARAMETER/TEST as the Transaction Name, choose HR_TRANSACTIONS as the Category, My#Parameter/Test as the Description, AbsenceManagement as the Approval Process ID, and tick Delegate Approvals check box.

2. Navigate to Set Up HCM > Common Definitions > Delegation > Configure Transactions.
    Choose Add a New Value, enter MY#PARAMETER/TEST for the transaction name and choose Approve for the Transaction Type.

3. Navigate to Peopletools -> Security -> User Profile and Change Email Address for user HCRUSA_KU0101 to an address that can receive email.

4. Log in as HCRUSA_KU0020 and navigate to Self Service > Manage Delegations and create a delegation.
    Select check box for My#Parameter/Test in Delegate Transactions grid, click Next.
    Select radio button for Cynthia Adams/KU0101 in Choose Delegate grid, click Next.

5. Check Email sent to Cynthia Adams (HCRUSA_KU0101)

Notice the link in the email includes &TRANSACTION_NAME=MY#PARAMETER/TEST . It should be &TRANSACTION_NAME=MY%23PARAMETER%2FTEST

With the parameters not encoded correctly and when a link is clicked that does a switch from a Classic Component to a Fluid (MAP) page, the parameters do not get passed correctly to the MAP URL which prevents the page from loading. This is an issue that has come to light in testing during reporting site upgrade from HR 9.0 to HR 9.2. It will affect ALL managers who approve a custom Workflow transaction, which includes a key field whose value ALWAYS includes a forward slash.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms