Change Log

Improvement

• namespace is now an optional attribute in the exports tag, previously it was mandatory
• value_int and value_boolean GraphQL arguments will work also with castable string data
• added property argument in the compact filter to be better compatible with the built-in Liquid implementation
• possibility to sort by property defined in user.yml in the users GraphQL query
• error handling of the new import CSV mechanism

Bug Fix

• fixed edge case scenario when invalid argument was provided in the parse_json filter
• fixed edge case scenario when resource was set to Model in Form

New Feature

• [Beta] new property type upload to replace custom_images and custom_attachments. It is still work in progress and the interface might change. Final documentation to be provided within the next few weeks.
• added sms_send GraphQL mutation to work similarly to email_send and api_call_send

Bug Fix

• gracefully handle error when admin_* mutation was invoked with name, but without required physical_file_path
• pos-cli logs sometimes included unnecessary internal error message
• added model_name as a restricted property name
• added graceful handling of a scenario of uploading a file with a name that's too long
• added better handling of invalid regpexp in regex_matches filter
• fix descriptions of multiple GraphQL mutations
• fix documentation example of raw_escape_string filter
• fix edge case scenario when integer is provided as a path name for the include tag
• {% form %}{% endform %} was rendering nothing instead of the form HTML tag
• fixed edge case scenario when invalid arguments were provided to precision argument in the time_diff filter
• fixed edge case scenario when invalid arguments were provided to the format_number filter

Bug Fix

• change default sort of modules in Partner Portal to show the newest first
• array_append will not crash when used on property with NULL value
• when using {% log form %} inside default_payload and then in callback_actions its value will appear the same

New Feature

• Officially deprecate the asset_path filter in favor of asset_url

Bug Fix

• model_update_all mutation will now update deleted data as well
• use support email in Partner Portal in notifications about failed module deployment

Improvement

• Form's metadata is now also accessible on the form object via form.metadata. You will be able to use Liquid as a value, for example:
• `

• resource: model
• metadata:
• hello: "{% assign var = "world" %}{{ var }}"

• {% form %}
• {{ form.metadata.hello }}
• ...
• {% endform %}
• `
• index..liquid will have a default slug pointing to root. For example, if you have a file in app/views/pages/my/page/index.html.liquid then the default slug will be my/page. The property max_level_deep will prevent any extra slug components by default, so in this scenario /my/page/abc will return a 404 error. To maintain backwards compatibility, if you manually set the slug property then max_level_deep will not be changed.

Bug Fix

• The misleading error message "Form configuration has not been found" which was rendered via pos-cli when you tried to delete a resource which did not exist has been fixed and will include the correct name of the resource which you try to delete.

Improvement

• Update error message when rendering a form with invalid configuration.
• Improved authorization scheme (for pos-cli) based on OAuth tokens - generated tokens will be scoped to one Instance. The old scheme is kept for backwards compatibility.

Bug Fix

• The admin_model_schema_update will properly update properties instead of trying to re-create them.

Improvement

• Moving / renaming names - improved mechanism of detecting which resource to update when either the physical file path or the name property changes to avoid creating duplicates and raise validation uniqueness errors. For example, when you move a file from:
• modules/my_modules/public/form_configurations/my_form.liquid to modules/my_modules/private/forms/my_form.liquid, we will recognize this is the same file (public changed to private and form_configurations changed to forms), even if the name property changes within the file
• modules/my_modules/private/forms/my_form.liquid to modules/my_modules/private/forms/some_dir/my_form.liquid, we will recognize this is the same file (moved the file into a new directory some_dir), but only if the name property will not change
• Additionally, we will also correctly recognize the file if you change the name property without changing the file's location. However, it is allowed to update the deprecated directory name to the new one, as well as to move file from public to private and vice versa - as described in the first example.

Bug Fix

• Fixed edge case scenario of creating a User Profile via GraphQL mutation, then exporting the data and trying to import it, which was causing a 500 error

Improvement

• name property will be automatically derived from physical_file_path for all admin resources like Authorization Policies, Notifications, Forms, Model Schemas etc. For example, app/authorization_policies/dir/my_policy.liquid will have the defult name dir/my_policy. For backwards compatibility, it is still possible to overwrite the default name using the name attribute.
• Deleted objects are not returned by default for models and users queries. To fetch soft-deleted records, you can still use filter for deleted_at field.
• When changing the type of a property, for example, from string to integer, all the data will be updated behind the scenes. In case of type casting error, a validation error message will be thrown and deploy/sync will fail, until data is manually fixed, for example, via GraphQL Mutations.
• GraphQL engine has been upgraded.

New Feature

• The notifications directory structure has been flattened - new directories are now app/emails, app/smses, app/api_calls. For example, instead of app/notifications/email_notifications/my_email.liquid you can now place it in app/emails/my_email.liquid.
• Added extra algorithms to JSON Web Token (JWT) filters and allow to specify algorithm for JWT mutation.
• Added extra validation for physical_file_path, to make sure files have proper extensions, for example, liquid for Forms, Authorization Policies and yml for Model Schemas.

Bug Fix

• Error message for layout_path / layout will not include confusing layouts/ prefix in the suggestions
• Improved Domain name internal validation.

Input Slider

Added Input Slider component to the figma design system.
For more information view the Figma component here and view the documentation here.

Improvement

• change soft user profiles validation to hard validation for Form
• In October we added extra notifications via pos-cli when trying to sync a Form with invalid fields - if it included profiles which did not exist, we were adding a warning message. For consistency and better UX, we are changing it to hard validation now, which means you will not be able to deploy/sync such forms anymore until the issue is fixed.
• server side handling of invalid file path
• When trying to sync a file from a path which does not match anything (for example app/my_form.liquid instead of app/forms/my_form.liquid), a meaningful error message will be shown now, instead of a success message. In such a scenario, the pos-cli deploy command will still succeed, however it will send a warning with a list of all the files which were ignored.
• Legacy Partner Portal domains will now redirect to [https://partners.platformos.com]
• A first User will not be automatically created on the new Instance
• Allow to filter admin_* GraphQL Queries by physical_file_path

New Feature

• Partner Portal API Instance Copy endpoint with documentation

Bug Fix

• update ReCaptcha to fix problems caused by Google API backwards incompatible changes