Page Comparison

...

if User->Fasit
  "CTS DSP Team FASIT"
else
  User->Org->Contract->DSPGroup.Name

...

Business logic can usually be implemented in business rules, UI Actions, script includes, scheduled jobs, and other code. This can make end user reporting more difficult, but building reporting structure on top of a primarily transactional database is not a good idea, precisely because it encourages denormalization and introduces complexity and the potential for confusion about what data to use (imagine 3 fields in different tables all representing the same object type but with slightly different logicsemantics).

We already warehouse data with third parties for reporting purposes, so we discourage any attempt to denormalize transactional tables purely for reporting purposes is discouraged..

Here is example UI action code for obtaining the correct DSP Group for a given user in the absence of a denormalized field or store proc:

// if user is FASIT, use FASIT group, else use the org's group
// gr = user's GlideRecord 
if(gr.u_facit == true) {
    gs.addInfoMessage('Assigned to FASIT DSP Group');
    current.assignment_group = sys_user_group_by_name('CTS DSP Team FASIT');
} else {
    current.assignment_group = gr.u_organization.u_service_contract.u_assignment_group.sys_id;
}