<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
0D54z00008s5MuBCAUOkta Identity EngineWorkflowsAnswered2024-04-16T11:10:07.000Z2023-03-01T16:34:07.000Z2023-03-07T07:13:38.000Z
  • TimL.58332 (Workflows)

    This does not currently exist as an option. I think something along this line might be on the roadmap. With that said. What some customers do will be to build out their own logging (often just recording failure conditions such as unmatched users, errors, etc..) to a table. It can then be exported as CSV and sent somewhere on a regular interval.

     

    Additionally, in the Syslog there have been some additional new workflows related events that record "changes" in workflows (not execution related). These can all be listed with:

     

    eventType co "workflows.user"

     

     

    Expand Post
  • CasperP.11596 (Customer)

    Hi Tim,

    We can add push data to a table, but it would be some much nicer (and easier) if it would be possible to export the flow data to a json file - that way we can easily use that data for verification.

    It would be nice if could be added to the product.

    Thanks,

    Casper

    Expand Post
  • TimL.58332 (Workflows)

    @CasperP.11596 (Customer)​  - If it is functionality you would like to see in the product then definitely create an idea (https://ideas.okta.com).

     

    The history as some sort of export is going to be complicated as context will be lost if it is just exported out as plain text. Currently the design of the current flow is just "filled in" based on the unique identifiers of the existing cards. If that context is removed then the data makes far less sense.

     

    As an example of what I mean I created 3 assign cards. The first assign card sent data to the second card, then the second card to the third card. I ran the flow, then deleted the middle assign card and re-added the card. Since each time you create a new card it is essentially just a unique identifier. Since the identifier changed the data no longer has context and can't map.

     

    image

    Expand Post
  • CasperP.11596 (Customer)

    @TimL.58332 (Workflows)​, I umderstand why you might see it like that, but I suspect that the data already is stored in some form or another, like for example JSON. If I could get my hands on that JSON then I could parse it and get the data I need to do validation.

     

    I will add it to ideas.okta.com.

     

    Thank you.

    Expand Post
This question is closed.
Loading
Workflow history Export ?