Adding scoped field to global table

[jeremy_gardner]

Is there a way to add a scoped field to a global table?   I'd like to add a custom field to cmdb_ci so that our scoped app can leverage customer's data/relationships in the CMDB, and I see an option for "Allow new fields" option on the form, but it's hidden from everybody but maint.  

Alternatively, is there another way to accomplish something similar?

Thanks,

Jeremy

[Pradeep Sharma]

Hi Alexey,

Can you please share your instance details to "pradeep.sharma@servicenow.com" so that I can investigate it further.

[aklimenko]

Now it works for me too.

[jeremy_gardner]

Pradeep, that worked for me, thank you!   Two things.  

One, you might want to update the Wiki section to include ability to add fields.   Currently it only mentions ability to add things like ACLs, BR, Client Scripts, etc but not new fields.

Two, how are these global changes captured in our custom application?   When we go to install this somewhere else, will we need to somehow enable them before we install our app?

Thanks!

Jeremy

[Pradeep Sharma]

Hi Jeremy Gardner

Sorry for the delay in my response.We will pass the feedback to the documentation team to update the wiki.

Response to your second question :

• These fields will get created on the customers instance when they install the application even if they do not have allow configuration checked.
• Also you have to mention all the changes made to the sys tables in the installation document.

I hope this helps

[Uncle Rob]

We've got the exact same issue in two different places:

1)   Reference Field on Task

Our app makes no assumption on the task types people use, and we have the ability to create tasks from a component of our app.   Ideally we want a reference to our app's main record so customers can track the efficacy of their efforts.   Problem?   Can't add a field to Task.   Now we're messing with using Correlation ID, but it feels way too hackish.

2)   UI Macro Category Choice

We have a hand full of UI Macros we use to help users configure elements of our solution (for reasons that will be obvious when / if we show it).   For reference qualifier's sake (ie "select the UI macros you'd like to incorporate) we wanted to have a UI Macro Category of our own.   But that conflicts with the choice list being in Global Scope.