{"id":33715,"date":"2026-04-22T12:03:16","date_gmt":"2026-04-22T12:03:16","guid":{"rendered":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/?p=33715"},"modified":"2026-04-30T12:05:53","modified_gmt":"2026-04-30T12:05:53","slug":"control-dff-visibility-vbcs-oracle-fusion-hcm","status":"publish","type":"post","link":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/blog\/control-dff-visibility-vbcs-oracle-fusion-hcm\/","title":{"rendered":"How to Control DFF Visibility Using Visual Builder Studio in Oracle Fusion HCM"},"content":{"rendered":"\n

Introduction:<\/strong><\/h2>\n\n\n\n

Conditional Display of DFF Fields Using VBS in Oracle Fusion HCM During Multi-Project Data Migration<\/h2>\n\n\n\n

When organizations migrate HR systems to Oracle Fusion HCM, managing configuration differences across multiple business units and legal entities becomes critical. In large transformation programs\u2014especially those involving parallel projects\u2014ensuring that users see only relevant fields during transactions such as hiring employees can significantly improve data accuracy and user experience.<\/p>\n\n\n\n

In this blog, we explore how Visual Builder Studio (VBS) can be used to conditionally display Descriptive Flexfields (DFFs) on the Assignment page based on Business Unit, using a real-world migration scenario.<\/p>\n\n\n\n

Project Background<\/h2>\n\n\n\n

During a recent HR system migration project, employee data was being moved from HR.net<\/strong> to Oracle Fusion HCM<\/strong>. The organization was running two parallel implementations within the same Fusion environment:<\/p>\n\n\n\n

    \n
  • Hartree Project<\/strong> \u2013 Already live in Oracle Fusion<\/li>\n\n\n\n
  • EDFM Project<\/strong> \u2013 Newly being onboarded into the same environment<\/li>\n<\/ul>\n\n\n\n

    The EDFM setup was significantly larger and more complex, consisting of:<\/p>\n\n\n\n

      \n
    • 100+ Legal Entities<\/strong><\/li>\n\n\n\n
    • 12+ Business Units<\/strong><\/li>\n<\/ul>\n\n\n\n

      To support EDFM-specific data capture requirements, 10+ Descriptive Flexfields (DFFs)<\/strong> were created on the Assignment page<\/strong>.<\/p>\n\n\n\n

      However, these fields were only relevant for EDFM business units<\/strong>, not for Hartree.<\/p>\n\n\n\n

      The Business Requirement<\/h2>\n\n\n\n

      When a user performs a Hire an Employee transaction:<\/p>\n\n\n\n

        \n
      • If the Business Unit belongs to EDFM, the system should display the EDFM-related DFF fields.<\/li>\n\n\n\n
      • If the Business Unit belongs to Hartree, those DFF fields should remain hidden.<\/li>\n<\/ul>\n\n\n\n

        Solution Approach Using Visual Builder Studio (VBS)<\/h2>\n\n\n\n

        To meet this requirement, Visual Builder Studio (VBS) was used to customize the Assignment page UI.<\/p>\n\n\n\n

        VBS allows developers to add conditional logic that controls the visibility, behavior, and interaction of fields in Oracle Fusion Redwood pages.<\/p>\n\n\n\n

        Key Implementation Steps<\/strong><\/h3>\n\n\n\n
          \n
        1. Configure Descriptive Flexfields (DFFs)<\/strong><\/li>\n<\/ol>\n\n\n\n

          First, the required EDFM-specific fields were created as DFF segments<\/strong> on the Assignment entity\/Page<\/strong>.<\/p>\n\n\n\n

          Examples of fields might include:<\/p>\n\n\n\n

            \n
          • EDFM Cost Code.<\/li>\n\n\n\n
          • EDFM Contractual Hour Band.<\/li>\n\n\n\n
          • EDFM Job Category Coffee Only.<\/li>\n\n\n\n
          • EDFM Vacancy Reference Number ETC\u2026.<\/strong><\/li>\n<\/ul>\n\n\n\n

            These fields were deployed and made available on the Assignment page.<\/p>\n\n\n\n

              \n
            1. Identify Business Units<\/li>\n<\/ol>\n\n\n\n

              The organization categorized business units based on project ownership.<\/p>\n\n\n\n

              Example:<\/p>\n\n\n\n

              Business Units<\/strong><\/td> <\/td><\/tr><\/thead>
              EDFM DV20 Coffee<\/td> EDFM<\/td><\/tr>
              Back Office<\/td>Hartree<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

              Only the EDFM business units should populate configured DFF fields.<\/p>\n\n\n\n

                \n
              1. Apply Conditional Visibility Using VBS For Hire Employee and Add Pending Worker<\/li>\n<\/ol>\n\n\n\n

                Inside Visual Builder Studio, visibility rules were applied to the DFF fields.<\/p>\n\n\n\n

                The logic checks the selected Business Unit during the hire transaction.<\/p>\n\n\n\n

                Example Logic:<\/strong><\/p>\n\n\n\n

                If Business Unit = “ALL EDFM BU\u2019s”<\/p>\n\n\n\n

                Then Show EDFM DFF Fields<\/p>\n\n\n\n

                Else Hide EDFM DFF Fields<\/p>\n\n\n\n

                This logic was extended to include all EDFM-related business units.<\/p>\n\n\n\n

                \"\"<\/figure>\n\n\n\n
                \"\"<\/figure>\n\n\n\n
                \"\"<\/figure>\n\n\n\n
                  \n
                1. Configure the Visibility Rule Hire Employee and Pending worker<\/li>\n<\/ol>\n\n\n\n

                  Within VBS:<\/p>\n\n\n\n

                    \n
                  1. Navigate to the Hire an Employee \/Add Pending Worker.<\/li>\n\n\n\n
                  2. Locate the Assignment<\/li>\n\n\n\n
                  3. Select the DFF fields<\/li>\n<\/ol>\n\n\n\n

                    $fields.BusinessUnit in [\u2018ALL EDFM BU\u2019s’]<\/p>\n\n\n\n

                    If the condition evaluates to true, the DFF fields appear.<\/p>\n\n\n\n

                    If false, the fields remain hidden.<\/p>\n\n\n\n

                    \"\"<\/figure>\n\n\n\n
                    \"\"<\/figure>\n\n\n\n
                      \n
                    1. <\/li>\n<\/ol>\n\n\n\n

                      Benefits of This Approach<\/h2>\n\n\n\n

                      Implementing conditional field visibility using VBS provided several advantages:<\/p>\n\n\n\n

                        \n
                      1. Improved User Experience<\/strong><\/li>\n<\/ol>\n\n\n\n

                        Users only see fields relevant to their business unit.<\/p>\n\n\n\n

                          \n
                        1. Reduced Data Entry Errors<\/strong><\/li>\n<\/ol>\n\n\n\n

                          Irrelevant fields are hidden, preventing accidental input.<\/p>\n\n\n\n

                            \n
                          1. Cleaner UI<\/strong><\/li>\n<\/ol>\n\n\n\n

                            The Assignment page remains streamlined and easier to navigate.<\/p>\n\n\n\n

                              \n
                            1. Flexible Configuration<\/strong><\/li>\n<\/ol>\n\n\n\n

                              Additional EDFM business units can be easily added to the visibility rule.<\/p>\n\n\n\n

                                \n
                              1. Supports Multi-Project Environment<\/strong><\/li>\n<\/ol>\n\n\n\n

                                Both Hartree and EDFM projects can operate within the same Fusion instance without UI conflicts.<\/p>\n\n\n\n

                                Best Practices for Similar Implementations<\/h2>\n\n\n\n

                                If you are implementing conditional UI logic in Oracle Fusion HCM, consider the following best practices:<\/p>\n\n\n\n

                                  \n
                                1. Use Clear Business Unit Mapping<\/strong>
                                  Maintain a documented list of business units associated with each project.<\/li>\n\n\n\n
                                2. Avoid Hardcoding Where Possible<\/strong>
                                  Consider referencing configuration tables if the list of business units is large.<\/li>\n\n\n\n
                                3. Test Multiple Scenarios<\/strong>
                                  Validate visibility rules for:<\/li>\n<\/ol>\n\n\n\n
                                    \n
                                  • EDFM Business Units<\/li>\n\n\n\n
                                  • Hartree Business Units<\/li>\n\n\n\n
                                  • Future Business Units<\/li>\n<\/ul>\n\n\n\n

                                    Conclusion<\/h2>\n\n\n\n

                                    As organizations consolidate HR platforms into Oracle Fusion HCM, the need for flexible UI customization becomes essential. Using Visual Builder Studio (VBS) to control the visibility of Descriptive Flexfields (DFFs) based on Business Unit is a powerful approach to managing complex multi-project environments.<\/p>\n\n\n\n

                                    In the EDFM migration scenario, this solution ensured that only EDFM users interacted with EDFM-specific fields, while Hartree users experienced a simplified interface\u2014leading to improved usability and cleaner data capture.<\/p>\n\n\n\n

                                    If you’re working on Oracle Fusion HCM implementations, Redwood UI customizations, or VBS configurations, this approach can help streamline your UI while supporting multiple business structures within the same environment.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                    Introduction: Conditional Display of DFF Fields Using VBS in Oracle Fusion HCM During Multi-Project Data Migration When organizations migrate HR systems to Oracle Fusion HCM, managing configuration differences across multiple business units and legal entities becomes critical. In large transformation programs\u2014especially those involving parallel projects\u2014ensuring that users see only relevant fields during transactions such as […]<\/p>\n","protected":false},"author":1,"featured_media":33716,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[18],"tags":[],"class_list":["post-33715","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oracle-hcm"],"acf":[],"_links":{"self":[{"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/posts\/33715","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/comments?post=33715"}],"version-history":[{"count":1,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/posts\/33715\/revisions"}],"predecessor-version":[{"id":33717,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/posts\/33715\/revisions\/33717"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/media\/33716"}],"wp:attachment":[{"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/media?parent=33715"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/categories?post=33715"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/tags?post=33715"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}