Thursday, May 2, 2024
HomeJavaWorkflows Ideas #43: Multi-Tier JSON Object, Utilizing Atlassian Property With Workflows, Looking...

Workflows Ideas #43: Multi-Tier JSON Object, Utilizing Atlassian Property With Workflows, Looking out Movement Historical past and Permitting Delegated Admins to Run Flows – Java Code Geeks


Welcome to a different Okta Workflows Ideas submit. Learn all earlier suggestions.

On this submit:

  • Making a multi-tier JSON object
  • Utilizing Atlassian Property with Okta Workflows for asset administration
  • Meetup replay: looking circulation historical past and permitting delegated admins to run flows

Making a multi-tier JSON object

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

It is a actually candy tip. You may create a multi-tier JSON object with a single Object-Assemble card.

Discover that the sphere identify, person.e-mail, makes use of a dot-notation:

Object-Assemble card

End result testing this card:

Testing the Object-Assemble card

JSON end result:

{    "person": {       "e-mail": "person@okta.com"    } }

Thanks Daniel for this nice tip!

Utilizing Atlassian Property with Okta Workflows for asset administration

Bilal Habib, IT Infrastructure Engineer for MADE.COM, wrote a weblog submit Utilizing Atlassian Property with Okta Workflows for asset administration. Within the weblog submit you’ll be taught they use Atlassian Property and Okta Workflows for a part of their asset administration. 

At made.com we use Atlassian Property for asset administration. This wasn’t at all times the case. We used to make use of Google Sheets as a supply of fact for all of our asset administration. This didn’t work. We had many issues with it, and over time we tried completely different options. Finally, our safety workforce discovered Atlassian Perception and began utilizing it for his or her property. Their expertise turned out so nice that we determined to trial Atlassian Perception for our IT asset administration. It introduced us nice profit, reminiscent of splitting the property down into completely different objects, an object for {hardware} and an object for the homeowners ‘Folks’. This helps to resolve an issue, reminiscent of monitoring down what gadgets somebody owns and having a straightforward historical past overview.

On this weblog I’ll showcase how we use Okta Workflows to generate a ‘Folks’ asset. In Atlassian Property you may hyperlink objects with different objects, so in our case we will hyperlink a Folks object with an object outlined for a laptop computer. The probabilities are limitless. At MADE we additionally take into account contracts and danger homeowners as property as effectively.

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

Proceed studying

Meetup replay: looking circulation historical past and permitting delegated admins to run flows

We hosted one other on-line meetup overlaying tips on how to search circulation historical past and permit delegated admins to run flows. In case you missed it, hit the hyperlink beneath to observe a replay and skim the Q&A. And, don’t neglect to subscribe our Crowdcat channel to get notified once we stay.

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments