How do you assign a default Support Group for Classes?

[Dan Berger]

I am looking for the best practice to default CIs to a 'Class Owner' Group when a new CI is inserted.  We have a custom field called 'CI Owner Group' that is very much like the 'Support Group'.

For instance, when a Windows Server is created, I want the CI Owner group to be defaulted to 'LAN - Data Center'.

I have created a custom look-up table that has the CI Class and Class Owner group pairs:

I plan on creating a script that will query this table using the Default value:

 

My first solution was to create a 'Before' Insert Business rule which worked, but I thought it would be a maintenance nightmare since I hard coded the groups by sys_id in the script.  Using a look-up table would make it easier to update class owners and add new class/class owners when they are identified.

Although this seems like it would work, I am concerned about limiting the number of custom tables and I am looking for an OOB or best practices solution.

[Allen Andreas]

Hi,

If you had a field on the class table that references groups (like the support group field), then you would just use that?

I'm not understanding what you hard coded in script for?

On insert, in the business rule, you could gliderecord query the table class record, find the class owner group that is referenced, and go from there. 

Or better yet, you would just add a reference to group there on the table, set the default value in the default value field of that field..and that's it. Then on any new record it's auto-set without a BR?

or....finally...

there's these group fields on the class table already:

Can you not use "Managed by Group?"

Please mark reply as Helpful/Correct, if applicable. Thanks!

[Dan Berger]

Thanks--I started with a Business Rule that had the class/class owner pairs hard coded.  Then, I created the table and used a gr query like you suggested.  That is working well.

In our system, the CI Owner group builds, owns and maintains the hardware and the Application owner (Support group) owns the software running on the hardware.  That is why we need two groups.

The issue is that we want to limit the number of custom tables because of licensing so we are looking for other solutions, preferably oob or some other best practices for defaults.

In addition, we don't want to add business rules, so we would like to use the default value on the column.

[Allen Andreas]

Hi,

Yep, I got all that from your post.

I then posted a screenshot of 4 groups that's with the OOB class tables:

I would imagine that of those 4...1 of those can work for you.

That would negate a custom solution/table, that would negate a BR too, and you could set the default value, like I mentioned above and be done.

Please mark reply as Helpful/Correct, if applicable. Thanks!