Understand the Test Run tables in Unica Interact Flowchart
Recently, many customers contacted me for queries related to the Interact Flowchart Test run. In one such case, I observed that the Test run of flowchart stopped running, because of the data being inserted into the background table was greater than the table column size. In another scenario, the Interact user wanted to understand which audienceID falls under which segment. To gain this information, the user was repeatedly running the flowchart in a test run to view the result in the flowchart itself. The input data was huge and the customer did not want to reduce it. Hence, the flowchart run completion took a significant amount of time. While designing the flowchart in Unica Interact, the developer generally test runs the flowchart to ensure that the configuration is correct. But what happens if the flowchart fails with an error? What happens to the data? Where does it get stores? They have become the common issues for which the user always seeks an answer. So, I penned down this blog, which further talks about the tables that are created in the background when a flowchart runs. It talks about what data gets stored where. We talked about how, while executing a test run of the flowchart in the Interact session, the developers observe various error messages. All this information is stored in 4 different types of tables. When an Interact session flowchart is executed, in the background, it creates 4 types of tables in the Profile database- TESTATTR_n, TESTCOUNT_n, TESTSEG_n and TESTERROR_n tables, where _n indicates the number which is generated at run time. This number (_n) is the same for all the above tables for the same Interactive Flowchart. In the present case, Unica will generate TESTATTR_142, TESTCOUNT_142, TESTSEG_142, and TESTERROR_142. To figure out the correct answer to the question,...