Job Data Modernization

PeopleSoft HCM PUM #37

Product Documentation Update

November 06, 2020

Updated on February 18, 2021
Copyright © 2021, Oracle and/or its affiliates
PeopleSoft HCM 9.2.036 Product Documentation Update: Job Data Modernization.

Copyright © 2021, Oracle and/or its affiliates.

This software and related documentation are provided under a license agreement containing restrictions on use and
disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or
allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform,
publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this
software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any
errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the
U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs
embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer
documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer
software" or “commercial computer software documentation” pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure,
modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system,
integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such
programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified
in the license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud services
are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not
developed or intended for use in any inherently dangerous applications, including applications that may create a risk of
personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all
appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates
disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under
license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services
from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any
kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement
between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred
due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement
between you and Oracle.
The business names used in this documentation are fictitious, and are not intended to identify any real companies currently
or previously in existence.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For
information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

1 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Contents
Job Data Modernization ...................................................................................................................................................................................................................0

Job Data Modernization Feature .................................................................................................................................................... 4

Top Level Architecture ................................................................................................................................................................................................................................ 4
Implementation Areas ....................................................................................................................................................................................................................... 4
Installation and Navigation Collections................................................................................................................................................................................................... 5
Transaction Flow .......................................................................................................................................................................................................................................... 6
Scenario 1 : Creating a New Job Row Request ............................................................................................................................................................................. 7
Scenario 2 : Correcting an Existing Job Row ................................................................................................................................................................................ 7
Scenario 3 : Re-Editing an Ongoing Request............................................................................................................................................................................... 7
Approval Flow................................................................................................................................................................................................................................................ 7
New Roles & Permission Lists ................................................................................................................................................................................................................... 8
Roles ...................................................................................................................................................................................................................................................... 8
Permission Lists .................................................................................................................................................................................................................................. 9
Phased Implementation Recommendation ........................................................................................................................................................................................... 9

Configuring and Managing the Job Data Search Page ................................................................................................................11

Setting Up Search Configuration ............................................................................................................................................................................................................. 11
Customizing Search Criteria and Search Results for the Job Data Modernization Feature ............................................................................................ 11
Considerations and Limitations .................................................................................................................................................................................................... 15

Configuring and Administering Activity Guide Composer ........................................................................................................ 16

Customizing Activity Guide Composer Configurations for the Job Data Modernization Feature ......................................................................................... 16
AGC Category Setups ...................................................................................................................................................................................................................... 16
AGC Template Configuration-Customizations ......................................................................................................................................................................... 17
Related Content Service (RCS) Setup........................................................................................................................................................................................... 19

Configuring and Administering Page and Field Configurator .................................................................................................. 21

Configuring Pages and Fields to Display for a Job Data Request ...................................................................................................................................................21
Adding Criteria Fields to Control AG Steps and Fields ............................................................................................................................................................24
Configuring Fields to Display in the ‘View Details’ Component ......................................................................................................................................................24
Configuring Event Mapping to Enable PFC Setup..............................................................................................................................................................................24
Migrating PFC Demo Data Using ADS................................................................................................................................................................................................... 26
Limitations of Using PFC for the Job Data Modernization Feature ............................................................................................................................................... 27

Manage Customization ....................................................................................................................................................................28

Overview ....................................................................................................................................................................................................................................................... 28
Job Data Modernization - Manage Customization ............................................................................................................................................................................ 28
Use Case 1: Adding Custom Page into Fluid Job flow.............................................................................................................................................................. 28
Use Case 2: Adding Custom Fields into Fluid Job Component using Drop Zones........................................................................................................... 29
Use Case 3: Adding Custom Record and Fields into Fluid Job Component without Drop Zones ................................................................................ 29
Use Case 4: Adding Custom Fields into Fluid Job Component without Drop Zones ...................................................................................................... 29
Steps to Create the Staging Record ....................................................................................................................................................................................................... 29
Steps to Create the Custom CI................................................................................................................................................................................................................ 30
Security for Custom CI.............................................................................................................................................................................................................................. 30
Map Source and Staging Records ...........................................................................................................................................................................................................31
Configure Job CI ..........................................................................................................................................................................................................................................31
Job Data Installation .................................................................................................................................................................................................................................. 32
Maintaining Customizations Using Drop Zone Areas ....................................................................................................................................................................... 33
Changes Needed on the Fluid Job Data Component .............................................................................................................................................................. 33
Drop Zone configurations ..............................................................................................................................................................................................................34
Changes Needed on the View Details Component .................................................................................................................................................................. 35
Page Styling Considerations .................................................................................................................................................................................................................... 37

Administering Approvals Configurations.....................................................................................................................................39

Modifying AWE Thread Descriptions .................................................................................................................................................................................................... 39
Configuring Additional Actions............................................................................................................................................................................................................... 39
Adding and Deleting Approval Steps ................................................................................................................................................................................................... 40

2 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
 Configuring Approvals Based on Different Job Actions .................................................................................................................................................................. 40
Configuring a Process Definition ID with User Defined Criteria........................................................................................................................................... 40
Modifying the Approval Page ..................................................................................................................................................................................................................42
Approval Process Setup ............................................................................................................................................................................................................................ 42
AWE Events Used for Approvals ............................................................................................................................................................................................................ 44
Email Notification Templates ................................................................................................................................................................................................................. 44

Administering Transaction Summary .......................................................................................................................................... 47

Transaction Summary in the Job Data Modernization Feature ......................................................................................................................................................47
Configuring Transaction Summary .............................................................................................................................................................................................47
Configuring Fields From a Grid .....................................................................................................................................................................................................47
Transaction Summary on the View Details and Approval Component ............................................................................................................................. 49

Managing Related Information in the Right Pane ......................................................................................................................52

Configuring Additional Links in the Related Information Right Pane ........................................................................................................................................... 52
Adding New Links on the Delivered Tile ..................................................................................................................................................................................... 53
Adding a New Tile with Clickable Links in the Related Content Frame ......................................................................................................................................... 53

Attachments in the Job Data Modernization Feature ............................................................................................................... 54

Attachments Framework Implementation and Related Setups ..................................................................................................................................................... 54
Customizing Attachment Types .................................................................................................................................................................................................. 54
Framework Related Setups ........................................................................................................................................................................................................... 54

OTHER FEATURE UPDATES ............................................................................................................................................................57

The Job Data link in Guided Self Service (GSS) and Position Management ................................................................................................................................ 57
Customizing the Job Data Link to Point to Modern Job Data From Other Features ................................................................................................................. 57
Other Process Updates ............................................................................................................................................................................................................................. 57

3 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
JOB DATA MODERNIZATION FEATURE
PeopleSoft Human Resources is delivering Job Data in Fluid with a modern and frictionless data entry experience. Job Data
Modernization offers administrators the ability to:
 Configure search criteria, search results, and transaction fields
 Attach documents
 Validate and review changes before submission
 Configure approvals as needed
This document is to help technical users with the configuration and customizations they might need to complete during
implementation.

Top Level Architecture

The following diagram illustrates the architecture, setup, and frameworks leveraged for the feature.

Top Level Architecture for Job Data Modernization

Implementation Areas
Listed below are the major implementation areas for the Job Data Modernization feature. This document will explain each of
these topics in more detail in the upcoming chapters.
Configurable Search: The Search Configuration feature enables you to design custom search pages for a content reference
based on your organization’s needs. Administrators can set up searches that use either a standard record search or elastic
search definitions. Your organization has control over which fields to display and their order. Configurable search allows the
user to save the search criteria and view recent searches when defined in the setup.
PeopleBooks reference: PeopleSoft HCM 9.2: Core Functionality: Application Fundamentals: Managing Configurable Search:
Setting up Search Configuration.
Activity Guide Composer (AGC): Activity Guide Composer enables you to define a guided process for users to complete
Job transactions. The design of the AGC is to help functional configurators setup or modify the Activity Guide template for
the feature. We recommend that functional configurators work with a technical developer before making any changes as the
template configuration changes affect how the guided process works.
PeopleBooks reference: PeopleSoft HCM 9.2: Products: Core Functionality: Enterprise Components: Working with the
Activity Guide Composer.

4 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Page and Field Configurator (PFC): This framework allows you to configure the visibility of pages and fields for a
component. You can control the visibility of the pages and fields for different security roles. Job Data Modernization uses
this framework to control the visibility of steps and page fields in the guided process. Using this configuration, you can
control the page and field visibility for different job actions as well.
PeopleBooks reference: PeopleSoft HCM 9.2: Products: Core Functionality: Enterprise Components: Page and Field
Configurator.
Related Content Framework (RCF): PeopleSoft leverages RCF to display related information in the Job Data pages. It is
useful in managing available real estate on the screen better. It provides a scalable and more configurable space for you to
add any additional information, like analytics and policy documents.
PeopleBooks reference: PeopleTools: Products: Development Tools: Portal Technology: Understanding the PeopleSoft
Related Content Framework.
Transaction Summary: This functionality enables you to configure a set of fields to display on the Summary step in the
guided process based on action and shows current and proposed values. Administrators can choose a default configuration.
In cases where there are no configured criteria, the page uses a default configuration for displaying the current and
proposed values on the Summary page. Transaction Summary provides many configurable features like setting field order
and functional grouping as well. You can review the delivered configuration and make changes based on data entry
requirements for each action.
PeopleBooks reference: PeopleSoft HCM 9.2: Products: Core Functionality: Application Fundamentals: Working with
Common Components: Configuring Transaction Summary.
Approvals Framework (AWE): This framework helps organizations leave earlier workflow technology where you had to
make changes in the Application Designer to enable new Workflow steps. With AWE, it is easy to configure the workflow
process using PIA. Job Data Modernization uses the Fluid Approvals functionality.
PeopleBooks reference: PeopleSoft HCM 9.2: Products: Core Functionality: Approvals Framework.

Installation and Navigation Collections

The Job Data Modernization feature delivers the Manage Human Resources fluid dashboard, which provides tiles that give
access to setup and feature pages.
Use the Manage Configurations tile to access a navigation collection of setup pages used to configure the Job Data
Modernization feature.

Figure: Manage Human Resources dashboard

Enable modern Job Data functionality using the Job Data Installation page. This is required for HR administrators to access
the fluid Manage Job tile.

5 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Figure: Job Data Installation setup in the navigation collection

Use the Job Data Installation page to define functionality setting for Job Data Modernization feature, like attachments,
approvals, and the review process. Use this page to enable modern Job Data access from the Position Management and
Guided Self Service (GSS) pages.
To use the modern Job Data feature, select the ‘Fluid Job Data’ check box and assign necessary roles to ensure the users
have appropriate access. Selecting the check box will show Fluid Job Data instead of Classic Job Data when users click the
Job Data link in the Guided Self Service pages or Position Management pages (including Fluid Position Management).

Note: The Mange Job tile will be available when the user possesses any of the delivered modern Job Data requester or
approver roles but will get an error message if the ‘Fluid Job Data’ flag is turned OFF on the installation setup.

Enable the ‘Review Process’ to indicate that users should review higher job data rows when they correct a transaction or add
a retro job data row.

Note: Currently this functionality is supported only when retro rows are added or corrected by modern Job Data. If you add
or correct a retro job data row using any other feature or process, the review process will not execute.

By default the delivered CI name HR_JOBDATA_SAVE_CI will be displayed, if you have any customizations, then the CI
name need to be replaced with the custom CI name.
Define if approval is needed when adding job rows, correcting existing job rows, or both. While enabling approvals, the
system provides the AWE Process IDs by default, but that can override based on the requirements.
Field level functionality details are available in PeopleBooks: PeopleSoft HCM 9.2: Workforce Data Management: PeopleSoft
Human Resources Administer Workforce: Using the PeopleSoft Fluid User Interface to Manage Job Data.

Transaction Flow
This diagram illustrates that while submitting a request (job row); fluid job transaction details are saved to staging records.
Once the transaction is approved, data is pushed to the actual job records. All existing post job data update events will fire as
they work currently with classic Job Data.

6 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Figure: Transaction-data flow diagram

Scenario 1 : Creating a New Job Row Request

When users request a new job row, data copied from JOB record’s most effective dated-effective sequence row below the
selected date of request, to the newly inserted row. Users can make required changes, validate and submit the data for
approval.
If approvals are not enabled in Job Data Installation page (i.e.—an AWE Process ID is NOT associated with 'Enable for new
transaction' option), data gets pushed directly to the job records after that data is inserted to the staging records.

Scenario 2 : Correcting an Existing Job Row

When a user edits an existing job row, the process copies data from the JOB record’s equivalent effective dated-effective
sequence row. The user can make required changes, validate, and submit the data for approval.
If approvals are not enabled on the Job Data Installation page (i.e.—an AWE Process ID is NOT associated with 'Enable for
updating existing transaction' option), data gets pushed directly to the job records after that data inserted to the staging
records.

Scenario 3 : Re-Editing an Ongoing Request

Editing an ongoing request happens when either 1) the requester re-edits a pushback or withdrawn request, or 2) the
approver tries to change the details of an in-progress request (using the ‘Edit Details’ link for the approver).
In this scenario, the data not copied to the actual job records yet, but it does modify the staging records. When the user
relaunches the request, the system copies the data from the staging records to the fluid job component and presents it to
the user. The user can make required changes, validate, and submit the data.

Approval Flow
If the approver approves the request, the system copies the data to the job records from the staging records using the
component interface.
1. If the transaction is approved, staging data is pushed to the job records using the component interface.
2. If the approver denies the request, the transaction is terminated and completed. No data is copied to the job
records.
3. If the approver pushes back the request, the row is routed back to the requester; the user may rework and submit it
again or delete the transaction.

7 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Figure: Approval flow

Component Interface: As shown in the previous diagrams, the process uses the component interface to push data from the
staging records to the job records. HCM delivered the new CI, HR_JOBDATA_SAVE_CI, for this purpose.

New Roles & Permission Lists

Roles
ROLE NAME USE PERMISSIONS ASSIGNED

HR Admin HCCPCF1000
This role is responsible for administering the Approval
Approver HCCPHR3314
transactions to create a new Fluid Job Data request.
Fluid

HR Admin This role is responsible for administering the Approval

HCCPCF1000
Correction transactions to correct or edit the existing Fluid Job
HCCPHR3314
Apvr Fluid Data request.

HR
This role is responsible for administering the Job action HCCPCF1000
Administrator
transactions in Fluid Job Data. HCCPHR3314
Fluid

8 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
 HR Review This role is required to delete Fluid Job Data
Administrator transactions.

HR View This role is required to access View Details in Fluid Job

HCCPHR3316
Administrator Data.

Job Data AG This role is required to make modifications to the AG

Administrator template setup of the Job Data Modernization feature.

Permission Lists
PERMISSION LIST DESCRIPTION OBJECTS/PAGELETS ASSIGNED ROLES

• Administer Workforce GBL HR Admin Approver Fluid

Menu HR Admin Correction Aprv Fluid
o Manage Job HR Administrator Fluid
o Job Data Related
Actions
o Job Data Submit
Confirmation
o Job Data View
o Job Data Fluid
o Job Data Related
HCCPHR3314 Edit Fluid Job Data
Information

• Eoaw Myappv FluMenu

o Approval History View

• HR Install Job Menu

o Job Data Installation
o Configure Job CI
o Map Job Staging
Records

• Administer Workforce GBL HR View Administrator

Menu
o Manage Job
o Job Data Related
Fluid Job Data View Actions
HCCPHR3316
Only o Job Data View

• Eoaw Myappv FluMenu

o Approval History View

Phased Implementation Recommendation

9 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
If your organization would like to initially rollout the Job Data Modernization feature for certain business units or locations,
implement the following:
 Associate the required roles to access the Job Data Modernization feature for the HR administrators that belong to
the business unit or location so that only those administrators will have access to Modern Job Data.
 In cases where the HR administrator has access to employees from different business units or locations, and you
would like to restrict the administrator to have access to only the employees of a specific business unit or location,
then you can clone the delivered search record associated in Configurable Search configuration. Then add the
filter/add condition in the Where clause to restrict the data by business unit and/or location.

PeopleBooks reference: PeopleSoft HCM 9.2: Core Functionality: Application Fundamentals: Managing Configurable Search:
Setting up Search Configuration.

Depending upon the feature roll-out approach taken by your organization, you will need to look into redirecting users to
either Fluid version of Job Data or Classic version of Job Data.

10 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
CONFIGURING AND MANAGING THE JOB DATA SEARCH PAGE
This topic discusses configuring and managing the Search page for the Job Data Modernization feature.

Setting Up Search Configuration

The Search Configuration feature enables you to design custom search pages for a content reference based on your
organization’s needs. Administrators can set up searches that use either a standard record search or elastic search
definitions. Your organization has control over which fields should appear in Search Criteria and Search Results sections and
the order of fields. Configurable Search even allows the user to save the search criteria as well as view recent searches when
defined in the setup.
The PeopleBooks includes details regarding other options. PeopleBooks reference: PeopleSoft HCM 9.2: Core Functionality:
Application Fundamentals: Managing Configurable Search: Setting up Search Configuration.

Customizing Search Criteria and Search Results for the Job Data Modernization Feature
Navigation: Enterprise Components > Configurable Search > Manage Search Configuration

Figure: Search Configuration-General page with Standard Search as Search Type

Figure: Search Configuration-General page with Elastic Search as Search Type

11 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Status: Select Active to activate the search page. When the status is Inactive, the system will use the standard Tools
delivered search for the component.
Search Type: Select a search type. Options include:
 Elastic Search: Uses a search definition to perform a search.
 Standard Search: Uses a search record to perform a search.
Search Definition: This field is available when you select Elastic Search as the search type. Enter the search definition that
the system should use for this search page. For the Job Data Modernization feature, you can use the delivered search
definition HC_HR_JOB_DATA.
If your organization needs more or different fields to be a part of the search criteria or search results, then create a new
search definition based on HC_HR_JOB_DATA, remembering to consider the data security aspects and use the same in the
Search Configuration. Ensure the Elastic Search Definition is in a deployed state.

Note: Currently, Elastic Search is not Real-time; the results are based on the last time the index was updated.

Search Record: This field is available when you select Standard Search as the search type. Enter the record name the system
should use for this search. Supported Records types are SQL Table and SQL View.

Figure: Search Configuration-search record association

For Modern Job Data you can use the delivered search record EMP_SRCH_COR_FL.
If your organization needs more, different, or wants to include custom fields as part of the search criteria or search results,
then create a new record based on the EMP_SRCH_COR_FL, remembering to consider the data security aspects and use the
same in the Search Configuration. For multi-language enabled systems, you also need to review the Related Language
record associated to the base record.

Note: The Search record associated in this configuration is only for search page purpose, it will not replace the existing
search record associated to the actual component or menu override search record.

Configure Fields Page

Configure the fields to display in the search criteria and search results, along with their order.

12 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
13 PRODUCT DOCUMENTATION UPDATE
Copyright © 2021, Oracle and/or its affiliates
Figure: Search Configuration-Configure Fields page

In the case of a Standard Search, click the ‘Reload Fields’ button to populate the ‘Configure Criteria and Results fields’ grid
with all the fields from the associated search record. Based on the search keys, alternate search keys, and list items defined
in the record definition, the system will default the fields to be part of the criteria and results.
If your organization needs additional fields as part of the search criteria or search results, you can include them by selecting
the respective check boxes. Ensure that the additional fields you select have the proper record level indexes defined to
better handle the performance.
In the case of an Elastic Search, the system will select all the indexed fields to be part of the criteria and the results, it will pick
the fields (list box item) from the actual search record (search record associated at Component or Menu Item level).

Figure: Record field properties

14 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Include Image in Results: If the Employee Photo feature is not available in your system and you still want to display the
employee photo, then use EMPL_PHOTO as the source record.

Considerations and Limitations

• When configuring search record fields that require a prompt table, such as Location or Company, etc., you must
associate the prompt table in the record definition. You cannot configure the prompt table from Search
Configuration.

• Related prompts will NOT work as expected in most of the cases. For example, when working with a related prompt,
if the State field has a prompt record with a high-level key filed as Country, then the Country field value controls the
results on the search page.

• If a search record field is associated with a dynamic prompt, the prompt icon will not be shown in search page for
that field. In such cases, ensure that the prompt record (Record Type: SQL Table or SQL View) is associated to the
search record field, to have the prompt lookup on the search page.

• Search events (Search Init and Search Save) will not get triggered.

• Previous in List and Next in List options will not be available in transaction page to traverse to the next/previous
row from the results set.

15 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
CONFIGURING AND ADMINISTERING ACTIVITY GUIDE COMPOSER
This topic discusses configuring and administering activity guide templates for the Job Data Modernization feature.

Customizing Activity Guide Composer Configurations for the Job Data

Modernization Feature
The Activity Guide Composer (AGC) framework is designed to improve the deployment and management of fluid Activity
Guides (AG) by separating the technical and functional configuration.
PeopleBooks reference: PeopleSoft HCM 9.2: Products: Core Functionality: Enterprise Components: Working with the
Activity Guide Composer.
The AGC feature enables you to create activity guide templates that identify the steps a user should take to perform a
transaction. Additionally, use Page and Field Configurator (PFC) to hide and unhide the steps and fields required to perform
the job data transaction.
This section discusses how to configure and administer the Job Data activity guide and the changes needed for customizing
a page or step in the AG.

AGC Category Setups

PeopleSoft HCM delivers the AGC category and template setups for Job Data Modernization as system data. For
customizations, you do not need to modify anything in AGC Category setup; you should do this in the Activity Guide
Templates setup only.

Figure: AGC Category configuration

Use the following pages to manage the category information:

Category: Use the Instance Create Method to initialize instance properties, participants, and action item properties, or even
to add or delete action items. For example, it can manipulate the steps of the AG template in that specific instance.
Security: The Security page controls participants and their privileges to the AGC category and templates.
Context: Use contextual data defined as key fields to uniquely identify each activity guide instance. Apart from main keys
like employee ID/employment record/effective date/effective sequence to uniquely identify a Job row, there is an extra key
'Operator ID' to create instances for each logged in user per job data row. Context data fields are set in sync with the fields
that are defined in the Related Content Services (RCS) corresponding to each page in the activity guide.
Actions: Define action items that would enable the user to perform additional actions, such as exit an activity guide.

16 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Images: Identify images that you want to display in the sub banner of the fluid activity guide and associate the method to
fetch the same.
Steps: You must define a related content service that corresponds to each page or step in the activity guide. Associate steps
to a related content service that navigates the user to an application transaction page. For modern Job Data it is pages from
a single component saved as single transaction.

AGC Template Configuration-Customizations

You can configure and maintain additional activity guides and rules needed for users to complete personal and business
transactions.

Figure: AGC Template configurations

The Activity Guide Template Composer will guide you through a series of configuration steps where you will be able to select
options and enter parameters to configure your activity guide.
The delivered one is marked as system data and cannot be modified (01/01/1900). You can add a new effective dated
template and customize it.
Activity Guide Type: Job Data is a Single component Optimized Guided Vertical Non-Sequential activity guide.

Note: When you clone or insert a new row for an existing template, the system copies the same activity guide type over and
you cannot select a different activity guide type for the new template.

Security: Add any custom roles responsible for utilizing the activity guide process as End User.
Additional Actions: The delivered Job Data AG uses custom Exit and Submit buttons, through which you can have
additional logic performed.
To have validations and additional logic on Submit and Exit buttons, use the System Button Override method.
Steps for System Button Override:
1. Add button to the step page (transaction page in JOB_DATA_FL component) with specific style class.
For Submit – “ps_ag-custom-button-submit”
For Exit – “ps_ag-custom-button-exit”
2. Use “psc_hidden” to hide the button.
3. Invoke default action from PeopleCode. Sample Code (in button’s Field Change event).
Declare Function genOpenButtonScript PeopleCode FUNCLIB_PTGP.FUNCLIB FieldFormula;
AddOnLoadScript(genOpenButtonScript("#submit"));
AddOnLoadScript(genOpenButtonScript("#exit"));

Examples: PeopleCode (CompRecFld) - JOB_DATA_FL(GBL).HR_JOBFLD_WRK.SUBMIT_PB FieldChange

PeopleCode (CompRecFld) - JOB_DATA_FL(GBL).HR_JOBFLD_WRK.EXIT_BTN FieldChange

17 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Sub Banner: Employee Name is the primary display field. You can specify a static or dynamic image to display in each
activity guide instance. In the feature template setup, in addition to Name, Details (concatenated string of Employee ID-
Employment record-OrgRelationship description-Military Service description) and Job title details, you can have employee
photo appear as well. It displays an empty photo (placeholder image) in cases where the employee does not have a photo in
Identification Data. The ‘getEmployePhoto’ method defined in category setup handles the employee photo association.

Figure: AGC Template –Organize and Configure Steps configuration

Organize and Configure Steps: Rename the Drop Zone steps/pages using the Organize and Configure Steps page if
needed. Customize the pages using the delivered Drop Zone areas.
You can add custom fields using the Drop Zone pages, or the Drop Zone areas at the top and bottom of other main pages.
PeopleBooks reference: PeopleSoft HCM 9.2: Products: Core Functionality: Development Tools: Fluid User Interface
Developer’s Guide: Creating Pages for Fluid Applications: Creating and Configuring Drop Zones.
Additionally, use Page and Field Configurator (PFC) to hide or unhide the steps and fields required to perform the job data
transaction.
When you create an activity guide template, the system also creates a PeopleTools activity guide template using the
PeopleTools Activity Guide application process integration (API). This combines the technical data from the activity guide
category and the functional data from the activity guide template to save a PeopleTools activity guide template.
The ‘Instance Create Method’ specified in the setup will be executed whenever an activity guide instance is created from
AGC-AG template. When you create an instance from the template, the instance properties and action item details are
initially set based on the template definitions. The system controls this with the ‘InstanceCreation’ method.
1. Activity Guide steps are based on Page and Field Configurator (PFC) ‘Configure Page Visibility’ setup.

While creating the AG launch URL, the required data is passed as context data or URL parameter, to match the PFC
criteria setup. While creating the instance (before launching the AG), the ‘InstanceCreation’ method does a criteria
match per PFC setup. The PFC criteria sequence match and ‘Configure Page Visibility’ setup determine if it will hide
or unhide the AG steps. The method picks up the pages that need to be hidden, find outs the activity guide item ID
by matching it with RCS defined for each AG step, and hides the corresponding step in that instance.

This is specific to our feature. Methods check whether ‘Event Mapping’ is enabled for the request component (AG
component) Content Reference-Job Data Fluid.

2. Set the AG pagelet title.

18 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
 Methods set the AG pagelet title to the corresponding request Action-Action Reason description. For example, if
the user is requesting a Promotion transaction with the reason of Outstanding Performance, the default label of
‘Job Data’ is replaced with concatenated description- ‘Promotion - Outstanding Performance’.
For information on ‘Configure Page Visibility’ and ‘Event Mapping’, see the Configuring and Administering Page and Field
Configurator topic in this documentation.

Related Content Service (RCS) Setup

Define a related content service that corresponds with each page in the activity guide. Associate steps to a related content
service that navigates the user to an application transaction page.
Example: Job Data: Work Location page from JOB_DATA_FL component.

19 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Figure: Related Content Services definition page.

Add the URL parameters to uniquely identify a specific job request row, which includes:
1. Key parameters like EMPLID, EMPL_RCD, EFFDT, and EFFSEQ.
2. Parameters to match PFC criteria ACTION_CD, ACTION_REASON, REG_REGION, BUSINESS_UNIT,
HCR_JOB_WIP_STATUS.
3. Additional parameters for certain validations while launching the request component.

20 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
CONFIGURING AND ADMINISTERING PAGE AND FIELD CONFIGURATOR
This topic discusses how to configure and administer the Page and Field Configurator utility for the Job Data component.
PeopleBooks reference: PeopleSoft HCM 9.2: Products: Core Functionality: Enterprise Components: Page and Field
Configurator.

Configuring Pages and Fields to Display for a Job Data Request

The criteria section allows the administrator to select a field and then associate conditions. Select the ‘Edit Criteria’ link to
open the ‘Select Field’ page to select any visible level zero field on the component.

Figure: Page and Field Configurator – Selecting a Field to define criteria

If there is more than one condition defined, then each condition will be joined using the logical operator ‘AND’ internally.
For example, if different sets of fields or pages are required for different business units with the same action code, then the
criteria can be formed by combining the fields that are in level 0.
Configure Field Properties: Use to hide fields that are not required for that job request.
Configure Page Visibility: Use to hide or unhide the page as a whole in the component. It also has the capability to make a
page (activity guide steps) as display only.

21 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Figure: Page and Field Configurator – Configuration page

22 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
For this feature, the visible level zero fields are Action, Action Reason, Regulatory Region, Business Unit, Status (Request
status like INI, CIN, PBN, PRO,etc.), Organizational Relationship, Person of Interest Type, Military Service, etc. fields. Even
though the fields are ‘visible level zero fields’ in the design settings of the Application Designer page, PeopleCode or fluid
page style (psc_hidden) will hide them and therefore they will not be available in the page header.
The Regulatory Region and Business Unit fields in level zero are the ones users select on the Manage Job component,
Request Details secondary page. Those values are passed as a context or URL parameter to the activity guide component. In
this way, the PFC controls the appearance of the transaction steps and fields of the activity guide. This will not set or change
the actual Regulatory Region or Business Unit field values of the employee for that job data row.
The criteria are evaluated when the component is loaded (Post Build event). Any application level PeopleCode that is fired
after the component configuration has been executed can overwrite the changes.

Note: Customers should make sure that the criteria setup in PFC and the component, page, field properties or PeopleCodes
are in sync. For example, if a required field is made invisible using PFC, custom logic should be added to populate a value for
it.

In this feature, while creating the activity guide instance (before launching the AG), ‘InstanceCreation’ method does a criteria
match check per PFC setup. Based on the criteria sequence match and ‘Configure Page Visibility’ setup, the AG steps will
hide or unhide to the user.
Oracle recommends that you do NOT hide the ‘Summary’ and ‘Validate’ pages, as the ‘Configure Page Visibility’ is mainly to
control the pages and steps where a user enters request related data. Configure Page Visibility also lists pages marked as
‘Hidden’ in the component definition, as you can override the settings done in the Application Designer. Oracle also
recommends that you do not make any such pages visible, as we do not have corresponding activity guide steps in the
template setup.

Figure: User List setup of Page and Field Configurator

Use the ‘User List’ page to define the list of users to whom this configuration needs to be applied. The demo data is
configured at ‘Header Level’ only. The option ‘Sequence Level’ will allow the user to define separate user lists for each
sequence number. With ‘Sequence Level’, the lowest matching criteria will get applied unless the setup is NOT configured to
use ‘Apply Additively’ on the criteria setup page.
For the Job Data Modernization feature, Edit Details functionality for final level approvers and requesting a job data change
are using the same component JOB_DATA _FL. Users who have the ‘HR Admin Approver Fluid’ or the ‘HR Admin Correction
Apvr Fluid’ roles should see all the fields and pages in the Edit Details functionality. However, the user with the ‘HR

23 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Administrator Fluid’ role who created the job row should see only a limited set of fields required for that action code.
Therefore, if a user has the ‘HR Administrator Fluid’ role in addition to either the ‘HR Admin Approver Fluid’ or the ‘HR
Admin Correction Apvr Fluid’ role, the user will see all the pages and fields on the Job Data fluid component.

Adding Criteria Fields to Control AG Steps and Fields

If you want to have additional field(s) to control the pages and fields inside the AG component, follow these steps.
For the example, assume the follow: Action-'Termination', Action Reason-'Self-resignation', and a Sub-Reason field value of
‘lower pay’.
1. Add the Sub-Reason (say SUB_REASON) field to DERIVED_JOB_HDR record and bring it to
‘HR_JOBDATA_LVL_SBF’ subpage in level zero (Component-JOB_DATA_FL). Keep the page field property ‘Display
Only’ selected and ‘Invisible’ deselected to make it a visible level zero field.
Refer ‘ACTION’ field in HR_JOBDATA_LVL_SBF subpage.

2. Modify the Related Content Services corresponding to AG steps to accommodate the new parameter.
Recommendation is to add to all the RCS definitions corresponding to each AG steps, as it should work even if the
first step ‘Work Location’ is hidden for the job request.

3. Modify the AG launch URL PeopleCode references to add the new parameter with a value.
Example: Modify the request details secondary page on ‘Manage Job’ component to get the ‘Sub-Reason’ value
from the user. Change the PeopleCode on the ‘Continue’ button to pass this as a URL or context data to launch the
AG.

4. On JOB_DATA_FL component PostBuild PeopleCode, get the Sub-Reason value using

%Request.GetParameter("SUB_REASON"); assign it to DERIVED_JOB_HDR.SUB_REASON.Value.
This will assign the Sub-Reason value to level zero visible field, which in turn allows the controlling of the AG fields
using the PFC criteria setup.

5. Additionally, modify the Application Class PeopleCode methods related to instance handling, which controls AG
steps.
Refer to the Application Class PeopleCode-HR_JOBDATA_UTILITIES. AG_InstanceManage and
HR_JOBDATA_UTILITIES.InstanceProcess, and modify the methods inside to process the new parameter.

Configuring Fields to Display in the ‘View Details’ Component

The View Details (JOB_DATA_VW_FL) component shows each job data row in a single page, with the details concatenated as
sections one below the other.
For the View Details page, when you click the ‘Next’ and ‘Previous’ buttons on the page, it will not refresh the component or
fire page activate PeopleCode. Hence, the criteria setup based on the Action value will not help to control the field display as
it does in the Fluid Job Data component.
Oracle recommends showing all the fields in View Details component. Additionally, configure PFC for the View Details
(JOB_DATA_VW_FL) component for any section you need to hide from any of the logged in users (for example, if a level 1-
HR Administrator should not see any of the Salary and Compensation related information) by doing the following:
1. Add a new sequence without any criteria and configure field properties to hide all the fields inside Salary,
Compensation sections. This should be all the fields that are not marked as ‘Invisible’ inside Application Designer
page field properties.
2. Use ‘User List’-‘Applies To’ functionality to apply the defined sequence to the level 1-HR Administrator only.
3. Configure the Event Mapping on PostBuild or Page Activate to enable PFC setup.

Configuring Event Mapping to Enable PFC Setup

The PFC configuration defined for the component will become effective only if the services defined by the utility are mapped
to the corresponding portal registry entries. This is done using Event Mapping functionality available from PeopleTools 8.55.
Navigation: PeopleTools > Portal > Related Content Service > Manage Related Content Service.

24 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
The related content definition EOCC_POSTBUILD contains the application class PeopleCode that needs to be hooked to the
target components PostBuild PeopleCode events. The configuration criteria validation and application will happen only
once. The criteria are evaluated when the component is loaded (PostBuild Event). Any application level PeopleCode, which is
fired after the component configuration has been executed, can overwrite the field changes.
For the Job Data Modernization feature, use the below configuration to hide the fields and pages/steps per the criteria
setup. Hiding or unhiding the pages in the component or controlling the AG steps are purely from feature specific code
using ‘Configure Page Visibility’ setup.

Figure: Event mapping configuration for Page and Field Configurator usage in Job Data fluid component.

For the Manage Job component, if any of the fields on the ‘Create Job Action’ or ‘Correct Job Data’ secondary modal page
are to be hidden, use the below configuration:
Example setup shows the fields Regulatory Region, Business Unit fields hidden in the modal page using PFC setup.

Figure: Page and Field Configurator – Sample Configuration for Manage Job component.

25 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Figure: Event mapping configuration for Page and Field Configurator usage in Manage Job component.

Migrating PFC Demo Data Using ADS

We have delivered PFC configuration for all delivered actions as demo data.
You can use data set EOCC_CONFIGURATION to migrate PFC setup data from one database to another.

Figure: Sample ADS project for PFC setup data migration

26 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Figure: Sample ADS project for PFC setup data migration for ‘Manage Job’ and ‘Job Data’ component

Limitations of Using PFC for the Job Data Modernization Feature

1. PFC does not support non-data entry fields like group boxes and radio buttons.
Note: The modern Job Data pages are designed in such a way that when all the fields (fields NOT marked as
Invisible in the Application Designer page design settings) inside a group box are hidden, the group box title on the
page is hidden.
2. In PFC set up, do NOT use the ‘Required Field’ check box for the Job Data fluid component fields, as it makes that
particular field required for all the rows in the scroll, when only one row at a time is visible to the users.
3. The activity guide steps get are hidden or unhidden based on the ‘Configure Page Visibility’ of the component. As
the AG instance needs to be created before the component is launched, to hide/unhide pages (AG steps) feature
specific code checks PFC configuration. This is in addition to the PFC criteria mapping fired from post build event of
the component (as Event Mapping is configured for component PostBuild). Therefore, in total, the criteria matching
happens two times.
4. Fields on Drop Zone pages are currently not supported.

27 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
MANAGE CUSTOMIZATION

Overview
Manage customization for Fluid Job Data feature provides a simple to use, intuitive application for administrators to manage
their customization.

Manage customization provides the ability to reapply your customization from Classic Job to Fluid Job.

In general PeopleSoft recommend to utilize the Drop Zones to add custom fields, records and pages that are only used for
customizations. The manage customization will reduce implementation, customization time and retrofit efforts. The real
benefit is that you do not have to re-implement during an image update.

Job Data Modernization - Manage Customization

Job Data Modernization design allows customers to configure the Job transactions with or without approval. Whenever a
transaction is performed the data is saved to the staging records and then pushed to transaction records based on the
approval configuration using Component Interface of Classic Job Component.

When Approvals are enabled, the data for the in-progress, pushback, deleted, and rework status transactions will be
retrieved from the staging record and presented in Job Pages. When the transaction is approved, the changes are pushed
via CI to update the respective base/transaction records.

There are different features available to better manage the customization with fluid transactions as well like Drop Zones,
Event Mapping, Page and Field Configuration, Activity Guide Composer etc.. Apart from these there are few pages delivered
with Fluid Job Data feature like Map Staging Records and Configure Job CI and these are available via the Manage Job tile to
provide a more flexible and easier way for customers to handle/map custom records.

The below sections will explain how to associate Custom Pages and Custom Record Fields added to the delivered Classic
Pages to Fluid Job Component/Pages using Drop Zone and without Drop Zone.

Note: The configuration and setup for customization will be carried out to level 2 of the Job record. The Manage
Customization setup pages are designed to work only for Manage Job transaction.

The below use cases are illustrates with some examples

Sample Custom data
Record: HR_XYZ_JOB
Staging Record: HR_XYZ_JOB_STG
Sub Page: HR_JOB_XYZ_SBF
Component Interface: HR_JOB_XYZ

Use Case 1: Adding Custom Page into Fluid Job flow

Handle the new custom page in classic Job data.

Perform the following the steps:

1. Clone the custom source record HR_XYZ_JOB to create the respective staging record HR_XYZ_JOB_STG . Follow
the Steps to Create the Staging Record .

2. Create a fluid subpage HR_JOB_XYZ_SBF for the classic custom page HR_JOB_XYZ. Have a look on Page Styling
Considerations during subpage creation.

3. Ensure the classic custom page is tagged to the classic JOB DATA component.

4. Clone the delivered CI HR_JOB_DATA_SAVE_CI to create the respective custom CI HR_JOB_XYZ. Follow the Steps
to Create the Custom CI for naming standards.

5. Tag the subpages to the Drop Zones on the Drop Zone configurations for the Fluid Job Data JOB_DATA_FL and
the View Details JOB_DATA_VW_FL components.

28 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
 6. Add the source and staging records on the Map Job Staging Records page.

7. Integrate the custom CI on the Configure Job CI page.

8. Add the custom CI name on the Job Data Installation page.

Use Case 2: Adding Custom Fields into Fluid Job Component using Drop Zones
Handle the custom fields inside a delivered record or a custom record.

1 Custom fields in a delivered record.

Perform the following the steps:

1. Modify the respective staging record HR_XYZ_JOB_STG . Follow the Steps to Create the Staging Record .

2. Create a fluid subpage HR_JOB_XYZ_SBF and add the custom fields. Have a look on Page Styling
Considerations during subpage creation.

3. Configure the above created subpage HR_JOB_XYZ_SBF to the Drop Zones on the Drop Zone configurations
for the Fluid Job Data JOB_DATA_FL and the View Details JOB_DATA_VW_FL components.

4. Clone the delivered CI HR_JOB_DATA_SAVE_CI to create the respective custom CI HR_JOB_XYZ. Follow the
Steps to Create the Custom CI for naming standards.

2 Custom fields inside a custom record – Follow the use case 1.

Use Case 3: Adding Custom Record and Fields into Fluid Job Component without Drop
Zones
Handle the custom record fields directly on the fluid job data pages

Perform the following the steps:

1. Clone the custom source record HR_XYZ_JOB to create the respective staging record HR_XYZ_JOB_STG. Follow the
Steps to Create the Staging Record

2. Modify the existing fluid subpage and place the custom record fields. Have a look on Page Styling Considerations
during subpage creation.

3. Clone the delivered CI HR_JOB_DATA_SAVE_CI to create the respective custom CI HR_JOB_XYZ. Follow the Steps
to Create the Custom CI for naming standards.

4. Add the source and staging records on the Map Job Staging Records page.

5. Integrate the custom CI on the Configure Job CI page.

6. Add the custom CI name on the Job Data Installation page.

Use Case 4: Adding Custom Fields into Fluid Job Component without Drop Zones
Handle the custom fields directly on the fluid job data pages

Perform the following the steps:

1. When you have custom fields alone to migrate, modify the delivered staging record using Map Job Staging Records
page section.

2. Place the custom fields into the delivered fluid subpages.

Note: Due to customization, if the structure of the delivered job data component changes, then you need to follow the
manage customization steps. If no customization exist, then the existing fluid job data works.

Steps to Create the Staging Record

1. Clone the respective source record so all the fields in the source record are in the staging record.

29 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
 2. Identify the highlighted fields EFFDT, EFFSEQ, and HCR_ACTN_SEQN as key fields in the staging record.

3. Build the staging record HR_XYZ_JOB_STG.

Figure: Mandate key fields for staging record creation- HR_XYZ_JOB_STG.

Steps to Create the Custom CI

1 Clone the delivered component interface: HR_JOB_DATA_SAVE_CI.

2 Drag the custom records and their associated fields.

Property Name of all key fields should be named “KEYPROP” + field name, so the PROBATION TYPE should be
“KEYPROP_HR_PROBAT_TYPE”.

3 Name all other data fields “PROP”_+ field name, so the field UNION SENIORITY DATE should be
“PROP_HR_UNION_SEN_DT”.

4 Change the property name for the record to “COLL_” + name of record, so the record HR_XYZ_JOB will become
“COLL_HR_XYZ_JOB”.

Figure: Component interface details.

Security for Custom CI

The custom CI must be tagged to the following permission list.

30 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
 PERMISSIONS ASSIGNED DESCRIPTION

HCCPHR3314 Edit Fluid Job Data

HCCPHR3310 Job Data

Map Source and Staging Records

This page is a setup page for the source and staging records of delivered and custom CI.

Add the source record HR_XYZ_JOB and staging record HR_XYZ_JOB_STG in the Map Job Staging records. The mapping
done in this page will be reflected in the Configure Job CI page.

Note: HCR_JOB_STG, PER_ORG_INS_STG, PER_ORG_ASG_STG, and BEN_PRG_PRT_STG are not editable due to some
technical limitations. Do not replace these staging records, however you can add or remove the fields for customization. You
can replace the remaining delivered staging records with the custom staging record.

The delivered source record name are not editable, whereas the custom record name are editable .The flag
HCR_CUSTOM_REC used to ensure the custom record.

Figure: Source and staging record mapping.

Configure Job CI
This page is a setup page for CI. Add the new custom CI on the Configure Job CI page.

31 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Figure : Add the new component interface

Click the Load/Reload button to populate the source and staging records. The source and staging records grid will load the
records from the CI. If the staging records are not populated by default, then a new staging record needs to be associated,
then save the page.

Figure: Source and staging records for the selected component interface.

Job Data Installation

By default, the CI displays the default CI name on the installation page. Replace it with the custom CI name HR_JOB_XYZ and
save.

32 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Figure: Tag the component interface HR_JOB_XYZ in Job data installation page.

Now proceed with the transactions using the Manage Job tile.

Maintaining Customizations Using Drop Zone Areas

This topic explains how to maintain your customizations using delivered Drop Zone (DZ) areas and related setups or
configurations.
You can add custom fields using the Drop Zone pages or the Drop Zone areas at the top and bottom of other main pages.
Suppose the requirement is to change the delivered Drop Zone 1 step/page to a custom page as shown below.

Figure: Job Data fluid Drop Zone 1 step as custom page.

Changes Needed on the Fluid Job Data Component

Create a custom fluid subpage, say HR_JOB_XYZ_SBF. Follow the 2-column layout like other pages and subpages inside the
activity guide (AG).
AG Composer setup changes: Add a new effective dated template and customize it.

33 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Figure: On the AGC Template Configuration, add a new effective dated template.

Rename Drop Zone steps/pages using ‘Organize and Configure Steps’.

Figure: Drop Zone 1 step renamed as ‘XYZ Company Job’.

Customize the pages using the delivered Drop Zone areas. Top and bottom Drop Zones are available in all the main pages
inside the AG.

Drop Zone configurations

Navigation for Drop Zone configuration: PeopleTools > Portal > Configure Drop Zones.
Configure Drop Zones- Drop Zone 1 page for the Fluid Job Data component (Activity Guide component-JOB_DATA_FL).

34 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Figure: Configuring bottom drop zone of Drop Zone 1 page.

Data storage related changes:

• Create corresponding staging records and store the custom data while submitting the request.
Refer to Application Class: HR_FLUID_JOBDATA:STGTransactions PeopleCode method-SaveDatatoStg.
• Restore/paint in-progress request data to the AG component-when the requester re-edits a pushback or
withdrawn request, or the approver changes the request data using the ‘Edit Details’ link by using the Application
Class: HR_FLUID_JOBDATA:STGTransactions, PeopleCode method-LoadDatafromStg.

Changes Needed on the View Details Component

Corresponding to AG component, the changes should be made in the View Details component as well.

Figure: View Details page Drop Zone 1 section as custom subpage.

35 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Create a replica page of HR_JOB_XYZ_SBF as HR_JOB_VW_XYZ_SBF (if needed). HR_JOB_VW_XYZ_SBF has page fields
using the below highlighted property (to avoid showing disabled edit boxes-when display only).

Figure: Page field property set to ‘Text Only’

Drop Zone configurations: Navigation for Drop Zone configuration: PeopleTools > Portal > Configure Drop Zones.
Configure Drop Zones-Drop Zone 1 subpage for View Details (View/Display only component-JOB_DATA_VW_FL).
Customize the pages using the delivered Drop Zone areas. Top and bottom Drop Zones are available on all subpages inside
the View Details page and correspond to the main pages in the AG.

Figure: Configuring bottom drop zone of Drop Zone 1 subpage/section in View Details page.

36 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Rename the group box label if the section on the View Details page should show as ‘XYZ Company Job’ instead of Drop
Zone 1 (no configurable options in PIA exists).

Figure: View Details page Drop Zone 1 section as custom subpage, group box label renamed as ‘XYZ Company Job’ instead of ‘Drop Zone 1’.

Refer to the below methods to paint the data on the View Details component:
• Function UPdate_Mode_N PeopleCode DERIVED_JOBDATA.EMPLID FieldFormula.
• Function UPdate_Mode PeopleCode DERIVED_JOBDATA.EMPLID FieldFormula.
• Function RELOAD_STAGING PeopleCode FUNCLIB_HRF_JOB.EFFDT FieldFormula.
• Function EDIT_JOB PeopleCode FUNCLIB_HRF_JOB.EFFDT FieldFormula.

Page Styling Considerations

• Best practices is to follow the 2-column styling for the pages and subpages in line with other delivered pages.

37 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
 • Specific to this feature, the related descriptions are shown below to display control field instead of adjacent to it.
Please follow the styles applied to related display container, display control field, and related display field to have a
similar implementation.

If the display control field is empty, add logic to hide the related display field in,
-Main Page Activate PeopleCode. Refer HR_JOBDATA_WL_FL Page Activate PeopleCode.

If the display control field is controlled by another field change and gets empty, then add logic to hide the related
display field in the field change PeopleCode.
Example, the Work Location page Business Unit (BUSINESS_UNIT) field change controls the Department (DEPTID).
Refer JOB_DATA_FL.GBL.JOB.BUSINESS_UNIT.FieldChange(Component PeopleCode).

• Select the ‘Adjust Layout for Hidden Fields’ property for the group boxes to hide the group box title if all the fields
inside are hidden.

38 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
ADMINISTERING APPROVALS CONFIGURATIONS
With the Job Data Modernization feature, the Approval Workflow Engine (AWE) routes job data request approvals. The
following sections explain the AWE configuration for the modern Job Data functionality. Please refer to PeopleBooks
documentation on the topic to understand the basic functionality of AWE.
The modern Job Data functionality, by default, uses the process IDs ‘JobActions’ (Create-new transaction) and
‘EditJobActions’ (Correct-updating existing transaction), which are registered with the AWE transaction registry.

Modifying AWE Thread Descriptions

The feature delivers the Application Class HCR_JOB _AWE.threadDescr to use for the following purposes:
1. To set the thread description of the request in the approval chain.
2. To set the Summary description of the request in the Pending Approvals page of fluid approvals.
3. To populate the approver information in the approval chain.
In order to override any of the delivered descriptions, clone the application class and override the appropriate method.
Update the thread package and class fields of process IDs to point to the cloned class.

Configuring Additional Actions

There are new transaction IDs under the Mobile Approval Options for each of the AWE process IDs ‘JobActions’ and
‘EditJobActions’. Additionally, both are tagged under the newly created ‘Manage Job’ transaction group, as shown in the
following screenshots:

Figure: Mobile Approval Options for Manage Job transactions.

39 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
The Fluid Approvals framework utilizes this configuration to control the availability of approval actions on the approvals
page and validations for comments.
Navigation: Enterprise Components > Approvals > Approvals > Mobile Approval Options.
‘Approve’, ’Deny’, and ‘Pushback’ actions are turned ON for the feature. ‘Mass Approvals’ and other actions can be enabled
by checking the respective check box for the transaction. The event handler application package used by the AWE process
definition is configured and this application class needs to be cloned to do any additional processing for the newly enabled
actions.

Adding and Deleting Approval Steps

Add or delete approval steps by modifying the delivered AWE process definition. Please refer to the peopleBooks
documentation on Approval Process Setup for more information.
peopleBooks reference: PeopleSoft HCM 9.2: Products: Core Functionality: Approvals Framework: Setting Up Approvals
Framework Process Definitions.
While AWE controls the steps in the approval process, the WIP status corresponding to each step is defined by translate
values of the HCR_JOB_WIP_STATUS field.

Configuring Approvals Based on Different Job Actions

Administrators can configure different process definition IDs for an AWE process ID associated to modern Job Data
transactions. The definition level criteria should be set as user-defined criteria. This criterion determines which process
definition ID to use for the approval process. In the delivered system, a single process definition ‘ByRoles’ for process IDs
‘JobActions’ and ‘EditJobActions’ are delivered with the definition level criteria as always true.
Configure separate definition IDs with different user defined criteria to use different approvals based on transaction specific
data.
A common use case may be routing a request for a pay rate change transaction to the compensation administrator and a
termination request to the benefits administrator.

Configuring a Process Definition ID with User Defined Criteria

Prerequisites: User lists for different transactions are defined.
1. Navigate to Enterprise Components > Approvals > Approvals > Approval Process Setup.
2. Search for the process definition for the Manage Job Transactions. ‘Job Actions’ is the delivered process definition
for Create (New Job Data row) transaction.
3. Click the Clone Approval Process link to clone the approval process.

Figure: Copy Approval process definition.

40 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
 4. Enter the Definition ID description and date.
5. Under the Definition Options section, click the Definition Criteria link.
6. On the Criteria Definition page, change the Criteria Type to 'User Entered'.

This criterion is used to determine which definition ID is to be used to process the approval.

Note: If multiple definitions return criteria of true, the definition with the highest priority is used.

Figure: Configure criteria

7. Under the User Entered Criteria section, provide the description.

8. Use the Field Criteria section to select a record and field on which to control and filter ranges of data or types of
data placed in the file you want to use in the approval process.
Example: For Action=Termination.
Select a record that you want to use in defining approval criteria.
Record Name: HCR_JOB_STG
Field name: Select the Action field from the prompt.
Criteria Operator: Equals
Value: TER
9. Under the Definition Option section, define the Stage/Path/Step for your approval flow.

41 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
 Figure: Configure process definitions

10. Set the status of approval process definition as active.

Note: Please set the status of the delivered definition (Criteria as always) to inactive.

Modifying the Approval Page

The system uses the Enterprise Component feature ‘Page Composer’ to build the approval pages presented to the approval
users. The required changes can be made for the compositions ‘JobActions’ and ‘EditJobActions’ under the definition
‘APPROVALS’ in this setup.
Navigation: Enterprise Components > Page Composer > Page Composer
PeopleBooks reference: PeopleSoft HCM 9.2: Products: Core Functionality: Enterprise Components: Page Composer.
Edit Details link: This link will be available if the user is a final level approver and authorized to access the ‘JOB_DATA_FL’
component in Correct History mode.
Please refer Application Class PeopleCode-HCR_FLUID_APPROVALS.FieldEvents.doLinksSection method for the
implementation.

Approval Process Setup

HCM delivers the following Process IDs: ‘JobActions’ for Create Job Data row and ‘EditJobActions’ for correct/update an
existing job data row.
Definition ID: by Roles
Navigation: Enterprise Components > Approvals > Approvals > Approval Process Setup.
The approval process for the Job Data Modernization feature uses role-based user list definitions. It is a single stage, single
path process definition.

42 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Figure: Process definition setup of ‘JobActions’ for Create job data row

Figure: Process definition setup of ‘EditJobActions’ for correct/update an existing job data row

43 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
AWE Events Used for Approvals
The following events are delivered as part of the approval process. The Fluid Approvals component is configured as the
target component for all the notification types.

EVENT NAME DESCRIPTION PROPERTIES

On Process Launch This is triggered when the request Notification type: Email
gets submitted and approval flow is
Participants: Requester
launched successfully.

Route for Approval This is triggered when the request Notification type: Email and Push
gets routed to an approver at any level Notification
in the approval chain.
Participants: Approvers

On Final Approval This is triggered when the final Notification type: Email and Push
approver approves the request. Notification
Participants: Requester

On Final Denial This is triggered when the final Notification type: Email and Push
approver denies the request. Notification
Participants: Requester

On Cancel This is triggered when the requester Notification type: Email and Push
withdraws the request. Notification
Participants: Approvers

On Terminate This event triggered when the Notification type: Email and Push
approval is terminated. This is used by Notification
the approvals to pushback a request
Participants: Requester
from any level of approver to
requester.

Email Notification Templates

This section discusses the generic notification templates used for all the email notifications.
The following generic templates are in use to define the email notifications configured in AWE Approvals. The following
table lists the template definitions and the code where it is used. If the email needs to be modified to alter the content or to
include additional parameters, update the template definition or add additional parameters in the PeopleCode.
Navigation: PeopleTools > Workflow > Generic Templates.

TEMPLATE NAME USE PARAMETERS USAGE

EditJobActionRequestAck Acknowledgement for %1 – URL to approval Configured as email

Request-Email notification component template in AWE
sent to the requester when a %2 - ID of the employee for configuration for
correction transaction is whom the request is in process ID:
submitted for approval. progress EditJobActions

44 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
 %3 – Name of the employee Event: On Process
for whom the request is in Launch
progress
%4 – Description of Action

EditJobActionRequestDenied Email notification sent to the %1 – URL to approval Configured as email

requester when the component template in AWE
correction request denied. %2 - ID of the employee for configuration for
whom the request is in process ID:
progress EditJobActions
%3 – Name of the employee
for whom the request is in Event: On Final Denial
progress
%4 – Description of Action

EditJobActionRequestPushback Email notification sent to %1 – URL to approval Configured as email

requester when approval is component template in AWE
push back for review for a %2 - ID of the employee for configuration for
correction transaction whom the request is in process ID:
progress EditJobActions
%3 – Name of the employee
for whom the request is in Event: On Terminate
progress
%4 – Description of Action

EditJobActionRequestSubmitted Request Submitted for %1 – URL to approval Configured as email

Approval-Email notification component template in AWE
sent to the approver when a %2 - ID of the employee for configuration for
correction request submitted whom the request is in process ID:
for approval. progress EditJobActions
%3 – Name of the employee
for whom the request is in Event: Route for
progress Approval
%4 – Description of Action

JobActionRequestAck Acknowledgement for %1 – URL to approval Configured as email

Request-Email notification component template in AWE
sent to the requester when a %2 - ID of the employee for configuration for
new job row request whom the request is in process ID: JobActions
submitted for approval. progress
%3 – Name of the employee Event: On Process
for whom the request is in Launch
progress
%4 – Description of Action

JobActionRequestApproved Email notification sent to %1 – URL to approval Configured as email

requester when a new job component template in AWE
row request approved. %2 - ID of the employee for configuration for
whom the request is in process ID: JobActions
progress
%3 – Name of the employee Event: On Final Approval
for whom the request is in
progress
%4 – Description of Action

45 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
 JobActionRequestDenied Email notification sent to the %1 – URL to approval Configured as email
requester when a new job component template in AWE
row request denied. %2 - ID of the employee for configuration for
whom the request is in process ID: JobActions
progress
%3 – Name of the employee Event: On Final Denial
for whom the request is in
progress
%4 – Description of Action

JobActionRequestPushback Email notification sent to %1 – URL to approval Configured as email

requester when approval is component template in AWE
push back for review, for a %2 - ID of the employee for configuration for
new job row request whom the request is in process ID: JobActions
progress
%3 – Name of the employee Event: On Terminate
for whom the request is in
progress
%4 – Description of Action

JobActionRequestSubmitted Request Submitted for %1 – URL to approval Configured as email

Approval-Email notification component template in AWE
sent to the approver when a %2 - ID of the employee for configuration for
new job row request whom the request is in process ID: JobActions
submitted for approval. progress
%3 – Name of the employee Event: Route for
for whom the request is in Approval
progress
%4 – Description of Action

JobActionRequestWithdrawn Email notification sent to the %1 – URL to approval Configured as email

approver when the requester component template in AWE
withdraws a new job row or %2 - ID of the employee for configuration for
correction of an existing job whom the request is in process IDs: JobActions
row. progress and EditJobActions
%3 – Name of the employee
for whom the request is in Event: On Cancel
progress
%4 – Description of Action

46 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
ADMINISTERING TRANSACTION SUMMARY
Transaction Summary displays a list of fields that changed during a guided transaction, comparing old and new values for
the fields.
The process captures and stores a snapshot of a configured field’s value as the “Old Value” from the component buffer. On
the final step of the transaction, the process again captures a snapshot of values and stores them as the “New Value”. This
information is then presented as a side-by-side summary of changes.
This summary can be saved and retrieved later to view the summary of changes.

Transaction Summary in the Job Data Modernization Feature

Modern Job Data uses the Transaction Summary framework to show a list of fields on the Summary page (last step of the
guided process) that were changed by the user during the job request. The Summary page allows the user to review the
changes and submit the transaction.
The fields that are listed on this page are derived from Transaction Summary configuration page.
This framework utilizes component level event mapping. Once the fields are configured, the administrator should select the
CREF and create event mapping by clicking the Apply Configuration button on the Map to Portal Registry page.
PeopleBooks reference: PeopleSoft HCM 9.2: Products: Core Functionality: Application Fundamentals: Working with
Common Components: Configuring Transaction Summary.

Configuring Transaction Summary

Navigation: Set Up HCM > Common Definitions > Transaction Summary > Configure Transaction Summary
Use the Transaction Summary Configuration component to configure different sets of fields to display for different actions.
The setup provides a provision to select fields from pages of the selected component. The administrator is allowed to define
different criteria based on the business requirements. The administrator is also allowed to configure related descriptions for
fields driven though code.
Please note the following while configuring the Transaction Summary:
• Oracle recommends that important fields that you expect the user will change during the transaction be configured
here.
• Transaction Summary is dependent on data in the component buffer and transaction keys.
Note: A known limitation, the changes to key fields like effective date and effective sequence, will not be tracked in
the transaction summary.
• Fields on Drop Zone pages are currently not supported. As such, if there any Drop Zone pages, the changes to
fields will not be tracked.
• Transaction Summary is timestamped data, stored and retrieved for later use. The data captured on the requester’s
component will not be translated when the transaction is viewed in other languages.

The user will see a subset of fields on the actual application page, based on whether or not he or she has enabled the ‘Show
only changed’ flag and what fields have changed. If multiple criteria evaluate to true, the framework will use the one with the
lowest sequence number to generate the summary.

Configuring Fields From a Grid

When configuring fields from a grid in an application page:
• Mark one of the key fields as the group header.
• Mark all other fields from the grid as group members by assigning them the same group number value.
The combination of group header and group number will group fields from a grid row in the transaction summary.
If not done, each field will be processed as an individual field having multiple rows.
• From the grid, configure only important fields to keep the transaction summary meaningful.

For Example: The Pay Component grid has many columns, as shown here.

47 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
 Pay Components columns

From this grid, the administrator should configure important editable fields that are expected to be changed by the
user.
Since the value of the compensation rate 75.00000 is meaningful only when appended with the Rate Code value
KAUTO, the Rate Code field is marked as the group header. Other fields from the grid should be assigned the same
group number. An example of this grouping is shown in the following image.

Compensation fields marked as group 1 members

At runtime, when a group header field is processed, all fields with the same group number are processed together
and are presented as a group on the summary page, demarked with a grey separator between each group of fields.

Figure: Transaction summary details

48 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Transaction Summary on the View Details and Approval Component
The Modern Job Data feature utilizes the Transaction Summary to display a summary of changes in the View Details
component for completed or in progress rows. The Transaction Summary framework is utilized to display the summary of
changes to the approver.
To achieve this, the transaction summary is saved to the Transaction Summary record. This record is configured in the
transaction summary configuration
For Fluid Job data, it uses the record ‘HCR_JB_TRAN_SUM’.

Figure: Configuring Transaction Summary record on the setup page for Job Data fluid component

Figure: Transaction Summary in the View Details page

49 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
In the Approvals component, the data is presented in a table format.

Figure: Transaction Summary in the Approvals page.

If the approver edits the transaction using the Edit Details link in the Approval component, changes made by the approver
are merged with the existing transaction summary.
As shown in the previous example, the position number is changed from 1900003 to 1900005. If the approver modified the
position number to 19000007, he or she will see this change in the Summary step of the activity guide.

Figure: Transaction summary details in the activity guide Summary step after the approver making changes to the requested data

50 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
After the change is committed by clicking on the Submit button, the changes are merged with the existing summary to show
the original value of a field as Current Information when transaction was initiated. The Proposed Information column
displays the latest value for the field.

Figure: Transaction summary details in the Approval page after the approver making changes to the request data.

51 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
MANAGING RELATED INFORMATION IN THE RIGHT PANE
Related content on fluid pages can be based on either an explicit related content service definition as in the case of the
delivered RC tile (Reference Links) or a content reference definition. The related content service should be configured at the
component level to be displayed as related information in the right pane.
1. Create an RC service of type PeopleSoft Tile if service parameters are required. Alternatively, directly use the
content reference definition (of the content to be displayed in the right pane) to be displayed as a tile.
2. Under People Tools > Portal > Related Content Service > Manage Related Content Service, assign the related
content service to Content Reference “Fluid Structure Content > Fluid Pages > Workforce Administrator > Job Data
Fluid” as the Component Level Related Content.

Figure: Configuring related content

3. Map any service parameters if required.

4. Access the Content Reference in step 2 and test it.
PeopleBooks reference: PeopleTools: Products: Development Tools: Portal Technology: Understanding the PeopleSoft
Related Content Framework.

Configuring Additional Links in the Related Information Right Pane

A Reference Links tile is delivered to be used as related content in the Activity Guide component.

Figure: Reference links in related information right pane

The tile is published using tile wizard and is delivered with two clickable links:
1. Maintain Teleworkers: Opens the Maintain Teleworkers component in a new window.
2. View Details: Opens the View Details component in a new window. It is used to view employee job details in a
separate window.

52 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Adding New Links on the Delivered Tile
In the Application Designer, modify the HTML area “HCR_JOB_RI_LINKS” as required to add additional links.

Figure: HTML–HCR_JOB_RI_LINKS.

If binds are used in the HTML code, modify the method setTileHTMLArea in HCR_JOBDATA_UTILITIES:RelatedInfoTile
application class PeopleCode.

Figure: PeopleCode to configure html area.

Method setTileHTMLArea() is used to set the content area of the tile to HTML.

Adding a New Tile with Clickable Links in the Related Content Frame
To configure related content:
1. Create a dummy page and component.
2. Publish it as a tile using ‘Tile Wizard’ setting content type as HTML.
3. In the App class PeopleCode, implement setTileHTMLArea() method to set the content of tile from the HTML area.
4. Assign this tile as related content to the content reference “Job Data Fluid”.
PeopleBooks reference: PeopleTools 8.58: Portal Technology: Using Tile Wizard.

53 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
ATTACHMENTS IN THE JOB DATA MODERNIZATION FEATURE
Fluid Attachments related functionalities can be enabled or disable at the feature level using the Job Data Installation page.
Additionally, use Page and Field Configurator to hide the Attachment step if you do not want to use Attachments feature in
the guided process.
See PeopleBooks for more details. PeopleBooks reference: PeopleSoft HCM 9.2: Workforce Data Management: PeopleSoft
Human Resources Administer Workforce: Using the PeopleSoft Fluid User Interface to Manage Job Data.

Attachments Framework Implementation and Related Setups

To implement the Attachments framework for this process:
1. Create and associate a record, which holds the key values to differentiate each job request row, and
HR_ATT_DD_SBR subrecord definition (e.g.: HR_JOB_ATTCHMNT).
2. Configure framework related setups like Configure Keys, Define Authorization Entries, Define Attachments,
Maintain Definitions, etc. under the navigation Set Up HCM > Common Definitions > Attachments.
3. Insert the subpage (HR_ATTCH_FL_SBF) at level zero on the Attachments transaction pages.
4. Add necessary PeopleCode on the Postbuild or Page Activate event to initiate attachment processing.

Figure: HR_JOBDATA_ATT_FL page activate PeopleCode.

5. Add necessary PeopleCode on the request submit (Submit button field change) to save the attachments.

Figure: Attachments save processing on Submit button.

Note: Correction of an existing row brings in attachments that were added as part of the completed transaction. The store
keys are updated during save to store the attachments related data in this scenario.

Customizing Attachment Types

URL properties for the URL definition ‘HR_ATTACHMENT_FLU’ can be configured for restricting the file types that can be
uploaded to or downloaded by the Fluid Attachment Framework. However, it is important to understand that any restriction
on this URL will be applicable to all the Fluid Attachment transactions within the HCM product. This piece left untouched by
the Application Teams, you may configure this as per the business requirements.
Further details on how to configure file restrictions is available under the “Restricting the File Types That Can Be Uploaded
or Downloaded” section in PeopleBooks in the link below:
https://docs.oracle.com/cd/E55243_01/pt854pbr0/eng/pt/tpcd/task_ApplicationDeploymentandSystemConfigurationCo
nsiderations-8974b5.html#ud075bbd6-997f-457d-a4fd-099a6a031fbf
More technical details are available in
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=361446846664745&id=2382737.1&_afrWindowMod
e=0&_adf.ctrl-state=m9izzti1c_4

Framework Related Setups

54 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Store the record used to launch the Document Definition and store the attachments added by a user to a specific row of job
data (i.e., differentiate the row of job data to which the attachment belongs).

Figure: Attachments framework delivered setup to define the keys, under navigation Set Up HCM > Common Definitions > Attachments > Configure
Keys

Figure: Defining authorizations for Job Data Modernization feature.

The Modern Job Data feature delivered roles are added with proper Authorization IDs. Add any custom role for this feature
here in order to access the View Details, Approval, and Job Data activity guide pages without receiving an error.

55 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Figure: Defining Attachments Configurations for Job Data Modernization feature.

Attachment Type: Select either ‘Attachment’ or ‘URL’ attachment type if you want to define common attachments or URLs,
such as policies, handbooks, FAQs, and so forth. Select the ‘Document Definition’ attachment type if you want to create an
entry to enable users to create their own attachments for a specific row of application data.
When a transaction requires approval, the approver sees a section to view attachments on the approval screen if ‘Enable
Fluid Attachments’ is selected on the Job Data Installation page.

56 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
OTHER FEATURE UPDATES

The Job Data link in Guided Self Service (GSS) and Position Management
The current behavior of the ‘Go To Job’ link is mentioned here:
All GSS transactions for which 'allow DB update' is not selected in the Workflow Configurations page are displayed on the
GSS administrator's page when the status indicator 'Administrator Action Required' is selected.
The administrator selects one of the 3 options, saves and clicks the 'Go To Job' link to go to Classic Job Data for the selected
employee to verify all details. The default option selected is "Select this option to approve the transaction and update the
database”.
When the ‘Fluid Job Data’ check box is selected on the Job Data Installation page, the GSS ‘Go To Job’ link will redirect the
user to the modern Job Data pages in Fluid. The Job Actions Summary page for the concerned employee will open up in a
new tab. User should access the Job Actions Summary page in Correct History mode to view or edit all the job data rows.
The ‘Go To Job’ link is accessible for other status indicators as well, like Approval in process, Denied, and so on. The behavior
remains unchanged, except for the fact that the Fluid Job Actions Summary page will display in a new tab, instead of in the
Classic pages.
UOW# 137361, Bug- 31768782-FLUID JOB DATA : GSS RECORD PEOPLECODE CHANGES should be applied to avail this.
Similarly, Fluid Position Management will take the user to the modern Job Data feature if UOW# 137385, Bug-137385- FLUID
JOB DATA :POSITION FLUID RECORD PEOPLECODE CHANGES is applied.

Note: When the same transaction is added from both GSS and modern Job Data, approvals are enabled, and the fluid job
approval transaction is underway while GSS transaction is completed, the user will need to delete the in-progress row from
Job Action Summary in modern Job Data. This way, only the completed (GSS) row will show.

Customizing the Job Data Link to Point to Modern Job Data From Other Features
Oracle delivered code changes to point to modern Job Data instead of classic when the ‘Go To Job’ or ‘Job Data’ link is
accessed from GSS or Position Management. Except for these two areas, all other features will still point to classic Job Data.
Example: Old Worklist and Email notifications will point to classic Job Data only.
Refer any of the below code lines to customize the ‘Job Data’ link to point to modern Job Data instead of classic Job Data.
• FUNCLIB_WF.TRANSFER_TO_CORE.FieldFormula Record PeopleCode.
• POSITION_DATA_FL.GBL.DERIVED_HR.JOB_DATA FieldChange Panel Group Record Field PeopleCode
• POSITION_DATA_V_FL.GBL.DERIVED_HR.JOB_DATA FieldChange Panel Group Record Field PeopleCode.

Other Process Updates

The Job Data rows that are added by the update processes will be available in the Job Actions Summary for the employee.
As an example:
Mass Update: Navigate to Mass Update under Workforce Administration > Collective Processes, select a mass update
definition, and make change to data in the Mass Update Definition to use a new effective date.
After saving the page, run the Mass Update process, such as a Department Change, to load the changes to the group of
employees associated with the mass update definition.
After the process ends successfully, verify it in the modern Job Data.
A job row with the action ‘Data Change’ with a new effective date will appear employee in modern Job Data for the
concerned.

57 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Figure: Defining Mass Update

Figure: Managing Mass Updates.

58 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates
Figure: Data Change row got added as of December 15, 2020 for K0G014.

Note: Existing Mass Update functionality will not trigger approvals configured on modern Job Data. Custom changes will
need to be done if a Mass Update action update initiated should go through approvals before the Job Data is updated.
Note: As of now, the Review functionality will not trigger if the retro job data row is added or corrected by any other feature
or process. Currently this functionality is supported only when retro rows are added or corrected by modern Job Data
feature.
To trigger review functionality for other process updates, perform additional coding on the Classic Job Data component
SavePostChange PeopleCode. Please refer method ‘SaveReviewData’ used in PeopleCode (CompRecFld) -
JOB_DATA_FL(GBL).HR_JOBFLD_WRK.SUBMIT_PB FieldChange to implement the same.

59 PRODUCT DOCUMENTATION UPDATE

Copyright © 2021, Oracle and/or its affiliates