BCUI - Suspense Search Export - AssigneeId Is A Number Instead Of BCUI UserID

(Doc ID 2308548.1)

Last updated on SEPTEMBER 25, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.17.0 and later
Information in this document applies to any platform.

Symptoms

On : 7.5.0.17.0 version, Customer Care

ACTUAL BEHAVIOR
---------------
When the Suspense payment search results are exported in Billing Care User Interface (BCUI), the assigneeId is returned as a number (i.e 3001) instead of a userID (i.e John.Doe).
The export functionality is enabled by extending the search template XML provided in the SDK. (CustomTemplatePaymentSuspenseWorker.java is removed, and customRegistry entries related to makePaymentSuspense are removed during export).

From the json:
{
"type": null,
"args": ["3001"],
"format": [],
"styles": [],
"types": [],
"name": "assigneeId"
}

EXPECTED BEHAVIOR
-----------------------
Instead of the value 3001, this should have been something like "John.Doe" the BCUI user's ID to whom this suspense payment has been assigned.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Make a suspended payment
2. Assign to a user ID for the suspended payment
3. Export the search template



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