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 Act! Companion, 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 v18.104.22.168
Need to support admin preference
API build v22.214.171.124
RTF Conversion for v22
API build v126.96.36.199 (required for v22 new features)
Tier Limitation Messaging when Contact Threshold Hit
Enable Standalone Deployment for Web API
Opportunity: DaysInStage is not compatible
OrderBy : Child Entity
Mixing OData Custom Fields and Non-Custom Fields
Remove / Plug API Methods We Do Not Want Exposed for Multi-tenant
Update Webhooks Documentation for Better Scaling of Multi-tenant API
MA: If Contact ID does not exist, map Contact ID from SendTo Email Address
Metadata Refresh for SSO
Move Caching Mechanism to Traditional Cache
API Drain Stopping Before Removing Threads from Cache
Phone Number Masking
API build v1.0.503.0
Pass Stage and Process Names when creating an opportunity
Unable to sort opportunities by null
API build v1.0.496.0
Locking Model Mutex Failing
Add Logging for Mutex Requests
FilterBy Opportunity Source
Enum Search on Opportunities
Allow Request with Authorize Valid Tokens
API build v1.0.490.0
Create Contact: Requires amaScore to be passed
When creating a Contact using the API the value for recordOwner is set to the same as recordManager
Contact: AltEmailAddress & PersonalEmailAddress
Groups Migration Enablement
Add 'Act' to Custom Headers
Add a Count Method for Main Views
API build v1.0.460.0
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.