Personalization Utilities

Update: The Appian Health Check report was reporting back false positives as high risk. Please ignore my original message.

It throws an error saying that the function can't accept null parameters even if you actually pass parameters to it.

Here is the actual error message:

2020-02-07 13:36:31,484 [ajp-nio-8009-exec-5] ERROR com.appiancorp.process.engine.ExpressionGroup - An error occurred while evaluating expression: deactivatedUsers:fn!getdeactivatedusersby(
    field: "email",
    value: ".",
    operator: 2
  ) (Expression evaluation error at function fn!getdeactivatedusersby: Null argument not allowed)

Dan and Jacob Edelman I've reached out to the developers to request a new version of the plug-in

May I know what function in particular? getDeactivatedUsersBy() ? What does it do?

We just updated to 19.2 and now the function doesn't work anymore.  Did you find the issue?

We are using this plug-in, and in Appian health check report it's flagged as high risk because it's referencing the removed/deprecated Appian APIs. So, will there be an update that will address these issues?

Sounds good, thank you!!

Hi tylerb844 there is no limit but ideally batching or off-hour execution is preferred

Hi,

Is there a limit to the number of members who can be deactivated using the deactivate users smart service?

I'm running into an issue with the getDeactivatedUsersBy() function. The error being thrown is that I am passing a null parameter even though I am providing values for each of the inputs. Has anyone else run into an issue with the plugin? We are on version 19.1 and the function call I have setup is fn!getdeactivatedusersby(field: "email", value: ".",operator: 2) - the goal being grab all deactivated users (all valid email addresses should have a period in them)