Objects

An object is a fundamental entity in your event store, representing "something" that moves through your process and is associated with activities. Common examples of objects include orders, parts, shipments, and customers.

An object has four key inputs:

1. A name

   This is the reference label for the object, used consistently throughout Konekti and in any connected downstream systems.

2. A source table

   The table supplying the data from which the object is constructed. Each row—after any applied filters—must represent a single instance of the object. For example, a table of orders where each row corresponds to one order.

3. The identifier

   A column that uniquely distinguishes each row in the source table. Konekti enforces this uniqueness and will issue warnings if duplicates are detected.

4. Filters

   Conditions that narrow down the source table to include only the rows relevant to the specific object being defined.

tip

If a basic filter is insufficient to prepare your table for object creation, consider using a combined source. This allows you to preprocess or enrich the table before it becomes the basis for your object.

Identifying Objects in Your Data Set

To find objects in your data, follow these steps:

1. Identify the Table:

   • Locate a table that contains a unique instance of the object on every row.
   • Find the identifying column(s).
   • For example, consider the table below where each row represents a Purchase Order Line, uniquely identified by PO_ID and Line_ID.

   PO_ID	Line_ID	Product	Quantity	Price_usd	Created_date_time	Latest_GR_Date
   001	001	Wire, black, 2.5m	100	100,00	01/11/2023 16:01:00	01/12/2023
   001	002	Wire blue, 2.5m	825	825,00	01/11/2023 16:01:00	01/12/2023
   001	003	Reel ABC	75	750,00	20/11/2023 12:14:00	01/12/2023
   002	001	Wire, yellow, 10m	5000	5820,25	21/11/2023 11:18:23	01/02/2024

2. Validate Object Instances:

   • Ensure that the chosen table contains all the instances of the object you are interested in.
   • In some systems, 'completed' and 'open' documents may be stored in separate tables. Use the Combined source to union these tables before creating the object. (If you create separate object for open and completed documents, remember that you can only pick one of them as a case object later.)