Release Notes 125

Announcements Release notifications
1

The weekly releases continue as we head into the holidays, bringing you more frequent updates, faster turnaround from development to launch, and lower risk through smaller, incremental changes. If you missed last week’s article on our new release process, you can catch up here.

Here are the highlights of this week’s release:

Use Enum descriptions in the UI

Descriptions for Enum values are now available in your app UI. They support translations and work like any other string property in databindings, functions, and filters.

Duplicate objects: new option to duplicate from database

Appfarm applications only load object values that are actively in use on the client. Previously, the Duplicate Object action node only duplicated client-available values, potentially missing data in the database. We’ve added a new option to duplicate values directly from the database, even when they’re not loaded on the client. This is now the default behavior. Existing action nodes will continue using client-only duplication. Note that choosing database duplication impacts performance and won’t work offline. Read more in our updated docs.

Manage consent in Appfarm Create

You can now manage your consent preferences at myaccount.appfarm.io/preferences. Set your preferences for communications and data usage to receive insights and personalized experiences. We may have some tailored insights coming your way before year-end!

You can find the full list of improvements, new features and bug fixes below.

What’s New

  • Option to duplicate all values in a duplicate object action node (#4600)
  • Allow an Enum description field to be used in apps as well (#4846)
  • My Account: Manage developer consents (#7134)
  • Add “Referrer Policy” setting to Iframe component (#7295)

Bug Fixes

  • Component param: some multiref properties seem possible to select but shouldn’t be. (#7272)
  • If solution-quota max manual snapshots are less than 5 it looks like you can take a snapshot even though you can’t (#7285)
  • Wrong data type for iterator context properties in filter edit (#7312)
Enum description - use in app
2

Just letting you know that there seems to be some unintended consequences of the new Enum features. I have had multiple services break because they used Enum.value, when after the last release it seems they should use Enum.value.value instead?

image
image299×120 3.06 KB

image
image300×319 4.71 KB

3

We followed this up in DMs and have concluded that the issues were not related to the Enum features. Services can still use Enum.value.

4

In our solution all of the existing duplicate object action nodes have automatically been set to “duplicate from database“.

Will this only read additional properties that are “missing“ in the client, or will it override all runtime object properties with the property values stored in the database?

5

Hi, it’s a bit unclear to us why the duplicate action nodes in your solution have been set to “Duplicate from database”. We will look into this, as the action nodes in the solutions we have checked have been set to “Duplicate client values”.

It will not override runtime values, only read values for properties that are missing in the client.

6

Okay got it, thanks for looking into it!