Automation - Create Org's from Assets with users

[Dominik Hebestreit]

Hi folks,

I have a question!

We have several stores (locations) with several employees.

I would like to use the Organizations function for our JSM project.

The aim is that if, for example, an employee from STore-001 creates a ticket, it automatically says “Share with Store-001” at the bottom.

As I have several locations with several employees, I would like to do this via the API.

Has anyone ever done this? I am currently trying to map this.

I have the schema “AD Azure” for the assets and there I have the object type “Locations”

Here are all locations with their USers.

My plan was:

1.) Scheduled task every day.
2.) Lookup Assets AQL -> objectType = "Locations" AND Name IS NOT EMPTY
3.) Branch....

Unfortunately I don't know how I can design this further, I've never worked with it before.

Does anyone have any ideas?

[Marc - Devoteam]

HI @Dominik Hebestreit 

You can't use the Organisations feature in relation to assets.

You can create your Organisations via the API, see.api-rest-servicedeskapi-organization-post 

You could then use the endpoint api-rest-servicedeskapi-organization-organizationid-user-post to add a user, or use postman and a list of email adresses to add the right users to the right org.

[Dominik Hebestreit]

Hi @Marc - Devoteam 

I think I will have to build this with Python and then send suitable POSt reqeusts to the API...
Are there any other alternatives to solve something like this?

I wonder how big service providers do it. They hardly maintain it manually, do they?

[Marc - Devoteam]

Hi @Dominik Hebestreit 

You can setup your orgs and then add a mail domain to on org, and use automation to add users to the right org.

Or by use of automation create and org based on the mail domain to customer is using.

You will need to start somewhere.

Also big orgs usually don't use orgs, they don't want other customers to be notified or even have the open to share requets

[Dominik Hebestreit]

Good morning @Marc - Devoteam ,

thanks I understand.

That will not work for me. We are a big internal company. All stores are using the same domain.

We have in our old system (GLPI) the same function. When a person from a store creates a issue/service request, all people of this store can view it.

This is only for our stores.

Best regards,

Dominik!

[Marc - Devoteam]

Hi @Dominik Hebestreit 

So your option is to create a setup using the API or manually.

But as it's only internal, why would you want to limit transparency within the company.

On issues spanning a store, you can't select multiple orgs, then you would still need and org where everyone is in.

But that's a decision to be made, as this will result that every user is still in 1 or more orgs and they can share with one or more orgs and defaulting is not an option in the share with field.