Trying to append description

Question

Have a custom new user form that has a list of departments and I am trying to append the description so if the someone selects multiple departments, the multiple departments are listed in the description.

Current simplified business rule:

If(location name)property equals (location) then
Modify the user: set Description to '(location)'

Further down in the rule:

If (department name) property equals 'Yes' then
Modify the user: set Description to '%description% (Department Name)

Seems to work fine when I only do one department. Getting a description of (location) (Department Name), but if multiple departments are selected, the description just changes to (location) (last department selected). According to the execution log: the previous department name just gets overwritten.

Any ideas?

Comments

Hello,

Sorry for the confusion, but we are not sure what exactly you have configured. The department property is singlevalued and there is no possibility to specify multiple departments in it. Could you, please, post here or send us (support@adaxes.com) a screenshot of the business rule you have?

---

Sorry,

I have created custom attributes for each of our departments because I could not use the department field, since it only allows a single choice.

When I say department name, I'm just referring to the custom attributes that have been created.

---

Hello,

Thank you for clarifying. For us to suggest a solution, please, provide a screenshot of the custom form with all the attributes that correspond to location and department names. You can post the screenshot her or send to us at support@adaxes.com.

Answer 1

Hello,

Thank you for the provided details and screenshots. The thing is that you have all the actions for updating the description property set in a single custom command right after each other using value reference %description%. All value references resolve into the corresponding values before executing the entire custom command (same works for business rules and scheduled tasks). As such only the last action in your command for incrementing description will work. This behaviour is by design and cannot be changed. To achieve the desired, you need to use the below script instead of all the actions/conditions in your custom command. In the script:

• $propertyToIncrementName – Specifies the LDAP name of the property whose value will be incremented.
• $propertyValueMap – Maps LDAP names of Boolean properties with the values that will be incremented to the value of the property specified in variable $propertyToIncrementName.

$propertyToIncrementName = "description"  # TODO: modify me
$propertyValueMap = @{
    "adm-CustomAttributeBoolean1" = "Tournament Office"
    "adm-CustomAttributeBoolean2" = "Bowler Service"
    "adm-CustomAttributeBoolean3" = "Bowling Ball Express"
    "adm-CustomAttributeBoolean4" = "Brackets"
    "adm-CustomAttributeBoolean5" = "Check In/Entries"
    "adm-CustomAttributeBoolean6" = "Finance"
    "adm-CustomAttributeBoolean7" = "Lane maintenance/Tech"
} # TODO: modify me


# Get value of the property to increment
try
{
    $propertyValue = $Context.TargetObject.Get($propertyToIncrementName)
}
catch
{
    $Context.LogMessage("Property $propertyToIncrementName is empty.", "Warning")
    return
}

# Get values to increment
$valuesToIncrement = @()
foreach ($keyValuePair in $propertyValueMap.GetEnumerator())
{
    try
    {
        $addValue = $Context.TargetObject.Get($keyValuePair.Name)
    }
    catch
    {
        continue
    }

    if($addValue)
    {
         $valuesToIncrement += $keyValuePair.Value
    }    
}

# Increment values
foreach ($value in $valuesToIncrement)
{
    $propertyValue = $propertyValue + $value
}

# Update the user
$Context.TargetObject.Put($propertyToIncrementName, $propertyValue)
$Context.TargetObject.SetInfo()