After creating the new LU's we must add some important business logic to these.
Changing business logic for new entity CompanyCar. Open the customization CompanyCar-Cust.plsql file in Developer Studio.
If you want to change a standard error message you can do that by overriding the specific standard error message method. In this case we want to write the registration number in the error message since this is not the standard behavior we override the method. An overridden method must have a super call, otherwise it is not an overridden method. The example below is an example of an pre-override of a method, this means that this code is run before the other code is run.
In this example we have added post-override code to a method. This means that this code runs after the previous layers code. Here we have added some business logic that checks that we don't buy to expensive cars to our company.
Here we have added some new business logic that can be called from a client to calculate the price of a car. Since this is a completely new method we don't need to add any annotation before the method regarding overtake and override. Other annotations might occur, like security annotations.
When you added the reference to CompanyCar from PersonInfo you received some new code in the template. This code check if it is a correct reference in method Check_Common.
In this case we want to add a new business rule that checks that a car only can be assigned to one person. We do this by adding a new method called Check_Car and the we call this method from Check_Common which means that we have to do an override of Check_Common.
