ID 2430452.1 The Basics of Transaction Console v3.2

The Basics of Transaction
Console
Cloud HCM Common Feature Release Updates 22B
March 2022, Version 3.2

Copyright © 2023, Oracle and/or its affiliates
1 The Basics of Transaction Console / Version 3.2

Copyright © 2023, Oracle and/or its affiliates / Public
Disclaimer
This document in any form, software or printed matter, contains proprietary
information that is the exclusive property of Oracle. Your access to and use of
this confidential material is subject to the terms and conditions of your Oracle
software license and service agreement, which has been executed and with
which you agree to comply. This document and information contained herein
may not be disclosed, copied, reproduced or distributed to anyone outside
Oracle without prior written consent of Oracle. This document is not part of your
license agreement nor can it be incorporated into any contractual agreement
with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist
you in planning for the implementation and upgrade of the product features
described. It is not a commitment to deliver any material, code, or functionality,
and should not be relied upon in making purchasing decisions. The
development, release, and timing of any features or functionality described in
this document remains at the sole discretion of Oracle. Due to the nature of the
product architecture, it may not be possible to safely include all features
described in this document without risking significant destabilization of the code.
Safe Harbor Statement

The preceding is intended to outline our general product direction. It is intended
for information purposes only, and may not be incorporated into any contract. It
is not a commitment to deliver any material, code, or functionality, and should
not be relied upon in making purchasing decisions. The development, release,
and timing of any features or functionality described for Oracle’s products
remains at the sole discretion of Oracle.
Note: In the images or examples included in this document regarding: user

details, company names, addresses, emails, and/or telephone numbers
represent a fictitious sample of data (based upon made up data used in a demo
environment). Any similarity to actual persons, living or dead, is purely
coincidental and not intended in any manner.

Change History
Date Release Description

July 5, 2021 21B Added:
12 Archived Transaction Summary
8.2.1.1 Days Parameter
8.2.1.2 Security Role Information
8.2.1.3 Execution Options
July 5, 2021 21C changed 7.1 Pending and Completed Detail  Approval History
July 5, 2021 21C Updated Error Diagnostic Report in 7.2.1 Instructions
July 5, 2021 21C Refreshed attachments:
hrc_arm_process_vl.xlsx
wftaskmetadata.xlsx
October 1, 2021 Any Updated 7.1 Pending and Completed Detail  Approval History
added 13 Frequently Asked Questions
March 15, 2022 22B Updated 8.2.2 Archive Transaction Console Completed Transactions 8.2.2.3
Execution Options
Added 7.4 Approval Transaction Cache Corrector
Updated Appendix C
Added attachment TAC Seeded Console Fault Details.xlsx

Table of Contents
OVERVIEW ........................................................................................................................................................................... 7
Security Role Information ..................................................................................................................................................... 7

TRANSACTION SUMMARY ................................................................................................................................................... 8
1 TRANSACTION MANAGER ..................................................................................................................................................... 8
1.1 Checkbox ............................................................................................................................................................................... 8
1.2 Name .................................................................................................................................................................................... 8
1.3 Process Name ........................................................................................................................................................................ 8
1.4 Status .................................................................................................................................................................................... 9
1.5 Approver (aka Assignees on 21D) ........................................................................................................................................... 9
1.6 Submitted On ...................................................................................................................................................................... 10
1.7 Submitted By ....................................................................................................................................................................... 10
1.8 Issue Priority ........................................................................................................................................................................ 10
1.9 Issue Assignee...................................................................................................................................................................... 10
2 FACETED SEARCH .............................................................................................................................................................. 11
2.1 Global Search....................................................................................................................................................................... 11
2.2 Defaulted Filter .................................................................................................................................................................... 11
2.3 Hide Filters .......................................................................................................................................................................... 11
2.4 Filters Configurable Options ................................................................................................................................................. 11
2.5 Preset Search Criteria........................................................................................................................................................... 11
2.5.1 Status ........................................................................................................................................................................... 11
2.5.2 Issue Priority ................................................................................................................................................................ 12
2.6 Name .................................................................................................................................................................................. 12
2.7 Process Name ...................................................................................................................................................................... 12
2.8 Submitted By ....................................................................................................................................................................... 12
2.9 Person Number.................................................................................................................................................................... 12
2.10 Advanced Filters ................................................................................................................................................................ 12
2.10.1 Issue Date................................................................................................................................................................... 12
2.10.2 Issues.......................................................................................................................................................................... 13
2.10.3 Issues Assigned To ...................................................................................................................................................... 13
2.10.4 Issue Type................................................................................................................................................................... 13
2.10.5 Assigned To ................................................................................................................................................................ 13
2.10.6 Approver .................................................................................................................................................................... 13
2.10.7 Submitted By .............................................................................................................................................................. 13
2.10.8 Search Comments ....................................................................................................................................................... 13
2.10.9 Task Number .............................................................................................................................................................. 13
2.10.10 Transaction ID........................................................................................................................................................... 13
2.11 Saved Search...................................................................................................................................................................... 14
3 ACTIONS ........................................................................................................................................................................ 15
3.1 Reassign .............................................................................................................................................................................. 15
3.1.1 Reassign to User ........................................................................................................................................................... 15
3.1.2 Reassign to Parallel Participants ................................................................................................................................... 16
3.1.3 Send to Initiator ........................................................................................................................................................... 17
3.2 Withdraw ............................................................................................................................................................................ 17

3.3 Recover ............................................................................................................................................................................... 17
3.4 Terminate Process ............................................................................................................................................................... 17
3.5 Approve / Reject .................................................................................................................................................................. 17
3.5.1 Override Approval ........................................................................................................................................................ 17
3.6 Resubmit ............................................................................................................................................................................. 18
3.7 Download ............................................................................................................................................................................ 18
3.8 Alert Initiator On Error ......................................................................................................................................................... 18
4 PRIORITY MENU ............................................................................................................................................................... 19
5 TRANSACTIONS FROM: DATE STRING PARAMETER .................................................................................................................... 19
6 REFRESH ON DEMAND ....................................................................................................................................................... 19
7 TRANSACTION DETAIL ........................................................................................................................................................ 20
7.1 Pending and Completed Detail ............................................................................................................................................. 20
7.2 Error Details......................................................................................................................................................................... 23
7.2.1 Instructions .................................................................................................................................................................. 23
7.3 Interaction with Events in Transaction History Timeline ........................................................................................................ 26
7.4 Approval Transaction Cache Corrector.................................................................................................................................. 26
7.4.1 Opt In Feature .............................................................................................................................................................. 26
7.4.2 Security Role Information ............................................................................................................................................. 27
7.4.3 Worked Examples......................................................................................................................................................... 27
8 TAC SCHEDULED PROCESSES ............................................................................................................................................... 31
8.1.1 Opt In Feature .............................................................................................................................................................. 32
8.2 Archive Transactions ............................................................................................................................................................ 33
8.2.1 Worked Example .......................................................................................................................................................... 33
8.2.2 Archive Transaction Console Completed Transactions .................................................................................................. 34
8.2.2.1 Days Parameter ......................................................................................................................................................... 34
8.2.2.2 Security Role Information .......................................................................................................................................... 35
8.2.2.3 Execution Options...................................................................................................................................................... 35
8.2.2.4 Approval Notification Archive Dashboard .................................................................................................................. 36
8.2.3 FYI Notifications Expiration Period................................................................................................................................ 37
9 TAC ALERTS .................................................................................................................................................................... 39
9.1 Alert Initiator On Error ......................................................................................................................................................... 39
9.1.1 Transaction Manager Manual Alert .............................................................................................................................. 39
9.1.2 Approval Rules Automated Alert .................................................................................................................................. 39
9.2 TAC_RESUBMIT_ALERT ........................................................................................................................................................ 42
10 ANALYTICS .................................................................................................................................................................... 43
11 APPROVAL DELEGATION ................................................................................................................................................... 47
11.1 Category ............................................................................................................................................................................ 48
11.2 Allow this user to approve their own transaction ................................................................................................................ 51
12 ARCHIVED TRANSACTION SUMMARY ................................................................................................................................... 52
12.1 Archive Transaction Details Page ........................................................................................................................................ 52
13 FREQUENTLY ASKED QUESTIONS ......................................................................................................................................... 54
APPENDIX A ....................................................................................................................................................................... 57
RESUBMIT ACTION SUPPORTED PROCESSES................................................................................................................................. 57
APPENDIX B ....................................................................................................................................................................... 58
RESOURCES ....................................................................................................................................................................... 58

APPENDIX C ....................................................................................................................................................................... 59
WHAT’S NEW .................................................................................................................................................................... 59

Overview
Transaction Console (TAC) is a modernized application designed for administrators to monitor the entire lifecycle of
transactions, including administrative actions to recover failed processes and enable Alert Initiator on Error.
You can navigate from Tools — Transaction Console for below work areas:
1. Transaction Summary (a.k.a. Transaction Manager)
2. Analytics
3. Approval Rules
4. Archived Transaction Summary
Security Role Information

Use the delivered job role Human Capital Management Application Administrator
(ORA_HRC_HUMAN_CAPITAL_MANAGEMENT_APPLICATION_ADMINISTRATOR_JOB).
or
Grant your custom roles with these functional privileges:
• Perform HCM Approval Transaction Actions (PER_PERFORM_APPROVAL_TRANSACTION_ACTIONS_PRIV)
• Review Approval Transactions (PER_REVIEW_APPROVAL_TRANSACTIONS_PRIV)
• Manage Approval Rules (PER_MANAGE_APPROVAL_RULES_PRIV)
• Review Archived Approval Transactions (PER_REVIEW_ARCHIVED_APPROVAL_TRANSACTIONS_PRIV)
Add HCM Transaction Administration Transaction Analysis Duty
(FBI_HCM_TRANSACTION_ADMINISTRATION_TRANSACTION_ANALYSIS_DUTY),
also Archived HCM Approval Task Transaction Analysis Duty
(FBI_ARCHIVED_HCM_APPROVAL_TASK_TRANSACTION_ANALYSIS_DUTY) for OTBI analyses.
and/or
Use the delivered SOA operator Role (SOAOperator) or SOA Admin Role (SOAAdmin) for higher level operations.
plus
Review HCM Approval Transactions as Administrator (ORA_PER_REVIEW_HCM_APPROVAL_TRANSACTIONS);
Review HCM Approval Transactions as Business User (ORA_PER_REVIEW_HCM_APPROVAL_TRANSACTIONS_
AS_BUSINESS_USER)
- see Securing Workflow Transactions (Doc ID 2430452.1) for details.

Transaction Summary
The TAC default landing page:
1 Transaction Manager
A tabular display of the transaction details with following columns:
1.1 Checkbox
You can select a transaction or select from the header for all transactions so to take an action.
1.2 Name
Object Name of the transaction. This hyperlink can be:
2. The Person Name for Promotion, New Work Relationship processes etc.
3. The Grade Name, a business object.
4. Same as the Process Name, such as Approve Job Requisition.
5. When click, you will open the transaction detail page. See 7 Transaction Detail for more info.
1.3 Process Name
It is the Name of the flow to which the transaction belongs. See the paper The Basics of Approval Rules 2 Process
Name for details.

1.4 Status
Depending on the status of the transaction, an icon and mouse over description will display. See mapping of Status
Category vs. Console Status:
Draft: (Saved)Draft
In Progress: Auto Recovery, (Pending, Inflight)In Progress, Stuck, Submitted
Completed: (Successfully)Completed
Failed: (Errored)Failed
1.5 Approver (aka Assignees on 21D)

To whom the transaction is currently pending approval. Equivalent to Assigned to or Assignee in BPM Worklist.
Worked Example: Single Participant Multiple AORs Approval (link) that all representatives are listed.

1.6 Submitted On
The date of the transaction submitted by requester for approval.
1.7 Submitted By
Name of the requestor.
1.8 Issue Priority

Priority of the issue in case of a failed transaction.
1.9 Issue Assignee

The failed transaction has been assigned for the attention of a named individual.

2 Faceted Search
Faceted Search supports Saved Search, in which the filter criteria will improve system performance thereby user
experience. See 2.11 Saved Search.
2.1 Global Search

You can enter any keyword of the Name or Process Name columns in the search for a summary query.
2.2 Defaulted Filter

In current release, the filter is defaulted to Failed status. As it demands immediate attention. Remove any status filter
to get a summary of all statuses.
2.3 Hide Filters

Show Filters is the default display option. Click Hide Filters for a wider table space.
2.4 Filters Configurable Options

Alternative options also include Expand All, Collapse All, Reset, and the gear icon Configure for Self or Configure
for Others. For the current user login session only, choose Configure for Self. For site level setting, choose
Configure for Others and Activate Sandbox.
In the Personalize Saved Search: Default Criteria popup, the default filters are checked. Those unchecked are
advanced filters, see 2.10 Advanced Filters. You can reorder, enable or disable filters and click Save when done.
See What’s New for How-to personalize saved searches, also 2.11 Saved Search.
2.5 Preset Search Criteria

2.5.1 Status
By clicking Clear or removing the Default Filter: Failed, you will get a full summary of all transactions that are not yet
archived. Click Status link to filter the query results.
Auto Recovery: The transaction encountered a failure on SOA side that trying to recover from it.
Completed: Transaction Completed.

Draft: The transaction is saved by the Initiator and not yet submitted.
Failed: Error occurred while the transaction processing was unsuccessful.
In Progress: Transaction being processed by SOA and is pending in the approval queue for approver action.
Stuck: Transaction submitted that is yet to be processed by SOA.
Submitted: Transaction submitted by a User. Intervention is not required.
Also see 1.4 Status.
2.5.2 Issue Priority

Based on the Urgent-Important Matrix, you can assign a priority to a failed transaction so that you can query all failed
transactions in that priority order.
2.6 Name
A text field where you can enter the string to find a match by scanning through the transaction summary.
2.7 Process Name

A text field where you can perform specific keyword search. Also see Basics of Approval Rules Appendix A Process
Names vs. BPM Tasks.
2.8 Submitted By
Submitted By text field accepts full or partial Display Name, having all transactions from one user available at a
glance.
2.9 Person Number

This filter is to query the person number of whom effected by the transaction.
Worked Example: GBI257 is the person number of Veda Moss. When GBI257 is filtered then all transactions in
respect to Veda Moss will return.
2.10 Advanced Filters

2.10.1 Issue Date
Issue Date exhibits preset search criteria, for example: Last 7 days, Last 14 days, Last 30 days, Range (specify). The
filter helps to retrieve transactions based on the date the issue is created. Best to use with 2.10.2 Issues.

2.10.2 Issues
Based on the Issue assignee, this filter presents two preset search criteria: All Issues, My Issues.
2.10.3 Issues Assigned To

Enter this filter with display name to populate all failed transactions to whom the transaction is assigned, see Issue
Assignee column in Transaction Manager. Also see 7.2 Error Details re: Assigned To.
2.10.4 Issue Type

Worked Example: Enter BPEL in the text field to retrieve all transactions with issues of type BPEL reported.
2.10.5 Assigned To
This filter accepts a partial name and returns the transactions based on the person to whom the transaction is
currently assigned to, and then populates the display name onto the Approver column in Transaction Manager.
2.10.6 Approver
This filter returns the transactions either completed or in progress status that have been approved or rejected by said
user. Note: This text field accepts username only, because display name will incur system performance issue.
2.10.7 Submitted By
2.10.8 Search Comments
Available to failed transactions, Admin user can click Actions for the Add Comments option. Thereafter you will
have the ability to search by service request or bug or helpdesk ticket number.
2.10.9 Task Number

This filter allows you to find the transaction using its task number, see p.8 worklist notification.
2.10.10 Transaction ID
The text field accepts multiple Transaction IDs, which are separated by a comma. There can be cases where users
are required to perform mass actions on bulk transactions.

2.11 Saved Search
The Saved Search feature allows users to conserve the frequently used search criteria. Default Criteria is seeded.
You can mix and match the default and advanced filters then click Save to enter a Name for the common search
criteria. Thereafter you can change the setting via Manage Saved Searches option. Also see 2.4 Filters
Configurable Options.

3 Actions
A user, depending on function security, can perform set of actions on a transaction. The set of actions in this table
are available on both the Main and Detail pages:
EnabledDisabled Selective Task (see 3.5.1 Override Approval)
Actions Withdraw Recover Reassign Add Terminate Approve Reject Override Resubmit
Status Comment Approval
AUTO see 3.6 Resubmit
        
RECOVERY
COMPLETED         based on
status and
profile options
DRAFT         
FAILED only for only for only for      

invalid approval invalid
approver process participant
failure
IN      (disabled only for only for  
PROGRESS for FIN) assignee assignee
login login
STUCK         if profile

option is
enabled
SUBMITTED         
On multiple selection of checkboxes in the transaction table, the least common set of actions (applicable for the
selected transactions) are rendered. Be cautious when considering mass action, you should evaluate each transaction
individually for the most appropriate action.
The Download action is only available on the Main page.
Note: An error will be thrown for an action selected in TAC of which task level action is disabled in BPM task
configuration.
3.1 Reassign
To change the Assignee, the Reassign action is available for an inflight transaction. Two options you can choose:
3.1.1 Reassign to User

You can find a single user either by Display Name or Username.

3.1.2 Reassign to Parallel Participants
Worked Example: Configuring Parallel Participants Voting Approval Rule (post)
The Admin User can replace approvers with another user via the Reassign action.
The Reassign action renders once new instruction is complete.
The change is trackable.

3.1.3 Send to Initiator
Use case: return transaction for correction.
3.2 Withdraw
The Withdraw option will pull out the transaction from current assignee and mark the transaction as completed
(equivalent to Cancel and End). The exact Withdraw action in BPM Worklist.
3.3 Recover
The Recover action is available to a failed transaction in case of a BPEL failure. When the transaction is recovered, its
status will change back to Pending. If recover is complete without correction, the transaction retains its failed status;
in this case the existing issue record is closed with a new issue record created for the transaction.
Add SOA operator Role (SOAOperator) or SOA Admin Role (SOAAdmin) to your user account or the SOA-operated
Recover action will not work.
3.4 Terminate Process

The Terminate Process (equivalent to Abort and End) option is only available to Admin User - that action leaves an
audit trail.
By ending the transaction, the requestor can then resubmit a fresh one. In some cases, this action can unlock a page
in read only mode amid approval pending queue, such as Approve Performance Goal.
Post Terminate Process action, the transaction will be marked as completed. Hence this action is not available to a
transaction which is already in a completed status.
Add SOA operator Role (SOAOperator) or SOA Admin Role (SOAAdmin) to your user account.
3.5 Approve / Reject

The Approve/Reject actions are secure by function privileges, see Enable Transaction Security in Securing
Workflow Transactions (Doc ID 2430452.1) for setup details.
3.5.1 Override Approval

The Force Approval action is currently available to Talent Management Approve Performance/Development Goal
and Approve Performance Document only - no notifications to users. This is normally a HR Helpdesk ticket to
approve on behalf so the last user update remains intact, no loss of data.

3.6 Resubmit
The Resubmit action is available to terminated or stuck transactions. Here’s a use case: the ability to re-initiate the
transaction approval process using a new routing rule at the time of re-submission so to correct the last task
outcome. See Appendix A for the list of supported processes.
Conflict check: If any existing Approved/Error/Pending/Saved/Bypassed Approval transaction which potentially
contradicts with the transaction being resubmitted, then it is assumed that a conflict prevails hence no resubmit
option.
An Opt In Feature by setting the Site level profile option value to TRUE. Navigate to Setup and Maintenance –
Task: Search: Manage Administrator Profile Values – Code: HCM_TAC_RESUBMIT_ACTION.
From 21A onwards, Resubmit option is also available to transaction with either Withdrawn/Expired/Rejected status
providing that both profile options HCM_TAC_RESUBMIT_ACTION and
HCM_TAC_RESUBMIT_FOR_ALL_NON_APPROVED are enabled.
3.7 Download
You can export the transaction summary into csv file via the Download action. Either selectively check the
transactions or no checkbox selection for a full download. The csv file contains additional information that you will
need for troubleshooting:
Name|Header|Status|Process Name|Submitted On|Issue Assignee|Submitted By|Transaction ID|Approvers|Assigned
On|Issue Title|Issue Type|Issue Date|Issue Description|Resolution|Task|Rule|Comment
See 2 Process Name in The Basics of Approval Rules (Doc ID 2430452.1) for more details.
3.8 Alert Initiator On Error

Available to Failed transactions only, with this action you can optionally send an error notification to the initiator that
includes a link to resubmit the transaction if applicable. Also see 9.1 Alert Initiator On Error for configuration
options.

4 Priority Menu
This is to set the priority to the issue for a failed transaction.
5 Transactions From: Date String Parameter
Query parameter is based on Transaction Submission Date.
6 Refresh On Demand
Users can click once the Refresh icon to initiate the process on Transaction Summary landing page. New statuses will
automatically be shown, definitely no need to constantly press for refreshes.
Also see 8.1 Refresh Transaction Administrator Console Transaction Status and 8.1.1 Opt In Feature for more
details.

7 Transaction Detail
On Transaction Manager results table, click the Name hyperlink for specific details.
7.1 Pending and Completed Detail

Information you can find on this page:
 Status: status of the transaction, also see 1.3 Status for info.
 Process Name: the process name to which the transaction belongs, also see Appendix A Process Names vs. BPM
Tasks in The Basics of Approval Rules.
 Transaction ID: name of the transaction before the transaction id

 Submitted On: date on which the transaction was initiated
 Submitted By: display name of the requestor

 Approval History: approval chain dynamically-regenerated during the Refresh Transaction Administrator Console
Transaction Status. Specific to HCM, the improved Approval History Component exhibits the past, present and
future approval stages of the transaction. Parallel Participants and Static Approval Group are supported.
Note: FYI information is not displayed in the approval history.
To make Future Approvals invisible because of confidentiality reasons and system performance issue, create
profile option DISABLE_ADVANCED_TAC_FUTURE_APPROVALS_DISPLAY and set its value to true.
(Navigation) FSM > Search: Task: Manage Profile Options

Profile Option Code DISABLE_ADVANCED_TAC_FUTURE_APPROVALS_DISPLAY
Profile Display Name DISABLE_ADVANCED_TAC_FUTURE_APPROVALS_DISPLAY
Application HCM Central Components
Module HCM Common Architecture
Description Profile option to disable rendering of future approvals
Start Date 1/1/1951
Site Level  Enabled
 Updateable
(Navigation) FSM > Search: Task: Manage Administrator Profile Values

Profile Option Code Site Level
DISABLE_ADVANCED_TAC_FUTURE_APPROVALS_DISPLAY true


 Comments and Attachments: data in chronological order entered by the requestor upon submission and
subsequent notification interactions updated via Actions: Add Comments, Add Attachment and from the Approve /
Reject actions:
All the Comments and Attachments submitted by Initiator or Approver or both will be shown in "Comments and
Attachments" component regardless of which state the transaction is in. User's Display Name printed.
• Comments are stored in plain text format.
• URL attachment is a redirect link, which will open in a new tab.
• Document attachment displays as file attachment downloader link.
Note: Comments and Attachments component is not available to failed transactions.
 Issue Comments: showing comments added by Admin User of the latest issue associated with the transaction.
Also see 2.10.8 Search Comments.
 Action menu: available actions for this transaction.

 View Transaction History: on click user will be redirected to a timeline component at the bottom of the page:
Note: The View Transaction History, available to non-bypass approvals, is disabled when the transaction has Bypass
Approvals enabled. Also see 7.3 Interaction with Events in Transaction History Timeline.
This timeline component captures and represents the following events as a part of transaction summary till date:
Submission: This event represents the date and time of the submission of the transaction. This is the first event
represented in the timeline.
Error: This event represents any fault that has been encountered in the transaction at any time during the flow of
it. This event in the timeline can be interacted with. Click an event to see the error details in the segment above the
timeline component. This will show all the relevant information regarding the error that occurred, along with the
link to download the diagnostic logs.
Assigned To: This event represents the tasks that are assigned to users as apart of approval rules.
Approved / Rejected: This event represents the approve/reject events on the transaction by the approvers.
Reassigned To: This event represents the reassign activity performed on the transaction. It shows the username
by whom it was reassigned and to whom it was reassigned along with the time of the event.

Delegated To: This event represents any delegation activity occurring on the transaction as a part of configured
delegation rules. It shows the username by whom it was delegated and to whom it was delegated along with the
time of the event.
Withdraw By: This event represents any withdrawal action performed on the transaction. It shows the username
by whom the withdrawal was performed along with its date.
Terminated: This event represents any terminate action performed on the transaction. It shows the username by
whom the terminate action was performed along with its date.
Acquired: This event represents any tasks that were acquired by a particular user for a specific transaction.
Resubmitted: This event represents any resubmit action performed on the transaction along with the username
by whom the activity was performed.
Completed: This is a terminal event and is generated only for transactions that have moved to completed state
along with the date of completion.
7.2 Error Details

As an Admin User, you can click the Name link from Transaction Manager table to open the Failed Transaction
Detail page:
7.2.1 Instructions
Each issue has a downloadable Diagnostic Log file which includes comprehensive information about the error for
debugging purposes.
Real-time data is generated via the Console Fault Details framework. To provide precise messages, the Fault Payload
is parsed and checked for useful information to supersede the seed messages:
• Issue Description: indicates possible cause of the issue.

• Resolution: suggestions how the issue can be resolved.

Fault Information from Fault Payload:
Error Diagnostic Report (aka Diagnostic Log): downloadable for issue resolution.
Color Legend: problematic ruleset is printed in red for prompt attention; correct ruleset in green.

7.3 Interaction with Events in Transaction History Timeline
Except the Submitted and Completed/Terminated events, all other events in the timeline can be interacted with. On
selecting a supported event, the event gets highlighted and the segment above the timeline component changes
accordingly. With an Error event, the details regarding the error is displayed.
Following screen displays the page content on selection of an error event. Details of the corresponding error is
rendered in the section above transaction history, which includes the issue description, resolution along with the
diagnostic log:
7.4 Approval Transaction Cache Corrector

Scenario: Approved transaction still displays “In Progress” status due to data integrity issue.
Additional reference: Effective Date in Employment Flows 21A, 21B, 21C, 21C AUG.
This 22B new feature provides a way for Admin users to make guided corrections to TXN Cache in the front end. You
must first raise SR to work with Development for the exact fixes.
7.4.1 Opt In Feature

(Navigation) FSM > Search: Task: Manage Profile Options > Create
Profile Option Code HCM_EDIT_DATA_CACHE_ENABLE
Profile Display Name HCM_EDIT_DATA_CACHE_ENABLE
Application Global Human Resources
Description Profile option to make guided corrections to TXN Cache
Start Date 1/1/1951
 Updateable
(Navigation) FSM > Search: Task: Manage Administrator Profile Values > Search
HCM_EDIT_DATA_CACHE_ENABLE TRUE or FALSE

7.4.2 Security Role Information
This Cache Corrector task flow is secure by function privilege Review Approval Transactions
(PER_REVIEW_APPROVAL_TRANSACTIONS_PRIV).
7.4.3 Worked Examples

a. On Transaction Summary, select the problem transaction and choose Actions: Edit Data Cache.
b. Warning: You're trying to edit the data cache of this transaction again. The changes you make will
overwrite the pervious changes. Continue anyway?
c. The Cache Corrector UI populates.
d. Enter Xpath, corresponding info populates alongside Edit Node and Cancel buttons.

e. Enter New Value then select Edit Node. Click Yes to confirm.
f. Click OK to close.
g. Scenario: Warning is raised when the Xpath or Node isn’t valid. Click Yes to proceed.
h. Add Node button appears for new Xpath to be added.

i. Select Data Type LOV: Long (a number) and enter New Value (a string), an Error is raised when the data
type of entered value mismatches with that of selected data type.
j. Click Cancel and Yes to confirm.
k. Scenario: When the Xpath contains PII, Current Value is concealed; New Value and Data Type are
protected from update.
l. Scenario: Error
You specified an incorrect path for the node. Try again after entering a valid path.

m. In Transaction History, Edit Data Cache is recorded for audit purpose.

8 TAC Scheduled Processes
Navigate to Tools – Scheduled Processes – Schedule New Process:
8.1 Refresh Transaction Administrator Console Transaction Status

If a transaction moved to Failed or Auto Recovery state, the HRC_TXN_CONSOLE_ENTRY table will get updated only
when the user click opens the transaction or only when the "Refresh Transaction Admin Console" job is run.
This process updates the status of a transaction in the Console and can be run on demand by clicking the  Last
Refresh icon. It is now delivered with a default schedule to run every hour out of the box to update all transactions to
their current state and trigger Alert Initiator on Error, see the Approval Rules tab. Note: the new ESS job will cease
to run when an existing schedule is detected.
Download Log and Output:

In method execute..
Application module fetched successfully..
==========================Updating of transactions to ERRORED started..==========================
Updating the status of PENDING transactions to ERRORED..
Table updated successfully.
Committed result for TAC ESS:
Preparing alert title and description for sending the alert..
***********In method sendAlerts..***********
Alert id fetched: 300100148162554
Alert sent successfully..
ESS refresh for updating PENDING transactions to ERRORED succesfully ended.
==========================Updating of transactions from ERRORED to PENDING started..==========================
Updating the status to pending for errored transactions..
ESS refresh for updating transactions ERRORED to PENDING succesfully ended.
==========================Updating of transactions to STUCK started..==========================
Updating the status of transactions to STUCK..
ESS refresh for updating transactions to STUCK succesfully ended.
ESS refresh to Sync Completed Console Entry transactions to PENDING started..==========================
Updating the status of transactions to COMPLETED..
ESS refresh to Sync Completed Console Entry transactions to PENDING successfully ended.
==========================Checking PENDING transactions for AUTO_RECOVERY started..==========================

IsRMIDeprecated set to: true
Updating the status for pending not stuck transactions..
==========================Checking PENDING transactions for AUTO_RECOVERY successfully ended.==========================
ESS refresh for updating transactions to ERRORED succesfully ended.
ESS refresh for updating transactions to STUCK succesfully ended.
ESS refresh for updating transactions ERRORED to PENDING succesfully ended.
Checking of PENDING transactions for auto-recovery successfully ended.
ESS refresh for updating transaction's CONSOLE_STATUS to PENDING to SYNC with Data Table succesfully ended.
Total transactions processed: 393
Total time elapsed processing all the available transactions: 1.8482166666666666 minutes.
Total transactions updated fron PENDING to ERRORED: 2
Total transactions updated to STUCK: 12
Total transactions updated from ERRORED to PENDING: 0
Total transactions updated from Completed to Pending to SYNC with Data table: 0
Total transactions checked for AUTO_RECOVERY: 379
Total time elapsed processing the auto recovering transactions: 1.7283833333333334 minutes.
Total time elapsed processing the pending transactions: 1.7284166666666667 minutes.
Total time elapsed processing and sending alert: 0.0 minutes.
8.1.1 Opt In Feature

• Navigate to Setup and Maintenance – Task: Search: Manage Profile Options
• Navigate to Setup and Maintenance – Task: Search: Manage Administrator Profile Values
To enable the Refresh ESS job to update IN PROGRESS transactions to COMPLETED, create and enable the
profile option TAC_ESS_ENABLE_PENDING_TO_COMPLETED.
To enable the Refresh ESS job to update IN PROGRESS transactions to AUTO RECOVERY, create and disable the
profile option TAC_ESS_DISABLE_AUTORECOVERY; set to TRUE to disable Auto Recovery check of the
transactions.
To enable the logging of the details of transactions that has been processed, create and enable the Profile Option
TAC_ESS_DETAILED_LOG which needs to be set to true for enabling the detailed logging of the transactions.
The TAC Refresh process will move the underlying state of all transactions to their current state. Possible status
changes that are handled by the ESS job are as follows:
From IN PROGRESS to ERRORED
In the event of transactions getting faulted because of any reason such as invalid user, server errors etc., the
Refresh converts these pending transactions to ERRORED state.

From ERRORED to IN PROGRESS
When the faulted or ERRORED transactions are recovered or rectified, these transactions are then identified by
Refresh and the ESS job moves the state of the transactions back to IN PROGRESS.
From IN PROGRESS to COMPLETED
In the event of any transaction getting approved or rejected or terminated or withdrawn or the transaction getting
completed, the Refresh identifies such transactions and moves their status to COMPLETED.
From SUBMITTED to STUCK
Once a transaction is submitted by user, the SOA server (which primarily checks and verifies the approvals)
processes the transaction. In event of any SOA server issue or any other issue due to which SOA server is not able
to process the transactions, the transactions then get STUCK. The Refresh identifies such transactions and moves
their states to STUCK.
From IN PROGRESS to AUTO RECOVERY
When a transaction encounters a failure at SOA side and trying to recover from it, the Refresh identifies such
transactions and moves their states to AUTO RECOVERY.
8.2 Archive Transactions

On the Approval Rules tab, you can now define various settings (see screenshot) for by when and for which processes
be archived. The Archive Transactions process improves TAC system performance. Also see 8.2.1 Archive
Transaction Console Completed Transactions.
By default, the archive period is set to 3 Months.
8.2.1 Worked Example

When the period is set to N months for a process, then all transactions of that process for which the completion
date has passed more or equal to N months, will fulfill the ageing criteria of Archive/Purge process.
Supported options:
Don't Archive: this option allows a process and all of its transactions to never be archived.
3 Months: this option is applied to a process and all of its transactions for which the completion date has aged
more or equal to 3 months, are eligible for the Archive/Purge process.

8.2.2 Archive Transaction Console Completed Transactions
This ESS job is configured to archive and purge transactions based on:
Ageing: Completion date of a transaction has aged more than the Archive Period settings for that transaction
process (example, Promotion).
Task Criteria: All the tasks of a transaction have been purged via the Archive/Purge process, see How Workflow
Tasks Are Archived and Purged for more details.
Status: Transaction is in COMPLETED state.
The Archive Transactions Console Completed Transactions now includes a standard parameter where Admin
can check All or selective process names to be run on demand.
8.2.2.1 Days Parameter

Definition: The (whole) number of days to be considered for the archive period.
To render the additional Days option, create and enable profile option HRC_ARCHIVE_DAYS_SHOW.
(Navigation) FSM > Search: Task: Manage Profile Options
Profile Option Code HRC_ARCHIVE_DAYS_SHOW
Profile Display Name HRC_ARCHIVE_DAYS_SHOW
Application HCM Central Components
Description Profile option to render Days parameter in Archive ESS Page scheduler

Start Date 1/1/1951

 Updateable
(Navigation) FSM > Search: Task: Manage Administrator Profile Values
HRC_ARCHIVE_DAYS_SHOW True
8.2.2.2 Security Role Information

Add Run Approval Transactions Archive Process
(PER_RUN_APPROVAL_TRANSACTIONS_ARCHIVE_PROCESS_PRIV) function privilege to custom roles for the
ability to view and run this ESS job.
8.2.2.3 Execution Options

Scheduled Processes
If the Days and Process Name parameters are null then the Archive ESS job will run with the settings defined in
8.2 Archive Transactions. For instance, Don't Archive, 3 Months, 6 Months, 9 Months.
Caution: Customers are strongly advised to schedule this process outside their peak hours on a daily basis.

Transaction Manager: Rules
Admin can conveniently click the Archive icon for the process to run asap.
Once the above defined conditions are met, transactions will be archived and will no longer be searchable in the
"Transaction Summary" Tab.
Note: The 20C What’s New Automatically Archive Workflow Tasks Once a Day ESS job (link) is a precursor of
the Archive Transaction Console Completed Transactions ESS job.
8.2.2.4 Approval Notification Archive Dashboard

For a rapid start, uptake the Dashboard (link) from Report Sharing Center and follow the installation instructions.
a. Log into OTBI (https://host:port/analytics), navigate to Catalog - Shared Folders - Custom - Human
Capital Management.
b. Create a new folder, in the Tasks container click Unarchive. Choose BPM_Worklist.catalog from your local
drive and click OK. On the uploaded BPM Worklist, click Expand. On HCM Dashboard, click Edit.

c. In the Catalog container, drag the corresponding sections over the inherited sections and delete the one with
a warning sign. Click Save then Run.
d. Just click Continue for a full report. See R13 Approval Notification Archive 13NOV17.xlsx from the same post
for sample output preview with setup data.
8.2.3 FYI Notifications Expiration Period

You can set FND_NOTIFICATION_EXP_PERIOD profile option values between 1-29 days, per business requirement,
for the number of days after which FYI notifications to expire. The default value is 7 days. Without a sensible Expiry
process, your users must click Dismiss on each FYI notification in order to populate the data into OTBI subject areas.
Note: Alert FYI works in the same fashion as BPM FYI. See Appendix B for available resource items# 1-3.

Download Log and Output:
Archive Job started
No. of transactions got successfully archived - 759
No. of transactions got failed while archiving - 0
Archive Job finished

9 TAC Alerts
It is business critical to have the ability to configure event alerts to concerned parties for prompt attention. The
Runtime Alert API extracts the message content from the seeded data model onto the TAC Error Alert template.
Navigate to Tools – Alerts Composer – Search: TAC_%Alert – Action: Edit
9.1 Alert Initiator On Error

Two options are available for sending the TAC Error Alert:
9.1.1 Transaction Manager Manual Alert

Transaction basis, user manual action. See 3.8 Alert Initiator On Error.
9.1.2 Approval Rules Automated Alert

Process basis, system generated alert.
a. Click Manage Recipients and Message from the Edit menu.

b. Click Add Recipient, choose Communication Method and enter comma separated email distribution list. Click
Apply to close. * Customer can add extra message text but the seed HTML structure must remain as-is.
c. Configure Run Options, click Save and Close.

d. Run this test:
i. Action: Alert Initiator on Error
ii. Issue Assignee: zanc_zben_super_user will not receive said Alert.

iii. Alert Recipient Email: Surlina Yin

iv. Submitted By: Jasmine Garrett
Note: Actions in this FYI alert notification have no practical relevance – DO NOT USE. Only
Admin User can take appropriate actions via the Transaction Manager (see 3 Actions).
9.2 TAC_RESUBMIT_ALERT
Alert is sent to Initiator upon resubmission of a transaction. You can compose the Message Text using existing
tokens if required.

10 Analytics
Log in to BI Answers (https://host:port/analytics/saw.dll?bieehome) – Catalog – Shared Folders – Human Capital
Management – Transaction Administration – Embedded Content – Transaction Manager.
1. To preview, click Open Transaction Summary.
2. Parameters are defaulted.
3. To change or duplicate the dashboard for different defaults and permissions, choose Copy.

4. Navigate to /Shared/Custom folder, for example, the Human Capital Management subfolder, and click Paste.
Choose Edit dashboard to correct component settings.
5. Expand the folders for Transaction Summary. Click Open to verify that the dashboard continues to run.
6. To modify, return to the custom subfolder, locate the Transaction Summary and click Edit.
7. Select the Criteria tab for the subject area to proceed with changes.

8. Return to Transaction Console, select the Analytics tab.
9. Open the Search panel, enter Transaction Summary and Sort By Name then click Search to return results.
10. Select the Dashboard icon for the Report Information popup dialog. Click Done to close.
11. Click Add Favorites. This is set at User level.
12. Repeat for 8.2.1.1 Approval Notification Archive Dashboard.
13. Click Report View.

14. Click Remove from Favorites if no longer needed.
15. Click Snippet for the Transaction Summary dashboard. Click E-Mail to share.

11 Approval Delegation
(Navigation) Me — Roles and Delegations — Account Management — Approval Delegations
With audit support, this responsive Account Management page allows users manage delegations in addition to
security actions. See Role Delegation for further details. Note that Administrators can also set up approval
delegations for others.
Alternatively, users can navigate to BPM Worklist (https://host:port/integration/worklistapp) — Username —

Preferences — My Rules for setting up complex rulesets. Note that that there is no support of view
interchangeability between the two UIs.

11.1 Category
Categories are a property of tasks configured in the table wftaskmetadata. One or more tasks can fall under the same
category. Basically they are used to generalize the classification of tasks. Worked Example : ProfileCoreHumanTask
and ApprovePerformanceGoal tasks share the same category “Talent (e.g. Goals, Performance)“.
You can download wftaskmetadata spreadsheet from Doc ID 2430452.1 and filter column R ‘Category’ to reveal the
default setting of tasks, see column C ‘Name’. Note: in current release there are 342 of 456 tasks without a category.
Users can select one of the predefined values, and click Save. The Delete option renders when the user clicks Edit.
Note: If multiple approval delegation rules on same category concurrently exist in the same time period but with
different delegate each, then the oldest relevant Approval Delegation Rule is to be executed.
The Category list of values are derived from the General tab of the Task in BPM Task Configuration.
If a task gets configured with a new category or a specific category in the table gets renamed, then a new category
would be visible to users.

To simplify the user experience, you can create your own set of categories to support approval delegations.
11.1.1 Highlight the Task and click Edit.
11.1.2 Overwrite the pre-existing Category with a new label name.
11.1.3 Click Save then Commit Task.
11.1.4 Query the new category.

11.1.5 Requery the category and repeat the same with a new task.
11.1.6 Requery the new category and confirm results.
Note: To remove a pre-existing category, it needs to be removed from every task it is associated to. One task can
only have one category, but one category can have multiple tasks grouped into it.

11.1.7 Verify the new category in the responsive UI.
11.2 Allow this user to approve their own transaction

Definition of “this user”: it refers to the new Delegated Approver, not the requestor of the transaction.
Worked Example: HR delegates Employee A (who reports to Manager B) to approve Change Location.
Later, Manager B requests location change for Employee A that approval should be routed to HR. In this case
Employee A has become the delegated approver for own transaction, but the checkbox is not selected, the approval
notification is therefore redirected to Employee A’s line manager for approval. See also Avoid Assigning Approvals
to Specific Users (link) for additional info.

12 Archived Transaction Summary
Data is populated from the ESS job, see 8.2.1 Archive Transaction Console Completed Transactions.
UI table view lists Object Name, Status, Process Name, Submitted On, Submitted By, Approvers, Completion Date and
Archive Date. You can download the CSV file in which you will find two additional columns:
Name|Status|Process Name|Submitted On|Submitted By|Approvers|Completion Date|Archive Date|Transaction ID|Task|Rule
12.1 Archive Transaction Details Page

In the Archive Console Page, the listed Archive Transaction renders object name a link to its corresponding details
page in which you will find:
Basic Details: This component appears at the top of details page with transaction's information of Status, Process
Name, Object Name with Transaction ID, Submitted On and Submitted By.
Approval History: This component not only shows the hierarchy approver(s) including the initiator's details, but
also when the transaction is configured to bypass approvals. For more info, see 7 Transaction Detail  The
Approval History Component.
Comments and Attachment: This lists all comments and documents attached to a transaction by both
approver(s) and initiator. The physical copies are retained for inspection. For more info, see 7 Transaction Detail
 Comments and Attachments.
Issue Comments: This lists all the comments that were attached to a failed transaction. For more info, see 7
Transaction Detail  Issue Comments.
Timeline: As the name suggests, this component showcases all the transitions of a transaction through its
lifetime. For more info, see 7 Transaction Detail  View Transaction History. Similar Example: see 7.1 Pending
and Completed Detail. Shown below is Bypass Approvals worked example.

13 Frequently Asked Questions
13.1 I am unable to find one Category when creating Transaction Security Profiles.
You can create a transaction console security profile with name HCM Family Transaction Summary View All,
select HCM Family and ignore Category and Subcategory, or select Exclude Subcategory if necessary. See
hrc_arm_process_vl spreadsheet in Doc ID 2430452.1 for details.
13.2 Why am I not able to see all the status filters? Why am I not able to see the detailed Issue description and log files
on Transaction Details page for failed transactions?
Check your security access, whether Transaction Admin Console or Transaction Self-Service Console. For
Transaction Admin Console, your user account needs a data role for the delivered
ORA_HRC_HUMAN_CAPITAL_MANAGEMENT_APPLICATION_ADMINISTRATOR_JOB.
13.3 Why do I get this message: "The approval history is not available for this transaction"?
After the Terminate Process action, this message "The approval history is not available for this transaction"
appears in the transaction detail.
13.4 Why the Approver, Assigned To and Submitted By - Transaction Console Filters are not working as expected?
Submitted By filter: enter the parameter with either display name, first name, or last name.
Assigned To filter: enter username as a criteria.
Approver filter: enter username for the query.
13.5 Why we can get up to 500 transactions in the downloaded csv file?
It is a technical limitation that download action can only support up to a maximum of 500 transactions.
Streamline your download or use OTBI for reporting purpose.
13.6 Why do I get a blank page on Transaction Summary?
Try clear your Saved Searches.
13.7 Will the TAC Refresh process affects or holds or interrupts the inflight transactions?
The Refresh ESS job runs behind the scenes asynchronously, it neither interrupts any transaction from getting
created nor holds any TAC related processes from running.
13.8 Will the running of TAC Refresh process degrade system performance and impact user experience?
There should be no impact on TAC overall performance. Raise a service request for technical investigation if and
when necessary.
13.9 What is the difference between a Transaction and a BPM Task?
Transaction: a Record to represent a flow which transitions from initiation to termination states. Example, Hiring
an employee, Salary change etc.
BPM Task: a Task is a building block of a transaction which is created to handle the approval flow. A transaction
may have multiple tasks but a task will have only one transaction associated with it. In the case of parallel
participants, there will be a task associated with each participant.

13.10 How to enable notifications to appear under the Bell icon?
Check Notification Mode, it is defaulted to All for enabling Bell and Email Notification types.
Note: Worklist Notification is always-on.
13.11 Why are Approval Notifications still pending in the Bell icon when already acted upon via email ?
Two types of notifications will populate onto the Bell icon: 1. Actionable, 2. FYI.
Only users open Bell then select either Approve or Reject action to complete transactions will automatically
dismiss and reduce the counts, else not. See How to Synchronize Bell Notifications to Email (Doc ID 2483741.1).
13.12 How to mark FYI notifications as read?
Users must select the Dismiss button on Bell or Show All option for Dismiss All button on Notifications page.
Also see 8.2.2 FYI Notifications Expiration Period.
13.13 What function privilege is needed to run ‘Synchronize Notifications in Global Header’ ESS job?
Add FND_MANAGE_SCHEDULED_JOB_DEFINITION_PRIV to custom role.
13.14 How often should 'Synchronize Notifications in Global Header' be scheduled to run?
Run this ESS job every 2 hours and it is restricted to process up to 500 records.
13.15 How to avoid receiving the same FYI notification twice?
Define Task Aggregation for each workflow task in BPM.
Implementation considerations:
None: user sees the task as many times as it is assigned to him or her.
Once per task: user only sees one time worklist task (or notification) in the task life cycle.

Once per stage: user sees the task only one time in a stage.
All Stages: user sees the task in all stages of task life cycle.
Note: Aggregation is available only when the assignees are from the same set. For example, if you assign a task
to user A and another to both user A and user B; then user A sees two separate tasks. The two assignments are
not aggregated because the assignees are not exactly the same.
13.16 Why we are seeing wrong approver in approval history when using ‘prohibit user self approval’ feature?
Approval history will display future approvers according to the defined approval rules. During task assignment,
it will evaluate the user against 'prohibit user self approval' to determine and skip sending approval notification.
13.17 What causes “Approval History is not available” message?
Check Task Owner (non-configurable attribute), revert to 'FUSION_APPS_HCM_ADF_APPID' for HCM workflows.

Appendix A
Resubmit action supported processes

Appendix B
Resources
1. SOA Purge Details of a Software as a Service (SaaS) Fusion Apps Environment (Doc ID 2175534.1)
2. Automatically Expire Outstanding FYI BPM Tasks (Doc ID 2449251.1)
3. Oracle HCM Cloud Configurable Notifications and Subject Lines (Doc ID 2331021.1)
4. How to Create BI Publisher Report on Workflow Notifications ? (Doc ID 2135790.1)
5. Recruiting Cloud: Creating Unsecured Approval Notifications (Doc ID 2725482.1)
6. Recruiting Cloud: Alerts and Notifications (Doc ID 2587000.1)
7. Recruiting Cloud: How to Format a Date in Alert Composer Notifications (Doc ID 2661442.1)
8. Understanding Alerts in Oracle Fusion Learning Cloud (Doc ID 2543297.1)
9. Learning Cloud: How To Exclude Terminated Employees From Receiving Alert Notification (Doc ID 2727552.1)
10. Learning Cloud: Users Receive a Duplicate Resource Alert Email that Begins with FYI (Doc ID 2664565.1)
11. Oracle Talent Management Cloud List of Delivered Notifications (Doc ID 2234224.1)
12. Alert Templates for Event Based Journeys (Doc ID 2777961.1)

Appendix C
What’s New
Module Feature Update Version
Absence Management Approval Notifications with Preview in the Responsive Worklist Update 20A
Absence Management Area of Responsibility (AOR) Support for Absence, Update 20B
Disbursement and Donation Approvals
Absence Management Obtain Approval from the Line Managers of All Affected Update 20B
Assignments for an Absence
Absence Management Review Absence Plans, Future and In Progress Absences and Update 20B
Future Transactions Impacted Due to Local and Global
Transfers
Absence Management Route Work Schedule Assignment Approvals to the Update 21A
Appropriate Manager
Absence Management Plan Balances on Approval Notifications Update 22A
Applications Security Extending Regenerate Security Profiles for Transaction, Update 22A
Recruiting, and Payroll
Career Development Development Plan Approvals Request for Information Update 20D
Extended Request Feature
Career Development Configure Comments and Attachments for Development Plan Update 21A
Approval Transaction
Career Development Bypass Approvals for Specific Development Goal Conditions Update 21B
Career Development Define Expiration Policies for Development Goal Approvals Update 21B
Career Development Add Learning to a Development Goal When Approvals Are Update 21D
Enabled
Career Development Career Development Approval Transaction Aging Policy Update 21D
Career Development Simulate Development Goal Approval Rules Update 22B
Compensation Preview Salary, Individual Compensation Approval Information Update 20A
in the Worklist
Compensation Preview Worksheet Approval Information in the Worklist Update 20A
Compensation Individual Compensation Approval Notification Enhancements Update 20B
Compensation Individual Compensation Approval Notifications Can Show Update 20C
Input Values
Compensation Route Approvals Using Launching Assignment Hierarchy Update 20D
Compensation New Columns Added to Grade Step Progression Results Page Update 21B
and Transaction Report
Compensation Prevent New Individual Compensation Submission when Update 21B
Previous Submissions are Pending Approval
Compensation View Note Count In Approvals Task Update 21B
Compensation Update of Worksheet Approvals Task Update 22A
Compensation Change in Transaction Design Studio Show or Hide Regions Update 22B
Behavior for Change Salary

Compensation Disabled Alerts No Longer Appear In Alerts Analytic In Update 22B
Approval Task
Compensation Enable Save and Save and Close Buttons in Salary Actions Update 22B
using HCM Transaction Design Studio
Compensation Enable the Save and Save and Close Buttons in Individual Update 22B
Compensation Actions Using HCM Transaction Design Studio
Global Human Resources Additional Transaction Design Studio Support for Share Update 20A
Personal Info Task
Global Human Resources Data Comparison in Notification Message After Approval Update 20A
Global Human Resources Enhanced Security for Employment-Related Approval Update 20A
Notifications
Global Human Resources Include Comments and Attachments When Submitting Share Update 20A
Transactions for Approval
Global Human Resources Bypass Document Type Configuration Approval Update 20B
Global Human Resources Data Visibility in Document Records' Post Approval Notification Update 20B
Global Human Resources Effective Date from Advanced Search Carries Over to the Update 20B
Transaction Page
Global Human Resources Send Changes to Employee Photos for Approval Update 20B
Global Human Resources Improved Checklist Transaction Titles in Transaction Console Update 20C
Global Human Resources Improved User Experience in Document Record Approval Update 20C
Notifications
Global Human Resources Route Employment Approvals Using Current Assignment Update 20C
Hierarchy
Global Human Resources Simplify Document Record Approval When Approval Is Set to Update 20C
No
Global Human Resources Support for Additional Person Info in Transaction Design Update 20C
Studio
Global Human Resources Enhanced Transaction Approvals Support Multiple Update 20D
Assignments in Global Human Resources
Global Human Resources Secured Approval Notifications for Employment Flows Update 20D
Global Human Resources Audit the Transactions Done Using Responsive Employment Update 21A
Pages
Global Human Resources Bypass Approvals for Specific Change Personal Information Update 21A
Sub Processes
Global Human Resources Flexibility for Approver to Edit Document Record Submitted for Update 21A
Approval
Global Human Resources Improved User Experience for In-Progress Employment Update 21A
Approval Notifications
Global Human Resources Route Document Record Approvals Using Current Assignment Update 21A
Hierarchy
Global Human Resources Display Approval Details After Approval Completion Update 21B
Global Human Resources Enable Completion of Document Record Transactions When Update 21B
Initiator is Terminated

Global Human Resources Flexibility for Initiator to Edit Document Record Submitted for Update 21B
Approval
Global Human Resources New Document Records Approval Payload to Retrieve Update 21B
Requestor Information
Global Human Resources Source Assignment Attributes Added To Add Assignment Update 21B
Approval Payload
Global Human Resources Additional Assignment Attributes and Manager Type Attribute Update 21C
Added in Employment Approval Rules
Global Human Resources Approvals Support for Job Responsive Pages Update 21C
Global Human Resources Position Approvals: Route Approvals Based on the Incumbent Update 21C
Global Human Resources Prepare for Changes to the Change Personal Information Update 21C
Approval Rule
Global Human Resources Approvals Support for Location Responsive Pages Update 21D
Global Human Resources Benefit from the Enhancements to the Change Personal Update 21D
Information Approval Rule
Global Human Resources Introduction of New Approval Payload for Standard Update 22A
Component Salary Basis Type and Other Enhancements
Global Human Resources Simulate Employment Approval Rules Update 22A
Global Human Resources Simulate Workforce Structures Approval Rules Update 22A
Global Human Resources Additional Configurable Sections for Position Details, Job Update 22B
Details, and Location Details in Transaction Design Studio
Global Human Resources Simulate Person, Area of Responsibility and Share Information Update 22B
Approval Rules
Global Human Resources Transaction Design Studio Improvements for Personal Info Update 22B
Responsive Pages
Global Payroll Subledger Transaction Number Display in Process Results Update 21A
Details
Global Payroll Update Employee’s Payroll During Change Assignment Update 22B
Transaction
Goal Management Performance Goals Approval Transactions OTBI Reporting Update 20B
Goal Management Transaction Design Studio Support for Performance Goal Update 20C
Library
Goal Management Goal Plan Approvals Request for Information Extended Update 20D
Request Feature
Goal Management Disable Comments and Attachments in Approval Requests Update 21A
Goal Management Bypass Approvals for Specific Performance Goal Subprocesses Update 21B
Goal Management Define Expiration Policies for Performance Goal Approvals Update 21B
Goal Management Bypass Approvals for Performance Goal Sub Processes Update 21C
Goal Management Goal Management Approval Transaction Aging Policy Update 21D
Goal Management Convert Performance Goal Approval Data Into HDL File Update 22A
Goal Management Simulate Performance Goal Approval Rules Update 22B
HCM Common Transaction Design Studio for HCM Experience Design Studio Update 21D
Enhancements

HCM Common Transaction Design Studio for HCM Experience Design Studio Update 22A
Enhancements
HCM Common Transaction Design Studio for HCM Experience Design Studio Update 22B
Enhancements
HCM Common Atom Feeds for Additional HCM Transactions Update 21A
Architecture
HCM Common Enhancements to Approvals and Notifications Update 21D
Architecture
HCM Common Enhancements to Approvals and Notifications Update 22A
Architecture
HCM Common Enhancements to Approvals and Notifications Update 22B
Architecture
HCM Common Features New Enhancements to Transaction Console Update 20B
HCM Common Features Enhancements to HCM Approval Rules Update 20C
HCM Common Features Enhancements to the Human Capital Management Approval Update 20C
Rules Page
HCM Common Features New Enhancements to Transaction Console Update 20C
HCM Common Features Performance Improvements for HCM BIP-Based Approval Update 20C
Notifications
HCM Common Features New Enhancements to Transaction Console Update 20D
HCM Common Features Areas of Responsibility Based Approval Routing Policies Update 21B
HCM Common Features New Enhancements to Transaction Console Update 21B
HCM Common Features Performance Improvements for HCM BIP-Based Approval Update 21B
Notifications
HCM Common Features Transaction Design Studio for HCM Experience Design Studio Update 21B
Enhancements
HCM Common Features Performance Improvements for HCM BIP-Based Approval Update 21C
Notifications
HCM Common Features Position Approvals: Route Approvals Based on the Incumbent Update 21C
HCM Transactional New Attributes in Transaction Administration Real Time Update 20C
Business Intelligence Subject Area
Human Capital Transaction Design Studio Improvements for Personal Info Update 22B
Management for United Responsive Pages: Legislative Information
Kingdom
Learning Enhancements to Learning Request Approval Workflow Update 21D
Learning Learning Assignment Withdrawal Transactions in Transaction Update 21D
Console
Learning Cloud Learning Request and Non Catalog Learning Request Approval May Maint Pack for
20B
Learning Cloud Learning Request Approvals Support in Transaction Console May Maint Pack for
21B
Learning Cloud Use Defined FlexFields to Build Rules for Approval Workflows Update 20A
Learning Cloud Added Communities to Learning Item Contribution Approval Update 20C

Learning Cloud Learning Cloud Now Uses the Transaction Console Update 20C
Payroll for China Hide the Person Legislative Attributes Delivered by Oracle via Update 22B
Transaction Design Studio
Performance Configure Performance Approval Rules Based on Setup and Update 20A
Management Ratings
Performance Performance Document Approval Enhancements Update 21A
Management
Recruiting Configure Offer Approval Rules Based on Additional Fields Update 20A
Recruiting Extend Requisition Approval Rules with Flexfields Update 20B
Recruiting Configure Offer Approval Rules Based on Flexfields Update 20C
Recruiting Update Requisitions Post Approval Using HCM Data Loader Update 20C
Recruiting Configure Interview Schedules Using Transaction Design Update 21B
Studio
Recruiting Banners for Job Offer Approval Update 21C
Recruiting Banners for Job Requisition Approval Update 22B
Time and Labor Approval Notification for Time Cards Redesigned Self-Service Update 20A
Pages Introduction
Time and Labor HCM Transaction Design Studio for Time and Labor Update 20A
Enhancement
Time and Labor Worker Approval Task Introduction Update 20A
Time and Labor Time Card Approval Enhancements Update 20B
Time and Labor Transaction Design Studio for Time and Labor Enhancement Update 20B
Time and Labor Responsive Time Card Approval Enhancement Update 22B
Workforce Modeling Improved Workforce Modeling Approval Notification Update 20C

Connect with us
Call +1.800.ORACLE1 or visit oracle.com. Outside North America, find your local office at: oracle.com/contact.
blogs.oracle.com facebook.com/oracle twitter.com/oracle
Copyright © 2020, Oracle and/or its affiliates. All rights reserved. This document is Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be
provided for information purposes only, and the contents hereof are subject to change trademarks of their respective owners.
without notice. This document is not warranted to be error-free, nor subject to any other
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC
warranties or conditions, whether expressed orally or implied in law, including implied
trademarks are used under license and are trademarks or registered trademarks of SPARC
warranties and conditions of merchantability or fitness for a particular purpose. We
International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or
specifically disclaim any liability with respect to this document, and no contractual
registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open
obligations are formed either directly or indirectly by this document. This document
Group. 0120
may not be reproduced or transmitted in any form or by any means, electronic or
mechanical, for any purpose, without our prior written permission. Disclaimer: This document is for informational purposes. It is not a commitment to deliver any
material, code, or functionality, and should not be relied upon in making purchasing decisions.
This device has not been authorized as required by the rules of the Federal
The development, release, timing, and pricing of any features or functionality described in this
Communications Commission. This device is not, and may not be, offered for sale or
document may change and remains at the sole discretion of Oracle Corporation.
lease, or sold or leased, until authorization is obtained.


ID 2430452.1 The Basics of Transaction Console v3.2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ID 2430452.1 The Basics of Transaction Console v3.2

Uploaded by

Copyright:

Available Formats

The Basics of Transaction

Cloud HCM Common Feature Release Updates 22B

March 2022, Version 3.2

1 The Basics of Transaction Console / Version 3.2

Safe Harbor Statement

Note: In the images or examples included in this document regarding: user

2 The Basics of Transaction Console / Version 3.2

Date Release Description

3 The Basics of Transaction Console / Version 3.2

Security Role Information ..................................................................................................................................................... 7

4 The Basics of Transaction Console / Version 3.2

5 The Basics of Transaction Console / Version 3.2

6 The Basics of Transaction Console / Version 3.2

Security Role Information

7 The Basics of Transaction Console / Version 3.2

8 The Basics of Transaction Console / Version 3.2

1.5 Approver (aka Assignees on 21D)

9 The Basics of Transaction Console / Version 3.2

1.8 Issue Priority

1.9 Issue Assignee

10 The Basics of Transaction Console / Version 3.2

2.1 Global Search

2.2 Defaulted Filter

2.3 Hide Filters

2.4 Filters Configurable Options

2.5 Preset Search Criteria

11 The Basics of Transaction Console / Version 3.2

2.5.2 Issue Priority

2.7 Process Name

2.9 Person Number

2.10 Advanced Filters

12 The Basics of Transaction Console / Version 3.2

2.10.3 Issues Assigned To

2.10.4 Issue Type

2.10.9 Task Number

13 The Basics of Transaction Console / Version 3.2

14 The Basics of Transaction Console / Version 3.2

FAILED only for only for only for      

STUCK         if profile

The Download action is only available on the Main page.

3.1.1 Reassign to User

15 The Basics of Transaction Console / Version 3.2

The Reassign action renders once new instruction is complete.

The change is trackable.

16 The Basics of Transaction Console / Version 3.2

3.4 Terminate Process

3.5 Approve / Reject

3.5.1 Override Approval

17 The Basics of Transaction Console / Version 3.2

3.8 Alert Initiator On Error

18 The Basics of Transaction Console / Version 3.2

19 The Basics of Transaction Console / Version 3.2

7.1 Pending and Completed Detail

 Transaction ID: name of the transaction before the transaction id

20 The Basics of Transaction Console / Version 3.2

(Navigation) FSM > Search: Task: Manage Profile Options

(Navigation) FSM > Search: Task: Manage Administrator Profile Values

21 The Basics of Transaction Console / Version 3.2

 Action menu: available actions for this transaction.

22 The Basics of Transaction Console / Version 3.2

7.2 Error Details

• Issue Description: indicates possible cause of the issue.

23 The Basics of Transaction Console / Version 3.2