Oracle DRM PSU 11.1.2.4.345 Test Results

Oracle released 11.1.2.4.345 Patch Set Update (PSU) under Patch 27200129 in late 2017. We gave an overview of the defects fixed in the PSU in this blog post.

After extensive testing in our Dev, Stage DRM environments, we discovered 3 new defects caused after the installation of PSU 345.

The derived JavaScript property which returns the node objects/structured arrays on certain data types was not working correctly on PSU .344 resulting in incorrect derived values, however Oracle introduced a few changes in PSU .345.

 

New Defect 1: DRM External Connection not displaying UNC Path after Upgrade

Overview: In the DRM 11.1.2.4.345, external connections field doesn’t display the path reference in the UNC path section for a “server file” type external connection.

Oracle has acknowledged the defect (SR 27363210).

Impact/Workaround: Although there are no workarounds to display the UNC path on .345, the underlying connection still exists at the database level and all the processes that use the external connection should work fine (Exports, Imports etc).

Recommendations: It is recommended to take the backup of all external connection details before the application upgrade for reference and/or update the External Connection descriptions as a reference of the UNC Path.

Reference of External Connection (Server File) On 11.1.2.4.345

1

Reference of External Connection (Server File) On 11.1.2.4.344

 2

New Defect 2: Batch client returns DRM-23198: The File name that was specified xxxxx cannot be used because it is rooted

Overview: If the export is set on the target to be a server file and in the batch-client call there is an outfile, an error will be displayed.

Oracle has acknowledged the defect (SR 27883804)

Impact/Workaround: Depending on the needs of the export in your respective DRM application, the following workarounds are available:

Workaround #1

  1. Copy the export to a new name
  2. Edit the target tab of the export setting it to Client file
  3. Save the export
  4. Edit the process to use the new name

Workaround #2

  1. Edit the target tab of the export setting it to Client file
  2. Save the export

 

Reference of the error:

Below is the error from the batch call for the above defect:

4/16/2018 4:15:41 PM – *** Oracle DRM Batch Client starting ***

4/16/2018 4:15:41 PM – Started job for Export Export Node Name Prefix Exception

4/16/2018 4:15:49 PM – An error of type ‘EServerError’ occurred while running Export. Error message: DRM-23198: The file name that was specified (‘E:\DRM_Staging\Export Node Name Prefix Exception.txt’) cannot be used because it is rooted.

4/16/2018 4:15:49 PM – => Error: DRM Server returned error: DRM-23198: The file name that was specified (‘E:\DRM_Staging\Node Name Prefix Exception.txt’) cannot be used because it is rooted.

4/16/2018 4:15:49 PM – *** Oracle DRM Batch Client stopping ***

 

New Defect 3: DRG Email Notifications not displaying the Sender Name

Overview: After upgrading to .345, the DRG email notifications no longer show the Sender Name.

Oracle has not acknowledged the defect yet.

Impact/Workaround: Sender Name will no longer be displayed in DRG notifications if configured in the application. Although this change doesn’t have any impact on DRG, in some cases depending on how Sender Name is used, users may find it inconvenient.

 

Major Changes to JavaScript Derived Objects

On the recent 11.1.2.4.345 PSU, Oracle made changes to the Objects (Derived Properties/Validations) using JavaScript in how they return the Node objects and structured arrays i.e: how properties with datatype: Global Node, Associated Node, Associated Group, Associated Nodes etc. return the value in derived JavaScript properties.

Change 1: For a given node, when the referred property value is blank/null, referred property data type returns node objects, now returns either a not handled null exception or null string based on the function(Prop/PropValue). The same scenario used to return a blank value on .344/previous patches.

Here are a few options to handle the null exception in the above cases on .345:

Option 1: When using .Prop Objects you should be able to explicitly call on the object’s .StringValue This should cast it successfully from the null object to the empty string, to allow for JS concatenation. As an example, you could use the following

var ACAF1 = node.Prop(“Custom.ACAF_Negative”).StringValue;

var ACAF2 = node.Prop(“Custom.ACAF_Positive”).StringValue;

var ACAF3 = node.Prop(“Custom.ACAF_Percent”).StringValue;

return ACAF1;

(or)

return ACAF1+’,’+ACAF2+’,’+ACAF3;

Option 2: In cases where you are using node.PropValue, you can implement a null object test either as an explicit logic branch or in-line, perhaps as a function. An example would be:

var ACAF1 = node.PropValue(“Custom.ACAF_Negative”);
var ACAF2 = node.PropValue(“Custom.ACAF_Positive”);
var ACAF3 = node.PropValue(“Custom.ACAF_Percent”);

return Null_Replace (ACAF1)+’,’+ Null_Replace (ACAF2)+’,’+ Null_Replace(ACAF3);

function Null_Replace(strValue)

{

if (strValue == null) return “”; else return strValue;

}

Change 2: If a derived JavaScript refers to any property with data type Global node or Associated node and has a node object assigned as the Property Value while the assigned node doesn’t exist in the hierarchy/version (Already deleted), the derived JavaScript will return null as opposed to the node object. This appears to be a good change as in such case, any node that is deleted should also be cleared if assigned as the Property Value.

4_LI

2 (i) Above – Reference on .345 where it returns null even when the property value has a node object assigned but doesn’t exist in the version.

4A_LI (2)2 (ii) Reference on .344 where it returns property value even when the property value has a node object assigned but doesn’t exist in the version. i.e., Roll Forward Account Property Value is AC_1051xx and AC_1051xx doesn’t exist.

 

By Sairam Arumalla, Oracle DRM Developer

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s