I thought that this would be a good opportunity to test the Page and Field Configurator.
As there were a dozen or so fields, I tried at first to use the 'Configure Page Visibility' grid, as you can make the page Display Only. But the problem with this was that the run control links and the 'Run' button were also disabled (as they didn't have the options set to be enabled when display only).
Instead I used the 'Configure Field Properties' grid and selected the fields from the lookup (a modal component) and selected the 'Disable Entry' option.
However, I noticed that the Pay Cycle field which was a series of radio buttons, was not available to select. From memory, the PeopleCode is querying the PSPNLFIELD table but skipping the Radio Button fields.
To get around this I was able manually insert the value into the database, e.g.
INSERT INTO PS_EOCC_CONFIG_FLD (PNLGRPNAME,MARKET,SEQUENCE_NBR,RECNAME,FIELDNAME,OCCURSLEVEL,RECNAME1,FIELDNAME1,LBLTEXT,PNLNAME,STDPNLNAME,PTCS_PNLFLDNAME,EOCC_LBL_OVERRIDE,EOCC_IS_REQUIRED,EOCC_DFLT_VALUE,EOCC_VISIBLE_FLAG,EOCC_DISABLED,FIELDTYPE,FIELDUSE,EOCC_FIELD_TYPE,EOCC_SBP_LEVEL,RECNAME_BASE,PTAI_SYSTEM_DATA)
VALUES (...)The 'Map to Portal Registry' page allows you to automatically create the Event Mapping using the EOCC% services.
So this catered for the first part of the requirement, and to cater for the second part of the requirement I was able to create another Event Mapping PeopleCode which sets the value of the two fields. I was able to configure this to run PostBuild after the EOCC_POSTBUILD service.
So there were no customizations to the delivered objects!
This was migrated by using the Data Migration Workbench and an Application Designer project.
- The Application Designer project contained the Application Packages, and the PeopleCode.
- The DMW project contained data sets EOCC_CONFIGURATION, RCF_SERVICES, and RCF_SERVICE_DEFINITIONS.
No comments:
Post a Comment