What is a Custom Component?

A custom component is a modified standard or self-designed UI element that may deviate from the standard behavior.

A custom UI element is used to cover specific use cases and requirements in SuccessFactors that were not previously covered by the Fiori Design Guideline. The Custom Component can be modified from pure styling to complex changes in structure and behavior. It can also be a combination of existing functions as a modification or extention of a standard UI element.

When to use a Custom Component?

For the use of a Customer Component, there must be a valid reason. The development must be approved by PM, Eng and the DSM Lead. There is approval process that is described below in this chapter. A custom component should not be developed for a single use case. The development of a custom component should always be valide for a number of use case.

Using a custom component is more complex as a standard UI element in the development. The specification for non standard component is extensive. The behavior that deviates from the standard must be explained in detail. The effort for the implementation and testing is approximatly 10 times higher for a custom component. For these reasons, the designer should first try to cover the use case with a standard UI.

How to request a Custom Component:

• Before developing a custom component, check existing component libraries for possibilities.
• Read the SFUX guideline first: List of existing custom components must be checked before customizing.
• The custom component must be reviewed with the Local DSM and approved by the global DSM Lead.
• The designer or PM will create a Jira to track and document the request.
• The custom component will be reviewed in a feasibility check together with PM and ENG lead.
• PM, ENG and DSM Lead need to give an approval. One NO is a rejection and can lead to a complete stop of the request.
• Details how to open the Jira ticket: Process

Process to request a Custom Component

How to request a Custom Component: create a Jira ticket.

Advantages of using Jira for the request:

• Jira will capture conversations between PM, Engineering, and Design, thus reducing number of follow-ups
• Help manage changing requirements
• Consistent reporting across all projects
• Provides transparency to entire organization and makes design work visible for all.
• Quickly identify any blockers or potential blockers
• Build a single source of truth for all the work that needs to be completed

Prerequisites for the process to request a Custom Component:

• In order to apply for a custom component, the component must be described in a design document.
• The design document should follow a consistent format:

Recommended template for describing a custom component within the Figma design document:

Design documents for custom component request should contain the following sections:

• Intro to the project - Introduction to the project, with main focus
• Custom component description:
  - Description of the requested custom functionality, with the comparison to the usage of standard controls.
  - List of uese cases of reusing the custom component in other SF modules
  - Review with DSM leads, approval by global DSM lead and further check points
• Change Log - List of changes with reviewer names and timestampe of the alternation