Sometimes you may need to define a single calculated date using multiple eligibilities. For example, there may be a typical definition of date of participation or earliest retirement date, and then alternatives that apply to certain subgroups of the plan. You can parameterize this in ProAdmin by defining multiple Calculated Dates that use the same Field to contain calculated date. The alternatives that apply to certain subgroups in this date of participation example should be processed first, and then the typical/default eligibility should be processed last. That's because once a calculated date has been affirmatively defined (i.e., eligibility was met, including the selection expression, if any), ProAdmin will ignore any subsequent calculated dates.

The Calculation Summary results will include the description of the "winning" Calculated Date definition.  

For example, if you defined three (3) eligibilities for the date field DateOfParticipation, and this happens:
1.   The eligibility is not met.
2.   The eligibility is met.  Result = 10/25/2017
3.   The eligibility is met.  Result = 4/25/2018
You would get 10/25/2017, because it is the first eligibility that was met.

If you reorder the 3 eligibilities for the date field DateOfParticipation like this:
1.   The eligibility is met.  Result = 10/25/2017
2.   The eligibility is met.  Result = 4/25/2018
3.   The eligibility is not met.
You would still get 10/25/2017, because it is the first eligibility that was met.

Finally, if you reorder the 3 eligibilities for the date field DateOfParticipation like this:
1.   The eligibility is met.  Result = 4/25/2018
2.   The eligibility is met.  Result = 10/25/2017
3.   The eligibility is not met.
You get 4/25/2018, because it is the first eligibility that was met.