Ennov InSight 7.0 API Changes
This table describes the API changes related to Product Family decoupling between Ennov InSight 7.0 and InSight 6.2.
Ennov InSight 7.0 includes the following API changes:
— Application has moved to the top entity in its own hierarchy.
— Application has a one-to-many relationship with the Product Family via the selectedProducts field.
— FamilyId field is removed.
— The uniqueness criteria for the Application has changed (Uniqueness for the API is used in "/create-or-update" controller operations).
| Entity Name | API/Controller | API 6.2 | API 7.0 Updates | Description |
| Application |
ApplicationRestContro ller CTAApplicationRestCo ntroller INDApplicationRestCo ntroller /application / application/cta / application/ind |
— Family Id required — selectedProducts field - is not required — Application uniqueness rule (appCode and familyId) or uuid" |
— Family Id is removed — selectedProducts field - required — Application uniqueness rule changed (appCode and appName) or uuid" |
If application is not found it executes an uniqueness expression. Unique expression is used in "/ create-orupdate" api. |
| ApplicationCou ntry | ApplicationCountryRe stController / application-country |
— Family Id is required — Old behavior - |
— Family Id is removed — New behavior - |
The behavior of how applicationId is |
| Event | EventRestController / event |
Example: { "queryFor": { "applicationId": |
Example: { "queryFor": { "applicationId": |
retrieved for use in queryFor has changed. |
| EventCountry | EventCountryRestCon troller /event-country |
APPLICATION_N AME }, ... } |
APPLICATION_C ODE + " " + |
|
| EventCountryS chedule | EventCountrySchedul eRestController / event-countryschedule |
APPLICATION_N AME }, ... } |
||
|
AppEventProdu ct |
AppEventProductRest Controller /event/ product |
Old behavior Example: { "queryFor": { "applicationId": APPLICATION_NAM E }, ... } |
New behavior Example: { "queryFor": { "applicationId": APPLICATION_COD E + " " + APPLICATION_NAM E }, ... } |
The behavior of how applicationId is retrieved for use in queryFor has changed. |
| FullProductPre sentation | LicenseFppController /license/full-productpresentation |
— Family Id is required — Old behavior Example: { "queryFor": { "applicationId": APPLICATION_N AME }, ... } |
— Family Id is removed — New behavior Example: { "queryFor": { "applicationId": APPLICATION_C ODE + " " + APPLICATION_N AME }, ... } |
|
| License |
This entity is inherited by ProductLicense Doesn't have direct controller |
— Family Id is required — registeredAtc is required — Old behavior Example: { "queryFor": { "applicationId": APPLICATION_N AME }, ... } — Old uniqueness rule - "Code and AuthorityId and FamilyID and ApplicationId" |
— Family Id is removed — registeredAtc is not required — New behavior Example: { "queryFor": { "applicationId": APPLICATION_C ODE + " " + APPLICATION_N AME }, ... } — New uniqueness rule - "Code and AuthorityId and ApplicationId" |
|
| MaAttachment |
MaAttachmentRestCo ntroller /full-productpresentation/ attachment |
— Family Id required — Old behavior Example: { "queryFor": { "applicationId": APPLICATION_N AME }, ... } |
— Family Id is removed — New behavior Example: { "queryFor": { "applicationId": APPLICATION_C ODE + " " + APPLICATION_N |
|
|
— Old uniqueness rule - "name and66 fppId and familyId and |
AME }, ... }Ennov InSight 7. — New uniquenessEnnov InS rule - |
API Documentation ight 7.0 API Changes 3 |
||
| ProductLicense | "/license/productregistration" |
Old behavior Example: { "queryFor": { "applicationId": APPLICATION_NAM E }, ... } |
Please check License as it inherits all changes. |
N/A |
| LicensePackag eSet | /license/packageset |
Old behavior Example: { "queryFor": { "applicationId": APPLICATION_NAM E }, ... } |
New behavior Example: { "queryFor": { "applicationId": APPLICATION_COD E + " " + APPLICATION_NAM E }, ... } |
The behavior of how applicationId is retrieved for use in queryFor has changed. |
| LicensePackag eSetCountry | /license/packageset/ country |
— Family Id required — registeredAtc is required — Old behavior Example: { "queryFor": { "applicationId": APPLICATION_N AME }, ... } |
— Family Id is removed — registeredAtc is not required — New behavior Example: { "queryFor": { "applicationId": APPLICATION_C ODE + " " + APPLICATION_N AME }, ... } |
|
| Subset (PDS) | PDSRestController /pd s |
Old behavior Example: { "queryFor": { "applicationId": APPLICATION_NAM E }, ... } |
New behavior Example: { "queryFor": { "applicationId": APPLICATION_COD E + " " + APPLICATION_NAM E }, ... } |
|
| Schedule (seq status schedule) | Schedule /sequenceschedule | Family Id is required | Family Id is removed | N/A |
| PDS Details |
/detail/* CountryDetailRestCon troller ActiveIngredientDetail RestController CharacteristicsDetailR estController CTADetailRestControll er DoseScheduleDetailR estController FluStrainDetailRestCo ntroller FunctionDetailRestCo ntroller IndicationDetailRestC ontroller LabeledIndicationDet ailRestController LabelingDetailRestCo ntroller ManufacturerDetailRe stController ManufacturingProcess DetailRestController MaterialDetailRestCon troller MedicalDeviceDetailR estController PackageSetDetailRest Controller PackagingDetailRestC ontroller RouteOfAdministratio nDetailRestController ShelfLifeDetailRestCo ntroller SpeciesDetailRestCon troller StepDetailRestControl ler SubstanceDetailRestC ontroller WithdrawalTimeDetail RestController |
Old behavior Example: { "queryFor": { "applicationId": APPLICATION_NAM E }, ... } |
New behavior Example: { "queryFor": { "applicationId": APPLICATION_COD E + " " + APPLICATION_NAM E }, ... } |
The behavior of how applicationId is retrieved for use in queryFor has changed. |