Skip to main content
Please be aware that while Forest make every effort to ensure that our platform updates are broadly compatible and offer detailed instructions for upgrading, Forest cannot guarantee that custom code developed by the developers will always be compatible with new versions of our software. This includes any custom modifications or extensions to core functionalities, such as method overrides or custom integrations. It is the responsibility of the developers to review and test their custom code to ensure compatibility with each new version. Our team provides comprehensive upgrade guides to assist in this process, but these cannot encompass the unique customizations that may be present in each customer’s environment. Therefore, Forest strongly recommend establishing a thorough testing protocol for your specific customizations to safeguard against potential issues during the upgrade process.

​
Upgrading to v4

Before upgrading to v4, consider the below breaking changes.
As for any dependency upgrade, it’s very important to test this upgrade in your testing environments. Not doing so could result in your admin panel being unusable.
To upgrade to v4, update the version in your Gemfile, then run: 
bundle install
In case of a regression introduced in Production after the upgrade, a rollback to your previous agent version 3 is the fastest way to restore your admin panel.

​
Breaking changes

​
New JWT authentication token

The information format of the session token have changed in v4.
You could be impacted if you use the user session in Smart Action controllers or Smart Routes
Calling forest_user in v3 
{
  "id": "172",
  "type": "users",
  "data": {
    "email": "angelicabengtsson@doha2019.com",
    "first_name": "Angelica",
    "last_name": "Bengtsson",
    "teams": ["Pole Vault"],
  },
  "relationships": {
    "renderings": {
      "data": [{
        "type": "renderings",
        "id": "4998",
      }],
    },
  },
  "iat": 1569913709,
  "exp": 1571123309
}
Calling forest_user in v4 
{
  "id": "172",
  "email": "angelicabengtsson@doha2019.com",
  "firstName": "Angelica",
  "lastName": "Bengtsson",
  "team": "Pole Vault",
  "renderingId": "4998",
  "iat": 1569913709,
  "exp": 1571123309
}
Consequently, the user information is now accessible as described below:
Propertyv3v4
emailforest_user.data.emailforest_user.email
first nameforest_user.data.first_nameforest_user.firstName
last nameforest_user.data.last_nameforest_user.lastName
teamforest_user.data.teams[0]forest_user.team
rendering idforest_user.relationships.renderings.data[0].idforest_user.renderingId

​
New filters query parameters format

The query parameters sent for filtering purposes have changed in v4.
You could be impacted if you have custom filter implementations.
Below are a few example of the new filter conditions format you can access usingparams[:filters]: 
{
  "field": "planLimitationReachedAt",
  "operator": "previous_year_to_date",
  "value": null
}

{
  "aggregator": "and",
  "conditions": [{
    "field": "planLimitationReachedAt",
    "operator": "previous_year_to_date",
    "value": null
  }, {
    "field": "planLimitationStatus",
    "operator": "equal",
    "value": "warning"
  }]
}

​
Important Notice

​
Agent logout

A consequence of the new session token format is:
Once an agent v4 deployed, all users of your project will be automatically logged out and be forced to re-authenticate to generate a newly formatted token. ​

​
Changelogs

This release note covers only the major changes. To learn more, please refer to the changelogs in our different repositories: