0 votes

image.png

image.png

Any advice would be greatly appreciated.

by (330 points)

1 Answer

0 votes
by (270k points)

Hello,

If you need the business rule to work exactly as you have it configured, but not get into a loop is perform the Account Expires property update using a script that will not involve the Adaxes pipeline. However, in this case the operation will not be logged in Adaxes. If the approach meets your needs, here is the script:

$Context.TargetObject.Put("accountExpires", "%accountExpires,-1d,18:00%")
$Context.TargetObject.SetInfo()

Related questions

0 votes
1 answer

We have a customized the help desk security role to allow only resetting passwords and unlocking accounts. We don't want them to be able to enable accounts that are disabled ... writing to certain "account options"? It seems that its an all or nothing setting.

asked Nov 14, 2019 by mark.it.admin (2.3k points)
0 votes
1 answer

Hi: I am trying to create a business rule that will stop a value change based on the existing value. For example, if the telephonenumber is 1234 for a group and has to ... the value it uses is the incoming value of the change, not the existing value. Thanks!

asked Jun 3, 2022 by crobitaille (80 points)
0 votes
1 answer

We have some accounts that we would like to prevent from changing their password on login when it is expired. This is because we have saml setup on individual interface pages ... of a loophole for us as we require dual factor and use saml to accomplish this.

asked Oct 26, 2021 by mark.it.admin (2.3k points)
0 votes
1 answer

Or is there another solution to solve this?

asked Sep 15, 2022 by boris (450 points)
0 votes
1 answer

Thanks for the info. I'm now grabbing the %adm-ManagerUserName% value, but need to remove the final 21 characters of it so it contains only their username and not our ... this in the PowerShell Script Editor for my business rule, I get the following error:

asked Mar 11, 2021 by mkvidera (60 points)
3,326 questions
3,026 answers
7,727 comments
544,682 users