I'm new to JSM - please forgive my ignorance...
In our CMDB, we want to designate a number of fields to be required for save or else disabled (some conditionally required based on the contents of other fields). This was all fairly easy in Cherwell... but I can't seem to get there in Assets.
As an example, each of the applications contains a couple of boolean fields called Available for request and Approval Required, as well as a "person selector" field for Approver Name.
- If Available for Request is True then the application is included in the list of Software Access Request options.
- If Available for Request is False then the application is not listed among the Software Access Request options AND Approval Required should be disabled.
- If Available for Request is True AND Approval Required is True, then the field Approver Name becomes required.
Am I missing something or approaching it wrong?
Hi @Mark
I'm not quite sure if I got you correctly. Would you like to have these constraints on the JSM form in the portal or on the create object screen in assets?
Maybe you could give some more information and also provide some screenshots?
Thanks for responding, Kai!
As I understand it, there are no forms available for Asset objects.
I'd like to control the Configuration Item owners' input so that required fields cannot be left empty and irrelevant fields are disabled or hidden. And as I mentioned above, whether a field is required or irrelevant will depend on the values in other fields.
As another example, I want to track (require) license counts for all licensed software, but if the app is home-grown, then the license fields should be hidden or disabled.
I'm not sure about CMDB maintenance being a portal thing. Previously, it was handled by "agent access," since CI edits occur virtually continuously as version, vendor, or license info change.
But either way, when the CI owner goes to update and validate their records, certain data requirements should be enforced.
Does that help to clarify my need?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.