Hello,
To reset the number in the global configuration, you can create an action for the Web Interface that allows you to input the initial number you want to set. The value from the action will be assigned to one of Adaxes virtual attributes of the user who launches the action. Such virtual attributes that are not stored in Active Directory, but you can use them in Adaxes the same as any regular attribute of AD objects. Also, you can create a Business Rule that will be triggered when the virtual attribute is modified to launch a PowerShell script. The script will update the number in the global configuration setting to the value that you specify.
For information on how to implement such a solution, see the following post on this support forum: Custom Command That Does Not Execute on Object. The initial number that will be set in the global configuration will be passed via the CustomAttributeInt1 virtual attribute, which you will need to add to the form used by the action. On step II.3 of the post, you need to use the following script:
$number = $Context.TargetObject.Get("adm-CustomAttributeInt1")
$settingsPath = $Context.GetWellKnownContainerPath("ConfigurationSetSettings")
$settings = $Context.BindToObject($settingsPath)
# Save the new number in the gloabal settings
$settings.Put("adm-CustomAttributeInt1", $number)
$settings.SetInfo()
# Clear custom attribute from user
$Context.TargetObject.Put("adm-CustomAttributeInt1", $NULL)
$Context.TargetObject.SetInfo()