Workflows Tips #18: Access All User Properties, Output for If/Else Condition, and Partial User Update
Tags: nocode, workflows, okta, ipaas
Published: 2022-08-25 18:48:55

---
title: Workflows Tips #18: Access All User Properties, Output for If/Else Condition, and Partial User Update
published: true
date: 2022-08-25 03:59:39 UTC
tags: NoCode,Workflows,okta,ipaas
canonical_url: https://maxkatz.net/2022/04/28/workflows-tips-18-access-all-user-properties-output-for-if-else-condition-and-partial-user-update/
---

Welcome to another Okta Workflows Tips post. Read all other tips ⤵️
{% embed https://dev.to/oktaworkflows/okta-workflows-tips-57bj %}
In this post:

- Use Read User card to access all user properties
- How to create output for an if/else condition
- How to do a partial user update

## How to use Read User card to access all user properties

When an Okta connection event fires it makes available many properties associated with the event. Some of the properties are user-related (under **Okta User** ). An Okta user has many more properties (and custom properties). To access all the properties use **Okta – Read User** card.

[![Using Read User card to read all user properties](https://katzmax.files.wordpress.com/2022/04/workflows_tips18_readuser.png?w=915)](https://katzmax.files.wordpress.com/2022/04/workflows_tips18_readuser.png)
<figcaption>Using Read User card to read all user properties</figcaption>

To see (and show/hide) all properties, click the **gear** icon in the card’s lower right and then select **Choose fields**. You can select what attributes to show on the card.

[![Choosing what attributes to show](https://katzmax.files.wordpress.com/2022/04/workflows_tips18_readuser2.png?w=434)](https://katzmax.files.wordpress.com/2022/04/workflows_tips18_readuser2.png)
<figcaption>Choosing what attributes to show</figcaption>

## How to create output for an if/else condition

The **Branching – If/Else** allows you to create a card output. The output will be set to value from either the true or the false condition. For example, you can use the output to compose a dynamic message. Here is how to create such output:

[![Creating output for If/Else card](https://katzmax.files.wordpress.com/2022/04/workflows_tips18_ifelse_animated.gif)](https://katzmax.files.wordpress.com/2022/04/workflows_tips18_ifelse_animated.gif)
<figcaption>Creating output for If/Else card</figcaption>

## How to do a partial user update

The Okta – Update User card has a number of important properties that you need to be aware of when updating a user profile.

[![Update User card](https://katzmax.files.wordpress.com/2022/04/workflows_tips18_update_user1.png?w=403)](https://katzmax.files.wordpress.com/2022/04/workflows_tips18_update_user1.png)
<figcaption>Update User card</figcaption>

There are two update options available **Partial** and **Strict** :

[![Update User options](https://katzmax.files.wordpress.com/2022/04/workflows_tips18_update_user2.png?w=504)](https://katzmax.files.wordpress.com/2022/04/workflows_tips18_update_user2.png)
<figcaption>Update User options</figcaption>

From Workflows [documentation](https://help.okta.com/wf/en-us/Content/Topics/Workflows/connector-reference/okta/actions/updateuser.htm):

> `Partial`: Updates a user’s profile or credentials with partial update semantics. Any properties that are not specified are ignored, and will maintain their current value.  
> `Strict`: Updates a user’s profile and credentials using strict-update semantics. IMPORTANT: All profile properties must be specified when updating a user’s profile. Any property not specified in the request is set to null.
> 
> <cite><a href="https://help.okta.com/wf/en-us/Content/Topics/Workflows/connector-reference/okta/actions/updateuser.htm" rel="nofollow">https://help.okta.com/wf/en-us/Content/Topics/Workflows/connector-reference/okta/actions/updateuser.htm</a></cite>

When you choose the **Partial** option, an option called **Pass Empty Values?** becomes available. It works like this:

> If `Yes`, all fields selected and filled in with valid values will be updated. All fields selected but left blank will be cleared, except special fields. See the note below. All fields unselected will remain unchanged.
> 
> If `No`, all fields selected and filled in with valid values will be updated. All fields unselected or left blank will remain unchanged.
> 
> <cite><a href="https://help.okta.com/wf/en-us/Content/Topics/Workflows/connector-reference/okta/actions/updateuser.htm" rel="nofollow">https://help.okta.com/wf/en-us/Content/Topics/Workflows/connector-reference/okta/actions/updateuser.htm</a></cite>

It’s import you are aware of this options as they can significantly change how the update works.

* * *

Two resources to help you learn more:

📌 Try this step-by-step getting started tutorial: [Build Your First Automation With Okta Workflows: Notify When User Is Suspended](https://dev.to/maxkatz/build-your-first-automation-with-okta-workflows-notify-when-user-is-suspended-1l3p-temp-slug-2933517).

📌 All the [Workflows resources](https://dev.to/maxkatz/okta-workflows-resources-1ebi) (docs, tutorial, office hours, templates, office hours and more)