Comments
This needs to be adressed ASAP, we have been losing more active subscribers than gaining new ones because of this! As of right now the only GDPR-compliant way to let people opt in to our 13 brands newsletters are with specific newsletter forms. We had to remove the "Yes please, send me your newsletters" from all our forms for events, webinars, white papers etc.
Agreed that this should be an "optional" parameter within the intercompany partnership activation setup and policies. Whilst completely agreed, in many cases the batch attribute information would be required and be as vital as the batch information, we should also consider the flexibility to allow this inheritance cross legal entity if the same attributes have the same purpose in both legal entities.
I agree that this functionality doesn't make sense in its current format. I can't imagine a scenario where you'd ever need a second authorisation if only thing on the journal that has changed, is 'Exported to Payment File' going from from false to true. Fixing this would be of great benefit to many users I'm sure!
We can’t use “Any to Organization “in an entity that is person as the verification for the party, any in this case can be used for person or organization and the other part will be used for organization which is conflicting with the logic of the relation to include the entity that you create the relation on in one of the party of the organizationAnd it goes the other way around if you are trying to use a relation that is “Any to Person “within organization entity you will face the same conflict.This is for verification as the entity type that you will create the relation for needs to be included in the relation type that you will be using.To avoid that you would need to use “Any to Any” in the relation and only then you will be able to use the same relation ID in both organization and person types. A change in the logic needs to be in place for Any to Organization to occupy person and vice versa.