Attribute Validation

[Heather Weatherholt]

I am working on an asset database in JSM and am working to have some fields validated.  Is there a validation sting that would make a field required, or cannot be blank?

I have found  I have found https://confluence.atlassian.com/proforma/regex-validation-1087521274.html as a source that I've been referencing to do this.  However, my dialog box to specific validation does not look like that.  When I am editing the attributes for my fields in my schema, I have the ... on the left-hand side of the screen for each attribute, and when I click on them, I get the option to configure, and when I choose that I get a tabbed dialog box, with one tab where I can specify it to be unique, one to set cardinality, and one to create the validation. 

I know that if I set an attribute as a label it becomes required, but I would need to be able to have more than one attribute as a label for the schema, and I haven't figured out how to do that yet and it is something we would like to do if possible - so if you know how to do that, I would appreciate an answer for that as well.

[Kian Stack Mumo Systems]

@Heather Weatherholt, 

If you want to require a value on a specific attribute of an asset, you should do the following:

On the Cardinality tab, set the minimum cardinality to "1". That will ensure that at least one value must be provided while creating the asset.

[Heather Weatherholt]

Thank you!  Now just to go back and re-edit the attribute that I need to make required.  Now just to figure out how I can have more than one attribute as a label.

[Kian Stack Mumo Systems]

You cannot have more than one attribute as the label. Why do you want to do that?

[Heather Weatherholt]

Because we have all of our different asset types (printers, laptops, desktops, etc.) in a different schema for each type. (Not sure why, not sure if I would have designed it this way if I was the one in charge of creating it.) So, if I need to search for a laptop that doesn't currently have a tag (which is what we currently have set for our labels) on it to see if it is in the system from before we started tagging things or because someone didn't input it correctly, etc, before creating a new entry for it, I have to go to the laptops and use the filter for the serial number and then go to the desktops, etc. to make sure that it didn't accidentally get created in the wrong schema.  Unfortunately, the "search this schema" at the top of the screen only searches for the object id, key, or label, so I can't search for a serial number in the box unless I make it a label.  Which by itself wouldn't be a bad idea but it is so much easier to spot a large barcode tag than it is to read that tiny serial number.

[Kian Stack Mumo Systems]

@Heather Weatherholt, 

Hmm, that does sound frustrating, but I'm not sure that there is really a better solution as you can only have one label field per object type.