Customer Distribution Rules

the administrator can upload the customer data at process level following are the features of the customer data upload at process level step process flow definition now, the customer data will now be uploaded and distributed at the process level itself, instead of the system level ameyo refresh table and customer prospect table each process will have its unique and separate ameyo refresh table, which will be named as "ameyo refresh table \<process id>" (here, process id is the id of the process ) also, each process will have its unique and separate customer prospect table, which will named as "customer prosect \<process id>" (here, process id is the id of the process) after upgrading the build to ameyo 4 7, the default ameyo refresh table and the default customer prospect tables for every process will be created if there are 5 processes, then 5 ameyo refresh tables and 5 customer prospect tables will be created as per the above mentioned naming conventions customer data upload customer data sill will be captured from different sources such as staging database architecture, api, files placed at ftp, or by uploading the data manually through csv file however, the backend configuration have to be done to instruct the ameyo system that which data should be inserted in which "ameyo refresh table \<process id>" table please refer to the following document to know more about the same transferring data from ameyo refresh table to customer prospect table from "ameyo refresh table \<process id>" table of a process, the data will be transferred to the customer prospect table, that is "customer prospect \<process id>", of that process mapping the columns the user still have to map the columns of "ameyo refresh table \<prospect>" table of a process with the columns of "customer prospect \<process id>" of the same process in "csutomer prospect column mapping" table however, now the user have to specify the id of the data table of that process of which ameyo refresh table and customer prospect table have to be matched please refer to the following document to know more about the same document on ameyo preprocessor http //oldsites ameyo net/view/engineering/home/certificationknowledgebase/forward feed and data allocation testing html creating the rules "customer segregation" rule tab from "system" → "system configuration" → "rule engine" has been removed a new tab "customer distribution rules" has been added in "process settings" a new "customer distribution rules" tab will be created for all existing and new processes in the ameyo system now, the administrator have to create the customer distribution rules at the process level to use the data available in "customer prospect \<process id> of a process applicability of the rules on customer data the created rules will be applied in runtime, that is, as soon as the "customer prospect \<process id>" table has some customer data, the rules will be applied and moving the matched data from "customer prospect \<process id>" table to the table definition of that process after applying the rule, the data will be moved to the data table definition of the process and will be deleted from "customer prospect \<process id>" table action if no data is matched for the applied rules if any customer data does not match any "customer distribution" rule, then it will remain idle in the "customer prospect \<process id>" table and will not be used in any operation of the ameyo system the user can use the options on user interface such as "export" or "export and extract" to download the data from the customer prospect table of a process after downloading the data, the user can access it and analyze what new rules can be created in "customer distribution rules" tab to use this data summary in nutshell, the customer data is now uploaded and managed at the process level each process has its unique "ameyo refresh table \<process id>" table and "customer prospect \<process id>" table in addition to transferring the data to these tables from the linked sources, the user can also upload the data to these tables the rules will also be created and applied at the process level the user can also download the data from customer prospect table of any process the complete page is divided into two following sections right section the right section provides the administrator with options to upload customers via csv, export customer data to a csv file, or perform both export and removal of customer data from the system it includes the following options upload customers click this button to import a list of customers from a csv file into the ameyo system it is recommended to use the following naming convention for csv files \<process name> \<timestampofexport> csv ensure that the column headers in the csv file match the table definition fields of the selected process if the headers in the csv differ from the table definition, use the provide header mapping option during upload to upload customer data from a csv file click upload customers a pop up window appears for you to select and upload the required csv file select the location where the csv file is stored select the csv file and click "open" it opens the csv file and displays the following pop up here, you can select the following options update duplicate records by default, the ameyo system will not upload those records of customer data which are already uploaded in the ameyo system you can check this option to update the already existing customer record with the latest data being uploaded example if a customer already exists at the process level with the following attributes twitter timezone facebook phone2 name phone3 phone4 phone5 email phone1 additional column john asia/kolkata john\@domain com 123456789 john john\@domain com 1234567891 na now, an administrator is uploading the following data, in which the phone2 column contains the different value and phone3 contains the new value twitter timezone facebook phone2 name phone3 phone4 phone5 email phone1 additional column john asia/kolkata john\@domain com 146797979 john 123479789 john\@domain com 1234567891 na now, if the administrator have selected "update duplicate records", then the ameyo system will merge the changed values and add the new values in the existing customer record that would like the following data twitter timezone facebook phone2 name phone3 phone4 phone5 email phone1 additional column john asia/kolkata john\@domain com 146797979 john 123479789 john\@domain com 1234567891 na provide header mapping use this option if the name of any column header of the csv file is different from the name of table definition fields (of the process) with this checkbox, you can map the column headers of csv file, having different name, to the table definition fields select this checkbox to show the options to map the csv column headers to the table definition fields the labels are column headers of csv files whereas the table definition fields are the values of drop down menus if all column headers of the csv file has the same name as that of table definition fields, then the administrator can skip this option ameyo preprocessor will validate the data during the upload process it can skip uploading some data and throw errors for any invalid data export click this button to download the already uploaded customer data and save it in csv file format on the disk export and extract click this button to download the already uploaded customer data, save it in csv file format on the disk, and remove the downloaded customer data from the ameyo system permanently 2 create a new rule it lets the administrator to create the new rules for the customer's data perform the following steps to create the new rule click "new rule" button the following page is opened provide the name of the rule in "rule name" column, through which you want to create the rule enter the description of the rule in "rule description" textbox click on the "conditions" tab to provide the conditions select any of the following types of the condition from the drop down list twitter timezone facebook phone2 name phone3 phone4 phone5 email phone1 after selecting the condition, you have to select any of the following operators in "operator" drop down menu < = != > provide the value in the rhs section which satisfies for the given condition the administrator can provide multiple conditions for the single rule click "add new condition" button to provide multiple conditions e action after providing the condition, now provide the action which will perform when the condition satisfies select the type of the action from the drop down list of "types" the actions available to select are "new," and "upload" new the "new" action creates the new entry according to the condition given above upload the action "upload" performs the following actions create the new customer if the customer matching the rule does not exist it will update the customer records that are already available for distribution update the customer record that is already available for distribution update and migrate the customer record that is already available in a lead other than specified in the rule select the campaign on which you want to upload the customer details, from the drop down list of "campaigns" select the lead on which you want to upload the data, from the "lead" drop down section f after providing all the information, click "save" button to create a new rule clicking save button redirects you to the main page of the customer rule edit the customer distribution rule the administrator can edit the created rule as well click on toggle icon present in the actions column of the rule the same page is opened as opened at the creation time of the rule the administrator can change all the information of the rule click "save" button after editing the rule delete the customer distribution rule the administrator can also delete the customer distribution rules select the rule which you want to delete and click on delete icon present in the actions column of the rule a confirmation pop up is arised click "yes" button to delete the rule, else click "no" if you want to delete multiple rules, then select all the rules and click "delete" button to delete all the rules at one click if the rule is deleted, then it can not be retrieved in any manner disable the customer distribution rule the administrator can disable the enabled rule perform the following steps to disable the rule select the rule, which you want to disable toggle the switch present in the status column of the rule to disable the rule enable the customer distribution rule the administrator can enable the disabled rule perform the following steps to enable the rule click "view disabled rules" checkbox to see the list of the disabled rules select the rule, which you want to enable toggle the switch present in the status column of the rule to enable the rule