Custom Actions - Use Cases

Custom Actions allow you to create shortcuts for frequent operations. Instead of navigating through the full form every time, users can quickly act from the list view or record details page, with only the required fields presented.

Let’s walk through two practical use cases in the context of an Employee Onboarding custom module.

Use Case 1: Add Immediate Hire at the Base Site

Let's say a company suddenly requires additional employees to join immediately at their base site due to a new project, critical business need, or urgent replacement. The HR manager must quickly process the onboarding for these candidates.

To simplify the process for HR, a custom action called Add High Priority Hire can be defined, enabling them to create records by filling in only essential fields (such as Name, Contact, Department, and Date of Joining) while other details (such as Site and Priority) are automatically populated with default values.

Admin Configuration

Field

Value

Display Name

Add High Priority Hire

Operation

Add

Actions

Field Update

 

Now, let’s apply the following to our example:

Click Save and publish the configuration.  

User Experience

After the configuration is published, the HR can:

The record will be created with both the user-provided information and default values. This ensures that urgent hires are logged quickly without unnecessary steps.

Use Case 2: Bulk Update Joining Dates

Consider a scenario where the onboarding schedule changes and the HR manager needs to update the date of joining for multiple hires at once.

To simplify the process for HR, a custom action can be created that allows them to update only the joining date without opening the entire form.

Admin Configuration

Field

Value

Display Name

Update DOJ

Operation

Edit

Actions

Field Update

 

User Experience

After the configuration is published, the HR can:

Custom Subentities - Use Case

Subentities are additional entities that are directly linked to a custom module record (parent entity) and technicians can store additional information to manage the record throughout its life cycle.

Let’s walk through a sample subentity in the context of an Employee Onboarding custom module.

Parent Module: Employee Onboarding

Custom Subentity: Equipment Assignment for tracking all the equipment assigned to a new employee during onboarding.

Admin Configuration

After you design, publish the subentity.

Now, add the subentity to the parent module and publish it. 

User Experience

After an HR creates a new Employee Onboarding record, they can add multiple Equipment Assignment entries to track which devices or items are given to the employee and their current status.