BillG.78194 (Customer) asked a question.
We are trying to automate an up to date table of our Okta Workflows. We can pull entire folders/flows with those export cards and upload them to a Google Drive/Github/etc., and we can collect information about workflows being created/deleted/activated/etc. from the log stream via Cloudwatch.
However, as best I can tell, there is nothing in the export as far as a workflow or folder uuid that correlates to the system log at all. The system log exports the ulid (currently a string of numbers, soon to be a longer string I believe) and the export pushes a very long string that isn't remotely similar for the uuid key/value.
Flow/Folder name is the same across both, but obviously as soon as a name is edited that connection would be broken.
Is there any way at all to correlate the system log stream workflow events to their corresponding workflows in an export?
@BillG.78194 (Customer) -- I am pretty sure the related events were updated in Production as of yesterday. For example here are some snippets from an event where I activated a flow. The Events and the "links" are now associated to a specific flow.
"displayMessage": "Flow activated",
"eventType": "workflows.user.flow.activate",
"target": [
{
"id": "00org73zewDVg0WjE5d6",
"type": "AppInstance",
"alternateId": "Okta Workflows",
"displayName": "Okta Workflows",
"detailEntry": null
},
{
"id": "01J07RMFV5W9G7A8XVAT7WA99Y",
"type": "Flow",
"alternateId": "dataConvertHelper",
"displayName": "dataConvertHelper",
"detailEntry": null
}
]
Here is an example History URL from that flow. Note the ID's match on the type: Flow
https://tlaborninc.workflows.okta.com/app/flows/01J07RMFV5W9G7A8XVAT7WA99Y/history/1acd4fbb-96d7-4ada-a8d3-9b4b402e6fa7
Folder/Flow names also will not change the identifier. So moving them inside the Workflows UI will not change them. So it can still be challenging to find where they are located if you have a lot of folders/flows. Since you will have to construct the URL https://subdomain.workflows.okta.com/app/flows/ID/ to "open" the flow. You can then view the folder name they are currently in.
Now Exports of Folders / Flows are not going to have an associated ID with them stored in their JSON as they are essentially "Blanks" and have ID's associated when they are imported into a system.