remove_dangling_box_placementsself.roles inside a where clause of an instances call does not workTRIM_LEFT('0041, '0') removes the zeros from the beginning.Instance Import permission will see the dialog and can only choose the option "delete instances" if they have in addition the Delete Instances permission.[1, 2, 3, 4, 5].filter(p => p > 3).CASE.documents or CASE.instances fails validationperson.first_name in an arrow function failsUNION function and infix operator |. So both UNION([1, 2], [2, 3]) and [1, 2] | [2, 3] are supported.Constants.SUPPORTER := 'tijana' makes it possible to use that constant in rules and have it changed easily.map(people, current.first_name) you can write people.map(p => p.first_name). flatten operator to extract one or more properties into a list from a list of dictionaries, e.g. get all the first names from the list of all people in a casesort(people, "last_name").case_activity_log/ endpoint to retrieve all activities and case/ID/activity_log to get the logs of a single case. Both endpoints support filtering by the type of activity and the age of the entry conf_version/ endpoint has been replaced with the version/ endpoint, providing information about both the software and the configuration versionmake_filename that turns any string into a safe filename. *_OF_ANY operators to raise errors CASE.created_at to be used in date functions like DAYS_AGOcontent-type header of our webhook requests now correctly classifies them as application/jsonCASE.number_of_missing_information calculation when using the expression in a rulepredefined_values when creating new cases using the public APItrue and false can now be provided again as boolean values (instead of just "true" and "false")CASE.number_of_missing_information to be not synced with the bubblesCASE.number_of_missing_information to be calculated wronglyVIEW_CONFIGURATION right to use the full text configuration searchCASE.created_at that shows when the case was createdMontserrat as a font option for smart documentsCASE.number_of_missing_informationelif for if-then-else operatorszip_export command has been simplified. You can now specify a local path where the export will be created.predefined_objects from the api call POST cases/ is handled to use the same serialisation as PATCH cases/{{ID}} (update field) and update the api example with a free text value. CASE.owner.process_key in addition to process_iddelete_all_data from being executed correctly sometimescontains only operator that checks if all the elements of a list are elements of another listzip_import to work for databases using sslis known and is unknown operators from not evaluating complex expressions