Create an event from scratch

You can set the Events & Actions Notifier to monitor specific events in Made2Manage and then associate actions with the event. When an event occurs meeting the criteria you specify, this triggers the alert or action you associate with the event.

To create an event from scratch

1. Open the Events & Actions (EANOTI) page.

   1. Select Utilities > Company Setup > System > Events and Actions >Events & Actions*.

   Or

   2. Search for EANOTI in the Navigation box and then select Events & Actions.
      The Events & Actions (EANOTI) page appears.
      

2. To add an event from scratch:

   » On the Toolbar, click New.

3. Set details about the event:

   1. Click the Object Name Lookup Reference.

   The Lookup For Object Name window appears.

   2. Highlight a row and click Select. Or, double-click the object to select.

      Click Cancel to exit from Lookup For Object Name screen.

   3. Click the Table Name arrow and select the table that contains the field that triggers the event.

      Additional Tables - You can select multiple tables.

   4. Select the check box in Select column. Based on the tables, the Relational Expression is created.

   5. Click Validate to verify the expression.

   6. Type a name for this event in the Name box. This is a defined description of the Event.

      For example, TEST

   7. Click the Status arrow in the header and select Active to begin using this event. Defaults to Active status.

      Or

      Select Inactive if you want to make the event active later.

   See step 6 and step 7 in “Creating alerts using existing entries in the Events & Actions Library” for more information.

4. Set the Fire Criteria.

   The SQL Server expression defines the Event trigger. Some knowledge of SQL Query may be required for Events that are more complex.

   Fire criteria allow you put limitations on the records that trigger the event. For example, if you are using INMASTX table and only want events to fire for Part No ES1030, you would set the fire criteria to the following:

   INMASTX.fpartno =‘ES1030’

You can bring up the expression for Fire Criteria using the Operators and Insert field not on form. See step 5.

5. Perform the following:

   » Click the Operators arrow and select the operator to insert an operator in the expression.

   The SQL Query operators may be used in defining the Fire Criteria.

   » To insert a field from another table into the expression, click the Insert field not on form arrow and select the field to insert.

   » Click Validate.

6. Click the Action tab.

   » You can configure the system to send an email from an address that is not associated with user management (for example, [email protected] or [email protected]).

   1. Select the Optional Email ID checkbox.

   2. Enter the required email address in the Optional Email ID field.

>[!Note]: When this option is enabled, the system sends the email from the address specified in the Optional Email ID field, not from the user who triggered the event.

>[!Note]: The optional sender email “domain” must match the “default email domain” configured as Active in the System Setup (CSSYS).

7. Select the Priority to send the alert.

8. Click the Recipient tab to select the notifications about the event:

   » Internal tab: Use this tab to specify the details of notifications to be sent to internal users. You can select the internal users or groups of users who should receive the alert messages and email.

≡ Attach related reports: Use this check box to attach related reports in email.

1. Select the Attach Related Reports checkbox.

2. The system displays a grid with columns such as, Report ID, Report Name, Default Selection and Checkboxes to select multiple reports.

3. Use the Report Copy/Template drop-down to select the required report variants for the object.

4. The selected reports will be included as attachments in the outgoing email.

Example: For a Sales Order Open event, you can select multiple reports from the grid. Choose the Internal SO Copy template for internal recipients and the Customer Copy template for external recipients.

≡ Current User: Use this check box to send an alert to the user who has triggered the event.

» External tab: Use this tab to specify the details of notification to be sent to external users. You can select all of the vendors or customers who should receive the alert emails and, SMS, and fax messages. You can also specify any additional recipients to receive the alert messages in the Email/SMS tab.

The external vendors and customers are displayed only when the Global Notifications check box is selected in the System Setup (CSSYS) page.

≡ Attach related reports: Use this check box to attach related reports in email.

1. Select the Attach Related Reports checkbox.

2. The system displays a grid with columns such as, Report ID, Report Name, Default Selection and Checkboxes to select multiple reports.

3. Use the Report Copy/Template drop-down to select the required report variants for the object.

4. The selected reports will be included as attachments in the outgoing email.

Example: For a Sales Order Open event, you can select multiple reports from the grid. Choose the Internal SO Copy template for internal recipients and the Customer Copy template for external recipients.

≡ Use Contact On Document: This check box displays only when the Global Notification check box is selected in the System Setup (CSSYS) page. Use this check box to send alerts to the Contact on the document instead of the email ID specified for the respective Customer (CUST) or Vendor (VEND) record.

≡ Include Salesperson: This check box is displayed only when the Global Notification check box is selected in the System Setup (CSSYS) page.

1. Select the Include Salesperson checkbox.

2. When the event is triggered, the system automatically sends an email to the salesperson associated with the object or event.

Example: For a Sales Order Open event, if you select Include Salesperson, the system sends an email notification to the salesperson linked to that sales order.

>[!Note]: The Include Salesperson option is available only for the following objects: -Opportunity -Quote -Sales Order -Sales Order Commission -Account
-Customer Invoice Credit Memo

>[!Note]: System sends an Email to the Salesperson only if the email id is entered in Salesperson (SLPN) screen, if the email id field is left blank the system does not send the email.

≡ Current User: Use this check box to send an alert to the user who has triggered the event.

>[!Note]: Check for any errors related to events under the Error Logs tab of the Alert Central (EAALRT) page. Check for any errors related to event actions, like email and report generation, on the View Log Files (VIEWLG) page.

9. In the Email tab, click the Recipient arrow and select whether to send an email message regarding this alert to the customer or vendor.

   » Current Customer - The Customer associated with the Event

   » Current Vendor - The Vendor associated with the Event

You must select either Current Customer or Current Vendor after selecting all of the customers or vendors within the grid to trigger the event.

If you are sending an email to the current user, verify that the email address is entered correctly on the E-mail tab of the User Management page.

The Recipient drop-down list is based on the document type you have defined for your Event. If the document is related to Customers or Vendors, that will be available in the drop-down. If the document is not specifically related to a document with a Customer or Vendor, the drop-down will be empty.

You can type any additional email address to send a message about this event in the Additional Recipients box.

10. Click Save on the Toolbar.

You can also add additional Operator.

» Select Operators arrow and select the required operator from the list.

You can also modify the Message field to include any additional information you would like to view.

» If you want to add additional syntax and methods into the Subject, Message, and Action fields respectively, then select the parameter from Insert field not on form arrow.

See step 5 above for more information.

11. Following is the syntax used in the Subject and Message fields:

    1. Description/Hardcoded values.

    2. Methods – This must start and end with ().

≡ If method does not have any parameter then it should be writ- ten like ()methodname().

≡ If there is any parameter then it should be written like ()Meth- odName(param1,param2)().

≡ If method contains field as parameter then field must start with << and end with >>.

≡ If parameter is a hard-coded value then String/Date must start and end with ‘. Integer/Decimal value must not start or end with ‘. Boolean value must be True/False

 3.  **Fields** – This must start with **\<\<** and end with **>>**
    

The message in the Message field is pulled from the Event Library (EAEVL) screen.

For example, **AR Invoice # <<armast.fcinvoice>> for <<armast fbcompany>> is in New, Not Confirmed Status.

≡ The value within the angle bracket is called << Field Name>>

≡ The value within the parenthesis is called ()Method()

≡ Following is the method used in the Action field

It is a collection of methods. Each method must be written on a new line. Here method should be written like MethodName or MethodName(param1,param2).

≡ If method contains field as parameter then field must start with << and end with >>.

≡ If parameter is a hard-coded value then String/Date must start and end with ‘. Integer/Decimal value must not start or end with ‘. Boolean value must be True/False. In Action, Primary methods accept the following type of parameters:

≡ Hardcoded values

≡ Fields

≡ Methods - This is similar to primary methods except for the method it is written. Parameterized methods must start and end with ()

12. Save the Event.

The shipping events that were using the fields (upsdate, ffrtamt, fno_boxes, fshipwght, and fmtrckno) from the shmast table must be recreated and used from the shmasttracker table.