In this release
IMPORTANT: These changes impacts members of the Jeto API Beta program only. Please read carefully since these could introduce breaking changes for your integration.
Jeto App Updates
Lazy loading & faster page load
API Beta Updates
Security patch
Unify Drafts and Campaigns under a UUID (Universal Unique Identifier)
New filtering, sorting, and pagination
Workato Connector (Beta) Updates
New "Get Campaigns Details" Action
Improved "Update Campaign" action
Support for new Jeto Paging, Filters, Sort
Jeto App Updates
Lazy loading (faster page load)
Campaigns, Launcher and Groups pages as well as other widgets have all been updated to use "lazy loading" so that Jeto now incrementally retrieves results on these pages as the user scrolls down to view more results, which makes initial display of the pages faster. Our latest performance tests on the /campaigns page resulted in an 86% load time reduction...so we're talking wayyyyy faster!
API Beta Updates
Security Patch
An important security issue that was blocking beta testing has now been resolved. You may now safely resume testing the Jeto API.
Unify Drafts and Campaigns under a UUID (Universal Unique Identifier)
Jeto now has UUID and unified Endpoints for Campaigns and Draft to serve as base for both Campaigns and Drafts
Here is why we did this: in Jeto, Campaigns and Campaign Drafts are 2 separate objects in our data model. Once a Draft is converted (Submitted) it creates a Campaign, and cannot go back to being a Draft anymore. Each objects where given a different ID which makes it complex to synchronize any 3rd party solution across the 2 objects. If you worked with Salesforce API before you are likely familiar with the high level of complexity that results from the Lead and Contact objects, which is a very similar situation here...but we won't make that mistake!
The unification of the UUID and Endpoints will save you the complexity of dealing with it separately. This unification includes:
The addition of a UUID (Universal Unique ID) that will remain consistant across Campaign Drafts and Campaigns.
The "Get Campaign details" by UUID will sort out the Draft vs Campaign dilemma for you:
If campaign exist, we return the campaign
If not It will return the draft
A new data element named "type" will indicate whether the object is a "campaign" or a "campaignDraft.
Both Campaigns and Drafts use a unified payload schema
Here is an example of the response you will now get when Creating a Campaign Draft via the API:
{
"status":"success",
"data":{
"type":"campaignDrafts",
"attributes":{
"launcher_id":74442,
"uuid":"e00325b1-953a-436a-9e84-d25a40640d11"
},
"id":7949
}
}
New Filtering, Sorting, and Pagination
Jeto API design would now have been up to industry standards without the addition of paging, filtering and sorting. These features have been added In version 2.0.2 Beta and will help ease of use for clients and maintain performance over time. Here is how it works.
You can add filters, sorting and paging parameters directly in the query string based on Industry Standards. Here are some examples:
Paging: Use "size" parameter to control the number of items returned (Up to 200 elements at the time).
Ex: /campaigns?size=100
Paging: Use "page" parameter to fetch additional pages (default page = 0.
Ex: /campaigns?page=1&size=100
Sort: Use "sort" to define ordering or the results (default = descending by most recently updated)
Ex: /campaigns?sort=type%2Casc
Filter: Use "filter=" and specify owner, type or status to filter specific campaign results.
Ex: /campaigns?filter=owner%3A7310&filter=type%3AEVENT
Search: Use "search" to get campaigns containing a specific string.
Ex: search=Jeto%20Demo
Workato Connector (Beta)
New "Get Campaign Details" action.
The Jeto Workato Connector (Beta) now supports the "Get Campaigns Details" Action. This helps retrieve all the info from any single campaign, including each campaign field and its corresponding value.
Improved "Update Campaign" action.
In addition the "Update Campaign" action has been improved to support "Datapills" which allow to use output data from a previous trigger or an action step
Support for new Jeto UUID
Following the addition of Campaigns UUID, Workato Connector API data schema was refreshed:
Triggers - Campaign is created or updated: UUID was added to response attributes
Trigger - New Campaigns: UUID was added to response attributes
Action - Get campaign details: supports using UUID as a campaign ID parameter
If campaign exist, we return the campaign
If not we return draft
Support for new Jeto Paging, Filters, Sort
The Action Get Campaigns was updated to support Filter, Sort, Search and Paging.
