Change Log

Improvement

• _destroy_all mutations run in background - timeouts on invoking destroy_all mutation could result in invalid ElasticSearch state
• error message for invalid page type
• pos-cli changelog is [kept separately].

New Feature

• asset_path filter, although it's recommended to keep using asset_url

Bug Fix

• allow to log form variable in validations
• issue with triggering error in forms due to missing user attributes
• invoking admin_* mutations in background tag

Improvement

• pos-cli changelog is [kept separately].

Bug Fix

• related model not respecting name when used in has one mode
• duplicating modules prefix when updating layou via admin_layout GraphQL
• deploy silently failing and returning success message

Improvement

• relative assets improvements - proper cache headers, no cookies
• migrations handling - user-friendly error messages
• pos-cli changelog is [kept separately].

New Feature

• JWT authentication - User has a new field jwt_token which can be then passed as an argument to the new jwt_decode_and_set_session mutation.
• Developer guide icon
• Learn more: [Authenticating a User with a JSON Web Token (JWT)]

Bug Fix

• user.yml properties fixed uniqueness validation
• updating user's Authentications via GraphQL mutations
• timeouts, which were affecting some instances during data import even for a small sample

Improvement

• authentications property for user create/update mutations
• authorization tokens for pos-cli are now per instance instead of global
• pos-cli changelog is [kept separately].

New Feature

• assets accessible via relative path - all assets located in assets directory can be now accessed via https://your-domain.com/assets/

Bug Fix

• property_array argument in mutation accepts now empty arrays instead of ignoring it

Improvement

• rename graph_queries to graphql
• rename form_configurations to forms
• pos-cli changelog is [kept separately].

New Feature

• unsubscribe modules in Partner Portal
• new [presigned_upload_url] GraphQL mutation
• allow to upload images and attachments via user / model / user_profile mutations

Bug Fix

• fix GraphQL error when you put hash into property array
• fix regression issue with custom 404 pages

Improvement

• replaced customizations with models in examples
• clean up output of form variable when custom_image/custom_attachment is provided

New Feature

• allow user to access their custom request headers via context.headers

Bug Fix

• filtering data by empty values - users and models endpoints will properly filter items with values that are empty. For example:
• `models(
• per_page: 20,
• filter: {
• properties: [{ name: "warning", value: "" }]
• }
• ) { ... }
• `
• removed articles about CustomAddress - there is a better way now via models - [https://documentation.platformos.com/developer-guide/records/using-geojson-format-geolocation]
• exception in data import is no longer raised when item with given external id does not exist
• 500 error when trying to include partial without a name - {% include '' %} will render user friendly error
• gracefully handle exception in jwt_decode filter
• gracefully handle empty string provided to parse_json filter/tag

Improvement

• admin_ GraphQL mutations - modules/my_module_name prefix will be automatically added to the name of notifications, authorization policies, etc., based on physical path, to make it consistent with the pos-cli behavior
• layout validation - added validation to the layout property of Page to make it impossible to assign layout which does not exist
• validate Model belongs to the defined Model Schema - when defining a Form with a concrete Model Schema name as resource, it will not be possible to use it to update the Model, which belongs to the different Model Schema
• form and data in the notifications - previously data was accessible if the Notification was triggered via GraphQL and form if it was triggered via Form. Now you can always use both, which should make it easier to re-use Notifications. Also, documentation for triggering an API Call Notifcation was updated accordingly to show both ways of triggering it.
• validation for related resources in GraphQL - GraphQL will return an error if you try to use invalid values (for example property name which does not exist) for related models.
• pos-cli changelog is [kept separately].

New Feature

• graphql models() can be filtered by related users: for example you can filter cars by owner name
• ` models(
• per_page: 10
• filter: {
• name: { value: "cars" }
• related_users: { join: { foreign_property: "car_id" }
• filter: { properties: [{ name: "name" value: "Mike" }]
• }
• }
• }
• ) { ... }
• `
• multilingual notifications - added locale attribute to Email/SMS/API Notifications, which accepts liquid, to evaluate to the locale which should be used for translations
• auth0 integration - added auth0 integration and documentation on how to integrate various Identity Providers (Auth0, Facebook, Twitter etc.) with platformOS

Improvement

• Last edit:
• page slug can now consist of any components: Previously the page slug had to be maximum three levels deep. The improvement allows you to provide any slug you want, for example /one/two/three/four/five. However, please note that if you define page /one/two/three/four you won't be able to access /one/two/three/four/five - template slugs still work only for three-level deep slugs.
• {{ form }} output improved: The form variable will not include magical keys anymore, the output now corresponds to the fields defined in form configuration.
• {{ hash }} and {{ array }} will render proper JSON: You don't need to use the json filter. {{ users | json }} will become {{ users }}. The change is backward compatible, meaning the extra | json is just unnecessary but does not break anything.
• added filter by searchable field to admin_pages graphql endpoint: With a new filter you can exclude some pages from being shown in search results.

Improvement

• pos-cli: the gui serve will return a user friendly message if the port is already taken.
• pos-cli: the audit command will be automatically run during deploy; its performance has been greatly improved.
• Redesigned emails for modules in Partner Portal
• Renamed Customization to Model and CustomModelType to Model Schema - all existing occurrences of deprecated namings were removed from examples, documentation and platform.

New Feature

• pos-cli: the old marketplace-kit has been forked into a new package - [pos-cli] ([on github]). From now on marketplace-kit is in archive mode and will no longer be developed.
• Follow these steps to migrate from marketplace-kit to pos-cli:
• When using local node installation (for example installed using nvm or brew):
• `npm r -g @platform-os/marketplace-kit
• npm i -g @platformos/pos-cli
• `
• When using global node installation (use sudo if the version without it does not work):
• `sudo npm r -g @platform-os/marketplace-kit
• sudo npm i -g @platformos/pos-cli
• `
• From now on, use the pos-cli command instead of the marketplace-kit command, and remember to update your scripts if they used marketplace-kit.
• form_submit mutation was added to GraphQL: This new mutation will trigger a form submission along with invoking authorization policies and validation. It accepts two parameters: form_name and params. This way, you will be able to easily validate any user parameters against a given form configuration and persist it if valid. Most useful for creating API endpoints which re-use existing form configurations.
• Added the possibility to fetch related users for the models GraphQL query - [Model]

Bug Fix

• Fixed a couple of issues related to ElasticSearch type collision removal - mainly for related models
• Removed MIT license hardcoded text in Partner Portal

Improvement

• form_name optional: No need to duplicate GraphQL mutation input via Form - the form_name attribute is now optional in GraphQL mutations like user_create, user_update, customization_update, etc. You can still use it if you want to leverage existing configuration doing something in a callback/async callback or for sending emails, but you don’t have to.
• Set http_status to Authorization Policy: Added possibility to set http_status to Authorization Policy (previously hardcoded to 403). This allows you to render your custom 404 when an Auth Policy is violated. Moreover, now you can also customize 403, 500, and 503 (maintenance) pages by creating a page with the corresponding slug - 403, 500, or 503.

Bug Fix

• Double error message: Fixed double error message for image validation (that occurred in some cases).