Documentation

Custom HTML Reference

In this article

This article contains all the information you need to know about each setting within a Custom HTML Page.

Jim Dekker

Published: 16-10-2019

Last updated: 16-10-2019

When creating a custom HTML page, there are a lot of things to keep track of! In this article, we’ll show you all the different settings a custom HTML page has to offer.


Close: Closes the current page.
Changes: Displays the history of changes made to the current page.
Save: Saves the current page and the changes you have made to it.

Page

Enabled: The enabled function allows you to enable or disable the usage of a page.
Redirect url: The redirect url redirects the page to the set url, you can leave this empty if you do not want to redirect your page.
URL: The URL is the path used to get to that certain pagePath: The path is the name used in the URL to direct the browser to your webpage.
Description: The description can be filled in for information about the webpage.
Request method: The chosen method is used for handling requests between your web browser and the Betty Blocks web server. More information can be found here: What are HTTP methods on web pages?
Content type: The content type is the way the page displays its data.
Enable page caching: The enable page caching function lets you define whether the page can be cached locally on the visitors' device.
Enable debug logging: If you activate debug logging on your page, a log record will be created every time the page is visited.
Enable CSRF (Cross Site Forgery Protection): Is protection from Cross Site Forgeries. More information can be found here: Cross-Site Request Forgery - CSRF
Authentication profile: With this option, you can select which authentication profile you want to use on all the pages inside the group. More information can be found here: What are Authentication Profiles?

Variables

Variables: Add variables to the page, which can be used in the action and template. Mostly used for dynamic values, like calculations, objects or collections. More information can be found here: What are variables?
Input variables: Add input variables to the page, which can be used in the action and template. Requires input by the user or application, for example through the url. More information can be found here: What are variables?

Request variables

Request variables: We've added request variables to the web module in order to let you use the available variables of the request of a page. More information can be found here: What are Request variables?
Template: Opens a page with information about the template you are currently using.
>_ Action(new): Opens a page that lets you create a new action for your current page.More information can be found here: What are actions?
Delete: Removes the current page and all of its components.
Cancel: Cancels the edit process of the current page.

Page changes overview


Close: Closes the current page you are on, this is the current page display, to close the display click on the [arrow] button again.
Changes: Closes the change display.
When: Displays when a change has been made.
Merged at: Displays when a merge took place.
User: Displays who made the change.
Action: Displays the kind of change that has been made.
Type: Displays what type of change has been made.
Object: Displays what has been changed.

Template info


Close: Closes the Template info page.
Edit: Opens Edit mode for the current template.
Kind: Shows the template type.
Layout: Shows the chosen layout for your template.

Template Edit page

Close: Closes the current page.
Page changes: Displays the history of changes made to the current page.
Save: Saves the changes made to the current page.


Template

Kind: Displays what kind of template you're working with.
HTML: Contains the HTML code that shapes your template.
Preview: Opens a small window with a preview of the current page.


Fullscreen: Displays your HTML window in full screen.
Layout: Gives you the option to choose between the different layouts available in your application.

Dependent items

Dependencies: are combinations of different functionalities and parts of your application the current group is dependent on. More information can be found here: What are Dependencies?
Delete: Deletes the current template for your page, this doesn't delete the page itself.
History: When clicked, the history button opens a small window that displays when and by who the last change was made. Scroll through all previous versions to restore to an earlier stage.


Cancel: Cancels the current process, also removes all the unsaved changes that were made.

Adding an action


Enabled: Turn this setting on to enable the action.
Help Text: Gives an additional option over the description of an action to say something or leave a note about the action.
Confirmation message: An action can have serious consequences, so you may want to reassure the user if they really meant to start the action. With the Confirmation message, you can set a custom message which is shown in a popup when the user initiates the action. They'll have to confirm this by clicking `Yes` or else the action won't start.
Debug action and events: Building an action and not sure why it's failing? This setting will be your best friend when developing. By turning this checkbox on, you can see the entire flow of your action from start to end in the logs. Go to 

/#newlogs:f=all  

(or click on the Logs button in the Builder bar) in your app and you'll see which action was executed at what time and who did it. Each step gets a timestamp so you'll see exactly how the action performs. You can also see what variables are available and what values they hold.
Log execution of action: Similar to Debug action and events but only logs the initiation of the action. This barely affects the performance, so feel free to use this setting if you see use to it.

Callback action

Enable Callback action: Check the Enable callback action checkbox and you'll be given the option to select an existing action or stick to `- New -` and the platform will create a new one for you. This action is executed after the current action is finished.

In this article