Task #1569
Updated by Radek Tomiška about 5 years ago
Working with provisioning operations is troublesome in current version. Some of the usecases, that cannot be solved using current agenda are: # * Execute all provisioning operations (on server, not one by one using UI, now we do it by modifying database data, so that the RetryProvisioningExecutor would do it for us) # * Filter provisioning operations by provisioned attributes (sometimes we would like to execute some operations, which should not be cancelled such as password provisioning and locking account in protection and cancel the rest) # * You can also consider implementing a View in which provisioning operations would be grouped into batches, that can be further expanded to see the individual operations contained in the batch