Release Notes                                                 Release Date: April 01, 2021.


The following are the CDP releases.

1. Enable event mapping for custom events (Behavioral Events)

2. Get parent bill number for return transactions

3. Customer registration and profile update (Member Care)

4. Merge line and bill-level files (Connect+)

5. File size limits (Connect+)

1. Enable event mapping for custom events (Behavioral Events)

In the behavioral events module, event mapping for custom events is now enabled. This is used in cases where you want to change the event name or attributes coming from other sources. The source event name and attributes can be mapped to a custom event name stored in our system. 

Use Case

The events coming from WebEngage are having space in their names and are not supported by our system. For example, an event named Promotion Viewed is coming from WebEngage. Since the system does not support event names with space, we create a custom event named promotionViewed. Now you can map the custom event’s name to the original event’s name coming from WebEngage. 

To create a custom event and map a source event, follow these steps. 

  1. Navigate to Organization Stetings > Master Data Management > Data Model > Behavioral Events.
  2. In the All Events tab, click + Add Event.
  3. On Add Events page, click + Create New Event to create a custom event with attributes and click Save.
  4. On the Behavioural Events page, search the created event using the event name.
  5. Click +Add Mapping to map the custom event with the source event. 
  6. On the Add Mapping page, select the source and add the event’s name and attributes coming from the source. 
  7. Click Save.

To view and edit mapping, follow these steps. 

  1. Navigate to Organization Stetings > Master Data Management > Data Model > Behavioral Events.
  2. In the All Events tab, search the mapped event using the custom event name.
  3. Click the mapped custom event and navigate to the Mappings tab to view the event mapping.
  4. In the Mappings tab, click the source event and modify the event mapping.
  5. Click Save.

2. Get parent bill number for return transactions

In a Return transaction type, the parent_bill_number is the unique transaction number of the original bill. This parent_bill_number can be added using Add Transaction API to link the return transaction with its original transaction. Now, parent_bill_number is enabled in the GET Transaction APIs. So, when a return type transaction is retrieved, we also get the parent_bill_number associated with that transaction. 

The following are APIs that can help you to retrieve parent_bill_number.

  1. Get Transaction API [v1.1]
  2. Get Customer Transactions API [v1.1]
  3. Get Transaction API [v2]

3. Customer registration and profile update (Member Care)

Now Member Care can be used to register new customers and edit profile details of existing customers. Service desk executives familiar with Member Care can use the platform directly for performing any profile updates or customer registrations. For details, see customer registration and customer profile update.

4. Merge line and bill-level files (Connect+)

Connect+ is a no-code data integration tool. Now it comes with support for joining line-level and bill-level data files and ingesting the joined file using Add Transaction API(v2) in one go/single template. In many orgs, line-level data and bill-level data come in separate files. The new Transaction LineItem Merge template on Connect+ will make transaction data ingestion seamless in such cases. 

To set up the Transaction LineItem Merge template, follow these steps.

  1. In Connect+, click Add dataflow to create a new dataflow on Connect+.
  2. Click +Select Template and choose the Transaction LineItem Merge template.
  3. In the Connect-to-Source stage, fill in the required FTP-related information - FTP location where the source line-level and bill-level files will be placed for ingestion.
  4. In the Join-data stage, enter details pertaining to the bill- and line-level files that need to be joined.

    The following are the fields to join the line-level and bill-level. 
    1. File 1 Regex: Enter the file name pattern for File 1. The pattern specified for the bill-level file is bill*.csv.
    2. File 2 Regex:  Enter the file name pattern for File 2. The pattern specified for the line-level file is line*.csv.
    3. File 1-2 Join Type: Choose the method for joining the two files - INNER JOIN, LEFT_OUTER_JOIN, and FULL_OUTER_JOIN. 
    4. File 1 Headers and File 2 Headers: Enter the headers on which bill-level and line-level files need to be joined.
    5. File Join Use Case: Select TRANSACTION_LINE_ITEM.
  5. After completing the above actions, the next steps are the same as setting up Transaction v2 add on Connect+. For details, see Configure Field Mapping & Data Transformation.

5. File size limits (Connect+)

Now we have added restrictions on the file size ingested via Connect+ to prevent the platform from overload. 

The following are the restrictions.

  • A file waiting for ingestion on Connect+ should not exceed 200 MB
  • Connect+ cannot allow more than 2 million records in a file. 

If a file exceeds any of the above conditions, an error message will appear on Connect+. 

Soon we will add notes for these restrictions on the user interface.