Welcome to another Okta workflow tips post. Read all previous tips.
In this post:
- Kandji video connector
- Build your first online workflow automation meeting without code
- Count the number of rows in a table
Workflows has a new Kandji connector that enables automation of Apple device management.
Watch this short video to learn how the Kandji connector in Workflow helps manage Apple devices:
The video features Arek Dreyer. Arek is a Senior Product Engineer at kandji.io, which provides next-generation Apple device management for macOS, iOS, iPadOS, and tvOS. Arek spent over 20 years as an independent trainer, author and consultant, and joined Kanji in 2021. He was very happy to discover the community of admins who love to help each other solve problems in the Okta Workflows space.
Online meeting: Build your first code-free workflow automation in 25 minutes
We have another online meeting without slides coming up 🚀.
🔮 Why it’s worth your time
Join this slide-free online meeting to learn how to create your first code-free workflow automation with Okta Workflows in 25 minutes.
🔭 You will learn
You’ll learn step-by-step how to create your first workflow automation without code, and also:
- Building a flow with the basic building blocks (events, schedule, actions, functions, and connectors)
- Flow testing and execution
And stay to get your questions answered. This is a session without slides (well, maybe just one or two at the beginning).
🎟 Register whenever
- When: Wednesday, September 28, 9am PT
- I want to attend: register now
📡 And one more thing, follow our events channel to get notified when we go live.
Count the number of rows in a table
To count the number of rows in a table, use Tables – Lookup Rows to search a table without a condition. This will return all rows (see note at the end for this). Then use List – Length map to return the number of items in the list.
It is just answer. It will work up to the map limit for search lines:
Maximum number of records to return. If no filter or constraint is applied to the table lookup, a maximum of 3500 rows from the selected table will be read from the Lookup Rows feature map.
This is a good solution if a table has less than 3500 records.
Here’s a solution from Tim LaBorn (Senior Technical Support Engineer for Workflows at Okta) if you have more than 3500 records:
The table itself has a maximum of 100k rows. It is possible to return a list of all rows, but this would require significantly more logic than the example provided. The lookup line map has the ability to set an offset. You could potentially create a helper flow that searches a table in a loop increasing by the offset value you use while combining lists until the search rows return no results, then stops the loop. The final combined table can then have the length used against it to get the total.