Thanks for you info Allan, we have found the below explaination which I think answers my question
Fields can be set as being compulsory at a database level. Those with a red asterix indicate those fields that have been set at this level. When a field is set at a database level however, it is required from the moment a record is created prior to saving.
Those fields with a black asterix have had the label changed and the asterix added, as a means of visually identifying other fields that are compulsory, but not on saving of the record. In work orders, the fields are compulsory at different stages in workflow, which is why we can't set them at a database level.
Cheers
JB
------------------------------
John Bauer
Mercury
------------------------------
Original Message:
Sent: 03-31-2026 22:57
From: Allan Henle
Subject: Difference between Red Asterisk and Black Asterisk in IBM MAS
Hi John,
I have not tested this theory myself, nor have I run into a Black Asterisk that I can think of, but I did some research. I found that a Red Asterisk is a hard system requirement. Think something like a WONUM when creating a new WO. This is a required field. Always required, no matter the situation. While a Black Asterisk may become required. Something like a conditional UI rule, or a needed field based on a status, etc.
I hope this helps you.
Thank you,
------------------------------
Allan Henle
Naviam
------------------------------