<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
0D54z00007TeTwxCAFOkta Identity EngineWorkflowsAnswered2022-03-02T20:32:20.000Z2022-02-25T22:30:47.000Z2022-03-02T20:32:20.000Z
  • FrankL.41685 (Customer)

    Thanks Natalia! I'm looking for information for processing a comma separated text output efficiently in Workflows.

  • TimL.58332 (Workflows)

    @FrankL.41685 (Customer)​ What you are asking is possible but each are different and use pretty round-about methods. The main issue is turning type "text" into type "file". You would need to pass it into a table then export the table to make it a type file.

     

    The "list" part is easy. That can be performed with "split". But it really depends on your source data and its structure. For example something like val1,val2,val3 "split" on "," would result in a list:

    val1

    val2

    val3

     

    However, if you have say headers: val1, val2, val3 (return carriage) 1,2,3 (return carriage) a,b,c (return carriage) and so on. It gets more complicated.

     

    Can you provide an example of the "CSV" you want to convert?

     

    Also, the actual use case would help too.

     

    Edit: Additionally, splitting on return carriage was easier than I thought. It is described in the help: https://help.okta.com/wf/en-us/Content/Topics/Workflows/function-reference/Text/text_split.htm

     

     

    Expand Post
  • FrankL.41685 (Customer)

    Hey Tim! Thanks for the writeup and suggestion! I did something similar with the "split" and "slice" to do a very hardcoded workflow for this. I have the example CSV uploaded to Case  01327143 if you want to take a look!

     

    Thanks,

    Frank

    Expand Post
  • TimL.58332 (Workflows)

    @FrankL.41685 (Customer)​  We put together an example flow that I believe meets your needs. There is definitely "some" manual setup required if the column structure changes. Essentially, the flow "normalizes" the sample data you provided. Separates the headers from the body. Turns the body into one large list. Then passes the large list into a helper flow using (Call flow). Inside the call flow it then slices out a segment of the list to create a row in the table. It then slices the list removing the already processed information and passes the new list back through the helper flow to repeat until the entire list is empty.

     

     

    Expand Post
This question is closed.
Loading
Okta Workflows - Text output to CSV or list