<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D54z00009v1EGCCA2Okta Identity EngineWorkflowsAnswered2026-03-16T09:00:23.000Z2023-12-19T21:35:32.000Z2023-12-21T15:14:20.000Z

7jv04 (7jv04) asked a question.

December 19, 2023 at 9:35 PM
How to change a custom attribute using Workflows

Hi All!

 

Relatively new here and I'm trying to simply update a custom Okta attribute "Pre-existing User?" which I created as a boolean type to show "true" when the user's last hire date is before (insert cutoff date of choice). My current flow validates if the user existed before just fine, but I haven't found a way to successfully set the boolean attribute as true in the Okta profile itself.

 

I'm just not yet finding the right way to change that profile attribute in Okta via Workflows. There is the Update Users Okta action card, which looks like what I need, but it is not updating the profile to change the boolean value to "true". I'm sure I'm missing something very simple.

  • 6 answers
  • 1.15K views

  • User15905896560008893663 (Vendor Management)

    Hi @7jv04 (7jv04)​ . Based on your first screenshot, you did not select the custom attribute in the input section, just the second one.

    Also, bare in mind that on your second screenshot, that has the custom attribute both in the input and output sections, it is set to string and not boolean.

     

    Expand Post
    Selected as Best

  • 7jv04 (7jv04)

    Update: Sort of figured it out using Assign If and using the output to set the value of true. This was my main objective. Curious why the attribute isn't changing to false when the condition is false... but technically I don't need it to for my use case.

    Image is not available
    ​

    Expand Post

  • User15905896560008893663 (Vendor Management)

    Hi @7jv04 (7jv04)​ . Based on your first screenshot, you did not select the custom attribute in the input section, just the second one.

    Also, bare in mind that on your second screenshot, that has the custom attribute both in the input and output sections, it is set to string and not boolean.

     

    Expand Post
    Selected as Best

  • 7jv04 (7jv04)

    Thanks Daniel! Very appreciated, however, I just found a completely different approach which was to simply write and expression in the HR to Okta mapping to set the boolean condition to true if hire date is before (date of choice). No need for a workflow. However, now I need to figure out if I can use an expression to create the user "login" attribute normally, or if they were hire after a particular date, then create their Okta "login" in the new format we decided to use going forward. Basically: if appuser.LastHireDate < ("2023-12-01T00:00:00") if false substring(appuser.EmployeeNumber, 3, 9) if true do nothing. I know IF is implied, but still trying to figure out Okta Expression syntax for "then"/"else".

    Expand Post

    • User15905896560008893663 (Vendor Management)

      You can use the if : else : expression

      For the first part would be something like this.

      [ (appuser.LastHireDate lt "2023-12-01T00:00:00")]

       

      You can use "and" an "or" to add more conditions inside.

       

      [ (appuser.LastHireDate lt "2023-12-01T00:00:00") and (substring(appuser.EmployeeNumber, 3, 9) eq 9) ] : true : false

       

      You would need top test and refine the expression as per your needs of course, but this would be the basics.

      Expand Post

  • 7jv04 (7jv04)

    I should add the whole goal her is to import pre-existing profiles without changing the attributes, unless they are new hires, then their login and email Okta attributes will be created following a new format. I hope that makes sense.

This question is closed.
Loading
How to change a custom attribute using Workflows