Job Data Modernization Frequently Asked Questions
Job Data Modernization Frequently Asked Questions
CONTENTS
FEATURE AND DEPLOYMENT RELATED 4
What is Job Data Modernization? 4
Is there a plan to modernize Person Data also? 4
Should I wait and update the Job Data Modernization and Person Modernization features together? 4
How much time do I have to deploy the Job Data Modernization feature? 4
Will the Classic version of Job Data be de-supported? 4
Why is Fluid the chosen interface for Job Data transactions? 4
What is the minimum PeopleTools version that is needed for this feature? 4
Can I use both the Classic version of Job Data as well as the Fluid version of Job Data for maintaining Job Data? 4
Can I be an early adopter of this feature? 5
NAVIGATION RELATED 5
Are there new tiles or homepages delivered with the Job Data Modernization feature? 5
How do I access links to setup and maintain tables? 5
SEARCH RELATED 6
Is the new search page that comes with Job Data Modernization configurable? Can we configure additional Search Criteria and
Search Results fields? 6
Can we configure our own Search Record or Search Definition? 6
How many Recent Searches can we show on the new search page? Is there a limit on how many Recent Searches we can show
on the search page? 6
How many My Saved Searches can users create and maintain? 6
Can we disable showing the photo in the search results? 6
Can we see a preview of the search page based on our configurations before we finalize the search configuration? 6
ATTACHMENTS 7
Can we add attachments to Job Data? 7
How are attachments managed in Job Data Modernization? 7
Is there any limitation on file formats or file types that we can attach? 7
Is there any limitation on the number of attachments that we can add using the Attachments feature? 7
Is there any file size limitation for the attachments? 7
Can we store attachments in our internal system or file server? 7
APPROVALS 7
Can you set up multiple approvals? 7
Do you have to use approvals for updating Job Data? 7
What new approval definitions are being delivered? 8
CONFIGURATIONS 8
Can you share a list of setup steps that are needed to configure the feature? 8
Are there any setups required for any of the new fields added as part of the Job Data Modernization feature? 8
Can you change or hide fields that display when requesting a job change? 8
FUNCTIONALITY IMPACT 9
Will the updates we make through Job Data Modernization also be reflected on the existing Classic Job Data page (and vice
versa)? 9
Will adding effective dated notes to Job Data work the same way? 9
Is there a dependency to use Fluid Position Management with Job Data Modernization or can we continue to use Classic
Position Management? 10
Will the Temporary Assignments functionality work the same way as it does with Classic Job Data? 10
Will Global Assignments and Workforce Contracts continue to update Job Data the same as Classic? 11
Will the “post Job data update events” continue to work on both Classic and Fluid versions? 11
Will email notifications work the same way as Classic Job Data? 11
Will the delivered processes that update Job Data, like Auto Termination of fixed-term jobs or merit increase, continue to work
on Classic and Fluid versions? 11
Is there any potential impact on Smart Templates/Template Based Hires? 11
Any potential impact on PeopleSoft Recruitment/Manage Hires that loads Job Data into Core HR? 11
CHANGE MANAGEMENT 12
What type of training content or feature collateral can I look forward to from Oracle to know more about the feature? 12
SECURITY 13
Are there any changes to security? 13
APPENDIX 14
Table A - Security Details – Roles and permission lists to grant access to the Fluid version of Job Data: 14
Permission Lists 15
Should I wait and update the Job Data Modernization and Person Modernization
features together?
You should not wait until Person Data modernization is available before deploying Job Data
modernization. The hire process does not use the Job Data component but uses separate
components for adding Organization Relationships for a person.
How much time do I have to deploy the Job Data Modernization feature?
You can implement it right away! Oracle support for the Classic/Classic Plus version of Job
Data pages will end on December 31, 2022.
What is the minimum PeopleTools version that is needed for this feature?
At a minimum, you should be using PeopleTools version 8.57.11 or higher for Job Data Modernization.
The recommendation is to use People Tools 8.58.
Can I use both the Classic version of Job Data as well as the Fluid version of Job
Data for maintaining Job Data?
Yes, but once you have decided to use the Fluid version of Job Data, it should be the only
method for data entry to update Job Data. However, this does not mean you cannot access
NAVIGATION RELATED
Are there new tiles or homepages delivered with the Job Data Modernization
feature?
Yes, there are several new tiles and new dashboard delivered with the Job Data Modernization feature.
The Manage Human Resources dashboard provides HR administrators a brand new dashboard that
functionally groups Job Data-related fluid tiles under a single page. There are three tiles pre-delivered
on this dashboard that include two new fluid tiles (the Manage Job tile and the Manage Configurations
tile) along with the existing HR Administration navigation collection tile.
View this blog post to see the new tiles and learn how you can use them.
SEARCH RELATED
Is the new search page that comes with Job Data Modernization configurable?
Can we configure additional Search Criteria and Search Results fields?
Yes, Job Data Modernization provides a powerful search configuration that delivers the following search
configuration capabilities:
• Switch between using a Basic or Advanced Search
• Configurable keyword search
• One-click search using the criteria from previous or frequent searches
• Save your search criteria and easily reuse a saved search
• Search using additional criteria such as HR Status, Department, Jobcode, Manager Name, and so
forth
• Configure the Search Criteria and Search Results fields that should appear on the page
How many Recent Searches can we show on the new search page? Is there a limit
on how many Recent Searches we can show on the search page?
You can show up-to 999 recent searches on the new Fluid search page. However, while configuring the
search, carefully consider the HR administrator’s user experience when determining the number of
recent searches you should feasibly display. We recommend showing 10 Recent Searches to the user for
an optimal user experience.
Can we see a preview of the search page based on our configurations before we
finalize the search configuration?
Yes, the new Manage Search Configuration enables you to save the configuration changes and then see
a preview of the search page.
ATTACHMENTS
Is there any limitation on file formats or file types that we can attach?
The PeopleSoft HCM application supports all common file formats and file types. There is no restriction
on any file formats and file types that you can attach. However, if you want to restrict any file type while
attaching a document, there are certain steps that you can follow to achieve this. You can find
information about Attachments Framework capabilities here: Configuring Attachments in Fluid
Framework.
Is there any limitation on the number of attachments that we can add using the
Attachments feature?
There is no limitation in PeopleSoft on the number of attachments that you can add using the
Attachments feature.
APPROVALS
want to use approvals for Job Data updates. Refer to PeopleBooks to know how to enable or disable
approvals functionality in the Job Data Modernization functionality.
CONFIGURATIONS
Can you share a list of setup steps that are needed to configure the feature?
To follow is a list of new configurations you can use to configure Job Data Modernization as per your
organization’s business process and requirements:
1) Job Data Installation: Enable Job Data Modernization by selecting Fluid Job Data, enable
attachments, enable approvals, associate approval definitions and enable the review process.
2) Manage Search Configuration: Configure Search Criteria and Search Results fields and more.
3) Activity Guide Composer: Assign a Label for the Drop Zone pages.
4) Enable or Hide the Drop Zone pages using Page and Field Configurator to isolate page
customizations.
5) Page and Field Configurator: Hide or unhide steps in the guided process and hide or unhide page
fields based on action, reason, and role.
6) Fluid Attachments Framework: Define attachment types and authorization configuration.
7) Approvals: Clone delivered approval definitions, edit delivered approval definitions, or create your
approval definitions.
8) Configure Transaction Summary: Configure fields you want administrators to review before
submitting action in the new Summary step provided with the guided process.
Are there any setups required for any of the new fields added as part of the Job
Data Modernization feature?
‘Approval Status’ is the only new field added in Job Data Modernization to support approvals. This
‘Status’ field is part of the staging table created to support approvals functionality in Job Data and not in
the core Job record. Status values are based on the approval flow.
Can you change or hide fields that display when requesting a job change?
Yes, you can use Page and Field Configurator to hide or unhide fields, hide or unhide pages, make fields
display only, mask fields, or change the label of a field in Job Data Modernization.
How many Drop Zones will be in Job Data and where are they located? Are there
limits to fields you can add to Drop Zones?
PeopleSoft will deliver Drop Zones at the top and bottom of each delivered Job Data Fluid page/step.
Additionally, the activity guide delivers four Drop Zone pages/steps to allow you to maintain your
custom page functionality currently in Classic Job Data.
It is important to note that Drop Zones will allow you to isolate customizations so future
uptakes of features delivered by PeopleSoft does not override your customizations. See
PeopleBooks documentation for Drop Zones.
How will my custom fields, records, and pages from the current Classic Job Data
component be retrofitted into the new Job Data Modernization component?
Refer to this Red Paper to learn how you can retrofit your existing customizations into the new Fluid
version of Job Data.
FUNCTIONALITY IMPACT
Will the updates we make through Job Data Modernization also be reflected on
the existing Classic Job Data page (and vice versa)?
Yes, but once you start using Job Data Modernization, we recommend that your HR administrators use
the Fluid pages only for updating Job Data because it has features like attachments, validation of data,
and a summary of changes that are not available in Classic Job Data. Updating data in Classic may result
in re-updating data to add an attachment or review the summary of changes in Fluid.
Only in rare and unavoidable scenarios, you may need to correct data in Classic Job Data. For such
scenarios, you can authorize selected administrators to be able to do corrections in Classic Job Data.
As mentioned earlier in this document, if your organization has decided to do a partial rollout
of Job Data Modernization, then data can be entered using the Classic version of Job Data for
the remaining set of employees. Even if you have opted to use the Job Data Modernization
feature, the Classic version of Job Data will still be available to help review core Job Data in
case of exceptions or errors caused due to any system updates or integrations. However, we
recommend that this type of access be limited.
Will adding effective dated notes to Job Data work the same way?
Currently in Classic Job Data you can add notes at the employee level. This will continue to work the
same way with the Job Data Modernization feature as well.
However, in case you wanted to add notes based on Effective Date in Job Data Modernization, you
could use the HR Notepad framework capabilities to define Effective Date as a key field for Job Data
configuration and add effective dated notes in Job Data. Use this PeopleBooks link to learn about HR
Notepad configurations: Configuring and Working with the HR Notepad.
How will Job Data changes affect the Manager Self Service or Guided Self
Service functionality?
When you enable Job Data Modernization on the Job Data Installation configuration page, the Job
Data-related links on the Position Management and Guided Self Service review pages will direct the user
to Job Data Modernization page instead of to the Classic pages of Job Data. For example, when a user
clicks the “Go To Job” link on the Manager Self Service administrator review page, the system will direct
the user to the Job Actions Summary page for the employee, which is the Fluid version of Job Data. See
screenshot of the Manager Self Service administrator review page with “Go To Job” link below:
Will the Temporary Assignments functionality work the same way as it does with
Classic Job Data?
The temporary assignment process will continue to work the way it works today. In case approvals are
used, the additional Job record to Hold Substantive Job is created upon final approval.
Will Global Assignments and Workforce Contracts continue to update Job Data
the same as Classic?
Yes, it will work the same way. Once you choose to use Job Data Modernization, if you create a Host
assignment record for an employee using the Global Assignments module, you can review and update
the Host Job Data record using Job Data Modernization. The Global Assignment transactions like
Home/Host Data and Add Host Assignment are not available in Fluid; these transactions continue to be
available in Classic.
Will the “post Job data update events” continue to work on both Classic and Fluid
versions?
The existing post Job Data update events will continue to work the same way as it does on both the
Classic and Fluid version of Job Data.
Will email notifications work the same way as Classic Job Data?
The delivered Email and Worklist notifications will continue to trigger from Classic Job Data as they do
today. The ‘Go to Job’ link in email and worklist notifications that trigger from Job Data will continue to
take users to the Classic version of Job Data instead of the Fluid version of Job Data.
Will the delivered processes that update Job Data, like Auto Termination of
fixed-term jobs or merit increase, continue to work on Classic and Fluid
versions?
Yes, these processes will work the same way as they do on both Classic and Fluid versions of Job Data. If
you want to use approvals with Job Data Modernization and expect that these processes should trigger
the approvals implemented in Job Data Modernization, then you will have to make changes to these
processes yourself to trigger approvals based on your organization's business process requirements.
Are there any new fields or tables added in the Job Data Modernization feature?
Will it affect my existing reports, Component Interfaces, or integrations if I
deploy this feature?
Existing integrations and reports should not be impacted as no new records/fields are being included in
core Job Data through the Job Data Modernization enhancements. However, to support Attachments,
Approvals and Summary page functionality, new records and new fields have been added in Fluid
version of Job Data. Refer to the bug numbers below to find details:
• New Records: Bug#31768252
• New Fields: Bug#31767133
• New Record-Derived Job Data: Bug#31767914
• New Record for Drop Zones: Bug#31767292
• New Search Record with Related Language Table: Bug#31796744
CHANGE MANAGEMENT
What type of training content or feature collateral can I look forward to from
Oracle to know more about the feature?
To start the process and help you plan early, we have published a feature readiness blog post on
blogs.oracle.com/PeopleSoft and this FAQ. Other collateral planned for the feature include:
• PeopleSoft HCM Update Image#36 Highlights Video
• Red paper has been delivered which provides implementation guidance to help implement the
feature.
• Detailed PeopleSoft Online Help (PeopleBooks) will provide feature documentation.
SECURITY
Table A - Security Details – Roles and permission lists to grant access to the Fluid
version of Job Data:
S. No: Role Description Detail Associated Permission
1 HR Admin Approver HR Admin Approver This is for Job Data HCCPCF1000- Chart Fields fluid
Fluid Fluid Modernization approver
HCCPHR3310 – Job Data
access.
HCCPHR3314- Edit Fluid Job
Data
This role is required to HCCPHR9005- Row security
carry out the final Administrator
approval role for HR
administrator
transaction approvals.
2 HR Administrator This role is responsible • Users having this role HCCPCF1000- Chart Fields fluid
Fluid for administering the will be able to access
HCCPHR3310- Job data
job action transactions the ‘Manage Job’,
of Fluid Job Data. ‘Manage HR’, and HCCPHR3314- Edit Fluid Job
‘Manage data
Configurations (Job
data Installation) tiles.
3 HR Admin Correction This role is responsible This role is required to HCCPCF1000- Chart Fields fluid
Apvr Fluid for administering the carry out the final
HCCPHR3310- Job Data
approval transactions approval role for HR
of correct/edit the Administrator Correction HCCPHR3314- Edit Fluid Job
existing fluid job data transaction approvals. Data
request
HCCPHR9005- Row security
administrator
4 HR Review Users having this role will Dummy role. No PLs
Administrator be able to delete job rows. associated.
7 Configurable Search Configurable Search Users having this role will EOCSF1000 Configurable
Admin Admin be able to define setups Search Setup
related configurable to
EOCSF2000 Configurable
set up.
Search Page
8 Configurable Search Configurable Search User having this role will EOCSF2000 Configurable
User User be able to access the Search Page
search UI.
9 Transaction Summary Transaction Summary This role provides access HCCPTS1000 -Transaction
Admin Admin to the setup pages to Summary Admin
define transaction
summary configurations.
Permission Lists
PERMISSION LIST DESCRIPTION OBJECTS/PAGELETS ASSIGNED ROLES
Copyright © 2020, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without
notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties
and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed
either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without
our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon 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, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group. 0120
Disclaimer: This document is for informational purposes. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing
decisions. The development, release, timing, and pricing of any features or functionality described in this document may change and remains at the sole discretion of
Oracle Corporation.