Changes

Different [[Password|In the upcoming November 2023 release, password]] [[Variables|variables]] can will be used depending on the [[Workflow|workflow]] task typedeprecated for improved security. [[UTA]] Activation task type uses @password@ Acknowledgment task type uses @randompassword@ or @checkactivatedpassword@  '''Task Type: User Activation''' * @password@ - Checks if All systems will be required to use the user is activated** if the [[User|user]] is not activated then generates a new random [[Password|password]] activation link variable (i.e. Your password is: ABCDEFGH)** if the [[User|user]] is activated then sends the text "current password" (i.e. Password is: current password)'''Task Type: Acknowledgment'''** <code>@randompasswordactivationlink@ - generates a new random [[Password|password]]** @checkactivatedpassword@ - checks if </code>) to send the [[User|user]] is activated*** if the [[User|user]] is not activated then generates to a new random [[Password|password]]*** if the [[User|user]] is activated then sends the text "existing password" (see '''Notes''' below)Because of the complex nature of the password creation and validation process it is not possible to automatically translate '''existing password''' into other languages. If you are sending an e-mail containing the @checkactivatedpassword@ variable you page where they can use the following syntax to display text other than "existing password" if required.*  For example, for an existing user the following will show the French translation of '''existing enter their desired password''' which is '''Mot de passe courant'''instead. If the user has not been previously activated the syntax will provide a randomly generated password as normal: <pre><!--@sscalculation(if(trim("@checkactivatedpassword@")="existing password","Mot de passe courant","@checkactivatedpassword@"))--></pre>