Easy Automation - Vendor JSON Schema Changes

Issue No: AP-7452
Created 6/24/2019 3:51:45 PM
Type Gap
Priority Major
Status Closed
Resolution Fixed
Fixed Version 19.1
Description Easy Automation has made some schema changes. Please make these changes in our end and update the framework that is associated with this. The new schema has been attached.   Framework documentation: [http://inet.irelyserver.com/pages/viewpage.action?pageId=100352391]   See their description below:   {color:#0000ff}Here is a summary of things that have been changed:{color}   * {color:#0000ff}Most importantly for i21, the Id field has been replaced with the Name field. This was discussed in the last meeting; the FOE team will need to make sure that users on the Enterprise side will be unable to change this field or else users may break the link with i21.{color} * {color:#0000ff}Added an additionalProperties key to Customer and Vendor with a false value. When Enterprise validates incoming requests, it will deny requests containing keys it does not recognize as explicitly defined in the schema (such as “Id” : 1234 or “Color” : “Purple”).{color} * {color:#0000ff}Removed the arbitrary requirements on contact info field for Vendor; they were largely there to test Schema validation{color} * {color:#0000ff}(Probably not relevant to i21) Changed the name of the GroupRequired and LocationRequired field to RequiresGroup and RequiresLocation for the Customer (sorry for this one, I know it seems arbitrary but the original task defined it this way){color} * {color:#0000ff}(also questionable in relevance to i21) Changed the OrganicType and VendorType fields to be enumerated strings (I like it better this way, for human readability of request files){color}