Difference between revisions of "MetaData - Processing Rules - Cross Form"

From All n One's bxp software Wixi

Jump to: navigation, search
(Cross Form Update Smart)
(Cross Form Update Smart)
 
Line 167: Line 167:
  
 
 
 +
 
Example:
 
Example:
 
<syntaxhighlight lang="xml">
 
<syntaxhighlight lang="xml">

Latest revision as of 09:30, 20 February 2017

1 Overview

For more information on

Area Link
MetaData please refer here MetaData_-_Start_Here
Processing rules please refer here MetaData_Process_Rules
Parameter construction please refer here MetaData_Program_and_Outcomes

2 Reference

This wixi article is meant to serve as a reference guide to a subset of MetaData Processing Rules.


3 Rules

3.1 Copy To Destination

This function allows you to specify a source value and then to sequentially add that value to a subsequent or previous number of fields.


Required fields to execute rule:

  1. Rule Name
  2. Form id (the same as the current sequence)
  3. Field containing the data to copy
  4. Destination field
  5. Number of times to copy the data
  6. Gap between each insert


Example:

Rule Name[[-SEP-]]Form Id[[-SEP-]]Fields to copy[[-SEP-]]Destination fields[[-SEP]]number of times to copy the data[[-SEP-]]Gap between each copy[[-SEP-]] [[-SEP-]] [[-SEP-]] [[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]]


Example (with replacement values):

Copy_To_Destination[[-SEP-]]1[[-SEP-]]strCDA_1_field_0_1,strCDA_1_field_0_2[[-SEP-]]strCDA_1_field_0_3,strCDA_1_field_0_4[[-SEP]]50[[-SEP-]]2[[-SEP-]] [[-SEP-]] [[-SEP-]] [[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]]

3.2 Cross Form Update

This function allows for the updating of records in one database with values stored in another


The Options field should be set to True if a CCL is required to be inserted as well in the destination campaign.


Required fields to execute rule:

  1. Rule Name
  2. Form id (the same as the current sequence)
  3. Destination field
  4. Form id (the same as the current sequence)
  5. Fields separated by comma’s
  6. Form id (the same as the current sequence)
  7. Fields to separate by comma’s


Example:

Rule Name[[-SEP-]] Form id [[-SEP-]]Destination field[[-SEP-]]Form id[[-SEP-]]Fields[[-SEP-]]Form id[[-SEP-]]Fields[[-SEP-]]Options[[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]]


Example (with replacement values):

CrossDatabase_Update[[-SEP-]]1[[-SEP-]]strCDA_1_field_0_1[[-SEP-]]2[[-SEP-]] strCDA_2_field_0_1 [[-SEP-]]3[[-SEP-]]strCDA_3_field_0_1[[-SEP-]]True[[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]] 


3.3 Cross Form Insert

This function allows for the creation of new records in a database using the values stored in another database. The system will auto generate the values for the system fields including the ID, Future Use, Status, Last Date Time, Last Agent Id, unless explicitly stated.


The Options field should be set to True if a CCL is required to be inserted as well in the destination campaign.


Required fields to execute rule:

  1. Rule Name
  2. Form id (the same as the current sequence)
  3. Destination field
  4. Form id (the same as the current sequence)
  5. Fields separated by comma’s
  6. Form id (the same as the current sequence)
  7. Fields to separate by comma’s


Example:

Rule Name[[-SEP-]]Form id[[-SEP-]]Destination field[[-SEP-]]Form id[[-SEP-]]Fields[[-SEP-]]Form id[[-SEP-]]Fields[[-SEP-]]Options[[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]]


Example (with replacement values):

CrossDatabase_Insert[[-SEP-]]1[[-SEP-]]strCDA_1_field_0_1[[-SEP-]]2[[-SEP-]] strCDA_2_field_0_1 [[-SEP-]]3[[-SEP-]]strCDA_3_field_0_1[[-SEP-]]True[[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]]


3.4 Cross Form Update Simple/Custom

This function allows for the updating of records in one database with values stored in another, using a custom group by clause


Required fields to execute rule:

  1. Rule Name
  2. Table name (values to be updated in)
  3. Fields to update
  4. Files that contain the values to update
  5. Form Id to search on
  6. Update search field
  7. Form id containing search value
  8. Update search value


Example:

Rule Name[[-SEP-]] Table name [[-SEP-]]Fields to update[[-SEP-]]Form id[[-SEP-]]Fields[[-SEP-]]Form id[[-SEP-]]Fields[[-SEP-]]Options[[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]]


Example (with replacement values):

CrossDatabase_Update_Custom[[-SEP-]]CDA_1[[-SEP-]]strCDA_1_field_0_7[[-SEP-]]strCDA_2_field_0_1[[-SEP-]]intCDA_2_Id[[-SEP-]]strCDA_1_field_0_7[[-SEP-]]CDA_2[[-SEP-]]strCDA_1_field_0_7[[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]][[-SEP-]] 


3.5 Cross Form Update Smart

This function allows for the updating of records in one database with values stored in another, using a custom group by clause. If a matching record is not found in the destination database then the MetaData will not perform and update. It does however perform a brand new record insert


Required fields to execute rule:

  1. Rule to process
  2. Table to insert to
  3. Fields to insert values into
  4. Values to insert into the fields
  5. Table with the values
  6. Fields to search for records
  7. values to search for
  8. Boolean add CCL
  9. CCL Outcome
  10. CCL Comments
  11. Boolean update current status
  12. New Status
  13. Part Matching Enabled
  14. Alternate matching patterns fields
  15. Alternate matching patterns value

Example:

Rule Name[[-SEP-]]Table to insert to[[-SEP-]]Fields to insert values into[[-SEP-]]Values to insert into the fields[[-SEP-]]Table with the values[[-SEP-]]Fields to search for records[[-SEP-]]values to search for[[-SEP-]]Boolean add CCL[[-SEP-]]CCL Outcome[[-SEP-]]CCL Comments[[-SEP-]]Boolean update current status[[-SEP-]]New Status[[-SEP-]]Part Matching Enabled[[-SEP-]]Alternate matching patterns fields[[-SEP-]]Alternate matching patterns value[[-SEP-]][[-SEP-]]


Example (with replacement values):

CrossDatabase_Update_Smart[[-SEP-]]11[[-SEP-]]strCDA_11_field_0_4,strCDA_11_field_0_7,strCDA_11_field_0_8,strCDA_11_field_0_9,strCDA_11_field_0_10[[-SEP-]]strCDA_12_field_0_4,strCDA_12_field_0_7,strCDA_12_field_0_8,strCDA_12_field_0_9,strCDA_12_field_0_10[[-SEP-]]12[[-SEP-]]strCDA_11_field_0_16{{--SEP--}}strCDA_11_field_0_17{{--SEP--}}strCDA_11_field_0_18{{--SEP--}}strCDA_11_field_0_4[[-SEP-]]--AccountFirstname--{{--SEP--}}--AccountSurname--{{--SEP--}}--AccountDOB--{{--SEP--}}--AccountIOB--[[-SEP-]]true[[-SEP-]]Real Time update from IOB [[-SEP-]]Real Time update process from DB Id:12[[-SEP-]]true[[-SEP-]]Real Time update from DB 11[[-SEP-]]true[[-SEP-]]strCDA_11_field_0_16{{--SEP--}}strCDA_11_field_0_17{{--SEP--}}strCDA_11_field_0_18{{##SEP##}}strCDA_11_field_0_16{{--SEP--}}strCDA_11_field_0_17{{--SEP--}}strCDA_11_field_0_4{{##SEP##}}strCDA_11_field_0_16{{--SEP--}}strCDA_11_field_0_18{{--SEP--}}strCDA_11_field_0_4{{##SEP##}}strCDA_11_field_0_17{{--SEP--}}strCDA_11_field_0_18{{--SEP--}}strCDA_11_field_0_4[[-SEP-]]--AccountFirstname--{{--SEP--}}--AccountSurname--{{--SEP--}}--AccountDOB--{{##SEP##}}--AccountFirstname--{{--SEP--}}--AccountSurname--{{--SEP--}}--AccountIOB--{{##SEP##}}--AccountFirstname--{{--SEP--}}--AccountDOB--{{--SEP--}}--AccountIOB--{{##SEP##}}--AccountSurname--{{--SEP--}}--AccountDOB--{{--SEP--}}--AccountIOB--[[-SEP-]][[-SEP-]][[-SEP-]]