Store MoH assignments on Accounts and Customers as the service attributes

 To use the inheritance mechanism provided by Service Features. Reduce porta-admin code complexity, unify approach of working with MOHs inheritances.

Problem overview

This is internal project to rework the current way of storing the assignments of MoHs to avoid problems  similar to ones described in tt#320939 which arise due to the limitation of current ways which define how the MOH description are stored within a database. Currently MoH entities are stored in separate table with references to assigned MoHs from Accounts and Customers tables. De facto porta-admin's code treats these references as a Account's/Customer's service feature with their inheritance mechanism and mechanism of GUI drawing, whereas they are not stored as service features. This leads to additional codes complexity, as it's required to 'translate' ordinary DB field into 'virtual' service feature.

Specifications

Definitions, acronyms and abbreviation

Music on hold (MOH) is the business practice of playing recorded music to fill the silence that would be heard by telephone callers who have been placed on hold. It is especially common in situations involving customer service.

References

1. https://en.wikipedia.org/wiki/Music_on_hold