nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community Discussions

The most recent content from our members.

Community Discussions

The most recent content from our members.

Getting the (Required, Recommended, Optional) options for extensible attribute using WAPI for NIOS

WitchElf

I am trying to the the options for the Required, Recommended, and Optional for the extensible attributes using the WAPI.

I am "reinventing" the wheel because we need a custom GUI for our use case with Infoblox. I've done everything that I need to do, except I can't find the said options/fields using the infoblox WAPI. I can manually set it in the custom GUI if it is required, recommended, or optional, but the problem now is that it is still possible for upper level users to use the NIOS GUI which makes having these options in the custom GUI not a possible plan.

Before anyone says anything, yes this can be solved by having a proper workflow or process, but I am just wondering if it is possible to get the extensible attributes options for required, recommended, optional fields. This way, I can have the workflow be, create extensible attributes in the NIOS GUI instead of custom GUI.

Any help would be appreciated.

Find more posts tagged with

WAPI

Comments

nic w

I'm not sure about the WAPI itself but I have customers that define EAs via CSV during import, so worst case you could do something hacky like that where the CSV import would create the EAs they need that are optional/recommended/required etc and then the workflow continues after successful import

Another option might be workflow approvals in NIOS, where lower-level users could log into the NIOS GUI only to create their EAs but the true DDI/senior team needs to approve the changes before they take effect