Process Data Model (relationship activity - case table )

Dear all,

I have a few different questions about the Process Data Model. I think there have been a few CELONIS adjustments in the past.

  1. Even though the relationship between activity and case table is correct (Process will be shown in the process explorer in the correct way) the display 1:N is mirrored (pic #1).

  2. In the past it was possible to declare/identify the case table with a ©. I can’t find this option any more in the drop down option (pic #2).

  3. In general we need to insert two sources (different systems) in the same process analysis.
    They are running in parallel and are differentiated by additional information in the case (pic #3). The data is written into the case table. Difference than usual (normal create case table syntax), we use the SQL Vertica “insert into” syntax like we used in the activity table. We have to match two different systems with different data sources. In my opinion it will work fine, but I am not really sure that we can use it that way.

  4. Although I only created the two tables (case and activity) in the process model a third table was created automatically in the analysis (activities_cases / pic #4). I can’t see this table in the process data model!

If you have any information for me I would be very grateful. thx

Hi @SH2020

thanks for your questions!

  1. On the edge, it shows how you have configured the join. If you click on the edge, you will see that you have configured “Activities” as the 1-side of the Join, and “Cases” as the N-side of the join. I would suggest to use the “Swap Tables” option in the Foreign key settings to configure it in the correct way. Then, the cardinalities will be shown as you expect.

  2. This is now possible by opening the context menu of the Activity table and then do “Assign Case Table”. The reason for this change is that we now support multiple Activity tables (and thus, multiple case tables) inside one DM, and by assigning a case table to an Activity table we can ensure that every Case table corresponds to the correct Activity table.

  3. In the transformations, you can access all the data in your data pool, which includes data from different data sources. So this should work as expected.

  4. Whenever you have an Activity table where no case table is assigned, we automatically generate a case table based on the Activity table at DM load. If you declare the Case table as described in Answer #2, and then do a full reload of your DM, this “Activities_CASES” table will be gone (because in this case, there is no need to auto-generate a case table, because you have specified one yourself).

Hope this helps!