--- title: "Customer Specific Requirement Configuration via Form Builder" slug: "customer-specific-requirement-configuration-via-form-builder" updated: 2026-05-29T06:26:15Z published: 2026-05-29T06:26:15Z canonical: "zenoplesupport.aqore.com/customer-specific-requirement-configuration-via-form-builder" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://zenoplesupport.aqore.com/llms.txt > Use this file to discover all available pages before exploring further. # Customer Specific Requirement Configuration via Form Builder **Overview** This feature enables Office Staff users to configure Assignment and Job Candidate requirements at the customer level using the Form Builder. It ensures that selecting a customer automatically applies their predefined requirement configuration, promoting consistency and efficiency. **Functionality** - This feature is available within the **Form Builder** in Zenople by Aqore and applies to **Job Candidate Management (JCM)** and **Assignment Management (AMS)** processes, with integration into **NHO** and **EIS** where applicable. - Office Staff can define and save requirement configurations specifically for one or more customers. The **Customer field is presented as a multi-select dropdown**, allowing configurations to apply to multiple customers as needed. - The Form Builder supports saving these configurations at the **customer level**. - When a customer is selected in the Form Builder: - The system copies the customer’s saved requirement setup into the **Customer Requirement** record. - The copied requirements are editable after being applied, and any edits do not affect the original customer-level configuration. - If no customer-specific configuration exists: - The system follows the default or global requirement behavior. - When option property **ShowJcmAmsTaskInNhoEis**is set to True: - - Job Candidate and Assignment tasks can be assigned to a person within **NHO** and **EIS** for customer specific Task. - Customer Requirement validation is triggered to check for incomplete customer-specific tasks related to the job candidate during assignment. - Validation occurs even if the person is not currently marked as a Job Candidate.