My Oracle Support Banner

Fusion Global HR : SIGNER_NAME Does Not Populate Only In Document Records For Checklist E-Signature Task (Doc ID 2904348.1)

Last updated on NOVEMBER 01, 2022

Applies to:

Oracle Fusion Global Human Resources Cloud Service - Version 11.13.22.04.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.13.22.04.0 version, Global Human Resources

ACTUAL BEHAVIOR
---------------
Using the E-Signature functionality within Journeys. Have created a data model that populates the SIGNER_NAME value when testing through Word and OTBI, but SIGNER NAME does not show on the signed document that flows to the employee's document records.

This is the document record that is produced once the employee completes the E-Signature task and it flows to their document records.


EXPECTED BEHAVIOR
-----------------------
Signer Name is not populating after the employee signs.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. E-Signature Checklist Task > Data Model and RTF file are created > open the task > sign > do not see the employee sign reflected in the pdf document


Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.