The friendly URL syntax https://example.com:5500/ords/r/mycompany/hr-app/updateemployees?session=13766599855150 has the following components:

session=13766599855150 is the session ID. A new ID is generated for each session. This parameter identifies which session is associated with the request.

hr-app is the application alias. This parameter identifies which application is being requested. An application alias is a user-friendly name that can be used instead of an application ID.

mycompany is the path-prefix which is by default the workspace name. This parameter identifies which workspace is being requested. A path-prefix is a URL segment that can be used instead of a workspace ID.

updateemployees is the page alias. This parameter identifies which page is being requested. A page alias is a user-friendly name that can be used instead of a page number.

The other option is incorrect because:

update-employees is not the PL/SQL procedure to update the employee details. It is the page alias that identifies which page is being requested.

Verified References: [About Friendly URLs] [Understanding URL Syntax]

A master detail form is a type of form that enables users to query, insert, update, and delete values from two related tables or views. A master detail form reflects a one-to-many relationship between tables in a database. Typically, a master detail form displays a master row and multiple detail rows. In APEX, you can create three types of master detail forms using the Create Page Wizard or the Create Application Wizard:

Stacked: A stacked master detail form contains a single page with editable interactive grids based on two related tables or views. Users select a row in the master grid to update the detail grid. Developers can create a stacked master detail with either the Create Application Wizard or the Create Page Wizard.

Side by Side: A side by side master detail form contains a single page with two editable interactive grids based on two related tables or views. Users can see and edit both the master and detail grids at the same time. Developers can create a side by side master detail with either the Create Application Wizard or the Create Page Wizard.

Two Page Drill Down: A two page drill down master detail form contains two pages based on two related tables or views. The first page is a non-editable interactive grid for the master table. Users click the Edit icon on the first page to edit details on the second page. The second page includes both a standard form for the master and an editable interactive grid for the detail. Developers can create a two page drill down master detail with only the Create Page Wizard.

When you create an Access Control Page using the Create Page Wizard, three of the following Access Roles get created: Reader, Administrator, and Contributor.These roles are predefined by APEX and correspond to the authorization schemes that control the access to the application, pages, or page components1. Reader role grants read-only access to the application. Administrator role grants full access to the application, including administrative and edit privileges.Contributor role grants edit privileges to the application, but not administrative privileges2. Developer role is not a default Access Role created by the wizard, but you can create your own custom roles and assign them to users on the Application Access Control page.

The Developer Toolbar is a component that appears at the bottom of every page in an Oracle APEX application when running in development mode. The Developer Toolbar provides quick access to various features and tools for developing and debugging an application. One of the options in the Developer Toolbar that enables developers to customize the look and feel of the application is Customize.

Customize: This option opens the Theme Roller tool that allows developers to modify the theme style of the application by changing colors, fonts, sizes, borders, shadows, and more. Developers can also create new theme styles or switch between existing ones using this option.

d event under the Drag and Drop PL/SQL Code attribute of the Calendar component. This attribute allows you to write PL/SQL code to update the event row in the database after the user drags and drops an event on the calendar. To reference the ID, the new start date, and the new end date of the dragged event, you can use these bind variables: :APEX.PK_VALUE, :APEX.NEW_START_DATE and :APEX.NEW_END_DATE. These variables are automatically populated by APEX when the user performs a drag and drop action on the calendar. For example, you can write something like this:

UPDATE events

SET start_date = :APEX.NEW_START_DATE,

end_date = :APEX.NEW_END_DATE

WHERE id = :APEX.PK_VALUE;