Reference Code SQL Missing Aliasing

I have a view that uses a reference code to format some activity values in our database. The SQL that is being generated by Yellowfin looks like this:

CASE
           WHEN activity IN(0, 1)
           THEN 'Client'
           WHEN activity IN(3, 4)
           THEN 'Depot'
           WHEN activity = 7
           THEN 'Lunch'
           WHEN activity = 5
           THEN 'Break'
           WHEN activity = 6
           THEN 'Refuel'
           WHEN activity IN(37, 38, 39)
           THEN 'Inspections/Paperwork'
           WHEN activity IN(32, 31)
           THEN 'Meeting'
           WHEN activity IN(30, 36, 35)
           THEN 'Training'
           WHEN activity IN(34, 12, 9, 10, 2, 15, 8, 33, 53)
           THEN 'Other'
           ELSE 'Unknown'
       END,
...
FROM events

The problem is that the Yellowfin is failing to alias the table and reference the alias in this CASE block. In other words, the SQL it should be generating would look like this:

CASE
           WHEN pickupEvent.activity IN(0, 1)
           THEN 'Client'
           WHEN pickupEvent.activity IN(3, 4)
           THEN 'Depot'
           WHEN pickupEvent.activity = 7
           THEN 'Lunch'
           WHEN pickupEvent.activity = 5
           THEN 'Break'
           WHEN pickupEvent.activity = 6
           THEN 'Refuel'
           WHEN pickupEvent.activity IN(37, 38, 39)
           THEN 'Inspections/Paperwork'
           WHEN pickupEvent.activity IN(32, 31)
           THEN 'Meeting'
           WHEN pickupEvent.activity IN(30, 36, 35)
           THEN 'Training'
           WHEN pickupEvent.activity IN(34, 12, 9, 10, 2, 15, 8, 33, 53)
           THEN 'Other'
           ELSE 'Unknown'
       END,
...
FROM events AS pickupEvent

The reason why this is important is because I want to join our events table to itself (to link the pickupEvents with their corresponding dropoffEvents). When I do this my view breaks because the activity column is now ambiguous between the two instances of the events table. I have not tested this, but I would expect the view to also break if I joined any other table that had an 'activity' column.

It is SQL best practice to always use aliases when defining tables and referencing columns in order to avoid ambiguity. Yellowfin needs to follow best practices in the SQL it generates.