Why & How to Use Oracle APEX Application Variables

Introduction

In the world of database development and management, Oracle APEX (Application Express) is an indispensable tool that allows developers to create powerful and scalable web applications. One of the core components of Oracle APEX is the various variables that enable flexible and dynamic application design.

In this blog, I will provide a detailed explanation of the different variables used in Oracle APEX, why they are important, and how they can be utilized. Additionally, I will include a small example for each variable to illustrate its potential use case. Let's dive into the world of Oracle APEX variables and discover their versatile applications!

1. APP_ID

1.1 Description

The variable APP_ID represents the unique ID of the application in Oracle Application Express (APEX). This ID is automatically generated when a new application is created and remains constant throughout the application's lifetime. It is a numeric value that uniquely identifies the application within the APEX workspace.

1.2 When could the use of this variable be useful?

The APP_ID is crucial because it serves as the primary identifier for the application. It is used in various contexts to uniquely identify the application, especially in URL generation, API calls, and other automated processes. Without a unique ID, it would be challenging to distinguish between different applications and perform specific operations. It is particularly useful in scenarios where you need to reference the application programmatically or generate dynamic URLs.

1.3 Example Usage

Suppose you want to generate a URL that directly navigates to a specific page within your application. You can use the APP_ID to ensure the URL correctly points to your application.

 

SQL

xxxxxxxxxx

 

1

DECLARE

2

  v_url VARCHAR2(4000);

3

BEGIN

4

  v_url := 'f?p=' || :APP_ID || ':1:' || :APP_SESSION;

5

  -- Additional logic here

6

END;

In this example, a URL is generated that navigates to the home page (page 1) of the current application. The APP_ID ensures the URL points to the correct application, while APP_SESSION considers the current session.

2. APP_ALIAS

2.1 Description

The variable APP_ALIAS represents the alias name of the application. This alias can be used as a more readable and memorable identifier for the application. Unlike APP_ID, which is numeric, APP_ALIAS is a string that can be customized to be more meaningful or easier to remember.

2.2 When could the use of this variable be useful?

Using APP_ALIAS is beneficial when you need a human-readable identifier for your application, such as in URLs, documentation, or when referencing the application in communications. It can make URLs more user-friendly and easier to share or remember.

2.3 Example Usage

You can use APP_ALIAS to create a more user-friendly URL for your application.

 

SQL

xxxxxxxxxx

 

1

DECLARE

2

  v_url VARCHAR2(4000);

3

BEGIN

4

  v_url := 'f?p=' || :APP_ALIAS || ':1:' || :APP_SESSION;

5

  -- Additional logic here

6

END;

In this example, the URL uses APP_ALIAS instead of APP_ID to create a more readable link to the application.

3. APP_DATE_TIME_FORMAT

3.1 Description

The variable APP_DATE_TIME_FORMAT specifies the date and time format for the application. This format is used to display dates and times consistently throughout the application, ensuring a uniform user experience.

3.2 When could the use of this variable be useful?

This variable is useful when you need to ensure consistent date and time formatting across your application, especially when displaying dates and times to users. It helps in maintaining a standard format that aligns with the application's locale or user preferences.

3.3 Example Usage

You can use APP_DATE_TIME_FORMAT to format a date in a PL/SQL block.

 

SQL

xxxxxxxxxx

 

1

DECLARE

2

  v_date VARCHAR2(100);

3

BEGIN

4

  v_date := TO_CHAR(SYSDATE, :APP_DATE_TIME_FORMAT);

5

  -- Additional logic here

6

END;

In this example, the current date is formatted according to the application's date and time format.

4. APP_IMAGES

4.1 Description

The variable APP_IMAGES provides the path to application-specific images, JavaScript, or CSS files. This path is used to reference static resources that are part of the application, ensuring they are correctly loaded and displayed.

4.2 When could the use of this variable be useful?

This variable is useful when you need to reference static files like images, JavaScript, or CSS files that are specific to your application. It helps in organizing and managing these resources, making them easily accessible within the application.

4.3 Example Usage

You can use APP_IMAGES to reference an image in your application.

 

HTML/XML

xxxxxxxxxx

 

1

<img src="# APP_IMAGES# my_image.png" alt="My Image">

In this example, the image path is dynamically generated using the APP_IMAGES variable, ensuring the correct path is used.

5. APP_NLS_DATE_FORMAT

5.1 Description

The variable APP_NLS_DATE_FORMAT specifies the date format for the database session. This format is used to ensure that dates are consistently formatted according to the application's locale settings.

5.2 When could the use of this variable be useful?

This variable is useful when you need to ensure that dates are consistently formatted according to the application's locale settings in the database session. It helps in maintaining a standard date format that aligns with the user's locale preferences.

5.3 Example Usage

You can use APP_NLS_DATE_FORMAT to format a date in a SQL query.

 

SQL

xxxxxxxxxx

 

1

SELECT TO_CHAR(SYSDATE, :APP_NLS_DATE_FORMAT) AS formatted_date FROM DUAL;

In this example, the current date is formatted according to the application's NLS date format.

6. APP_NLS_TIMESTAMP_FORMAT

6.1 Description

The variable APP_NLS_TIMESTAMP_FORMAT specifies the timestamp format for the database session. This format is used to ensure that timestamps are consistently formatted according to the application's locale settings.

6.2 When could the use of this variable be useful?

This variable is useful when you need to ensure that timestamps are consistently formatted according to the application's locale settings in the database session. It helps in maintaining a standard timestamp format that aligns with the user's locale preferences.

6.3 Example Usage

You can use APP_NLS_TIMESTAMP_FORMAT to format a timestamp in a SQL query.

 

SQL

xxxxxxxxxx

 

1

SELECT TO_CHAR(SYSTIMESTAMP, :APP_NLS_TIMESTAMP_FORMAT) AS formatted_timestamp FROM DUAL;

In this example, the current timestamp is formatted according to the application's NLS timestamp format.

7. APP_NLS_TIMESTAMP_TZ_FORMAT

7.1 Description

The variable APP_NLS_TIMESTAMP_TZ_FORMAT specifies the timestamp with time zone format for the database session. This format is used to ensure that timestamps with time zones are consistently formatted according to the application's locale settings.

7.2 When could the use of this variable be useful?

This variable is useful when you need to ensure that timestamps with time zones are consistently formatted according to the application's locale settings in the database session. It helps in maintaining a standard timestamp with time zone format that aligns with the user's locale preferences.

7.3 Example Usage

You can use APP_NLS_TIMESTAMP_TZ_FORMAT to format a timestamp with time zone in a SQL query.

 

SQL

xxxxxxxxxx

 

1

SELECT TO_CHAR(SYSTIMESTAMP, :APP_NLS_TIMESTAMP_TZ_FORMAT) AS formatted_timestamp_tz FROM DUAL;

In this example, the current timestamp with time zone is formatted according to the application's NLS timestamp with time zone format.

8. APP_PAGE_ID

8.1 Description

The variable APP_PAGE_ID represents the current page ID within the application. This ID is used to uniquely identify and reference the current page.

8.2 When could the use of this variable be useful?

This variable is useful when you need to reference or manipulate the current page, such as in dynamic actions, conditions, or URL generation. It helps in identifying the page context and performing page-specific operations.

8.3 Example Usage

You can use APP_PAGE_ID to generate a URL that navigates to the current page.

 

SQL

xxxxxxxxxx

 

1

DECLARE

2

  v_url VARCHAR2(4000);

3

BEGIN

4

  v_url := 'f?p=' || :APP_ID || ':' || :APP_PAGE_ID || ':' || :APP_SESSION;

5

  -- Additional logic here

6

END;

In this example, the URL navigates to the current page of the application.

9. APP_SESSION

9.1 Description

The variable APP_SESSION represents the current session ID. This ID is used to maintain session state and track user interactions within the application.

9.2 When could the use of this variable be useful?

This variable is crucial for maintaining session state and ensuring that user interactions are correctly tracked within the application. It helps in managing user sessions and providing a seamless user experience.

9.3 Example Usage

You can use APP_SESSION to generate a URL that includes the current session ID.

 

SQL

xxxxxxxxxx

 

1

DECLARE

2

  v_url VARCHAR2(4000);

3

BEGIN

4

  v_url := 'f?p=' || :APP_ID || ':1:' || :APP_SESSION;

5

  -- Additional logic here

6

END;

In this example, the URL includes the current session ID to maintain session state.

10. APP_SESSION_VISIBLE

10.1 Description

The variable APP_SESSION_VISIBLE represents the current session ID, but returns 0 if the user is not logged in. This helps in determining the visibility of the session.

10.2 When could the use of this variable be useful?

This variable is useful for determining whether a user is logged in and for handling scenarios where session visibility is required. It helps in managing user access and providing appropriate responses based on the session state.

10.3 Example Usage

You can use APP_SESSION_VISIBLE to check if a user is logged in before performing an action.

 

SQL

xxxxxxxxxx

 

1

IF :APP_SESSION_VISIBLE = 0 THEN

2

  -- User is not logged in, handle accordingly

3

ELSE

4

  -- User is logged in, proceed with action

5

END IF;

In this example, the code checks if the user is logged in before proceeding with an action.

11. APP_UNIQUE_PAGE_ID

11.1 Description

The variable APP_UNIQUE_PAGE_ID returns a unique page ID that can be used to prevent browser caching. This ID is generated to ensure that each page request is unique.

11.2 When could the use of this variable be useful?

This variable is useful when you need to ensure that pages are not cached by the browser, such as in dynamic or frequently changing content. It helps in preventing outdated content from being displayed to the user.

11.3 Example Usage

You can use APP_UNIQUE_PAGE_ID to generate a URL that includes a unique page ID.

 

SQL

xxxxxxxxxx

 

1

DECLARE

2

  v_url VARCHAR2(4000);

3

BEGIN

4

  v_url := 'f?p=' || :APP_ID || ':' || :APP_PAGE_ID || ':' || :APP_SESSION || '&u=' || :APP_UNIQUE_PAGE_ID;

5

  -- Additional logic here

6

END;

In this example, the URL includes a unique page ID to prevent caching.

12. APP_USER

12.1 Description

The variable APP_USER represents the current username of the application. This username is used to identify the logged-in user.

12.2 When could the use of this variable be useful?

This variable is useful for personalizing the user experience, tracking user activity, or applying user-specific logic. It helps in providing a customized experience based on the user's identity.

12.3 Example Usage

You can use APP_USER to display a personalized greeting to the user.

 

SQL

xxxxxxxxxx

 

1

DECLARE

2

  v_greeting VARCHAR2(100);

3

BEGIN

4

  v_greeting := 'Welcome, ' || :APP_USER || '!';

5

  -- Additional logic here

6

END;

In this example, a personalized greeting is generated using the current username.

13. AUTHENTICATED_URL_PREFIX

13.1 Description

The variable AUTHENTICATED_URL_PREFIX is used to generate URLs that require authentication. This prefix ensures that the URLs are only accessible to authenticated users.

13.2 When could the use of this variable be useful?

This variable is useful when you need to ensure that generated URLs require user authentication before access is granted. It helps in securing sensitive or restricted content.

13.3 Example Usage

You can use AUTHENTICATED_URL_PREFIX to generate an authenticated URL.

 

SQL

xxxxxxxxxx

 

1

DECLARE

2

  v_url VARCHAR2(4000);

3

BEGIN

4

  v_url := :AUTHENTICATED_URL_PREFIX || 'f?p=' || :APP_ID || ':1:' || :APP_SESSION;

5

  -- Additional logic here

6

END;

In this example, the URL requires user authentication before access is granted.

14. BROWSER_LANGUAGE

14.1 Description

The variable BROWSER_LANGUAGE represents the preferred language requested by the web browser. This language preference is used to tailor the content to the user's language settings.

14.2 When could the use of this variable be useful?

This variable is useful for localizing content based on the user's preferred language settings in their browser. It helps in providing a localized experience that aligns with the user's language preferences.

14.3 Example Usage

You can use BROWSER_LANGUAGE to display content in the user's preferred language.

 

SQL

xxxxxxxxxx

 

1

DECLARE

2

  v_language VARCHAR2(10);

3

BEGIN

4

  v_language := :BROWSER_LANGUAGE;

5

  -- Additional logic here to load content in the preferred language

6

END;

In this example, the preferred language is retrieved from the browser settings and used to load localized content.

15. CURRENT_PARENT_TAB_TEXT

15.1 Description

The variable CURRENT_PARENT_TAB_TEXT is used in applications that utilize two-level tabs. It returns the current parent tab level, providing context for the navigation structure.

15.2 When could the use of this variable be useful?

This variable is useful for navigating or displaying information based on the current parent tab in a two-level tab structure. It helps in maintaining context and providing relevant information based on the parent tab.

15.3 Example Usage

You can use CURRENT_PARENT_TAB_TEXT to display the current parent tab name.

 

SQL

xxxxxxxxxx

 

1

DECLARE

2

  v_tab_name VARCHAR2(100);

3

BEGIN

4

  v_tab_name := :CURRENT_PARENT_TAB_TEXT;

5

  -- Additional logic here to display or use the parent tab name

6

END;

In this example, the current parent tab name is retrieved and used in the application.

16. DEBUG

16.1 Description

The variable DEBUG indicates whether debugging is enabled (YES) or disabled (NO). This setting is used to control debugging features and output within the application.

16.2 When could the use of this variable be useful?

This variable is useful for conditionally enabling or disabling debugging features or logging within the application. It helps in diagnosing issues and understanding the application's behavior during development or troubleshooting.

16.3 Example Usage

You can use DEBUG to control debugging output in your application.

 

SQL

xxxxxxxxxx

 

1

IF :DEBUG = 'YES' THEN

2

  -- Output debugging information

3

END IF;

In this example, debugging information is output only if debugging is enabled.

17. HOME_LINK

17.1 Description

The variable HOME_LINK represents the home page of the application. This link is used to navigate users back to the application's home page.

17.2 When could the use of this variable be useful?

This variable is useful for generating links or buttons that navigate users back to the application's home page. It helps in providing a consistent and easy way for users to return to the main page.

17.3 Example Usage

You can use HOME_LINK to create a link to the application's home page.

 

HTML/XML

xxxxxxxxxx

 

1

<a href="#HOME_LINK#">Home</a>

In this example, a link to the application's home page is created using the HOME_LINK variable.

18. IMAGE_PREFIX

18.1 Description

The variable IMAGE_PREFIX provides the path where Oracle APEX images, themes, JS, and CSS files are available. This path is used to reference static resources provided by Oracle APEX.

18.2 When could the use of this variable be useful?

This variable is useful for referencing static resources like images, JavaScript, and CSS files that are provided by Oracle APEX. It helps in ensuring that these resources are correctly loaded and displayed in the application.

18.3 Example Usage

You can use IMAGE_PREFIX to reference a JavaScript file in your application.

 

HTML/XML

xxxxxxxxxx

 

1

<script src="#IMAGE_PREFIX#js/my_script.js"></script>

In this example, the JavaScript file path is dynamically generated using the IMAGE_PREFIX variable.

Natürlich, hier sind die erweiterten Beschreibungen für alle Variablen mit mehr Details und Informationen:

19. LOGIN_URL

19.1 Description

The variable LOGIN_URL provides the URL to the login page of the application. This URL is used to direct users to the login interface where they can authenticate themselves.

19.2 When could the use of this variable be useful?

This variable is particularly useful in scenarios where you need to ensure that users are redirected to the correct login page, such as:

• When creating a custom login button or link.
• When implementing session timeout functionality that redirects users to the login page.
• In error handling, to redirect users to the login page if an authentication error occurs.

19.3 Example Usage

You can use LOGIN_URL to create a login link in your application.

 

HTML/XML

xxxxxxxxxx

 

1

<a href="#LOGIN_URL#">Login</a>

In this example, the href attribute dynamically generates the URL to the login page using the LOGIN_URL variable, ensuring that the link always points to the correct login page.

20. LOGOUT_URL

20.1 Description

The variable LOGOUT_URL provides the URL to the logout page of the application. This URL is used to log users out of the application and terminate their session.

20.2 When could the use of this variable be useful?

This variable is useful in scenarios where you need to ensure that users are properly logged out, such as:

• When creating a custom logout button or link.
• When implementing a "logout" feature in a navigation menu.
• In session management, to redirect users to the logout page after a certain period of inactivity.

20.3 Example Usage

You can use LOGOUT_URL to create a logout link in your application.

 

HTML/XML

xxxxxxxxxx

 

1

<a href="#LOGOUT_URL#">Logout</a>

In this example, the href attribute dynamically generates the URL to the logout page using the LOGOUT_URL variable, ensuring that the link always points to the correct logout page.

21. PRINTER_FRIENDLY

21.1 Description

The variable PRINTER_FRIENDLY returns a value indicating whether the page is displayed in a printer-friendly view or not. It is typically used to conditionally format content for printing.

21.2 When could the use of this variable be useful?

This variable is useful in scenarios where you need to optimize the content of a page for printing, such as:

• When hiding or showing specific elements based on whether the page is in printer-friendly mode.
• When applying different styles or layouts for printed content.
• In generating reports that are intended to be printed.

21.3 Example Usage

You can use PRINTER_FRIENDLY to conditionally display content based on whether the page is in printer-friendly mode.

 

HTML/XML

xxxxxxxxxx

 

1

<apex:outputText rendered="#PRINTER_FRIENDLY#">

2

    This content is only visible in printer-friendly mode.

3

</apex:outputText>

In this example, the content is only rendered if the page is in printer-friendly mode, ensuring that it is only visible when the page is printed.

22. REQUEST

22.1 Description

The variable REQUEST holds the value of the request attribute when a button is clicked. It is used to determine which button or action triggered the request.

22.2 When could the use of this variable be useful?

This variable is useful in scenarios where you need to execute specific logic based on the button clicked, such as:

• When handling form submissions with multiple buttons (e.g., Save, Cancel, Delete).
• In conditional processing, to determine the action to be performed based on the button clicked.
• In dynamic actions, to trigger different behaviors based on the request value.

22.3 Example Usage

You can use REQUEST to conditionally execute logic based on the button clicked.

 

SQL

xxxxxxxxxx

 

1

IF :REQUEST = 'SAVE' THEN

2

    -- Execute save logic

3

ELSIF :REQUEST = 'CANCEL' THEN

4

    -- Execute cancel logic

5

END IF;

In this example, different logic is executed based on the value of the REQUEST variable, ensuring that the appropriate action is taken based on the button clicked.

23. SCHEMA_OWNER

23.1 Description

The variable SCHEMA_OWNER represents the schema owner of the APEX application. It is used to reference the schema in SQL queries and PL/SQL code.

23.2 When could the use of this variable be useful?

This variable is useful in scenarios where you need to reference the schema owner in your code, such as:

• When writing SQL queries that need to reference tables or views in the schema.
• In PL/SQL code, to dynamically reference the schema owner.
• In multi-schema environments, to ensure that the correct schema is used.

23.3 Example Usage

You can use SCHEMA_OWNER to reference the schema owner in a SQL query.

 

SQL

xxxxxxxxxx

 

1

SELECT * FROM #SCHEMA_OWNER#.employees;

In this example, the SCHEMA_OWNER variable dynamically references the schema owner in the SQL query, ensuring that the query is executed in the correct schema.

24. SQLERRM

24.1 Description

The variable SQLERRM holds the SQL error message. It is used to capture and display error messages when an exception occurs.

24.2 When could the use of this variable be useful?

This variable is useful in scenarios where you need to handle and display SQL errors, such as:

• In exception handling, to capture and log SQL error messages.
• When debugging, to display detailed error messages to help identify issues.
• In user interfaces, to provide meaningful error messages to users.

24.3 Example Usage

You can use SQLERRM to display an error message when an exception occurs.

 

SQL

xxxxxxxxxx

 

1

EXCEPTION

2

    WHEN OTHERS THEN

3

        htp.p('Error: ' || SQLERRM);

In this example, the SQLERRM variable is used to display the SQL error message, providing detailed information about the error that occurred.

25. SYSDATE_YYYYMMDD

25.1 Description

The variable SYSDATE_YYYYMMDD provides the current date in the format YYYYMMDD from the database server. It should be used instead of multiple calls to SYSDATE() to ensure consistency and performance.

25.2 When could the use of this variable be useful?

This variable is useful in scenarios where you need to consistently use the current date in the format YYYYMMDD, such as:

• When inserting or updating date values in tables.
• In reports and logs, to ensure a consistent date format.
• In date calculations and comparisons.

25.3 Example Usage

You can use SYSDATE_YYYYMMDD to insert the current date into a table.

 

SQL

xxxxxxxxxx

 

1

INSERT INTO logs (log_date) VALUES (#SYSDATE_YYYYMMDD# );

In this example, the SYSDATE_YYYYMMDD variable is used to insert the current date into the logs table, ensuring that the date is formatted correctly and consistently.

26. WORKSPACE_IMAGES

26.1 Description

The variable WORKSPACE_IMAGES provides the path to images, CSS, and JS files that are available for all applications within a workspace. This path is used to reference static resources shared across multiple applications.

26.2 When could the use of this variable be useful?

This variable is useful in scenarios where you need to reference shared static resources, such as:

• When including shared CSS or JavaScript files in multiple applications.
• In theming, to ensure that images and styles are consistently applied across applications.
• In resource management, to centralize the location of static files.

26.3 Example Usage

You can use WORKSPACE_IMAGES to reference a CSS file in your application.

 

xxxxxxxxxx

 

1

<link rel="stylesheet" href="#WORKSPACE_IMAGES# css/styles.css">

In this example, the href attribute dynamically generates the path to the CSS file using the WORKSPACE_IMAGES variable, ensuring that the correct path is used to load the CSS file.

27. APEX$ROW_NUM

27.1 Description

The variable APEX$ROW_NUM represents the currently processed row number of a tabular form. It can be used in validations, processes, and conditions to reference the current row.

27.2 When could the use of this variable be useful?

This variable is useful in scenarios where you need to perform operations or validations on specific rows in a tabular form, such as:

• When validating data in each row of a tabular form.
• In conditional processing, to apply logic to specific rows.
• In dynamic actions, to trigger behaviors based on the row number.

27.3 Example Usage

You can use APEX$ROW_NUM to validate data in the current row of a tabular form.

 

SQL

xxxxxxxxxx

 

1

IF :APEX$ROW_NUM = 1 THEN

2

    -- Perform validation for the first row

3

END IF;

In this example, a validation is performed for the first row of the tabular form using the APEX$ROW_NUM variable, ensuring that the logic is applied to the correct row.

28. APEX$ROW_SELECTOR

28.1 Description

The variable APEX$ROW_SELECTOR references the row selection checkbox of the currently processed row in a tabular form. It returns x if the checkbox of the current row is checked, otherwise NULL.

28.2 When could the use of this variable be useful?

This variable is useful in scenarios where you need to determine whether a specific row in a tabular form is selected, such as:

• When performing actions on selected rows.
• In conditional processing, to apply logic based on the selection status of the row.
• In dynamic actions, to trigger behaviors based on whether the row is selected.

28.3 Example Usage

You can use APEX$ROW_SELECTOR to perform an action only if the current row is selected.

 

SQL

xxxxxxxxxx

 

1

IF :APEX$ROW_SELECTOR = 'x' THEN

2

    -- Perform action for the selected row

3

END IF;

In this example, an action is performed only if the current row is selected using the APEX$ROW_SELECTOR variable, ensuring that the logic is applied to the correct row.

29. APEX$ROW_STATUS

29.1 Description

The variable APEX$ROW_STATUS represents the status of the currently processed row. It returns C if the current row is newly created, U if updated, or D if the row is to be deleted.

29.2 When could the use of this variable be useful?

This variable is useful in scenarios where you need to perform different operations based on the status of a row in a tabular form, such as:

• When inserting, updating, or deleting rows in a database.
• In conditional processing, to apply logic based on the row status.
• In dynamic actions, to trigger behaviors based on whether the row is new, updated, or marked for deletion.

29.3 Example Usage

You can use APEX$ROW_STATUS to execute different logic based on the row status.

 

SQL

xxxxxxxxxx

 

1

IF :APEX$ROW_STATUS = 'C' THEN

2

    -- Perform logic for newly created row

3

ELSIF :APEX$ROW_STATUS = 'U' THEN

4

    -- Perform logic for updated row

5

ELSIF :APEX$ROW_STATUS = 'D' THEN

6

    -- Perform logic for row to be deleted

7

END IF;

In this example, different logic is executed based on the status of the row using the APEX$ROW_STATUS variable, ensuring that the appropriate action is taken based on the row's status.

Conclusion

Oracle APEX variables are indispensable tools that you will frequently encounter and utilize in your development journey. By mastering these variables, you can significantly enhance the flexibility, functionality, and user experience of your applications.

Remember, this guide serves as a comprehensive reference to help you understand and effectively use these variables. Bookmark this page and refer back to it whenever you need a quick refresher or example usage.

Thank you for reading, and happy coding with Oracle APEX! Your journey to creating powerful and scalable web applications has just become a lot more manageable.

 {fullWidth}