SAP Knowledge Base Article - Public

2855985 - Q4 1911 - Platform Release Information FAQ

Symptom

This Knowledge Base Article is to document all major enhancements to be aware of in our Q4 1911 release. Also provides one stop shop for all out Platform Foundation documentation.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

Environment

SAP SuccessFactors HXM Suite

Reproducing the Issue

The documentation can also be found on the SAP Help Portal under SAP SuccessFactors Release Information, quick links under "What's New" section will provide the detailed release summary across application.

For extensive documentation on SAP SuccessFactors Platform including Admin Guide, Release Information and Implementation Guides see SAP Help Guide SAP SuccessFactors HXM Suite.

Direct Links to our Q4 1911 documentation:

Release summary Information:

Configuration Guides:

Integration Documents:

Administration Documents:

Implementation Guides:

End-User Information & References:

NOTE: You may check the bottom section of this KBA for list of KNOWN ISSUES identified post 1911 release.

Resolution

 **** Platform Module Specific Enhancements & Features 1911:

Universal Enhancements to Note:

1. Universal Person Auto-Complete Search Upgrade Within Q4 2019 Release (STE-8968)
- To enable a consistent search experience across the SAP SuccessFactors suite, companies utilizing the legacy person search functionality will be universally upgraded to Universal Person Auto-Complete Search. Universal Person Auto-Complete Search is available today in a few access points and modules, such as Employee Central, Org Chart and GDPR. More details can be found in this blog post.

2. Enhance Employee Import and Export Date Format (PLA-10657)
Previously, we only supported the date formats of "Month/Day/Year" (for example, 11/23/2018) and "Day-Month-Year" (for example, 23-NOV-2018) in the Hire Date and Exit Date fields for Employee Import, Basic User Import, and Employee Export. Now multiple date formats are supported according to the locales enabled for the customer's instance.

3. Enablement of the Refresh Framework for all customers (PLC-10582) 
- The Refresh Framework improves the stability of group refresh and the performance in some heavy workload scenarios, by automatically switching between the buffer mode and the on-demand (real-time) mode based on the detected refresh workload. [KBA 2766870 - RBP Refresh Framework FAQ]

4. We have made a number of accessibility improvements (UI-20144) that go into effect with the Q4 2019 release. For greater accessibility, we have increased the contrast of the Login button, and have made the Color Vision Adjustments options readable by screen readers. Make sure the login screen theme is now adopted to SAP Belize theme instead of SAP Bluecrystal. This was implemented to resolve a contrast ratio issue. See KBA 2860962 - Q4 Preview Release : SF BizX Login Default Theme Background Colour has changed to a lighter blue

 

Home Page

Component ID Feature Description Before & After Additional Information
LOD-SF-PLT-HOM UI-21372 Consistent Header Experience As part of the new shell bar the header of BizX pages will have width, height, padding, margin and font-size changes.

Alert icons of Notifications and To-do button part of the header will require to have to one constant foreground and background colors.

Action search field will now adhere to header area theme to be consistent with rest of header elements.

The label "Options" under the utility user menu has been renamed to "Settings" to make it consistent across the SAP applications.
Before: Feature Improvement 


After: All pages will have consistent Header Experience 
KBA 2859791 - Q4 1911 - User Experience Look & Feel - Enhancement of page header so it is now consistent with Fiori Design
LOD-SF-PLT-TDO UI-21117 Assign Supplemental To-Do items to Dynamic Groups As an administrator, you can now assign supplemental to-do items to dynamic groups. Previously, all supplemental to-do items were assigned to all users. Now you can target them to a particular audience.

Before: All supplemental to-do items were assigned to all users.

After: Administrators can now assign supplemental to-do items to dynamic groups.

KBA 2858209 - Q4 1911 - Assigning supplemental to-do items to specific permission roles or groups
LOD-SF-PLT-TDO UI-20428 Hide Overdue To-Do Items in Manage Home Page

As an administrator, you can now hide overdue to-do items in Manage Home Page to help users keep better track of their tasks. Previously, long overdue to-do items caused the to-do section to expand over time on the Home Page.

Before: Overdue request will be still displayed in to do tiles as they are not finished

After: Administrators can now hide overdue to-do items in Manage Home Page

KBA 2858280 - Q4 1911 - Hide overdue to-do items

Data Retention Management

Component ID Feature Description Before & After Additional Information
LOD-SF-PLT-DRM UI-20461 Purge completed To-Do items  You can now use Data Retention Management to purge completed to-do items from the database to improve the performance of the home page. Even though they aren't visible in the user interface, completed to-do items are still stored in the background for record-keeping. For organizations with a very large number of completed to-do items, this can affect page performance. Use the legacy purge type Purge Completed To-Do Items to purge completed to-do items that are more than a year old. Before: Purging of completed to-do items is dependent on the General Settings > Number of Days set in Manage Homepage.

After: Administrators can now purge completed to-do items. 
KBA 2859470 - Q4 1911 - Data Retention Management to purge completed to-do items ( Legacy Purge )

LOD-SF-PLT-DRM STE-9144 SupportAssignmentID inDRM/DRTM In Data Retention Management, you can now upload a list users to include in a purge request based on either User ID or Assignment ID.

Before: Administrators cannot use AssignmentID for selecting users to purge via DRM and DRTM.


After:
AssignmentID is now supported in DRM and DRTM.

KBA 2859532 - Q4 1911 -Purge by UserID or AssignmentID
LOD-SF-PLT-DRM PLS-7876

Notification History Purge

Notifications on the global header bar are only kept for 30 days.

Notifications older than 30 days are automatically purged. Extend the time period it possible based on request.

 

Before: Feature Improvement


After:
Notifications older than 30 days are automatically purged. Extend the time period it possible based on request.

KBA 2859054 - Notification retention and purge 


Search

Component ID Feature Description Before & After Additional Information
LOD-SF-PLT-SRH STE-13850 Hide Job title and Location fields in the search result for users without permission to view these fields. We’ll hide the job title and location fields in the search result when you have no permission to view these fields or when no data was maintained for them. Before, “No Data” was displayed in such situations.

Before: Before Q4  No Data displayed if no permission or no data for the job title or location field.

After: Administrators can now purge completed to-do items.

KBA 2859427 - Q4 1911 - Hide Job title and Location fields in the search result for users without permission to view these fields

LOD-SF-PLT-SRH STE-13594 Admins can control searching Inactive Employees in Auto-complete search results via RBP. As an administrator, you can now use Role-Based Permissions to control who can see inactive employees in the auto-complete search results. If you don't have permission to see inactive employees, they are excluded from your search results.

Before: Before Q4  Inactive users are showing up in the search results for auto-complete search functionality.

After: After Q4 , Inactive users will only show up for auto-complete search results if the user has RBP permission to see these inactive users.

KBA 2858918 - RBP to Control Inactive user search results in Module Pages People Search
LOD-SF-PLT-SRH STE-13357 Admins can control visibility of Photos in auto-complete search result via RBP. As an administrator, you can now use Role-Based Permission to control who can see the photos in the auto-complete search result. If you don't have permission to see the photo, the search result shows a default image.

Before: Before Q4  photos are visible in auto-complete search results.

After: After Q4, default image will be displayed in the auto-complete search results if the user has  no RBP permission to view.

KBA 2859065 - RBP to Control Photos in Module Pages People Search 


Picklists

Component ID Feature Description Before & After Additional Information
LOD-SF-PLT-PCK STE-15036 Picklist Center will always be available for Legacy and MDF picklists Previously, Picklist Center will only be enabled after migration. Now after 1911 Picklist Center will always be available. But different messages will appear on the top of the page indicating migration status. If the instance is not migrated, user will see “Legacy picklists haven’t been migrated yet. To manage them, go to Picklist Management”. Within a week after migration, user will see “Congratulations, you can now manage all your picklists in Picklist Center.”

Before: Before Q4  Picklist Center will only be available for instances which are migrated to MDF Picklist.

After: After Q4, Picklist center will always be available regardless if the customer is already migrated or not. If the customer is still in legacy picklists, they will see a link to access Picklist Management page if they want to manage their legacy picklists.

KBA 2858991 - Picklist Center showing available for non-migrated Legacy Picklist

User Management

Component ID Feature Description Before & After Additional Information
LOD-SF-PLT-USR PLA-8665 Manage Login Account tool to enable Account Decoupling as Universal We've decoupled accounts from users universally, meaning that a person can have multiple users but only one login account. The login account is active as long as the person has at least one active user.  The "Manage Login Accounts" admin tool allows you to view users' login account information, including login name and login method, and change the login account if necessary. You can access the system using login name or username. When you log into an Employee Central-enabled instance, the system automatically selects the user of the home employment, primary employment, or earliest active employment as the main user in the cases of global assignments, concurrent employment, or contingent workers, respectively. 

Before: Before Q4, there is no admin page to manage decoupled accounts for Global Assignment and Concurrent Employment cases on EC enabled instances.

After: After Q4, "Manage Login Accounts" tool will be available for admins to use for them to view users' login account information, including login name and login method, and change the login account if necessary.

KBA 2859043 - Q4 1911 - Manage Login Accounts tool
LOD-SF-PLT-UIM PLA-8760 Support RBP permission control on Basic User Import for Employee Central-enabled instances You can now use Role-Based Permissions to manage access to Basic User Import in Employee Central-enabled instances. A new option " Enable Control on Basic User Import in Role-Based Permissions” is available in "Manage Employee Central Settings". When you enable this option, only users who are granted with the Basic User Import permission can perform basic import.  


Before
: Before Q4, There is no separate permission to grant Basic User Import for EC enabled instances.

After: After Q4, when you enable this option, only users who are granted with the Basic User Import permission can perform basic user import.

KBA - 2859213 - Support RBP permission control on Basic User Import for Employee Central-enabled instances
LOD-SF-PLT-UIM PLA-9547 Super Admin user created from Provisioning can login via password in Partial SSO enabled instance In an instance that has enabled Partial SSO, you can choose PWD (username and password) as the login method for super admins when you create a super admin user in Provisioning.  

Before: Before Q4 , you cannot specify the login method during Super Admin Account creation in provisioning > Company Settings page.

After: After Q4, there is an option to select PWD login method while creating the super admin account in provisioning > company settings page.

KBA - 2859110 - Super Admin user created from Provisioning can login via password in Partial SSO enabled instance
LOD-SF-PLT-UIM PLA-7218 Show Picklist Label instead of Option-ID in subject report The Data Subject Information Report of User Management now shows the labels of picklist options. Before, picklist option IDs instead of labels were displayed in the report.

 

Before: Before Q4 , you cannot specify the login method during Super Admin Account creation in provisioning > Company Settings page.

After: After Q4, there is an option to select PWD login method while creating the super admin account in provisioning > company settings page.

KBA 2858701 - Q4 1911 - Data Subject Information Report shows picklist labels

Provisioning

Component ID Feature Description Before & After Additional Information
LOD-SF-PLT-PRV PLA-8665 Support Succession Data Model Version Control in Provisioning system You can now back up multiple versions of the Succession Data Model in Provisioning and restore a version for your instance. This feature helps protect your data and track the data model changes.

Before: Before Q4  there is no option in provisioning to retain and monitor Succession Data Model versions in the instance.

After: After Q4, users have an option to download older versions of the succession data model in Provisioning. This allows users with provisioning access to protect key data and better track Succession Data Model changes done in the instance.

KBA - 2859111 - Support Succession Data Model Version Control in Provisioning system

Instance Synchronization Tool

Component ID Feature Description Before & After Additional Information
LOD-SF-PLT-IST TLS-12602  Segregation of configuration and data for Instance Synchronization tool Customers had the option to select both data and configurations in one synchronization request. This functionality let’s customers to select synchronization type as Configurations or Data in the wizard. This is only supported for instances which has "DATA" artifact enabled in their instance.

Before: Before Q4 only availble artifacts are allowed to be selected by administrators when submitting sync. There is no option to only sync Configuration or Data from Source to Target.

After: After Q4, users have an option to sync either Configuration or Data from SOURCE to TARGET.

KBA 2860162 - Is it possible to copy only configuration or data during an Instance Sync?
LOD-SF-PLT-IST TLS-12437 Enter Valid User Name instead of User ID during sync While kicking off sync process from Instance Sync Monitor Tool, admin is supposed to enter valid “User Name” instead of “User ID”. User Name is also displayed in the Instance Sync Report.

Before: Before Q4 system will not ask you to enter target instance admin username when re-triggering a submitted sync from instance sync tool.

After: After Q4, the system will ask the admin user to enter target instance admin username when re-triggering a submitted sunc from instance sync tool.

KBA 2859605 - Rerunning a Sync

Instance Refresh Tool

Component ID Feature Description Before & After Additional Information
LOD-SF-SER-REF TLS-12589 Data Anonymization When instances are refreshed from production live as source then PII and sensitive data is also copied to the target instance. Data anonymization provides an ability to obfuscate such information in the target instance. This is a beta feature and would need explicit ask by the customer and the feature will be enabled within instance refresh tool. Sensitive fields for Employee Central, User Management & Recruiting are being targeted in this release in beta phase.

Before: Before Q4 only Recruiting fields are supported for Data Anonymization.

After: After Q4, data anonymization for IRT is now supported in sensitive fields in EC, User management and Recruting module.

KBA 2827300 - [BETA FEATURE] Data Anonymization for Recruiting Management - Instance Refresh Tool
LOD-SF-SER-REF TLS-12593 Learning Application supportability in IRT Instance Refresh can also be requested for Learning application that is integrated with HXM suite using this Instance Refresh Automated Tool. This is a beta feature and would need explicit ask by the customer and the feature will be enabled within Instance Refresh Tool. This will take care of restoring integration settings between BizX and Learning in the target instance.

Before: Before Q4 LMS refresh is not automated.

After: After Q4, LMS is now supported for IRT.

KBA 2835061 - Learning Management System Automated Refresh Process

Document Management

Component ID Feature Description Before & After Additional Information
LOD-SF-PLT-DOC PLT-73029 New Permissions To Manage Documents Based on Document Categories You can now assign document management permissions to document administrators based on document categories. 

 

Before: Previously, the Manage Document admin tool was enabled using a single permission called Manage Documents, allowing users to access all categories of documents.

After: Now, you can use the Manage Document Categories permissionto choosewhichcategory ofdocuments that a document administrator can access and restrict access according to an employee's role. The existing ADMIN users having Manage Documents permission will get the “All” categories permission.

 

KBA 2518360 - Manage Documents Feature


Job Scheduler

Component ID Feature Description Before & After Additional Information
LOD-SF-PLT-JOB PLS-6769 Job Scheduler: Processing Data Purge Historical job processing data in Job Scheduler will be purged periodically once it reaches the defined retention period. Job processing data includes job request details, job execution details, and job responses. The retention period is defined by each job type with a default of 6 months.

 

Before: Job processing data was not purged.

After: Job Scheduler will be purged periodically once it reaches the defined retention period. Retention period by default is 6 months.

KBA 2858263 - Job Scheduler: Processing Data Purge
LOD-SF-PLT-JOB PLS-2951 Job Scheduler: Audit Report You can now use the new Job Scheduler Requests report to create audit reports for all changes made to scheduled job requests created in Job Scheduler. The Job Schedule. Requests report is available in the Admin Center under Change Audit Reports>CreateConfigurationDataReport. You can see who hascreated, modified, or deleted a job request andwhen

Before: There is no audit report on job scheduler changes.

After: You can now use the new Job Scheduler Requests report to create audit reports for all changes made to scheduled job requests created in Job Scheduler.

KBA 2858462 - Change Audit report for Job Scheduler

Application Security

Component ID Feature Description Before & After Additional Information
LOD-SF-PLT-SEC SPF-610 Content Security Policy You can protect your system from attacks including Cross Site Scripting and data injection by enabling the Content Security Policy in Provisioning. To avoid any unintended blocking of resources in case of Content Security Policy violations, you can add the pages that contain such resources to the whitelist.

 

Before: No opt-in feature available for Content Security Policy.

After: New opt-in feature available for customers.

KBA 2863021 - Configuring Referrer Header and Content Security Header policies for a SuccessFactors instance
LOD-SF-PLT-SEC SPF-533 Referrer Policy You can protect your confidential information being disclosed through the referrer header when you are directed to an external website by enabling the Referrer Policy in Provisioning. You can also add trusted exceptions to the whitelist.

Before: No opt-in feature available for Referrer Policy.

After: New opt-in feature available for customers.

KBA 2863021 - Configuring Referrer Header and Content Security Header policies for a SuccessFactors instance

                                                                          ********************KNOWN ISSUES**********************

Component

JIRA ID

Description

Additional Information

LOD-SF-PLT-LGO           UI-21761                 

Theme Manager ->Login Logo -> Upload logo not dispalying post release & Upload company logo not displaying

KBA 2860392 - Post Q4 Preview Release Issue : Company logo not displaying
LOD-SF-PLT-THM UI-21769

Q4 Release - Text on login Page changed to Black text

KBA 2860388 - Q4 Preview Release Issue : SF BizX Logon Page Font & Logon Tab colour has changed
LOD-SF-PLT-PRX PLC-23079 After 1911 release issue when trying to proxy KBA 2861742 - After 1911 release issue when trying to proxy
LOD-SF-PLT-UIM ECT-127467 Status is not getting changed with basic user import (EC Enabled) KBA 2862041 - Post Q4 Preview Release Issue: Basic User Import is not working on EC enabled instances
LOD-SF-PLT-PCK PLA-11364 Unable to export legacy picklists from Picklist Management KBA 2866798 - Post Q4 Preview Release: Unable to export picklists from Picklist Management
LOD-SF-PLT-SRH PLS-9512 Intermittent Search Issues within the instance Resolved in December 1, 2019 [PTCH-31515] / For ALL Data Centers

Keywords

Release , 1911 , SAP Help , release , feature , Platform Release Information FAQ , Q4 , Admin Guide, Q4 Release , Foundation FAQ, Platform Release, 1911 Release , KBA , LOD-SF-PLT , Platform Foundational Capabilities , How To

Product

SAP SuccessFactors HXM Suite 1911