Question: What Feature Improvements and Fixes have Been Released for the Act! API?
Product: Product Family: Act! Growth Suite
Note: This article includes updates specifically for the Act! API only. To check out all the new features by product and version, please see the following website for What's New Since Your Version
If you would like to see articles on the improvements for Act! as a whole, Act! Marketing Automation or the Act! API, please see the following articles:
|What issues have been fixed in Act! updates?||What Feature Improvements have Been Released for Act! Marketing Automation?||What Feature Improvements have Been Released for Act! Companion?|
API build v1.0.460.0
API-50 Add Odata support for users
Highlights the API changes required to define field end points to support metadata calls / parameters on defined fields
Opportunity filtering by cast entity type
API build v1.0.449.0
Update RTF Conversion to Prevent HTML from being Stored in Database
API build v1.0.448.0
Enable the ability to convert RTF text to HTML & vice-versa to support the add-ons and consumption of text throughout the Act! product suite
Architecture to Support RTF Conversion
RTF Control Update for Notes
RTF Control Update for Activities
RTF Control Update for History
Marketing Leads - Ranked by AMA Score
API build v1.1.436.0
Activities: Apply Pagination
Opportunities: DaysInStage is Not Compatible
API build v1.0.419.0
When a registration is auto suspended, it will reactivate the registation after a configure about of time.
Filtering on custom fields.
Using a database username with an accented character such as ö, ò, å or ä means the API fails to connect therefore the User cannot access AMA, Act! Insights, Opportunity KPIs.
Webhooks needs to provide a way for the callback application to identity a callback response without saving the webhook_id during registration.
AMA is not seeing fields when metadata is modified. Act! is sending an old token after metadata is changed, now the API will force SDK drop on Pre-Auths.
When adding a custom phone or address fields the API would throw a duplicate index exception.
Unable to get notes by id and some of the other endpoints are not accessable.
Can't setting ActivityTypeId and ActivityPriorityId when saving or updating an activity.
When Act! throws and error the API was just fetching and returning all records.
Activity searching (api/activities) only returns the current users activities and not all activities viewable by the user.
Apply OData filter to all mutuble entities (companies, contacts, groups, opportunities, and products) - Add-on to issue #3.
Activities are returning NULL when there are no activities for the current user.
Private contacts were not being returned for the record manager.
Apply full OData specification when filtering on all entities (non-custom fields).
When getting companies with an OData filter the API was returning no results unless the query matched the same case sensitivity.
New AMAScore field added to the contact's entity.
Custom entities that contained datetime fields where always being displayed as the minumum datetime value.