Software Development

Workflows Tips #43: Multi-Tier JSON Object, Using Atlassian Assets With Workflows, Searching Flow History and Allowing Delegated Admins to Run Flows

Welcome to another Okta Workflows Tips post. Read all previous tips.

In this post:

  • Creating a multi-tier JSON object
  • Using Atlassian Assets with Okta Workflows for asset management
  • Meetup replay: searching flow history and allowing delegated admins to run flows

Creating a multi-tier JSON object

This tip is from Daniel Kuchenski, Director of IT and automation enthusiast.

This is a truly sweet tip. You can create a multi-tier JSON object with a single Object-Construct card.

Notice that the field name, user.email, uses a dot-notation:

Object-Construct card

Result testing this card:

Testing the Object-Construct card

JSON result:

{    "user": {       "email": "user@okta.com"    } }

Thanks Daniel for this great tip!

Using Atlassian Assets with Okta Workflows for asset management

Bilal Habib, IT Infrastructure Engineer for MADE.COM, wrote a blog post Using Atlassian Assets with Okta Workflows for asset management. In the blog post you will learn they use Atlassian Assets and Okta Workflows for part of their asset management. 

At made.com we use Atlassian Assets for asset management. This wasn’t always the case. We used to use Google Sheets as a source of truth for all of our asset management. This did not work. We had many problems with it, and over time we tried different solutions. Eventually, our security team found Atlassian Insight and started using it for their assets. Their experience turned out so great that we decided to trial Atlassian Insight for our IT asset management. It brought us great benefit, such as splitting the assets down into different objects, an object for hardware and an object for the owners ‘People’. This helps to solve a problem, such as tracking down what devices someone owns and having an easy history overview.

In this blog I’ll showcase how we use Okta Workflows to generate a ‘People’ asset. In Atlassian Assets you can link objects with other objects, so in our case we can link a People object with an object defined for a laptop. The possibilities are endless. At MADE we also consider contracts and risk owners as assets as well.

https://io.made.com/2022-10-24-using-atlassian-assets-with-okta-workflows-for-asset-management/

Continue reading

Meetup replay: searching flow history and allowing delegated admins to run flows

We hosted another online meetup covering how to search flow history and allow delegated admins to run flows. In case you missed it, hit the link below to watch a replay and read the Q&A. And, don’t forget to subscribe our Crowdcat channel to get notified when we live.

Published on Java Code Geeks with permission by Max Katz , partner at our JCG program. See the original article here: Workflows Tips #43: Multi-Tier JSON Object, Using Atlassian Assets With Workflows, Searching Flow History and Allowing Delegated Admins to Run Flows

Opinions expressed by Java Code Geeks contributors are their own.

Subscribe
Notify of
guest

This site uses Akismet to reduce spam. Learn how your comment data is processed.

0 Comments
Inline Feedbacks
View all comments
Back to top button