How can I establish a completly different Onboarding Job, so that the mandatory fields (Property pattern) from the normal "create user"-Job will be ignored.. Or in other words, how can I assign the required properties differentially?
Hello Boris,
It can be done by adjusting property pattern scopes accordingly. For details, have a look at section Different patterns for different users of the following tutorial: https://www.adaxes.com/help/MakePropertyRequiredAndSpecifyFormat/#different-patterns-for-different-users.
Is it possible to create a scripted action to create a new scheduled job, and for the job to delete itself when complete? Scenario is an over-night callout that requires a support user ... e.g. Will not run between 9am - 5pm, but will between 5pm - 9am. Rgds
During the creation of a new user I want to be able to select the job title from a drop-down list which populates different values based on which Department is selected. Is there a way to achieve this? Thanks. Dario.
We have a property pattern for a user's job title that lists all the aviable titles. I need to be able to add a new constraint to this within a custom command and from Powershell on a differant computer. Would you be able to help?
Hi there, i've a custom command with multiple powershell scripts (for clearance reasons). If for example the frist script produces an error i Write an Error but the next ... tried with an simple exit 1; I only Write-Errors on issues. Kind regards, Constantin
Hello I try to create a form that lets HR create a user themself, but they need the approval from the IT-Department, so the IT-Department can check the new employees personal data and configure their pc. Or do you have an alternative idea for this process?