Open
Milestone
Implement dynamic project type validation
Milestone ID: 241
The problem
As described in #3 (closed), project types are not yet validated. This leads to errors when Twingle adds new types, which are then transferred without having a correct representation as a campaign type in CiviCRM.
The idea
The idea is to implement a validation for incoming projects. This validation should dynamically compare the type of the incoming project with the allowed values defined in the Twingle campaign types.
The advantage of a dynamic validation is that it would be possible to manually create new campaign types that would then be allowed, while on the other hand existing campaign types could be deleted to completely exclude a Twingle project type from synchronization with CiviCRM.
All issues for this milestone are closed. You may close this milestone now.