Skip to main content

Editing an Event

Editing an event consists of three tabs:

  • Conditions
  • Attributes
  • Settings

Conditions​

The "Conditions" tab contains input fields for editing the event. These are the main event data: Name and

Marker
and conditions.

Modules​

In the conditions, you need to select a module that will determine the condition for sending the event. The following modules are available:

  • catalog
  • forms
  • orders
  • users

Conditions for the catalog module​

For the "catalog" module, in the "type" field, you can choose to filter by statuses, then select a specific status, thus subscribing to the event of changes in the status of catalog items, or you can subscribe to an event based on attribute sets and select a specific attribute.

Conditions for the forms module​

For the "forms" module, you need to select the type of form to which the event should be added. The following options are available:

  • Registration
    The event is created when a new user registers via the Content API or in the CMS.
  • Send Code
    The event is created when a new confirmation code is generated for the user, including during the registration of a new user.
  • Change Password
    The event is created when the user changes their password.
  • Submit form data
    The event is created when data from the selected form is submitted via the API.

For "Submit form data," you need to select a form (from forms with the type "Data submission") and the attribute you added for the email (this subscription will not apply to other attributes). When the form is submitted, the data is sent to the email address specified in this attribute. More details about forms are provided in the Forms section.

All events from the forms module include information about the user; the "Registration" and "Send Code" events contain the confirmation code.

Conditions for the orders module​

For the "orders" module, you need to select a specific order storage and status in the filtering fields that will be tied to the event.

Conditions for the users module​

For the "users" module, you need to select filtering by attribute sets and choose a specific attribute that will be tied to the event.

Method of Sending​

For all modules except "forms," you have the option to choose how to send the event notification. In Platform OneEntry, there are three methods:

  1. Push Notification - via push notifications
  2. Email - distribution via email
  3. Socket IO - using websockets. This method is needed to subscribe to certain events. For example, you can create price change events and notify users about it using Socket IO.

Who to Send To​

For the "catalog" module, you can select users who will receive notifications about the event. You can send notifications to all users of your

site
or to a group of users.

How Often to Send​

For events from the "catalog" and "users" modules, you can choose how often to send notifications: once per event or every time.

Attributes​

The "Attributes" tab contains a dropdown list for selecting a Set of Attributes.

After selecting a set of attributes, you need to fill in the values. In our case, this is the attribute "event_send_date," which has the type "Date and Time," and the attribute "event_desc" with the type "String."

You can use these attributes on the "Settings" tab to create a message template. They will be displayed by the key "event": {{ event.attribute_marker }}.

Settings​

The "Settings" tab contains two text input fields for creating a message template that users of your

site
will receive.

Available Variables

You can also use variables for your notification. A list of available variables is provided below the input fields for the notification template.

Mailing to Users (Mailing Mode)​

This functionality allows you to set up periodic email distributions to users who meet the specified conditions. Unlike standard events, the mailing is triggered not by changes in attributes but by meeting the conditions.

Setting Up Mailing​

  1. Creating an Event

    • Event Type: Users
    • Mode: Mailing (distribution)

  2. Setting Up the Schedule

    • Time: reference point (e.g., Monday at 10:00)
    • Frequency: selected from the options:
      • Daily
      • Weekly
      • Monthly
      • Custom interval

  3. User Selection Conditions

    • Examples of conditions:
      • Registration date > 2024-01-01
      • Subscription to mailing = true

Example of Operation​

  • Setup:

    • Time: every Monday at 10:00
    • Frequency: weekly
    • Conditions: users with an active subscription

  • Result:
    Every Monday at 10:00, the system automatically:

    1. Finds all users with an active subscription
    2. Sends them an email with the specified content

Practical Applications​

  • Weekly news digests
  • Inactivity reminders
  • Personalized offers
  • Mass notifications for user groups