3033503 - Latest Home Page Custom Card Limitations

Some custom tile configurations which aren’t currently available with the latest home page. If a custom can't be imported due to unsupported configurations you can either remove the unsupported configuration and import them or you can wait and rerun the import later, if support is added. This KBA outlines the unsupported custom tiles. 

SAP SuccessFactors HXM Suite

See list of current limitations for Custom Cards on the Latest Home Page :

• The Raw HTML specified as popover content in a custom card is sanitized before being rendered on the home page. The option to disable,  HTML sanitization that was available in the legacy home page, is currently not supported with the Latest Home page. Custom Tiles which use HTML insecure tags such as <script> and <iframe> tag are considered insecure and will be removed as part of HTML sanitization during the import (without corresponding closing tags) .

To summarize with the Latest Home Page when an HTML tag is invalid (For example, a tag with no equivalent closing tag, like <p> without a matching </p>), it would be removed (by the security library) for security reasons.  In legacy HomePage, if the setting “Sanitize all rich text inputs' was disabled, then invalid HTML content would have still worked while rendering on the home page. What this means if you copy the same invalid HTML content to the latest home page, it would be removed as sanitization of HTML input is happening all the time in latest home page irrespective of this setting.

Note : The import will not be able to proceed if there is no other content in the tile.

The popover content can be updated to use alternative content that don't use insecure tags such as <script> and <iframe> and then imported to The Latest Home Page. See examples of Safe HTML Tags below ( This is not a complete list and SAP does not provide such a list )  :

• • SAFE_HTML_TAGS: "a,img,p,b,u,i,table,tr,th,td,tbody,thead,tfoot,div,span,ul,ol,li,em,strong,font,h1,h2,h3,h4,h5,h6,o:p,br,style,blockquote,map,area,hr"

• • SAFE_HTML_STYLES:"text-align,text-indent,text-justify,color,margin,margin-left,margin-right,margin-top,margin-bottom,line-height,list-style-type,background-color,float,font,font-weight,font-size,font-style,font-family,border,border-right,border-left,border-bottom,border-top,border-width,border-style,padding,padding-right,padding-left,padding-bottom,padding-top,list-style,height,width,display,white-space,word-wrap,vertical-align,border-color,text-decoration"

• • SAFE_HTML_STYLES: "text-align,text-indent,text-justify,color,margin,margin-left,margin-right,margin-top,margin-bottom,line-height,list-style-type,background-color,float,font,font-weight,font-size,font-style,font-family,border,border-right,border-left,border-bottom,border-top,border-width,border-style,padding,padding-right,padding-left,padding-bottom,padding-top,list-style,height,width,display,white-space,word-wrap,vertical-align,border-color,text-decoration"
    
    

Alternative options for managing Third Party content are available on SAP Help Guide Adding or Editing Custom Cards on the Latest Home Page which include the option the below :

• Popover with video file - Use this option to embed a video file stored on a private site, such as your company intranet.
• Popover with inline frame - Use this option to embed content in an inline frame ("iframe"), such as a video on a public video site.
• JavaScript - Use this option to execute instructions in a JavaScript file: When a custom card is loaded on the homepage with a target JavaScript, the JavaScript content is not loaded yet. Once the user clicks the card, it will inject a script tag onto the page with the specified url. At that point the browser will execute the JavaScript file. It needs to be pure JavaScript (no HTML). Any JavaScript link would work here. All they need to do is make sure the JavaScript is served by themselves. . For this sample, they have created a small script here, to demonstrate how to use this custom card target.

• Pop over content cannot be empty for any language that has a title specified
• Assignment based on start date. Custom tiles with visibility that's relative to the employee's start date, such as for onboarding, can't be imported.
• Invalid date ranges. Custom tiles that are configured as visible during a date range but don't have a valid date range defined can't be imported. We added validation to ensure that date ranges are configured correctly.
• Static tiles with icons. "Static" type custom tiles can be converted to custom cards but not longer display an icon. The icon is replaced by a placeholder image. You can update the image after conversion.

Refer to SAP Help Guide for further details on Importing Custom Tiles from the Legacy Home Page

2979181 - Engagement Cards & Quick Actions on The Latest Home Page

3129891 - Unable to change theme for Custom Cards on the Latest Home Page

SAP Help Link for the Latest Home Page Experience for End Users

2979275 - New Experience for the Home Page 

2979675 - The Latest Home Page where to find To-Do's

2988059 - The Latest Home Page Limit to custom cards that can be displayed

3229364 - Is it possible to sync or copy Latest Homepage custom cards from one instance to another?

SAP Help Link Enabling the Sanitization of Rich Text Content

import custom tiles , import , custom cards , the latest home page , custom tiles , HTML , iframe , WEF-13566 , latest home page , home page , KBA , LOD-SF-PLT-LHOM , Latest Home Page , Problem