• Your organization must have Enable Custom Notifier turned on.
• You need permission to access the Notifier Rules and Custom Object Notifier Log pages.
• Decide who should receive the notification and what object state should cause it.

Each rule has four parts: a record type, a scope, one or more conditions, and a destination.

Record is created or updated ─┐

├─> Cetec ERP evaluates matching rules ─> Email and/or API call ─> Log entry

Scheduled job checks records ─┘

Use an object type to choose the kind of record to watch. Common examples include customers, quotes, purchase orders, order lines, parts, and inspections.

Use Object ID to set the rule's scope:

• Global applies the rule to every record of the selected object type.
• A specific object ID applies the rule only to that record. For line types, the field is labeled Line #.

Use the condition builder to define the criteria for a notification. Join criteria with AND when all must match, or OR when any can match. Available operators depend on the field and include equals, greater than or less than, text matching, blank or not blank, ranges, and Changed.

Changed means the selected field changed. It does not mean that the field currently has a particular value. Combine it with another condition when you need both, for example: “status changed” AND “priority equals Critical.”

Cetec ERP evaluates a rule when a supported record changes and during the Object Notifier scheduled job. The scheduled job also finds records whose saved values now meet a rule's conditions. The schedule is managed per environment, so scheduled notifications are not necessarily immediate.

Cetec ERP records successful rule activity to prevent duplicate notifications when Multiple Trigger is off.

1. Open Admin > Notifier Rules and select Create Rule.
2. Select the Object Type.
3. Enter a clear Rule Name. Include the business purpose, such as Alert purchasing when PO line due date changes.
4. Enter one or more recipient email addresses, separated by commas.
5. Select Create Rule. Cetec ERP opens the rule editor.
6. Choose the rule's scope:

• To create a global rule from Admin > Notifier Rules, leave Object ID set to Global.
• To create an object-specific rule from the same page, select the edit icon in the rule header. Then use Object ID to search for and select the object.
• In a supported Object module, open Utilities → Notifier Rules from the side menu, then select Create Rule. Cetec ERP opens a rule already scoped to the object you are viewing.
• On the same page, for a line Object Type, select an individual line to scope the rule to that line. Select All to create a separate line-specific rule for each current line.

7. In the condition builder, select a field, comparison, and value. Add condition groups when you need AND/OR logic.

8. Select Update to save the completed rule.

Test with a record that should meet the condition. Then open Admin > Custom Object Notifier Log and filter by the object type, object ID, or date. Confirm that the rule appears and that the intended recipients received the email.

For a global rule, start with a narrow condition. A broad condition can send notifications for many matching records.

Enable Multiple Trigger when the rule should be allowed to send again for later qualifying events. This is especially useful with a Changed condition, such as notifying the buyer each time a due date changes.

Leave it off when one notification is enough. Cetec ERP records a successful notification so that the same rule does not keep sending for the same matching record.

Enable Delete After Trigger for a temporary rule. Enter a Trigger Limit to choose how many qualifying notifications are allowed before Cetec ERP removes the rule.

• A limit of 1 makes a one-time rule.
• A higher limit enables repeated notifications until the limit is reached.
• If you leave the limit empty, the rule is removed after its first qualifying notification.

Use a descriptive name for temporary rules so they are easy to identify in the rule list.

Enter recipient addresses in Emails, separated by commas. Keep the list focused on people who can act on the notification.

For supported object types, you can also select Email to primary contact?. Cetec ERP then adds the primary contact of the customer or vendor linked to the triggering record. Verify that the related customer or vendor has a current primary contact with an email address.

Use Document URL to attach an existing Cetec ERP document. Enter one or more supported document paths, separated by commas. For example:

/api/document/123

/api/document/456

Only use documents that recipients are allowed to receive. If an attachment cannot be retrieved, Cetec ERP logs the attachment issue and still sends the notification and any other available attachments.

For Customer rules, the Customer Document selector can also attach one generated document for the customer that triggered the rule:

• Customer Statement
• Consolidated Invoice PDF
• Consolidated Invoice CSV

These generated documents are resolved when the notification is sent, so they reflect the triggering customer.

Open Admin > Custom Object Notifier Log to investigate a notification or confirm delivery activity.

You can filter the log by:

• Object Type
• Object ID
• Event
• Sent On date range

The log can show the rule ID, event, recipient list, document links, and, when configured, API call details and errors. Use the rule ID link to open the rule and review its current conditions and recipients.

Administrators can configure an API call in the rule editor. This is useful for notifying an approved external workflow or webhook when the rule qualifies.

1. Open the rule and select Edit.
2. In API Call, choose POST, PUT, or PATCH.
3. Enter the endpoint and JSON request body required by the receiving system. Use HTTPS for endpoints outside your trusted network.
4. If the endpoint requires a token in the query string, enter the parameter name and token on the Auth tab.
5. Save the rule and test it with a safe receiving endpoint.

API calls are independent of email delivery. A failed API call is recorded in the notifier log and does not prevent other configured destinations from running. Do not include passwords, personal data, or other secrets in the request body unless your organization's security and retention policies permit it.

1. Create a rule for PO Line.
2. Choose Global to cover all PO lines, or select a specific line.
3. Add the condition Due Date → Changed.
4. Add the purchasing team email address.
5. Enable Multiple Trigger so the team is notified of later due-date changes.
6. Save and test by changing a due date on a non-production or test record, where available.

1. Open the purchase order and select Utilities → Notifier Rules.
2. Select Create Rule. Cetec ERP preselects the purchase order you are viewing.
3. Add the condition Status → Changed.
4. Add the buyer's email address.
5. Enable Delete After Trigger and set Trigger Limit to 1.
6. Save the rule. The buyer receives one alert after the next status change, then Cetec ERP removes the rule.

1. Create a rule for Customer.
2. Add the customer condition that identifies the follow-up state.
3. Add the internal recipient or enable Email to primary contact?, if appropriate.
4. In Customer Document, select Customer Statement.
5. Save and verify the generated attachment from the notifier log and received email.

Check the following:

1. Open the rule and verify its Object Type, Object ID scope, recipients, and full AND/OR condition.
2. For a Changed condition, make sure the selected field actually changed. Merely saving an object without changing that field does not qualify.
3. Check whether the rule already sent and Multiple Trigger is off.
4. Check whether Delete After Trigger removed the rule after it reached its limit.
5. Review Custom Object Notifier Log for the object and date range.

Narrow the condition, use a specific Object ID, or turn off Multiple Trigger.

Confirm that the object type supports primary-contact delivery and that the linked customer or vendor has a primary contact with a valid email address. Also check that Email to primary contact? is selected on the rule.

Confirm that each entry in Document URL is a valid Cetec ERP document path, such as /api/document/123, and that the document is available for the notification (public). Check the notifier log and contact your administrator if the issue continues.

Open the notifier log and review the API error. Verify the URL, method, JSON body, token parameter name, and token with the owner of the receiving system. Test the endpoint independently before retrying the rule.

Review active rules regularly, especially global and multi-trigger rules. Update recipient lists when responsibilities change, remove temporary rules that are no longer needed, and test rules after changing related record fields or integrations.