Thursday, 30 March 2017

5 things about PeopleSoft Cloud Manager



PeopleSoft Cloud Manager was announced at OpenWorld 2016 . On Feb 14 it became available on Oracle Cloud Marketplace.  

  1. Cloud Manager is a PeopleSoft application which can define and manage instances of PeopleSoft in the Oracle Cloud.  
  2. PeopleSoft Cloud Manager only runs on Oracle Compute Cloud infrastructure and you can get it from the Oracle Cloud Marketplace .  Just search for Cloud Manager.   
  3. Cloud Manager is written in PeopleTools using the PeopleSoft Interaction Hub and needs it's own standalone instance just like any other pillar (HCM, FSCM, CRM, etc). 
  4. You can subscribe to software updates that you have an interest in which will be automatically downloaded for you.  This includes:
    • PeopleTools patches, 
    • application PRPs, 
    • PUM Images 
  5. Cloud Manager software is free for PeopleSoft customers but you pay for infrastructure used on the Oracle Compute Cloud.  OCC is charged on the basis of how many OCPUs you use and how much storage you use (there are other chargeable items which you can read more on here). 

Useful Links:


Monday, 20 March 2017

5 things about Fluid Page None Search Type


There are 3 search types you can specify for a Fluid component : None, Standard (also known as Pivot Grid ) and Master /Detail (on page, left side, persistant search results).

Here's 5 things about None:
  1. None is the default Search Type for a Fluid Component and is set in the Component properties Fluid tab.  It is often found in self service applications where the search data is  known and already exists in the database (e.g. employee id)
    Search Type = None
  2. A Search Type of None will not give you a search page (sorry to state the obvious here but some aspects of Fluid development are not always obvious).  However, the component still requires a search record.  This can be a record with no search keys such as the INSTALLATION table or a record with multiple search keys such as HR_SS_PERS_SRCH.  
  3. Even though the Component search record may have search keys a Fluid component will not present a search page.  Instead you must set search keys either in SearchInit PeopleCode event as the component loads or in a parameter record in a TRANSFER(...) function or  as parameters in the URL. 
    Set search keys in SearchInit

    Transfer with keys in record


    Search keys in URL parameters


  4. Use  SearchInit PeopleCode event  SetSearchBehaviorMode(0)to automatically execute the search and land on the first page.  
  5. If you need to open a Fluid Component in Add mode then append &action=A parameter to the transfer URL or use the "A" parameter in the TRANSFER function.  This is not as easy as it sounds with a Fluid component set to search type None and so if you need add mode it might be better to set search type = Standard (more on this in a future blog).

Thursday, 2 March 2017

5 things about PeopleSoft Page Composer

  1. Page Composer creates Fluid pages through configuration.  At the moment this is only available for Fluid Approvals (introduced in HCM & FSCM Images 020 and CRM 012 and ELM 015) but as a general framework for page construction you can see where Oracle is taking this.  It is part of Enterprise Components NOT PeopleTools. Although you will need to be on at least PeopleTools 8.54.27 or 8.55.10 (See Doc ID 2166359.1

  2. Page Composer pages are based on a Page Composer Registration in which you define the sections of the page (summary, header, detail, etc) and the data sources and custom business logic.  You can define up to 5 header and 5 line sections.  
  3. There is currently only one Page Composer composition type of APPROVALS.  The approvals pages are all based on the same component EOAWMA_MAIN_FL.  Page definition EOAWMA_RSLT_SBF renders the initial summary list view and page definitions EOAWMA_TXNHDTL_FL (header) and EOAWMA_TXNLDTL_FL (line) render the Detail you see when you click one of the summary list items.  (TOP TIP:  Of all the pages delivered with PeopleSoft I think I would try and avoid customising this page due to a) it's high complexity and b) the likelihood of it changing with each image release.  
  4. When defining the Page Composer Registration it takes a bit of trial and error to identify which page fields can be referenced and used.  Suggest looking at delivered Page Composer definitions in Image 020 and cribbing these for your own definitions.  
  5. You can assign custom PeopleCode to page field events.  Create an App Package class which extends class EOPC_RUNTIME:pcFieldEventAction and assign to a field in the Page Composer Registration Field Event page.