• State Not Answered
  • Replies 4 replies
  • Subscribers 62 subscribers
  • Views 1832 views
  • Users 0 members are here
Options
Related

Active Roles Web UI boolean value default to true

leejohnc
over 3 years ago

Is there a way in the ARS web ui to set a virtual attribute boolean value to a default?  I have a boolean VA on a web form that isn't populated.  Not all users are created by the sync service, so I need this attribute to default to true, regardless how a user was created.  I would prefer to have the value propagate when the form is opened (even if i have to use a scratch attrib not stored in the db, and retrieve that to put in the va that is stored in the db).

  • 0 over 3 years ago

    A property value generation policy rule can do this.  Just add it to a provisioning policy linked to the OU(s) where you are creating your objects.

  • 0 over 3 years ago in reply to JohnnyQuest

    I can do that, and it will apply the policy slowly to hundreds of thousands of objects when I 'check policy'.  I wish Quest would make the VA's stored in the DB obvious so you can do an UPDATE sql statement.  It would be a damn sight faster.

  • 0 over 3 years ago in reply to leejohnc

    You can identify Virtual Attributes in the Database by GUID, but updating the configuration DB directly  is not advisable unless you have a very specific requirement and do a database backup prior to running any SQL Queries against the DB...

    Why not just do a Sync Service "update" Workflow that Scoping the Updates to Only Users that do not have the value set to true or blank etc to true. You could also create a Workflow in ARS With a search activity and update users that do not have the Virtual Attribute Value Set to true. is right, an ARS policy will catch all new users created in this OU and write the value to true.

  • 0 over 3 years ago in reply to Jason.Griggs
    Jason.Griggs said:
    is right, an ARS policy will catch all new users created in this OU and write the value to true.

    Indeed this is how I understood the requirement.  In the original post, the ask was to have this attribute set to TRUE regardless of how a user is created - including in the Web UI.  My interpretation of that was therefore that it should show as TRUE in the User Creation Wizard.  Updating the state of the property on existing objects is a different kettle of fish and as  indicated, could be accomplished with an Automation workflow.  It would contain a search activity and a property update activity - codeless!!!