{"id":31010,"date":"2026-01-06T06:41:25","date_gmt":"2026-01-06T06:41:25","guid":{"rendered":"http:\/\/kovaion-new1.local\/pum-37-enhancement-more-on-page-and-field-configurator\/"},"modified":"2026-01-06T06:49:23","modified_gmt":"2026-01-06T06:49:23","slug":"pum-37-enhancement-more-on-page-and-field-configurator","status":"publish","type":"post","link":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/pum-37-enhancement-more-on-page-and-field-configurator\/","title":{"rendered":"PUM 37 Enhancement – More on Page and Field Configurator"},"content":{"rendered":"

PUM 37 Enhancement \u2013 More on Page and Field Configurator (PFC)<\/strong><\/p>\n

\u201cPage and field Configurator\u201d is a feature delivered by PeopleSoft for the configuration of certain pages and fields of classic and fluid pages based on the requirements. Users can do modifications like hide fields, modify labels, disable fields, default value for a field, disable the page based on condition without the use of application designer. It does not affect the original page in application designer. Multiple configurations are possible for the same component based on user role or criteria within transaction.<\/p>\n

Page and field Configurator supports two types of configurations-<\/p>\n

Standard Configuration<\/strong>: Normal modification can be done such as hiding field, set default field, label change, making field compulsory.<\/p>\n

Masking Configuration<\/strong>: User can mask the page fields based on condition.<\/p>\n

New features pertinent to PFC that PeopleSoft has delivered HCM image 37 are:<\/p>\n

    \n
  1. Extending field\u2013Based criteria to level 1 field:<\/strong>\u00a0Earlier fields available as criteria were limited to \u2018level zero\u2019 but now it has been extended to \u2018level one\u2019.<\/li>\n
  2. Extending PFC to create field change Events:<\/strong>\u00a0Based on the user inputs on the page, the fields can be changed based on the condition. This includes both level zero and level one field.<\/li>\n
  3. Streamlined Selection of fields:\u00a0<\/strong>Select the fields that should be available in field list or as criteria.<\/li>\n
  4. Set a field values to bank:\u00a0<\/strong>If a field is hidden or display only through PFC then it can be set to blank ensuring no values is saved in the database only if the sequence has criteria.<\/li>\n<\/ol>\n

    <\/p>\n

    Fig. 1: Set value to Zero<\/strong><\/p>\n

    Steps to mask a field using page and field Configurator: Quick Re-cap<\/strong><\/p>\n

    Navigation:\u00a0<\/strong>Enterprise Component> Page and field Configurator> Page and field Configurator.<\/p>\n

      \n
    • Select the component name for which configuration need to be done and configuration type should be masking.<\/li>\n
    • Add the criteria if required. It is an optional.<\/li>\n
    • Select the fields need to be masked on the page.<\/li>\n
    • Configuration can be restricted by applying role\/Userid using User list page.<\/li>\n<\/ul>\n

      <\/strong><\/p>\n

      Fig. 2: Masking page<\/strong><\/p>\n

        \n
      • Map the configurations to the corresponding portal registry entries using Map Configuration to Portal Registry page.<\/li>\n
      • Click on the apply configuration.<\/li>\n<\/ul>\n

        <\/strong><\/p>\n

        Fig. 3: Map to Portal Registry Page<\/strong><\/p>\n

        Extending PFC to create field change Events:\u00a0<\/strong>All the fields used as criteria will be included under field change event in event mapping. It is created only when \u201cApply Configuration: is clicked under Map to Portal Registry page.<\/p>\n

        <\/strong><\/p>\n

        Fig. 4: Event Mapping<\/strong><\/p>\n

        Streamlined Selection of fields:<\/strong>\u00a0The number of fields can be set as per the requirement and included in the criteria list. This is one time action.<\/p>\n

        <\/p>\n

        Fig. 5: Advance Options Page<\/strong><\/p>\n

          \n
        • When the fields are selected and there is a need to select the specific fields from advance options, then Select the \u201cRestrict to fields from Advanced Options\u201d checkbox. It will fetch all the fields which are included in criteria list. But this is optional functionality.<\/li>\n<\/ul>\n

          <\/strong><\/p>\n

          Fig. 6: Selection of criteria field<\/strong><\/p>\n

          To view the changes made using PFC,<\/strong><\/p>\n

          Navigation:\u00a0<\/strong>Workforce Administration > Personal Information > Biographical > Modify a Person<\/p>\n

            \n
          • Enter the Emplid and select the appropriate page to see the output.<\/li>\n
          • Telephone has been masked based on the condition which was specified during configuration.<\/li>\n
          • As the user changes the page, the configuration reflects on the page.<\/li>\n<\/ul>\n

            <\/strong><\/p>\n

            Fig. 3: Contact Information Page<\/strong><\/p>\n

            Benefits:<\/strong><\/p>\n

              \n
            • PFC is being enhanced in subsequent releases to ensure eased and beneficial use<\/li>\n
            • Eliminates the use of application designer.<\/li>\n
            • Reduces the cost and impact associated with customizations and upgrades.<\/li>\n
            • Data Masking can be enabled without customizing code<\/li>\n<\/ul>\n

              Author
              \nAmrit Kumar Gupta<\/strong>
              \nPeopleSoft Techno-Functional Consultant<\/p>\n","protected":false},"excerpt":{"rendered":"

              PUM 37 Enhancement \u2013 More on Page and Field Configurator (PFC) \u201cPage and field Configurator\u201d is a feature delivered by PeopleSoft for the configuration of certain pages and fields of classic and fluid pages based on the requirements. Users can do modifications like hide fields, modify labels, disable fields, default value for a field, disable […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[],"tags":[],"class_list":["post-31010","post","type-post","status-publish","format-standard","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/posts\/31010","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=31010"}],"version-history":[{"count":1,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/posts\/31010\/revisions"}],"predecessor-version":[{"id":31011,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/posts\/31010\/revisions\/31011"}],"wp:attachment":[{"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/media?parent=31010"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/categories?post=31010"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/stage.kovaionplay.com\/stage-kovaion\/wp-json\/wp\/v2\/tags?post=31010"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}