Blocworx Documentation
  • Welcome to Blocworx
  • The structure of Blocworx
    • What is a project?
  • Getting Started
  • How To's
    • How To's
      • Get Started: Build a Simple Module
      • Build a simple invoicing system
  • Page
    • Page Overview
      • Page Sections
      • Modules in Pages
      • Sub Pages
      • URL Links
    • Edit a Page
    • Manage Pages
  • Module
    • Module Overview
      • Module Sections
      • Blocs in Modules
      • Automated Reports
    • Module Editor
      • Add, remove and move Sections and Blocs
      • Edit Module Location & Icon
      • Edit Module Details
      • Import from another Module
      • Delete a Module
      • Make this module available to child instances
    • Manage Modules
  • Bloc
    • Bloc Overview
    • Bloc Front End Overview
      • Data Display
      • Advanced Reports
    • Bloc Editor Overview
    • Pdf & Doc File Template Builder
    • The Blocworx Process Flow
    • Edit Templates
  • Bloc Editor
    • Bloc Form Builder Preview
    • Fields, Tools and Charts
      • Standard Input Fields
        • QR Code
        • Text
        • Large Text Field
        • Checkbox
        • Multi Button
        • Dropdown from List
        • Date/Time Selector
        • Bluetooth (Beta)
        • Button
      • File & Image Fields
        • File Field
        • Multi File Field
        • Image URL Field
      • Linked Data Selection Fields
        • Dropdown from Bloc
        • Autocomplete
        • Radio Buttons From Bloc
        • Checkboxes From Bloc
        • Link Data Field
      • Content Editing Components
        • HTML Field
        • Separator Field
        • Content Editor For User (WYSIWYG)
        • Content Editor (WYSIWYG)
      • User Based Components
        • Create User Pop Up
        • Logged in Users Information
        • User Select Field
        • Signature & Authentication
      • Dynamic Output & Variable Components
        • Time/Date Difference
        • Auto Generate Field
        • Plain Data Field
        • Maths Field
        • Field Merge Builder
        • Label Field
        • Barcode Generator
      • Third Party Integration Components
        • Blocworx Gateway
        • Bartender Integration
        • File Builder
        • Mindee API
      • Charts, Results & Data Feeds
        • Local Data Doughnut Chart
        • Advanced Chart Set 1
        • Results Box
      • Sub Blocs, Tools & Components
        • Submit Button
        • Sub Bloc
        • Cross-Bloc Data Manipulator
        • Bloc List
        • Mail Alert
        • Calendar & Resource Planning
    • Field Create, Edit, Parameters, Rules and Actions
      • Creating a Field
      • Editing a Field
      • Field Parameters
        • Choose hidden options for this field
        • Mobile Configurations
        • Rule and Actions Based Parameters
        • Main Field Parameters
        • Conditional Value
        • Set Character View Limit
        • Conditional Visibility
        • Dynamic Data Update (Update Value Based On Another Date Field)
        • Field Names in Different Languages
        • Manage Field Actions
        • Load Data from Another Bloc
      • Field Rules and Actions
        • Can not be empty
        • Must Be Equal To
        • Cannot Be Equal To
        • Must be Between Two Values
        • Must be at least X number of characters
        • Must be exactly X number of characters
        • Item must have been entered elsewhere
        • Item must not have been entered elsewhere
        • A specific value is required elsewhere
        • A specific value cannot be present elsewhere
        • Populate another local field with data from elsewhere
        • Populate another local field with total from elsewhere
        • Max Allowed Duplicates
        • Can only be numbers/integers
        • Keep Data for Next Entry
        • Must be Certain Format
        • Cannot be Equal Another Local Field
        • Must be equal to another local field
        • Populate another local field with part of this field
        • Populate local field with data from another local field
        • Must have matching equivalent data in another form
    • Bloc Settings
      • Main Bloc Settings
      • Functional Behaviour Settings
      • Bloc Layout and Visibility Settings
      • Data Display Settings
      • User Restricted Data Settings
      • Manage and Build Templates
      • Bloc, User and Role Access
      • List of available Field Slugs
      • Manage Bloc Scheduler
  • Manage Data
    • Manage Data Overview
    • Raw Data and Counting Reports
    • Look Up/Edit Data
    • Find and Replace Data
  • Administration
    • Admin & Development Overview
    • Manage Users
      • Profile Filter
    • Roles & Permissions
      • Roles
      • Permissions
    • Manage Mail Alerts
  • App Settings
    • Sign In With Google
    • Timeout Setting
  • No Code Development
    • Manage Blocworx Instances
      • Parent and Child Instances
    • Edit Theme
    • Manage Modules
    • Manage Pages
    • Extra and Beta Features
Powered by GitBook
On this page

Was this helpful?

  1. Bloc Editor
  2. Fields, Tools and Charts
  3. Sub Blocs, Tools & Components

Sub Bloc

PreviousSubmit ButtonNextCross-Bloc Data Manipulator

Last updated 1 month ago

Was this helpful?

A Sub Bloc is a way of embedding any other bloc inside the existing bloc. Both the parent (host) and child blocs can have data connected to each other. This allows for the creation of tools like sub lists within a main form, or perhaps access to secondary data with the ability to update it while still in the first Bloc. The Sub Bloc itself is an existing bloc in your system which is chosen when creating the field.

Note: The passing of data from the parent bloc to a sub bloc (or vice versa) occurs when the rules/actions occur for the field you are passing the data from.

Hint: The main principle behind a Sub bloc is for having multiple records for a single "parent" record. For example, manging invoices, you could create an invoice and add multiple line items in the sub bloc. To use this effectively it is adviseable to do two things in the Sub Bloc: 1. For the linked field in the sub bloc, add the field parameter to make sure only the data related to the value of that field appears.

2. Apply our rule in the sub bloc linked field. This means as you keep submitting in the sub bloc you will have to re-enter the value in that field.

Initial Parameters

Parameter

Description

Type Module Name (optional)

This can be used for accessing Blocs outside of the module you are currently in. You may leave blank if you want to access the the blocs in the current module.

Select Bloc

Use this to choose the bloc you wish to embed

Select what will trigger the bloc to open

The Sub Bloc can be opened via a button, white heading text or simply always be open by default. This parameter allows you to decide this.

Select How the Bloc will be displayed on the screen.

The Sub Bloc can either be a smaller pop up, a full screen pop up or simply be embedded right into the parent bloc/form.

Linked Data Options (Sending Parent Field Data to Child)

Used to connect fields, where you match the parent field with the child field. Simply Select a parent field (a field located on your current bloc) and a child field (a field from the other bloc) and click "Add". This is for sending data from the parent bloc (host) to the child bloc (guest).

Linked Data Options (Sending Child Field Data to Parent)

This is the same as the above except in reverse. When values are changed in the child bloc they can be sent to the parent (useful for values like total counts or mathematical calculations).

Compact View

With this turned on the display of data and the form in the Sub Bloc will be smaller, tightened and space reduced and along with font sizes reduced. This is useful not only for allow more space on the page but also for distinguishing between the parent and child bloc on the form.

Hide the Close Button

This removes the X/Close Button from the bloc, meaning its impossible to close the bloc (useful in combination with more options below where you may want to guide someone through a series of sub blocs without letting them close one).

On Submit, Close the bloc

This is a UX feature in situations where you want the use to just add one value in the sub bloc and not get them to have to X out of it when they are done.

On submit, close the sub bloc and submit the parent form too.

This is a more advanced feature which is also UX based. You may want the user to add a value to the child bloc, but not have to go back to the parent bloc and do the same.

On submit, close the sub bloc and open another one.

Useful for forcing someone through a process or a series of pop ups. The Sub Bloc they would choose would be another field that is a sub bloc on the same parent bloc.

Show a button that will close the sub bloc and open another one.

This option will show a button in the Sub Bloc bloc that allows them to click and move onto the next chosen Sub Bloc. This is similar to the above option but avoids the requirement for the person to have to submit data to go to the next bloc.

For Linking Data: When the data updates on the parent bloc, the child data on the child bloc for that field automatically updates as well.

Don't forget, you can also on the child bloc so that the only data loaded in the child bloc is data associated with the value of a certain field, in this case you could choose the child blocs linked field.

set filtering options
Keep Data for Next Entry
Data Filtering Field
A very basic example of a Sub Bloc where another bloc called "Sub Bloc" is included in the bloc called "Parent Bloc". In this particular example the "Incoming Shipment Number" field has been linked with the "Shipment Number" field. This allows you to add multiple line items for every Incoming Shipment Number.