Using the Address Block in a Job Application Flow

The Address block in the job application flow uses the address styles and address formats configured in the Setup and Maintenance work area.

You define address styles using the Features by Country or Territory task, in the Setup and Maintenance work area. You use this task to define whether the Postal Address or the Supplemental Taxation and Reporting Address style is used for a given country. If the Human Resources extension is selected for a country, you can select any address style. If you select the Payroll or Payroll Interface extension, the address style depends on the localization. For details, refer to the document HCM Address Validation on My Oracle Support (ID: 2140848.1).

You define the address formats for countries using the Manage Address Formats task, in the Setup and Maintenance work area. You use this task to define the address elements and their display sequence. There are two exceptions where the display sequence isn't considered on career sites:

• The country field is always at the top of the Address block.

• The list of values (LOV) displaying the address elements is displayed at the top of the Address block, below the country. If there's more than one LOV element, they will be sorted based on the display sequence defined in the Manage Address Formats task. If there are a few address variations set for a country, the first variation is used.

How it Works for Candidates

The content of the Address block in a job application flow is dynamic. Address fields are rendered based on the Country value selected in the block. In some cases, the country is prepopulated for a candidate. If the candidate allowed to use their browser location, the country is filled based on that location. Otherwise, the country is filled based on the job requisition's primary location.

If address elements are set as dependent LOVs, the value for the higher hierarchy element (for example, State) has to be provided so that the lower hierarchy element can be selected (for example, City). During the profile import, the application attempts to import data to the Address block. If one of the higher hierarchy element is missing, elements lower in the hierarchy won't be populated. They will be temporarily stored and will auto-populate if the candidate selects a matching missing element.

If there's some data in the Address block and the value for Country is changed, the data is kept in all matching fields that aren't LOVs.

Example 1: In this example, the country is changed for Canada. When the country value is changed, values for LOVs aren't retrieved.

Before	After
Country (LOV): United States State (LOV): NY County (LOV): New York City (LOV): New York ZIP Code (LOV): 10165 Address Line 1 (free text): 120 Park Ave Address Line 2 (free text): 26th floor	Country (LOV): Canada Province (LOV): City (LOV): Postal Code (LOV): Address Line 1 (free text): 120 Park Ave Address Line 2 (free text): 26th floor

Example 2: In this example, the country is changed for Portugal.

Before	After
Country (LOV): Poland Province (free text): Malopolskie City (free text): Krakow Postal Code (LOV): 31-476 Address Line 1 (free text): ul. Bora Komorowskiego 25	Country (LOV): Portugal Region (free text): City (free text): Krakow Postal Code (LOV): 31-476 Address Line 1 (free text): 120 Park Ave

During a profile import from any source, data in the Address block is replaced by data imported from the profile.