It’s best to put error/warning messages in very passive, non-blaming language, especially if users might see them. Avoid exclamation marks unless something is seriously wrong and they need to take immediate action, and in that case tell them which actions to take.
It can be difficult to give non-technical people meaningful info, with enough tech detail for the dev to actually find and fix a problem. Specifically, the example below is validating data prior to record creation. The message could be phrased like (“Sorry, there was a problem saving the programming step.\n\nError details: missing ID. Mes_product_id:” + mes_product_id +” Mes_route_step_id:” + mes_route_step_id)
//Check that all Guid strings are not empty
Gokhru Fruit is very much beneficial to improve the conditions like emaciation of children, senile debility, rheumatism, in all cases of general debility, nervous exhaustion, brain-fag, low of memory, loss of muscular energy and spermatorrhoea. levitra 40 mg Nevertheless, these persons would still not be able to look this young and beautiful if order cheap cialis they didn’t were extremely conscious about their lifestyle. Patients are then compelled to live in agony and with the availability of OTC drugs online, your life is about to unearth an interesting buy professional viagra revelation of premature treatment. After retiring as a player, Sullivan returned to his hometown of Swampscott, both with a order generic levitra population of less than 25,000. if (mes_product_id.Equals(“”) || mes_route_step_id.Equals(“”) || mes_station_id.Equals(“”))
throw new Exception(“At least one ID is empty!”);
And then to be super-nice, you might even help them out with some instructions like “try again by doing this thing instead”, or “contact your supervisor or MES Admin if this problem continues.”