In that case, are you storing them as text values or as bit/boolean columns?

When you retrieve a checkbox field in workflow, there are "Is Set" values for each of the options.

If your columns are bit/boolean you can probably use those values directly, but if you're storing them as text values you'll need to do something more complex with some kind of conditions for each of the values.

Basically, think of columns as 1 dimensional like a line, but checkbox values are 2-dimensional like a set of rows, so in order to "flatten" than into columns for a single row you need to map them to other tokens.

For example, create a token for each column in your row, use the Is Set values in conditions, update the column tokens for the values that are selected, and then use all the tokens in the data insert.

You can use the NULL formatting option to treat empty values as "NULL" if you want them to be null rather than just empty strings in the database.

Token Formatting--Empty Tokens (laserfiche.com)

No, you want to keep that first Assign Token Values to create the tokens so they always exist, but create them without a value.

It's important to understand that Tokens in workflow are variables. They are used to hold values, but they can also be empty, so think of them like containers for the different values used in the workflow.

You need to create all those column Tokens so they exist and can be referenced, but in your case you only need to set a value if certain conditions are met. They always need to be created so you can reference them in the Insert Data activity without any errors, but they can absolutely be blank/empty.

As for the null value, the formatting is used when you use the tokens somewhere. For example, in your "Insert Data" activity, if you right click on one of the tokens where you're setting the value and open the Token Editor, you will see format as one of the options.

The formatting tells workflow how to "interpret" the data stored in the Token.

You want to create the tokens so you can use them in the Insert Data activity, but you only want them to have values if the conditions are met.

So you would reference "Is Set" in the Branch conditions.

The idea is that "Is Set" should only be used for the conditions because you don't want to store the true/false, you only want to use it to check if you need to set a value for the Tokens.

As a result, you'd start with your column tokens all empty.

Next, each branch would check "Is Set" to determine if you need to set a value for the associated token.

Create the empty tokens

Set your branch conditions

Set the values you want to use if the box is checked (i.e., if "Is Set" is true)

Then, use the tokens you created in the Insert Data.