--- title: "Order Confirmation Automated Notifications" canonical: "https://kb.myframeworks.com.au/space/FRAM/28383310/Order%20Confirmation%20Automated%20Notifications" format: markdown --- Order Confirmation Automated Notifications allow Frameworks to send notifications to customers and internal users when a sales order or quote is confirmed. Notifications can be sent by email or SMS to the customer, and as an in-application Frameworks Notification to a sales rep or user. Automated notifications reduce the need for manual follow up after an order is confirmed and give customers immediate confirmation that their order is being processed. The order confirmation functionality is driven by the **FWConfirm** system flag. When **FWConfirm** is enabled, an **Is Confirmed** checkbox appears in the header of every sales order and quote. Notifications are triggered when a user confirms the order through the **Actions** menu, at which point Frameworks evaluates the customer attributes and event subscriptions to determine which notifications to send. Implementing order confirmation notifications requires system-level configuration before customer-level attributes can be assigned. The **FWConfirm** system flag must be enabled to expose the confirmation workflow, mandatory validation must be configured for customer contact details, event subscriptions must be enabled for each notification channel, and the applicable attributes must be assigned to each customer who is to receive notifications. > If you would like assistance implementing order confirmation notifications, contact [DMSi Support](https://kb.myframeworks.com.au/page/support). ## Implementation Sequence This guide walks you through the complete implementation in the correct order: 1. [Enable the FWConfirm System Flag](#Enable-the-FWConfirm-System-Flag) 2. [Configure the Default Order Complete Branch Flag](#Configure-the-Default-Order-Complete-Branch-Flag) 3. [Configure Sales Order Confirmation Email Notifications to Customers](#Configure-Sales-Order-Confirmation-Email-Notifications-to-Customers) 4. [Configure Sales Order Confirmation SMS Notifications to Customers](#Configure-Sales-Order-Confirmation-SMS-Notifications-to-Customers) 5. [Configure Frameworks Notifications to Sales Reps and Users](#Configure-Frameworks-Notifications-to-Sales-Reps-and-Users) 6. [Assign Notification Attributes to Customers](#Assign-Notification-Attributes-to-Customers) --- ## Enable the FWConfirm System Flag The **FWConfirm** system flag enables the order confirmation functionality in sales orders and quotes. This flag must be configured first because it exposes the **Is Confirmed** checkbox and the **Confirm Order** and **Confirm Quote** actions that trigger the notification workflow. ### Configuration Steps 1. Click the **Frameworks Menu** and navigate to **System Administration > System Setup > Configuration > System Settings - Flags**. 2. Locate the **FWConfirm** flag. 3. Enable the **FWConfirm** flag. 4. Click **Save** to apply the change. ### Result When **FWConfirm** is enabled, an **Is Confirmed** checkbox appears in the header of every sales order and quote. The **Confirm Order** action becomes available in the **Actions** menu for sales orders, and the **Confirm Quote** action becomes available for quotes. Confirming an order or quote triggers any subscribed notification events. > ⚠️ ### Important Notes > ⚠️ > ⚠️ - When **FWConfirm** is disabled, the print order options are not available from the **Actions** menu for sales orders, and the **Accept Quote** and print quote options are not available for quotes, until the user confirms the order or quote. > ⚠️ - When **FWConfirm** is enabled and the **Is Confirmed** checkbox is already ticked (for example, because the branch flag **Default Order Complete** is enabled), no notifications are sent because no confirmation action is required. --- ## Configure the Default Order Complete Branch Flag The **Default Order Complete** branch flag controls the default state of the **Is Confirmed** checkbox on new sales orders and quotes. This flag must be configured after **FWConfirm** is enabled because it determines whether users are required to confirm each order manually or whether orders are pre-confirmed on creation. ### Configuration Steps 1. Click the **Frameworks Menu** and navigate to **System Administration > System Setup > Company & Branch > Branch Maintenance**. 2. Search for and select the branch requiring configuration. 3. Locate the **Default Order Complete** flag. 4. Set the **Default Order Complete** flag. 1. Disable to require users to confirm each sales order and quote manually. This is the required setting for automated notifications to be triggered. 2. Enable to pre-confirm all sales orders and quotes on creation. No confirmation action is required and no notifications will be sent. 5. Click **Save** to apply the change. 6. Repeat steps 2-5 for each branch requiring configuration. ### Result When **Default Order Complete** is disabled, the **Is Confirmed** checkbox is not ticked on new sales orders and quotes. Users must confirm each order or quote through the **Actions** menu, which triggers the notification workflow. When **Default Order Complete** is enabled, the **Is Confirmed** checkbox is ticked automatically and the confirmation action is bypassed, which prevents notifications from being sent. > ✅ Refer to [Branch Maintenance - Field Definitions](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28390994) for detailed information on the **Default Order Complete** flag. > ⚠️ ### Important Notes > ⚠️ > ⚠️ - Disable **Default Order Complete** on all branches where automated order confirmation notifications are required. Notifications rely on the **Confirm Order** or **Confirm Quote** action being performed manually. --- ## Configure Sales Order Confirmation Email Notifications to Customers Email notifications send an automated email to the customer when their sales order is confirmed. Email notifications are configured on the **Order Confirmation** event template and require the **Generic-Email** validation code to be set as mandatory so that a valid contact email is captured for every customer. ### Configuration Steps 1. Click the **Frameworks Menu** and navigate to **System Administration > System Setup > Configuration > Additional Validations**. 2. Locate the **Generic-Email** code. 3. Enable the **Mandatory** checkbox for the **Generic-Email** code. 4. Click **Save** to apply the change. 5. Navigate to **System Administration > Event Notifications > Setup & Administration > Event Definition Maintenance** and open the **Order Confirmation** event template. 6. Enable the **Subscribed** checkbox beside the **Event ID** field. 7. Enable the **Subscribed** checkbox beside the **Email** action. 8. In the **Condition** field, enter: `customer:getAttributeValue("Email-OrderConfirmation") = True` 9. In the **To** field, enter: `{order:contactEmail}` 10. In the **Subject** and **Body** fields, enter the message to send to the customer. For example: `Hi, Order {order:numTran} has been confirmed. Thanks.` 11. Click **Save** to apply the configuration. ### Result The **Order Confirmation** event template is subscribed to send an email to the customer whenever a sales order is confirmed and the customer has the **Email-OrderConfirmation** attribute set to true. The email uses the contact email from the sales order and applies the configured subject and body text. > ⚠️ ### Important Notes > ⚠️ > ⚠️ - The contact email is taken from the **Contact Email** field on the sales order. If the sales order does not have a **Contact Email** value, no email is sent. The **Contact Email** defaults from the **E-Address** field on the **General** tab of the customer record and can be overridden on the sales order. > ⚠️ - The **Email-OrderConfirmation** attribute must be assigned to each customer who is to receive email notifications. Attribute assignment is covered in Assign Notification Attributes to Customers. --- ## Configure Sales Order Confirmation SMS Notifications to Customers SMS notifications send an automated text message to the customer when their sales order is confirmed. SMS notifications are configured on the **Order Confirmation** event template and require the **Generic-Mobile** validation code to be set as mandatory so that a valid contact phone number is captured for every customer. ### Configuration Steps 1. Click the **Frameworks Menu** and navigate to **System Administration > System Setup > Configuration > Additional Validations**. 2. Locate the **Generic-Mobile** code. 3. Enable the **Mandatory** checkbox for the **Generic-Mobile** code. 4. Click **Save** to apply the change. 5. Return to **Event Definition Maintenance** and open the **Order Confirmation** event template. 6. Enable the **Subscribed** checkbox beside the **Event ID** field (if not already enabled). 7. Enable the **Subscribed** checkbox beside the **SMS** action. 8. In the **Condition** field, enter: `customer:getAttributeValue("SMS-OrderConfirmation") = True` 9. In the **To** field, enter: `{order:contactPhone}` 10. In the **Body** field, enter the message to send to the customer. For example: `Hi, Order {order:numTran} has been confirmed. Thanks.` 11. Click **Save** to apply the configuration. ### Result The **Order Confirmation** event template is subscribed to send an SMS to the customer whenever a sales order is confirmed and the customer has the **SMS-OrderConfirmation** attribute set to true. The SMS uses the contact phone from the sales order and applies the configured body text. > ⚠️ ### Important Notes > ⚠️ > ⚠️ - The contact phone is taken from the **Contact Phone** field on the sales order. If the sales order does not have a **Contact Phone** value, no SMS is sent. The **Contact Phone** defaults from the **Phone** field on the **General** tab of the customer record and can be overridden on the sales order. > ⚠️ - The **SMS-OrderConfirmation** attribute must be assigned to each customer who is to receive SMS notifications. Attribute assignment is covered in Assign Notification Attributes to Customers. > ⚠️ - SMS notifications require an active SMS integration with Frameworks. Contact [DMSi Support](https://kb.myframeworks.com.au/page/support) if SMS is not yet enabled in your environment. --- ## Configure Frameworks Notifications to Sales Reps and Users Frameworks Notifications send an in-application notification to a sales rep or user when a sales order they are associated with is confirmed. Frameworks Notifications do not require additional validation configuration and are available to all Frameworks users by default. > ✅ Refer to [Notification Action](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28408822) for detailed information on configuring the Notification action on an event template. ### Configuration Steps 1. Click the **Frameworks Menu** and navigate to **System Administration > Event Notifications > Setup & Administration > Event Definition Maintenance** and open the **Order Confirmation** event template. 2. Enable the **Subscribed** checkbox beside the **Event ID** field (if not already enabled). 3. Enable the **Subscribed** checkbox beside the **Notification** action. 4. In the **Condition** field, enter a condition to control which sales reps trigger notifications: 1. To notify for all confirmed orders, leave the **Condition** field blank. 2. To notify only when orders are confirmed for specific sales reps, enter: `can-do("REP01,REP02,REP05", customer:idSalesRep)` (replace the sales rep codes with your own). 5. In the **To** field, enter: `{customer:idSalesRep}` 6. Click **Save** to apply the configuration. ### Result The **Order Confirmation** event template is subscribed to send a Frameworks Notification to the sales rep on the customer record whenever a sales order for that customer is confirmed. The notification appears in the recipient's Frameworks Notifications inbox. ### Important Notes - Frameworks Notifications are independent of the customer's **Email-OrderConfirmation** and **SMS-OrderConfirmation** attributes. The customer attributes control customer-facing notifications only. - The sales rep on the customer record (defined by **customer:idSalesRep**) is the recipient. If a different recipient is required, adjust the **To** field accordingly. - The **Condition** field uses the `can-do` function to filter by sales rep code. Separate multiple sales rep codes with commas inside the quoted list. --- ## Assign Notification Attributes to Customers Customer attributes control which customers receive email and SMS notifications. The **Email-OrderConfirmation** and **SMS-OrderConfirmation** attributes must be assigned to each customer who is to receive notifications. Without the applicable attribute, the customer will not receive a notification even when the event template is subscribed. > ℹ️ If the **Notice** category or the **Email-OrderConfirmation** and **SMS-OrderConfirmation** attributes do not exist in your Frameworks environment, they must first be created in **Define Attributes** with a **Data Type** of **Logical**. Refer to [Define Attributes - Field Definitions](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28382778) for detailed information on defining attributes. ### Configuration Steps 1. Click the **Frameworks Menu** and navigate to **Receivables > Maintenance > Customer Maintenance**. 2. Search for and select the customer requiring notifications. 3. Click the **Attributes** tab. 4. Click **Add**. 5. In the **Category** field, enter `Notice` or search for it using the **Search** icon. 6. In the **ID** field, click the **Search** icon and select the required attribute: 1. Select **Email-OrderConfirmation** to enable email notifications. 2. Select **SMS-OrderConfirmation** to enable SMS notifications. 7. Enable the **Value** checkbox to activate the attribute. 8. Click **Save**. 9. Repeat steps 4-8 to assign the second attribute if both email and SMS notifications are required for this customer. 10. Repeat steps 2-9 for each customer requiring notifications. ### Result The assigned attribute activates the notification channel for the customer. When a sales order for this customer is confirmed, Frameworks evaluates the customer's attributes against the event template conditions and sends the applicable notifications. A customer with both attributes assigned will receive both an email and an SMS. > ⚠️ ### Important Notes > ⚠️ > ⚠️ - The attribute must have the **Value** checkbox enabled. An attribute that exists on the customer record but is not enabled will not trigger a notification. > ⚠️ - The customer's contact email is defined on the **E-Address** field on the **General** tab of the [customer record](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28389894), and their contact phone is defined on the **Phone** field on the same tab. Both values default onto sales orders as the **Contact Email** and **Contact Phone** and can be overridden on individual sales orders. --- ## Validation After completing all configuration steps, verify order confirmation notifications are working correctly. ### Test Checklist 1. Create a test sales order for a customer with the **Email-OrderConfirmation** and **SMS-OrderConfirmation** attributes assigned: - [ ] The **Is Confirmed** checkbox is not ticked on the new sales order (**Default Order Complete** disabled). - [ ] The **Contact Email** field contains a valid email address. - [ ] The **Contact Phone** field contains a valid mobile phone number. 2. Confirm the sales order through **Actions > Confirm Order**: - [ ] The **Is Confirmed** checkbox becomes ticked. - [ ] The customer receives the configured email. - [ ] The customer receives the configured SMS. - [ ] The associated sales rep receives a Frameworks Notification (if configured). 3. Check the Notifications Event Queue: - [ ] Click the **Frameworks Menu** and navigate to **System Administration > Event Notifications > Setup & Administration > Notifications Event Queue**. - [ ] Locate the Order Confirmation event matching the date and time of the confirmation. - [ ] The **Log** field records each notification action (email sent, SMS sent, Notification sent). ### Expected Outcome Order confirmation notifications are triggered whenever a user performs the **Confirm Order** or **Confirm Quote** action on a sales order or quote for a customer with the applicable attributes. Each notification channel is logged in the Notifications Event Queue for audit and troubleshooting. > ✅ ## Related Information > ✅ > ✅ - [Branch Maintenance - Field Definitions](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28390994) - Details of the **Default Order Complete** flag > ✅ - [Customer Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28389894) - Assigning attributes and managing customer contact details > ✅ - [Define Attributes - Field Definitions](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28382778) - Creating the **Email-OrderConfirmation** and **SMS-OrderConfirmation** attributes > ✅ - [Additional Validations](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28392046) - Configuring the **Generic-Email** and **Generic-Mobile** validation codes > ✅ - [Setup & Administration - Event Definitions](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28386126/Setup+Administration#eventdeftemp) - Managing event templates > ✅ - [Notification Action](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28408822) - Configuring the Frameworks Notification action > ✅ - [Event Definition Condition Logic](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/344948737) - Syntax and functions for event condition expressions > ✅ - [FWConfirm](https://sterlandsupport.atlassian.net/wiki/spaces/FSS/pages/13173558) - System flag definition