--- title: "Process Model Maintenance - Field Definitions" canonical: "https://kb.myframeworks.com.au/space/FRAM/28402124/Process%20Model%20Maintenance%20-%20Field%20Definitions" format: markdown --- The **Process Model Maintenance** screen allows you to create, edit and delete process models in Frameworks Production Scheduling. A process model is a related set of tasks grouped together to drive a manufacturing or assembly workflow, and once defined can be linked to a primary product so that the associated tasks are automatically generated on a Sales Order or Job Order. > ⚠️ **Important:** Process models linked to Assembly Kit products or Special Assembly Products in the Custom Manufacturing workflow must contain only Assembly-type tasks. Mixing Assembly and manufacturing task types (Detailing, Estimating, Manufacturing) is blocked on save. ## Screen Access From the **Frameworks Menu**, navigate to **Production Scheduling > Maintenance > Process Model Maintenance**. ## Screen Structure ![image-20260610-055837.png](media://c9f9ca69-dff9-4f2c-85bc-7357afda7b1f) The **Process Model Maintenance** screen is organised into four main sections: 1. **Search and Results** - Locate and select an existing process model. 2. **Model Details** - View and edit the header information for the selected process model. 3. **Tasks Grid** - Add, remove and edit the task lines that make up the process model. 4. **Command Buttons** - Create, save, cancel, delete or close the process model record. --- ## Search and Results ![image-20260610-055958.png](media://0bcc06ec-c5a7-4cd4-b6f3-23a0813eb118) The **Search and Results** section displays the list of existing process models and allows you to search for a specific model by ID. Click a **Model ID** hyperlink in the results grid to load the model into the **Model Details** and **Tasks Grid** sections. ### Model ID The **Model ID** search field allows you to filter the results grid to a specific process model. Enter a known model ID and click **Find** to return only that model. Leave the **Model ID** field blank and click **Find** to return all available process models. **Format:** Numeric | **Required:** No | **Editable:** Yes ### Find The **Find** button executes the search using the value in the **Model ID** field. If the **Model ID** field is blank, all process models are returned. **Action:** Click **Find** to populate the results grid with matching process models. ### ID (Results Grid) The **ID** column in the results grid displays the unique model ID for each process model. The **ID** value is automatically generated when a new process model is created. **Action:** Click the **ID** hyperlink to load the selected process model into the **Model Details** and **Tasks Grid** sections. **Format:** Numeric (hyperlink) | **Editable:** No (system-generated) ### Description (Results Grid) The **Description** column in the results grid displays the descriptive name entered for each process model. The **Description** value is used to identify the purpose of the process model in lookups across Frameworks. **Format:** Text | **Editable:** No (display only — edit via the **Description** field in the **Model Details** section) ### Page Navigation The page navigation controls at the bottom of the results grid allow you to move through pages of results and set the number of items shown per page. Use the **items per page** drop-down menu to change how many process models are displayed, and the navigation arrows to move between pages. --- ## Model Details ![image-20260610-060102.png](media://3b1737e4-b73b-486e-8ef3-3715098909f3) The **Model Details** section displays the header information for the selected process model. The **Model Details** section is where you enter the unique identifier, descriptive name and any general notes for the process model. ### ID The **ID** field displays the unique identifier for the process model. The **ID** value is automatically generated by Frameworks when **New** is clicked and cannot be changed. **Format:** Numeric | **Editable:** No (system-generated) ### Description The **Description** field identifies the purpose of the process model. Enter a clear descriptive name that explains what the process model is used for (for example, "Truss to Manufacture", "Door Manufacture", "Window Installation"). The **Description** value is shown in the results grid on the **Process Model Maintenance** screen and in lookups elsewhere in Frameworks, including when linking a process model to a primary product in **Product Maintenance**. **Format:** Text | **Required:** Yes | **Editable:** Yes ### Notes The **Notes** field allows you to record additional context or instructions about the process model. The **Notes** field is free text and is intended for internal documentation, such as describing when the model should be used or any special handling that applies. **Format:** Text (free text) | **Required:** No | **Editable:** Yes --- ## Tasks Grid ![image-20260610-060218.png](media://ed1ab110-0a67-410e-b58a-83ac8adada7d) The **Tasks Grid** section displays the task lines that make up the process model. Each row represents a single task that will be created on a Sales Order or Job Order when the process model is applied. Tasks are added from those defined in **Standard Task Maintenance**. > ✅ Refer to [Standard Task Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28388356) for information on defining the tasks available for use in process models. ### Add The **Add** button creates a new blank task line in the **Tasks Grid**. A new line is added below any existing tasks and is ready for you to enter the task details. **Action:** Click **Add** to insert a new task line. ### Remove The **Remove** button deletes the selected task line from the **Tasks Grid**. Select the task line by clicking on it, then click **Remove** to delete the line from the process model. **Action:** Click **Remove** to delete the selected task line from the process model. ### Line The **Line** column displays the sequential line number for each task in the process model. The **Line** value is automatically assigned in the order tasks are added. **Format:** Numeric | **Editable:** No (system-generated) ### Parent The **Parent** field identifies the parent task for a child task. If the task is a child of another task in the same process model, enter the **Task ID** of the parent task. Enter **0** if the task has no parent. The **Parent** field works with the **Auto Create Children?** checkbox to control whether child tasks are automatically generated on a Job Order when specific criteria are met against the parent task. **Format:** Numeric | **Required:** Yes | **Default:** 0 | **Editable:** Yes | **Related fields:** The **Auto Create Children?** checkbox on the parent task controls automatic creation of child tasks. ### Task ID The **Task ID** field displays the unique identifier for the task line within the process model. The **Task ID** value is automatically generated when the task line is added. **Format:** Numeric | **Editable:** No (system-generated) ### Code The **Code** field identifies the standard task being added to the process model. Enter a task code directly or click the search icon to open the Code Lookup finder and select from the available tasks. Available task codes are those defined in **Standard Task Maintenance**, including the **Production** and **Assembly** task types used in the Production Scheduling and Custom Manufacturing workflows. **Action:** Click the search icon to open the Code Lookup finder window. **Format:** Text (alphanumeric, lookup) | **Required:** Yes | **Editable:** Yes | **Related fields:** The **Description**, **Quantity** and **UOM** fields populate automatically based on the **Code** selected. ### Description The **Description** column displays the descriptive name of the task. The **Description** value is inherited from the task definition in **Standard Task Maintenance** and is populated automatically when the **Code** is selected. **Format:** Text | **Editable:** No (inherited from **Standard Task Maintenance**) ### Assignee The **Assignee** field allows you to assign a specific user to the task. The **Assignee** field is optional and is used when the task is always completed by the same person. Leave the **Assignee** field blank to assign the task later in **Process Management**. To assign a user, tab across to the **Assignee** field and enter the username. **Format:** Text (username, no validation) | **Required:** No | **Editable:** Yes ### Quantity The **Quantity** field sets the quantity for the task line. The **Quantity** field defaults to the value defined for the task in **Standard Task Maintenance** when the **Code** is selected, and can be overridden directly on the task line. > ⚠️ **Important:** For tasks with the **Assembly** task type, the **Quantity** is restricted to **1**. This restriction is enforced when the process model is used in the Custom Manufacturing workflow. **Format:** Numeric | **Required:** Yes | **Default:** Value from **Standard Task Maintenance** | **Editable:** Yes | **Related fields:** The **Code** field determines the default value populated into the **Quantity** field. ### UOM The **UOM** column displays the unit of measure for the task. The **UOM** value is inherited from the task definition in **Standard Task Maintenance** and is populated automatically when the **Code** is selected. **Format:** Text (UOM code) | **Editable:** No (inherited from **Standard Task Maintenance**) ### Days Due The **Days Due** field sets the number of days the task is due before or after the milestone selected in the **Milestone** field. The **Days Due** field works together with the **Relative To** and **Milestone** fields to determine the due date of the task on a Job Order. For example, a value of **7** in **Days Due**, with **Before** in **Relative To** and **Delivery Date** in **Milestone** schedules the task to be due seven days before the delivery date. **Format:** Numeric | **Required:** Yes | **Default:** 0 | **Editable:** Yes | **Related fields:** The **Relative To** and **Milestone** fields determine how the **Days Due** value is applied. ### Relative To The **Relative To** drop-down menu controls whether the task is due **Before** or **After** the milestone selected in the **Milestone** field. The **Relative To** field pairs with **Days Due** and **Milestone** to determine when the task is due on a Job Order. **Format:** Drop-down menu (Before / After) | **Required:** Yes | **Editable:** Yes | **Related fields:** The **Days Due** and **Milestone** fields work with the **Relative To** value to set the task due date. ### Milestone The **Milestone** drop-down menu selects the key event used to calculate the task due date. The **Milestone** field is used together with the **Days Due** and **Relative To** fields to determine when the task is due on a Job Order. Available **Milestone** options include: - **Delivery Date** - **Date Ordered** - **Original Delivery Date** - **Date Required** - **Today** **Format:** Drop-down menu | **Required:** Yes | **Editable:** Yes | **Related fields:** The **Days Due** and **Relative To** fields work with the **Milestone** value to set the task due date. ### Auto Create Children? The **Auto Create Children?** checkbox controls whether child tasks of the parent task are automatically generated on a Job Order when specific statuses or criteria are met. Enable the **Auto Create Children?** checkbox on the parent task to have its children created automatically as the Job Order progresses through Production Scheduling. **Format:** Checkbox | **Default:** Disabled | **Editable:** Yes | **Related fields:** The **Parent** field on child tasks links them to the parent task that controls automatic creation. ### Notes The **Notes** column allows you to record additional context or instructions specific to the task line. Click the **Notes** icon at the end of the task line to open the notes editor and enter free text. The **Notes** value is shown alongside the task in **Process Management**. **Action:** Click the **Notes** icon to open the notes editor. **Format:** Text (free text, opened via icon) | **Required:** No | **Editable:** Yes --- ## Command Buttons The command buttons section provides the primary actions for creating, saving and managing process model records. Most buttons display a keyboard shortcut in parentheses (for example, **New (I)**). ### New The **New** button creates a new process model. Clicking **New** generates a unique **ID** value, clears the **Model Details** section and adds a default blank task line in the **Tasks Grid**. **Action:** Click **New** to begin creating a new process model. ### Edit The **Edit** button enables editing on the currently loaded process model. The **Edit** button must be clicked before changes can be made to an existing process model. **Action:** Click **Edit** to enable changes to the loaded process model. ### Save The **Save** button commits any changes made to the process model. The **Save** button validates the process model before saving and is only enabled when there are unsaved changes. **Important:** When a process model is linked to an Assembly Kit product or a Special Assembly Product, Frameworks validates that the model contains only Assembly-type tasks. If the model contains manufacturing tasks (Detailing, Estimating, Manufacturing) alongside Assembly tasks, the save fails with the error *"Manufacturing tasks only — no Assembly task allowed."* **Action:** Click **Save** to commit changes to the process model. ### Cancel The **Cancel** button discards any unsaved changes and reverts the process model to its last saved state. **Action:** Click **Cancel** to discard changes without saving. ### Delete The **Delete** button removes the currently loaded process model from Frameworks. A confirmation prompt is displayed before the model is deleted. **Important:** Deleting a process model removes the model and all of its task lines. Process models that are linked to a primary product should be unlinked from the product before deletion to avoid breaking the link. **Action:** Click **Delete** to remove the loaded process model. Click **Yes** at the confirmation prompt to confirm. ### Close The **Close** button closes the **Process Model Maintenance** screen and returns you to the **Frameworks Menu**. **Action:** Click **Close** to exit the screen. --- > ✅ ## Related Information > ✅ > ✅ - Create a Process Model `[link to be added once published]` > ✅ - Maintain a Process Model `[link to be added once published]` > ✅ - Delete a Process Model `[link to be added once published]` > ✅ - Add a Process Model to a Primary Product `[link to be added once published]` > ✅ - [Standard Task Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28388356) > ✅ - [Process Management](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28410574) > ✅ - [Custom Manufacturing - Implementation Guide](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/737837057) --- ## Additional Information ### Task Type Validation When a process model is intended for use in the Custom Manufacturing workflow (linked to an Assembly Kit product or Special Assembly Product), the model must contain only Assembly-type tasks. Frameworks blocks the save and displays the validation error *"Manufacturing tasks only — no Assembly task allowed."* if the model mixes Assembly tasks with manufacturing task types (Detailing, Estimating, Manufacturing).