0 votes


I´m trying to customize the user creation process, that it is possible to define the user account activation date (when the account gets enabled) and the expiration date of the account.
I used two custom Adaxes attributes called CustomAttributeDate1 (Activation Date) and CustomAttributeDate2 (Expiration Date) in my form.

Everything woks fine, a scheduled task enables the account when the date is reached and the expiration date is set correctly.
But I want to limit the expiration date in the web form, that a requester cannot set the expiration date higher than activation date + 14 days.

When I open the properties of the AccountExpiration property name, I can only choose a date for "must be one of the following values only".
It is possible to copy something from the clipboard, but I don´t no how the expression could look like.

Could you please tell me, if something is possible?

Thank you

by (240 points)

1 Answer

0 votes
by (215k points)


Yes, that's possible, but not with Property Patterns. You can create a Business Rule triggered Before Creating a User. The Business Rule will cancel creation of a new user if the expiration date doesn't fit within your time limit. To create such a Business Rule:

  1. Create a new Business Rule.
  2. On the 2nd step of the Create Business Rule wizard, select User and Before Creating a User.
  3. On the 3rd step, add the Cancel this operation action and, optionally, specify a reason for canceling.
  4. Click OK.
  5. Now, you need to specify a condition when user creation must be canceled. Right-click your action and click Add Condition.
  6. Select the If <property> <relation> <value> condition type.
  7. Expand the <property> drop-down list.
  8. Select the Show all properties option.
  9. Select the CustomAttributeDate2 property.
  10. Select greater or equal.
  11. Click the Edit button embedded in the <value> field.
  12. Activate the Generate date tab.
  13. Expand the Set the date drop-down list.
  14. Select the Show all properties option.
  15. Select the CustomAttributeDate1 property.
  16. Specify plus 15 days.
  17. Click OK two times and finish creation of the Business Rule.

Related questions

0 votes
1 answer

I've enabled the "Account Expiration Notifier" builtin scheduled tasks. Currently, I'm testing it so I have "If account will expire in less than 300 days", it will send an ... SMTP settings are correct, seeing as I get the test send. What's going on here?

asked Jan 4, 2021 by keecit (40 points)
0 votes
1 answer

Hello, we're currently having issues to disabling user accounts on a specific date and time. When our HR department wants to start a "Offboarding", we're created a ... can we link it to the *After approval of disabling account field? Thanks in adavantage.

asked Aug 24, 2021 by BeliarsFire (20 points)
+2 votes
1 answer

I am attempting to build out a report that shows all user accounts were approved by two different persons before being created. I have the workflow running correctly, ... this data stored in a specific location thats accessible by the reporting engine? Thanks!

asked Dec 16, 2019 by hendersonw (210 points)
0 votes
1 answer

Hi, I'm trying to see if there's a way where from the web interface, I can have a simple single display to set an account expiry in the future. I don't ... to restrict other fields from being visible from other options, like Modify User. Is this possible?

asked Feb 24, 2016 by AdamFowlerIT (120 points)
0 votes
1 answer

Right now I have a scheduled task that runs on all user accounts and sends and HTML email to users when their password will expire. The problem with this method is that ... to look for users with expiring passwords. I could use some help sorting that out.

asked Jul 10, 2020 by dtb147 (250 points)
2,803 questions
2,538 answers
63,854 users