Hello,
The thing is that once an operation is initiated, Adaxes collects all Business Rules that will be triggered by the operation and resolves all value references (such as, for example, %unicodePwd% that you can use in emails to insert the new user's password). Only after resolving all value references Adaxes starts performing the actions. That is, the %unicodePwd% value reference gets resolved before you change the user's password in your Business Rule.
By the way, why don't you use the method provided in the following tutorial to generate a random password: http://www.adaxes.com/tutorials_Simplif ... eation.htm? If you use the %adm-RandomString% value reference on step 3 of the tutorial, the password will be set to a random sequence of characters. For example, %adm-RandomString,12% will generate a random password of the length of 12 characters. If you use this method for generating random passwords, the generated password will be included in your Welcome E-mail.
If, for some reason, you don't want to generate a random password with a Property Pattern using the method provided in the above tutorial, you'll need to send the Welcome E-mail with a script.