The round robin assignment of leads

lalitrane · 2 November 2020 20:56

Hi,

I am having a issue with the round robin lead assignment in Version 7.10.28

This workflow is running ‘always’ -

Condition -> Modules --> Language --> Equal To --> One of --> ‘blank’, Mandarin, Hindi, German.
Action --> Modify Record
2a. Record Type = Lead
2a1. Assigned To --> round robin --> ALL Users in Security Group --> Secruritygroupname

Expected Behavior
The round robin assignment should be excluding inactive user or employee status = terminated.

Actual Behavior
The round robin assignment is including the inactive user or employee status = terminated.

Does anyone know any workaround for this issue?

pgr · 3 November 2020 11:05

Hi, welcome to the Community!

I don’t really know the answer, but after a quick look at the code I would start digging here:

github.com

salesagility/SuiteCRM/blob/master/modules/AOW_Actions/actions/actionCreateRecord.php#L285


    }
    $value = $timedate->asDb($value);
    break;
default:
    if ($params['value'][$key][0] === 'now') {
        $date = gmdate($dformat);
    } elseif ($params['value'][$key][0] === 'field') {
        $dateToUse = $params['field'][$key];
        $date = $record->$dateToUse;
    } elseif ($params['value'][$key][0] === 'today') {
        $date = $params['value'][$key][0];
    } else {
        $dateToUse = $params['value'][$key][0];
        $date = $bean->$dateToUse;
    }

    if ($params['value'][$key][1] !== 'now') {
        $value = date($dformat, strtotime($date . ' '.$app_list_strings['aow_date_operator'][$params['value'][$key][1]].$params['value'][$key][2].' '.$params['value'][$key][3]));
    } else {
        $value = date($dformat, strtotime($date));
    }

The idea would be to add more conditions (optional_where parameter) to those get_linked_beans calls. Alternatively, add an if testing conditions before adding them to the $users array.

Of course, this only makes sense if you are a developer - if not, you can always open an issue on Github asking to add this…

lalitrane · 5 November 2020 20:18

Thanks pgr for your response. Unfortunately i am not a developer hence the code doesn’t make much sense to me. I have raised this issue on Github as well, hopefully it will get resolved there.

Do you happen to know any work around to get past this issue?

Thanks again!

pgr · 6 November 2020 10:30

Sorry, I don’t know of any workarounds…

For reference, here is the Issue:

I wouldn’t expect that to be fixed anytime soon, if I were you. You might be better off paying a developer to fix it for you, it doesn’t have to be too expensive. With luck, it’s a quick fix.