Not sure from your description, but I suspect your validation rule is not actually the conditions the way you want them to. It seems to me that you are using an IF() statement when you really do not need to. In the current setup of your rule
if(
($Profile.Name = "France User"),
OR(
Max_Quantity__c < Asked_Quantity_Number__c,
Asked_Quantity_Number__c < BatchQuantity_Number__c
),false
)
The way that the IF statemtne works is as follows
IF(logical_test, value_if_true, value_if_false)
You are saying that If the profile of the current user is 'France User', then the formula will evaluate to your OR statement. If the user is NOT a France user, then it will always return false. It will never look at the conditions in your OR statement. Perhaps this is what you are trying to do, but I'm thinking it isn't.
I think what you are trying to do is something more like this
AND(
($Profile.Name = "France User"),
OR(
Max_Quantity__c < Asked_Quantity_Number__c,
Asked_Quantity_Number__c < BatchQuantity_Number__c
)
)
This now checks that the current user is a 'France User' ANd one of the 2 conditions you listed are true.
You generally don't need to use an IF() if all of your functions within the rules return a boolean. It becomes redundant and complicates the rule.
Even though your first rule works, you might want to use this construct for that rule as well.
It has always worked with this. I've been writing Salesforce code over 3 years now. If you don't give it a name through code, it defaults it to it's ID.
The UI will require a user to input a String, but why does the code really need to force it to? The developer is the one creating the code and so then knows what should be acceptable.
If you really want to force the developer to not leave the name blank, create a validation rule. Have the validation rule check to see if the Id and Name field are the same, or the Name is blank. In either of those cases have it error.
TL;DR; This functionality has been around for years. Nothing has changed.
Best Answer
This isn't possible on standard pages using validation rules - the red "required" marker is only displayed when a field is required, either at the page layout or field level. A validation rule will mark the field when the error occurs, but this is after the user attempts to save.
You can do this in Visualforce, by conditionally rendering some additional classes, but that would mean (a) moving your whole page to Visualforce and (b) having some of your logic in the validation rule (the actual rule) and some in the page (the knowledge about whether to display the field as required to a particular user).
If your rule was specific to a profile rather than a user, you could have a different page layout for each profile and make the field required (or not) at the page level.