When creating a scheduled task, you select Object type. e.g.: User => can you add extra (LDAP) filters

Question

When creating a scheduled task, you select Object type. e.g.: User but can you add an additional filter, eg. where deparment is a value (HR, IT, ...) or where an extensionAttribute15 equals 'Mailbox'?

We have an external process (SFProvisioning) and HR or other people can request a mailbox for a person. We like to do this with a custom commend that set a value in AD e.g.: ExtAttrib15 and then run a scheduled task on all objects that have this value set to a specific value.

In a custom command you have when starting the 'pop-up' are you sure and at the end the summary witht the execution log.

Can you customize these pop-ups and/or can you during the progress of the CC add an extra pop-up when e.g more information from the requestor is needed?

Answer 1

Hello,

When creating a scheduled task, you select Object type. e.g.: User but can you add an additional filter, eg. where deparment is a value (HR, IT, ...) or where an extensionAttribute15 equals 'Mailbox'?

Unfortunately, there is no possibility to add filtering for the objects in the Activity Scope. However, you can use conditions in the scheduled task itself. For details, have a look at the following tutorial (step 9 seems to be exactly what you need): https://www.adaxes.com/help/ScheduleTasksForDirectoryManagement.

Can you customize these pop-ups and/or can you during the progress of the CC add an extra pop-up when e.g more information from the requestor is needed?

You can configure the confirmation notification for all custom commands or disable it entirely. The notification can be specified on the first step of the custom command creation wizard. To modify the notification for an existing command, select the command in the Administration console and click Edit next to Confirmation in the top right corner.

Unfortunately, there is no possibility to have pop-ups to request additional details during the process of the custom command execution. It can be only done using parameters as the first step before the execution itself. For details on using custom command parameters, have a look at step 5 of the following tutorial: https://www.adaxes.com/help/CreateCustomCommand.