Relationship CTA Reasons to be Shown with Global CTA types

Related products: None

What we are trying to do is move all the custom reasons made at the global level for a specific relationship to the relationship level on the backend and allow them to use the global types, they were implemented prior to the federated administration. Making it a seamless transition for all the end users. However, when we move the reason on the backend they do not show up when creating a manual CTA. 





Current Functionality and expected behavior. When creating a CTA Reason at the Relationship level it only is shown if you have a Relationship Level CTA Type and that is the Type selected when making the CTA for a relationship.





I understand the thought process behind this.





However, this forces a client to remake all the CTA Types, to include Risk, at the relationship level. This customer uses all of their default CTA types. To recreate this will be too big of an effort.





Working on it with the intended design forces a lot of duplication of effort. This means every time a new relationship type is created they have to remake all those CTA Types, not to mention you can't reuse the same name, such as Risk which is a problem in itself. And, they have different reasons so there is no point in making them at the global level.





The biggest issue here is they want to utilize the current reasons that are at the Global level at the relationship level and not lose all of their historical data and not have to have a huge effort to get it to work.





Solutions I could think of is to use reporting categories. However, again this will take too much effort as we have too many rules and reports that utilize the CTA type.
Be the first to reply!