1 ACCEPTED ANSWER
Ellen
Instead of reformatting all email addresses at once, then deleting the keywords, and trying to add the reformatted ones, you could process each email address individually by using recursion. Care should be taken when configuring recursive calls because you can end-up recursing infinitely which will require an app server reset or restart of whichever component is running the workflow logic (e.g. the Unity Scheduler).
Create an array property containing the email addresses and then use recursion to iterate through the array, updating each email address, then removing the email address that was processed from the array. The recursion stops when the array is empty.
The workflow layout should look like this (I created a System Task for ease of testing):
The rules and actions should be configured as follows:
ACTION: Create array of email addresses
Set Property Value from Keyword Record
Property: propEmailArray
Keyword Record: <whatever the name of the MIKG is>
Keyword Type: Email Address
Tick Set property to all keyword value instances
ACTION: Convert the array to a string:
Set Property to Expression:
Property Name: propEmailArray
CombineArray(%VpropEmailArray; ",")
TASK LIST: Update Email Address //everything below here, including a copy of the Update Email Address task list, is added to this task list
ACTION: Get size of string
Set Property to Expression
Property: propEmailArrayLength
Expression: Len(%VpropEmailArray)
RULE: Break processing if size of string is 0
Check Property Value
Property: propEmailArrayLength
Operator: =
Compare To: Constant value: 0
On True: ACTION: Break Processing: Break All Processing for Top-Level Item
On False: <leave empty>
ACTION: Get email address from string
Set Property to Expression
Property: propEmailAddress
Expression: Match(%VpropEmailArray;"([^,]*){1}$";true)
ACTION: Reformat email address
Set Property to Expression:
Property: propReformattedEmailAddress
Expression: Replace(%VpropEmailAddress; "--"; %K00728; true)
//The above two actions could be combined, but I've kept them separate for readability of the regular expressions.
ACTION: Replace email addr KW w/reformatted email addr
Replace Keyword
Keyword Type: Email Address
Old Keyword:
Property Name: propEmailAddress
New Keyword:
Property Name: propReformattedEmailAddress
//The next step is the most important - removing the processed email address element from the string!
ACTION: Remove email address from string
Set Property to Expression:
Property: propEmailArray
Expression: Match(%VpropEmailArray;".*\w(?=,)";true)
TASK LIST: Update Email Address
Ellen
Instead of reformatting all email addresses at once, then deleting the keywords, and trying to add the reformatted ones, you could process each email address individually by using recursion. Care should be taken when configuring recursive calls because you can end-up recursing infinitely which will require an app server reset or restart of whichever component is running the workflow logic (e.g. the Unity Scheduler).
Create an array property containing the email addresses and then use recursion to iterate through the array, updating each email address, then removing the email address that was processed from the array. The recursion stops when the array is empty.
The workflow layout should look like this (I created a System Task for ease of testing):
The rules and actions should be configured as follows:
ACTION: Create array of email addresses
Set Property Value from Keyword Record
Property: propEmailArray
Keyword Record: <whatever the name of the MIKG is>
Keyword Type: Email Address
Tick Set property to all keyword value instances
ACTION: Convert the array to a string:
Set Property to Expression:
Property Name: propEmailArray
CombineArray(%VpropEmailArray; ",")
TASK LIST: Update Email Address //everything below here, including a copy of the Update Email Address task list, is added to this task list
ACTION: Get size of string
Set Property to Expression
Property: propEmailArrayLength
Expression: Len(%VpropEmailArray)
RULE: Break processing if size of string is 0
Check Property Value
Property: propEmailArrayLength
Operator: =
Compare To: Constant value: 0
On True: ACTION: Break Processing: Break All Processing for Top-Level Item
On False: <leave empty>
ACTION: Get email address from string
Set Property to Expression
Property: propEmailAddress
Expression: Match(%VpropEmailArray;"([^,]*){1}$";true)
ACTION: Reformat email address
Set Property to Expression:
Property: propReformattedEmailAddress
Expression: Replace(%VpropEmailAddress; "--"; %K00728; true)
//The above two actions could be combined, but I've kept them separate for readability of the regular expressions.
ACTION: Replace email addr KW w/reformatted email addr
Replace Keyword
Keyword Type: Email Address
Old Keyword:
Property Name: propEmailAddress
New Keyword:
Property Name: propReformattedEmailAddress
//The next step is the most important - removing the processed email address element from the string!
ACTION: Remove email address from string
Set Property to Expression:
Property: propEmailArray
Expression: Match(%VpropEmailArray;".*\w(?=,)";true)
TASK LIST: Update Email Address
