Personalization Utilities

Hello,

we are developing a process to reset the user's password when the password is expired or forgotten.

This is because the client's policy does not allows the default reset functionality by sending mail, in fact the client does not want allow this kind of email.

We used then your smart service "Create User With i18n" in order to reset a password but  if we try to reset a password for an existing user, a message appears:

---------------------------
The following fields have invalid characters [Username: J50344] *Name fields may only contain letters, numbers, whitespace, and
the _ or - special characters and username can only contain letters, numbers, and the following special characters: @ . _ - .
It must not match an existing username regardless of case.
-----------------------------------

We tried then to disable the user and try again the process, but the result was the same.

Could you please help to understand how to use this smart service to reset password ?

Thank you in advance, best regards, looking forward to hear from you.

• Import Users from CSV smart service will now update existing user accounts in addition to creating new accounts.

Hi Eduardo,

We are upgrading our platforms to New Appian version 20.1. Can we expect an updated version of this plugin to support on Latest Version of Appian as It shows Compatible Version(s): 7.8+, 17.3

Thanks

Thanks justins797, we're concerned about the same issue.  Do you happen to know if the false positive reporting of removed/deprecated APIs is an overall issue with the health check?  Or is the Personalization Utilities plugin the only one affected?

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?