Ebury Mass Payments Migration: Filtering Data
Ebury acquired the payroll payments business, Frontierpay (aka Ebury Mass Payments), in 2019.
Ebury and Ebury Mass Payments (EMP) Operations Teams have until now, been using the BOS UI in split environments (same UI, different data, infrastructure, etc).
Ebury intends to merge EMP data into "Ebury Core" while maintaining the BOS UI, which all teams are familiar with.
Post-merge the Operations Team will be split along lines equating to these two entities. One team managing the dataset related to EMP and another one the data related to Ebury Core.
This RFC related to the issue of filtering data in BOS views depending on which entity the Operations Team user belongs.
This will be achieved by identifying the user, and whether that user is a member of EMP or Ebury Core.
All users are linked to a brand, as are trades, payments and clients; some brands are EMP brands, others are Ebury Core.
This RFC proposes identifying users based on brand membership and filtering accordingly.
To simplify matters, we propose adding a boolean property to the Brand model: is_emp_brand.
Problem Description
Ebury Core and Ebury Mass Payments users wish to see only relevant work responsibilities and not be distracted by information and transactions outside those responsibilities.
Background
EMP (aka FrontierPay) data is merging into Ebury.
This RFC is part of the RFC where is going to be defined how the boolean field is filled. In this one, is defined how ew are going to use that field to filter the resources based on the brand.
Solution
A Python class to filter brands, based on the users Brand and the state of a boolean param
hard_filter, via a Django QuerySet.
Alternatives
Alternative solutions that can be safely implemented in the available time have not been identified.
Caveats
n/a
Operation
n/a
Security Impact
n/a
Performance Impact
Will add additional queries into BOS views making them slower.
Developer Impact
n/a
Data Consumer Impact
n/a
User Impact
Will change the defaults for some form filters in BOS views.
Deployment
n/a
Dependencies
n/a