Friday, May 15, 2020

Drop Zones for Classic

PeopleTools 8.58 introduced Drop Zones for Classic. I previously wrote about a SQL query that helps us identify a list of delivered components (both Fluid and Classic) that contain Drop Zones.

Refer: SQL to list Components with Drop Zones

At the time of writing (April 13, 2020), I reported that I could not find any application PUM image that contained classic components with Drop Zones. I tried executing the same SQL in a HCM - PUM image 34 (which is also on 8.58.03) and to my surprise I found 20 classic components with Drop Zones. Kudos to the HCM team for leveraging a lot of the latest PeopleTools features such as Kibana Dashboards, Classic Drop Zones, etc.!!

Oracle ACE Director, Graham Smith, showed us (in detail with a simple example) how we can use the Drop Zones that are delivered for Fluid components.

Refer: http://i-like-trains.blogspot.com/2019/04/drop-zones-and-hcm-image-030.html

Further details can be found in PeopleBooks: Understanding Drop Zones

COMPANY_TABLE is an example of a classic component in HCM Image 34 which contains Drop Zones.






Let us create a simple subpage and test the Drop Zone feature in Classic.

Custom subpage with page field elements

Let us create a custom subpage (as described in the Peoplebooks referenced earlier). This contains the required group box (container) that encompasses the entire subpage. All other page elements on this subpage must be enclosed within this container. We need to also clear the group box label text, set label style to PAGROUPBOXLABELINVISIBLE, select Adjust Layout for Hidden Fields check box and optionally select the Hide Border check box.


Configure Drop Zone

PeopleTools > Portal > Configure Drop Zones




Demo


10 comments:

  1. Hi Sasank,

    I created custom subpage and added the dropzone on Location_table component. But, when i am going back to Configure Dropzones component to remove the dropzone, it is not showing me the page with my changes. Rather everything in grid is blank and instead of subpage there is written subpanel.

    ReplyDelete
    Replies
    1. By any chance, did you delete the subpage which you used in the drop zone?

      It appears that the subpage object might be deleted. You can verify by opening it in App Designer. See if you get any errors and report back. Thanks!

      Delete
  2. Hi Sasank,

    We are working with Applicant Portal, drop zone is working perfectly on internal applicant. However, when using the external applicant link, details on the drop zone is not available. I have performed trace and it seems that the drop zone in not being initiated when using external link

    ReplyDelete
    Replies
    1. Sorry for the delayed response.

      Good question. Have you compared security on the external site default user? You might want to create a service request on My Oracle Support for further clarification.

      Delete
  3. Hi Sasank -

    We currently have an invisible field in a delivered page. Just so we can control the prompt table via peoplecode.

    FIELD.PROMPT = %EDITTABLE.

    We then have a row init record peoplecode which drives the value of the edittable to some record.

    The question is, can the page detect the fields that are in the dropzone?

    ReplyDelete
    Replies
    1. Great question. Yes, I think so.

      But I have not tried this and would be curious what you find. Technically, what you add to the dropzone is in the component buffer so you can access it from anywhere within the context of that component.

      Delete
  4. Hi Sasank,

    Any tips on how to migrate the custom dropzones using appdesigner?

    ReplyDelete
    Replies
    1. You can review this document on MOS:
      E-PORTAL: How to Migrate Drop Zones and Event Mapping from One Environment to Another (Doc ID 2654704.1)

      Delete
  5. Hi Sasank,

    Can we drop a subpage with some fields to show data based on the main page? If yes, how can we achieve populating data into those fields?

    Thanks
    Biswa

    ReplyDelete
    Replies
    1. Hi Biswa - Once you add a dropzone to a page, anything you add (fields, etc.) become part of the component buffer.

      You can consider it similar to adding the fields directly on the page. Therefore, you can use the standards methods available to populate the data on those fields.

      Delete