Skip to content

Apiv4 entity parity

Here are the entities in APIv3 & not v4

In some cases by design - others we should maybe add...

Prioritised

Partially done - lets resolve

Standard crud - note that doing these involves checking all pseudoconstants are correctly defined

  • SmsProvider.php
  • Premium.php
  • RecurringEntity.php

Mailing related - in scope

  • MailingAB.php
  • MailingComponent.php
  • MailingContact.php
  • MailingEventResubscribe.php
  • MailingRecipients.php

From here on down we are out of scope for 'entity parity'

Order related - needed when we get to afform payment forms - out of scope for entity parity

  • Order.php
  • Payment.php

Varied utils - out of scope for 'entity parity' - ad hoc

  • SystemLog.php
  • User.php
  • Logging.php

Migration doubtful - to be done ad hoc if we decide to

  • ReportTemplate.php
  • ParticipantPayment.php - likely should not be brought over
  • CxnApp.php
  • Cxn.php
  • Profile.php

Do not migrate

  • ActivityType.php (by design)
  • CustomSearch.php (by design)
  • Constant.php (by design)
  • SurveyRespondant.php(by design)
  • MembershipPayment.php (by design - use Line Item)

Done

Edited by JoeMurray
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information