1. Loyalty Administration Guide
  2. Member Synchronization Workflows

Member Synchronization Workflows

Some of the Siebel Workflows involved in synchronizing member enrollment data between Siebel Loyalty and CrowdTwist are:

  • LOY Contact CrowdTwist Async Flow. Submits asynchronous requests to LOY Contact CT Integration Flow.

  • LOY Member CrowdTwist Async Flow. Submits asynchronous requests to LOY Member CT Integration Flow.

  • LOY Contact CT Integration Flow. Converts the Contact updates to LOY Member updates and sends the data to OIC for processing.

  • LOY Member CT Integration Flow. Sends Member inserts and updates to OIC for processing.

Batch User Import Flow

The typical steps involved in migrating (member) data from Siebel Loyalty To CrowdTwist are as follows:

  1. Siebel generates the csv file, containing the data to export, using the LOY Member CT Async Flow.

    For more information about how to invoke the data export functionality from the UI, see Data Export Flow.

  2. Oracle Integration Cloud (OIC) validates the csv export file, based on the defined mappings.

  3. OIC generates a json file and uploads it to the SFTP location, so that members are created in CrowdTwist.

If the batch user import fails, then do the following:

  1. Check the Data Export Status for any errors and then check the logs created on the server.

  2. If the Data Export status is Completed, then track the OIC status flow. If the OIC Flow status is in error, then track the OIC instance logs.

  3. If the OIC flow succeeds, then check the CrowdTwist Batch Processing status. If CrowdTwist Batch Processing is in error, then check the error.json file uploaded to the CrowdTwist SFTP location, and fix the error.

Data Export Flow

The steps to invoke the data export functionality from the UI are as follows:

  1. Navigate to the Administration - Data Export screen, then select the Data Export Administration view and do the following:

    • Add the adapter service (Service Name) that is required to export data in CSV format.

    • Configure the export engine with the parameters shown in the following table.

    For Siebel-CT Batch Import, use the "CSV Adapter Service" service and the "Siebel-CT Member Data Export" engine.

    Parameter Name Default Value Required Description

    Batch Split Size

    1000

    Y

    		 Used during initial data export, this parameter splits the total number of records based on the Batch Split Size value and creates different jobs. The maximum value for Batch Split Size must not exceed the total number of records which can be accumulated in a 10 megabyte (MB) file. The maximum file size supported by OIC flow at runtime is 10 MB and any size beyond this will result in error.

    Batch Submit Size

    		 100

    Y

    Each job will process this many records (as specified by this parameter) and invoke the adapter service to write the data to the CSV file.

    filepath

    N/A

    Y

    The file path where the CSV file will be created. This path must be accessible to the Siebel Server where the search component group is enabled, and also to the Configuration Agent that runs the JBS.

    Charset

    UTF-8

    Y

    CrowdTwist supports the UTF-8 charset (which is the default value) only for batch import.

    ExportOnly

    N

    Y

    If the value is Y, then the CSV file will be uploaded to Oracle Object Storage (OOS). Otherwise, the CSV file will be generated in the path specified by the filepath parameter.

    Delete File After Upload

    Y

    N

    It the value is Y or the parameter does not exist, then the CSV file will be deleted after upload. Otherwise, the CSV file will not be deleted.

    bucketname

    N/A

    N

    Name of the Oracle Object Storage (OOS) bucket where the CSV file will upload to.

    directory

    N/A

    N

    Name of the directory under the OOS bucket. If this parameter is left empty, the file will upload to the OOS bucket.

    fingerprint

    N/A

    N

    Finger print of the OOS user.

    key_file

    N/A

    N

    Private key file of the OOS user. This path should be accessible to the Configuration Agent that runs the JBS.

    namespace

    N/A

    N

    Name space of the OOS.

    region

    N/A

    N

    Name of the OOS region.

    tenancy

    N/A

    N

    Name of the OOS tenancy,

    userId

    N/A

    N

    User Id of the OOS.

  2. Go to the Data Export Category Definition view and do the following:

    • Create records for the data categories that you want to export and specify the BC Name (business component name) that they map to.

    • Define Category Fields in the grandchild applet.

    For Siebel-CT Batch Import, the BC Name is "LOY Member CT". This business component name and its fields are seeded data.

  3. Go to the Data Export Settings view and do the following:

    • Export the configured business component by adding it (LOY Member CT) to the search category.

    • Click Export to initiate the export operation.

    • Track the status of the export operation by checking the Status value.