Planet Crust has released a new update of Corteza, including new features and a long list of changes and fixes:

Release notes:

  • There is a known bug where multi-value fields crash the server or produce unexpected results in reports. If your configuration uses reports which utilize multi-value fields, skip this patch version.
  • Changed the workflow step configuration results section when no results are present for execute workflow, function, prompt, and iterator steps. The change was made because the results section was present even if no results were listed for the specified workflow steps The change was made by hiding the results section if no results are present (2b4619a).
  • Changed the uninformative RBAC rule import error messages reported by the provisioning system. The error was uninformative because RBAC rules, in this context, don’t use identifiers. The change was made because the error in question was uninformative and looked like this: failed to complete transaction: store encoder encode rbac-rule []: unsupported resource type '' for RBAC store encode. The change was made by allowing custom error reporting logic for specific resources such as RBAC rules (e2ac9c4).
  • Changed password constraints which saved their values as strings to save them as numbers. Additionally, the labels of the two fields were reworded to match the style of the other inputs in the password constraints section. The change was made because the password constraints were saved as strings; with this change, the constraints will be saved as numbers (aad919f, 703516c, a248000).
  • Changed the documentation about sanitizers and fixed the example links in module field validation tab to now point to the correct anchors. The change was made because the documentation was lacking information about field value sanitization. The change was made by updating the documentation with a new important section describing this behavior and changing the documentation links in the module field configuration to point to validators/sanitizers (9af28f2).
  • Changed record pages to reflect the operation (creating, editing, viewing) in the title of the public page. The change was made because the previous titles didn’t match the consistency of the other page titles. When you were editing a record instead of saying Editing a record page the title was saying Viewing record page, which was wrong. The change was made by changing the translation message of a record in the create, view and edit components (b3ded1b, f7a520f).
  • Fixed incorrect user count from the system metrics report due to system-defined users. The fix was made by excluding system users from the metric report We didn’t exclude them from the total, but they were excluded from the per-day aggregation (fd6465d).
  • Fixed the timestamp in the details of an action log being different as the one in search results. The fix was made by applying a custom formatting to the timestamp (a4596fb).
  • Fixed strict record value duplicate detection, which was preventing record creation with same values for fields for strict duplicate detection validation. The fix was made by validating duplication only for selected field (eac2f07).
  • Fixed sub workflows being unavailable in the workflow execution step after the server was restarted. The issue was caused by the initialization logic excluding sub-workflows from the filter. The fix was made by including the sub-workflows in the initial load, thus resolving the issue (d64b732).
  • Fixed action log search results not showing the correct outputs. The fix was made by fixing the lapsus where the from timestamp was used for both the from and to date range which resulted in no matches (1fa5f39, c63df82).
  • Fixed Low Code namespace export where the name contained characters like /, . broke the export because they broke the URL. The same issue was addressed for record export but with module name. The fix was made by URI encoding the filename and replacing dots with - as that caused the URL to be broken (1f0ea56, 920cc5a).
  • Fixed JSON codecs ident getting set to the field’s name instead of values, when editing a module/configuring field mapping. The JSON codec requires you to specify where the JSON object is located, not the name of the value. Since values are stored in values, the value has to be values (where the JSON is). The bug told Corteza to look for the column with the field name which probably never existed. The fix was made By correctly defaulting the values (580db32).
  • Fixed DAL connection configuration displaying the default DSN connection parameters instead of the configured one. The fix was made by properly merging the default values and user-provided configurations, as well as fixing edge-cases where the configuration was made available after the page had loaded In the later case, the user-provided configuration was never displayed instead of the default values (0b41074, f9f7e92).
  • Fixed using workflowID parameter in workflowList not working because the returning value was getting corrupted in JavaScript due to unsupported uint64. The fix was made by replacing []uint64 with []string for filterworkflowID that corrupted the input value for JavaScript (uint64 vs int64) In addition, the filtering was moved to the store level (ca7d4b0).
  • Fixed DAL code ignoring module ID when doing record lookup. If you wanted to select a record you were receiving the error message: Could not create record: check error messages on the form, and on the form it was saying: record not found This fix ensures proper module ID is used (one from the module field options)when doing lookup. The fix was made By using module-id from module field options and not field’s module ID (a8d2fef).
  • Fixed broken filter and codegen definition for workflow filters which resulted in generating broken filter functionality. Filtering subworkflows with subWorkflow 2 flag in workflowList was not returning any subworkflows. The fix was made by properly applying conditions when sub-workflow filter was used (5b2ba54).
  • Fixed missing dal connection translation by converting its error meta key reference to kebab-case. The fix was made by adding missing credentials translations to the locale under system/credentials (434, 9021d1b, baff7b7).
  • Fixed broken translation due to incompatible fileName case in locale. The fix was made by renaming the file name for resources as per expected format (kebab-case) (b2ad8c2).
  • Fixed record search endpoints needlessly degrading performance by computing totals and paging cursors even when not required. The performance hit was noticeable on larger datasets. The fix was made by short-circuiting processing sooner when totals and page cursor navigation was not required This doesn’t change external behavior as those parameters were not included even tho they were computed (24b5d7c).
  • Fixed data aggregation count function crashing the server when no arguments were provided (count()). The old version allowed this format while the new one did not and it crashed the server. The fix was made by adjusting validations and adding additional exceptions for this specific case (fd3552e).
  • Fixed action log search results did not change if you reset the filter parameters. The filter parameters are reflected in the URL. The fix was made by properly updating the search parameters in the URL (ca14671).
  • Fixed geometry values not being saved when changed manually in inputs. The fix was made by correctly detecting changes on the geometry value since it uses a more complex structure then the rest of the inputs (893e644).
  • Fixed record export filter not interpolating placeholders such as ${userID} which lead to non functional exports. The fix was made by adding evaluation to the record export filter to correctly evaluate and interpolate placeholders (9e9898b).
  • Fixed privacy web apps not being enabled in the default Corteza configuration. The fix was made by adding the privacy web applications to the HTTP_WEBAPP_LIST env variable (c8508f4).
  • Fixed Data Privacy Officer role unable to see or review requests in the privacy web application due to invalid permission configuration. The fix was made by updating provision YAML files with search and read on corteza::compose, corteza::compose:namespace, corteza::compose:module and corteza::system resources Additionally, Data privacy officer permissions were changed to be able to view and edit a privacy request (1d390f9, 69f33fa, 2b35b98, a5e192f, 18a687a).
  • Fixed missing translations for gateway, auth, dal sensitivity, and data privacy. The fix was made by adding the missing translations to corteza-locale (bb29fe2, 56046e9, e64befa).
  • Fixed errors on reports not being captured. The fix was made by properly capturing and displaying errors (8926c04).
  • Fixed required module field flag is not reflected on the corresponding model attribute on the nullable flag. The fix was made by explicitly setting the nullable flag on all attributes when generating models where fields set the required flag (eb89992).
  • Fixed incorrect type encoding for Low Code charts where numbers were represented as strings and references (IDs) as numbers instead of strings. The fix was made by adding a hotfix to assure that these exceptions are properly encoded and presented to Low Code charts The initial issue is on the database level but the exact solution is still up for debate and will be addressed later (55702ec).
  • Fixed Email, File, Number, String, and URL fields not showing validation errors. The error under the field now also indicates the duplicated value. You still need the field on the record itself in order to see the validation error. The fix was made by adding the missing errors component to field viewers that didn’t have it (that is shown for expression fields on record edit) (1cf316c, 6bebd21).
  • Fixed the suspended and revoke access buttons being shown even when creating a new user. The fix was made by only showing those buttons when editing a user (2c35552).
  • Fixed users unable to press the submit button when trying to edit a user and the submit button remaining enabled even if an invalid (or missing) email was provided. The fix was made by properly applying the permissions obtained from the API user object in the webapp User class and correctly updating the form’s state based on the email validation (d585399, 99775e1).
  • Fixed external auth providers not being re-fetched after updating user password. The fix was made by refetching the external auth providers after updating (07de6a6).
  • Fixed gauge chart step name not displaying when value was larger than the largest step. The fix was made by setting the default step name to the largest, since if we find another step where the value currently is, we will use that one instead (808e438).
  • Fixed extra whitespace disappearing when using a rich text editor for the String field. The fix was made by tweaking the configuration for the viewer (adding 'white-space': 'pre-wrap') and the editor (adding preserveWhitespace: 'full' to CRichTextInput parse options) (854e6c8, db1ace1).
  • Fixed being able to submit a federation node form even if URL and name were not defined. The fix was made by correctly validating the form and disabling the buttons as needed (0f5170d, b8a49fd).
  • Fixed ownership information not being displayed on the connection. The fix was made by using the correct value for the field ownership (by switching the value from connectionownership to connectionmetaownership) (d585399, 6e2e2b2).
  • Fixed unable to save auth clients when setting either the valid from or expires at. The fix was made correctly parsing date-time values we get from the API (04c8c4e).
  • Fixed incorrectly displayed error message when un-deleting messaging queue; it was displaying the error message Queue deleted instead of Queue restored. The fix was made Translations were added in locale and applied in admin (7af6c9e, e00a3da).
  • Fixed deleted messaging queues being un-deleted if they were edited. The fix was made by correctly preserving the deleted state when updating the messaging queue (90b5414).
  • Fixed incorrectly passed translations to Results/Namespace, Record and User. The fix was made by correctly passing translations via props and interpolation Previously, part of the translations were passed without using interpolation and the other translations were passed as attributes causing the texts to not be properly translated (bed2dfa).
  • Fixed the Corteza crashing when adding additional DAL connections. The issue was caused by improperly handled initial and empty states for the DAL connection resource. The fix was made adding exceptions to reject default configuration options (no connection params) and properly handling the default state on the web application’s connection editor (55636d9, f5297d3).
  • Fixed file uploads being rejected when specifying what MIME types are allowed or not. The issue occurred due to additional meta tags provided by the files or the underlying libraries. The fix was made by reworking how MIME types are validated by switching from comparing MIME type labels to a more robust library which was already used for detecting MIME types (ab987cc).
  • Fixed disappearing white spaces when using a rich text editor in the String field. The fix was made by adding ‘white-space’: ‘pre-wrap’ to String viewer and preserveWhitespace: ‘full’ to CRichTextInput parse options (a89208f, 854e6c8).
  • Fixed automation button resource translations not preserving between page refreshes. The issue was caused due to improper indexing as well as missing code to apply resource translations to record list selection buttons. The fix was made correcting resource translation indexing to start with 0 instead of 1 as well as adding missing code to correctly apply resource translations to record list selection buttons (7a5e839, 6d58bf4).
  • Fixed record page navigation and sorting issue. The fix was made by improving record iterator implementation for page navigation and sorting and also fixing store drivers to be consistent respective to their query language for dateTime, number, boolean data types (6f04666).
  • Fixed simple equality operator = in the filter query that checks for all values in multi-value fields but only the first one due to the changed encoding of record values. The fix was made by introducing new operators IN and NOT IN and should be used when filtering records containing value inside multi value field (f6e3035).

View the full changelog.

How to install Corteza

You can follow the offline deployment instructions for a local development or demonstration instance of Corteza. If you want to set up a live deployment, check out the extensive online deployment instructions. If you have questions, you can engage with other community members on the Corteza forum.

How to upgrade your Corteza instance

To upgrade your instance to the latest version of Corteza, follow our Upgrade Guide.

About Planet Crust

Planet Crust is the creator of and driving force behind Corteza, a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. For more information or to try Corteza on the cloud, please visit www.planetcrust.com.

About Corteza

Corteza is a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. Corteza comes with an Apache 2.0 license, and all code is published and can be reviewed at https://github.com/cortezaproject. All Corteza code is contributed to the Commons Conservancy Software Foundation. To stay up-to-date on the project, follow @CortezaProject on Twitter.

 

 

 

Planet Crust has released a new update of Corteza, including new features and a long list of changes and fixes:

Release notes:

  • Added support for DAL aggregation on the RDBMS level to improve performance on larder datasets by utilizing existing technology (1215511e2).
  • Changed privacy request comment loading indicator by introducing a spinner (46da70e).
  • Changed Corredor server to use a newer Pino version to the same version as elsewhere to avoid interface collisions (8893f33).
  • Changed Corredor server to no longer start if the provided configuration is invalid. The Corredor server now checks for validity and errors out if invalid (8893f33).
  • Changed JSON handling within the Corteza’s DAL package. We made the change to improve performance when processing a lot of JSON objects by switching to the valyala/fastjson package (ce6d7d02e).
  • Changed multi-value geometry field editor and viewer (32703e4, 46378d8).
  • Changed the API docs to be up to date and include automation endpoints (b03a09812).
  • Fixed memory leaks caused by DAL when running reports. The reporting logic didn’t close the open data sources (5d476dcfa).
  • Fixed invalid resource retrieval, which led to missing logos and fav icons on instances where the server and webapp are split. We resolved the issue by properly determining the URL for this scenario (1079236).
  • Fixed UI/UX issues in regards to the report builder’s tooltip and button sizes (bcf2b36), properly displaying page block headers and footers on plain page blocks (7e8fb2f).
  • Fixed duplicated result argument display on workflow function configuration. The issue occurred due to improper rendering condition (945f287).
  • Fixed expression values not being visible in the configuration sidebar when configuring workflows.
  • Fixed expression values not showing in the sidebar (2bae1bd).
  • Fixed failing namespace export when using namespace with characters such as / and .. The names are encoded before being sent over to avoid these issues (1d2fe47).
  • Fixed record edit/clone button not appearing on all records if no record page is present (71af271).
  • Fixed using ${ownerID} in filters, now properly uses the ownedBy value instead of the currently logged in user (like userID for its value does) (93f7ebc).
  • Fixed the process of undeleting auth clients (e69b0ef, 9ccdcae, 38626bd).
  • Fixed record export when the record count was 0 by preventing the export (2d7a1f6).
  • Fixed performance issues on integration gateway route reloading caused by re-registering all of the endpoints when one was updated (269cdb1ba, 955c4d9b9).
  • Fixed data corruption which was caused by an improper Low Code record value migration (7e4e4d3b5).
  • Fixed exporting records to a specific timezone by encoding the URI params (362ddca).
  • Fix workflow function errors caused by fetching an array of resources. The error was caused by a change in how expression types are determined and is temporarily patched with an edge-case exception (b581fe86a).
  • Improved error reporting on new user sign-up (57721291b).
  • Prevented stored XSS attacks in the logout back link by implying additional sanitation steps to the value (f1f4f4bd1).

View the full changelog.

How to install Corteza

You can follow the offline deployment instructions for a local development or demonstration instance of Corteza. If you want to set up a live deployment, check out the extensive online deployment instructions. If you have questions, you can engage with other community members on the Corteza forum.

How to upgrade your Corteza instance

To upgrade your instance to the latest version of Corteza, follow our Upgrade Guide.

About Planet Crust

Planet Crust is the creator of and driving force behind Corteza, a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. For more information or to try Corteza on the cloud, please visit www.planetcrust.com.

About Corteza

Corteza is a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. Corteza comes with an Apache 2.0 license, and all code is published and can be reviewed at https://github.com/cortezaproject. All Corteza code is contributed to the Commons Conservancy Software Foundation. To stay up-to-date on the project, follow @CortezaProject on Twitter.

 

 

 

Planet Crust, the driving force behind Corteza, is excited to announce a new major release: Corteza 2022.9. 2022.9 updates the UI and adds Data Privacy, a Data Access Layer, Record Revisions, Permissions Debugging, Duplicate Detection, ECharts and more.

Updated UI

Version 2022.9 has updated the Corteza UI with an improved, contemporary look. The new version also streamlines the user experience.

Corteza Privacy

Sponsored by EU, Corteza Privacy allows you to configure and describe where and how sensitive data is stored on a module-field level. It expands the current data storing capabilities and adds features that enable data privacy, giving administrators more control over data privacy and managing private data.

Corteza Privacy also includes a Data Privacy Console to allow users to self-service (e.g. request to remove, change or download personal data).

  • With information from data sources set on a specific data module, each record can hold detailed information about the ownership and location(s) of particular data.

  • System Administrators are obliged to provide a data storage location upon setting up a Corteza data module.

  • Corteza Privacy also enables the selection of predefined data policies or new policies to describe the processing purpose and rules at a record field level.

Read more

Planet Crust has released a new update of Corteza, including new features and a long list of changes and fixes:

Release notes:

  • Added a button to stop the automation session execution (4bdf43b, 6f72928, 8bcb405, 8b7791, 132948, bc62f7). We also added the button on the workflow trigger steps (3363a37). We added the feature to allow the termination of long-running or unresponsive workflows.
  • General UI/UX changes:
    • Changed the colour of the record deleted alert from info to warning variant (88b6006).
    • Fixed the app selector overflow where the user interface cut off the application labels on One (997d799).
    • Tweaked the responsive layout on the Reporter web application where blocks would overlap on smaller screens (287ed67).
    • Added missing translations and general UI and layout tweaks.
  • Changed the password reset flow to no longer log out of the current user (f7d1015). We changed to improve UX when the user would change their password multiple times in a row or the Admin web application. Corteza no longer invalidates the access token if it belongs to the currently authenticated user who is resetting their password.
  • Changed the Low Code record toolbar interface to only apply the can delete record operation to the delete button (56b5b5c). We changed as it introduced unexpected behaviour when users weren’t allowed to delete records.
  • Fixed missing translations on dropdown fields for funnel and gauge charts by moving gauge labels to tooltips (11640e6) and tweaking translations to be applied on initial load (65ea532, 9af61fa).
  • Fixed possible step corruption and other issues with fork and join steps (2521ac9).
  • Fixed missing translations for automation buttons on record list by fixing them on Corteza server (a2cea1c) and Corteza Low Code (eee5b37).
  • Fixed problematic database state when upgrading from older 2021.9 versions due to NULL constraints (fe464c4). The issue was caused by adding a table upgrade for the scenarios column where it explicitly demanded the column should not be NULL and expressly stated that the default value is, in fact, NULL. The database migration now correctly sets the default value to a non-NULL value.
  • Fixed calendars always show the month view as the default view regardless of what was configured on the page block. This is fixed by correctly applying the provided configuration options instead of constant values (8e46baa).
  • Fixed toolbar system button translations are disappearing when reordering pages. Toolbar system button translations were lost when reorganizing page hierarchy. The browser caused the issue due to cache clearing (c88f3a0).
  • Fixed the Low Code record page from raising errors by removing the view button for record pages without a record (a256393).
  • Fixed record lists not properly refreshing when viewed in the page builder (564c0aa). The filters weren’t properly handled when evaluated from the page builder. When viewing the page, however, the filters were evaluated correctly.
  • Fixed a bug which prevented the roles from being unarchived (11dfd0a). We fixed the bug by correcting the lapsus in the state when updating roles.
  • Fixed Number module field number display is limited to 3 decimals. The Number field now correctly allows precision (e3a8ecd, e1b08bf) with the default on 3 decimals (0b2aa68).

View the full changelog.

How to install Corteza

You can follow the local setup instructions for a local development or demonstration instance of Corteza. If you want to set up a live deployment, check out the extensive production setup instructions. If you have questions, you can engage with other community members on the Corteza forum.

How to upgrade your Corteza instance

To upgrade your instance to the latest version of Corteza, follow our Upgrade Guide.

About Planet Crust

Planet Crust is the creator of and driving force behind Corteza, a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. For more information or to try Corteza on the cloud, please visit www.planetcrust.com.

About Corteza

Corteza is a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. Corteza comes with an Apache 2.0 license and all code is published and can be reviewed at https://github.com/cortezaproject. All Corteza code is contributed to the Commons Conservancy Software Foundation. To stay up-to-date on the project, follow @CortezaProject on Twitter.

Planet Crust has released a new update of Corteza, including new features and a long list of changes and fixes:

Release notes:

  • Added a new option to the record list which forces the viewed records to be opened in a new tab instead of the current window. The feature was added to remove the need to navigate back and forth, re-apply filters when users are working on multiple records from a record list (25e7090, f7191e5, 98fc48e).
  • Added a new link to parent option to the Record module field which dictates wether the input value will be pre-filled with the parent’s record ID. The feature was added to allow some cases from not pre-populating the input, such as a module with a record field which points to itself (059ebf8, a79a852, 0e9de63).
  • Added support for resource translations on Low Code funnel and gauge charts. The feature allows the user to translate funnel and gauge chart step labels (9f61346).
  • Added Content-Type: text/javascript header to the config.js file served by Corteza server. The headers were added because when MIME sniffing was prevented, the web applications would stop working (1bdf2b5).
  • Added new .env AUTH_JWT_ALGORITHM option allowing you to configure what algorithm to use with your JWT tokens (480e70e, 8e42126).
  • The record list now waits for the filtering to finish before allowing further filtering. The change was made due to unexpected cases where filter A resulted after filter B so the record list showed data from filter A instead of B. The record list now waits for you to finish typing the query before fetching the data and locking the input (dea2d99).
  • Changed module field expressions to clear out the record value when the expression returns the value null. Previously, the field would show the zero-value for that type, such as 0 for Number field. The change was made to allow field expressions to clear out their values, useful for some specific cases (0bef905).
  • Changed the password reset policy to prevent users from re-using their old passwords. Previously, users could reset their current password to the same one as they’ve previously used, but now such a change is no linger allowed and caused the password reset to fail (b44024f)
  • General UI/UX changes; tweaked chart resource translation button sizes (255317a), remove console error about undefined module when creating a chart (482d971), fix record field multi delimiter (e7249fb)
  • Removed Boolean and Record fields when searching Corteza Low Code records using the search input box. The Boolean field was removed because the truthy/faulty evaluation produced too loose filters causing unexpected results. The Record field was removed because the values are searched using identifiers which caused confusion in some cases. You can use the field-specific filters to cover these two cases (dea2d99).Important: The API filtering still supports the same set of fields as it did previously. The exclusion was specific to Low Code record lists.
  • Removed the “delete” button on the create template user interface on the Admin web application. The button was removed because there is no need for it to be there since you can’t delete a not yet created template (b72bdd0).
  • Fixed the workflow expression editor modal discarding the changes when saving using the cmd+s shortcut. The cmd+s shortcut is now disabled when an expression editor modal window is opened (0803d25).
  • Fixed the trigger path change notification not disappearing when reverting using the cmd+z shortcut. The trigger path change logic now properly evaluates the cmd+z and cmd+y shortcuts (a43e106).
  • Fixed improper multi-value module field handling in Corteza Reporter tables. Previously, the multi-value field would cause the row to duplicate, but now it is shown as one where the values use the same multi-value delimiter as configured in the module field (d65a767).
  • Fixed RBAC rule provisioning issue where the rule migration attempted to create a duplicated RBAC rule entry. The migration step now skips any RBAC rules which would cause a duplicate error when migrated (1f657b3).
  • Fixed broken backwards compatibility for the workflow compose record delete function. A prior bug-fix introduced additional lookup parameters which were set as required, causing the old scenario where an actual Compose Record was provided to no longer work. The compose record delete function’s namespace and module arguments are no longer required but are enforced in the background logic (378d0f2).
  • Fixed improper password constraint validation where the input boxes didn’t properly validate some edge cases. The minimum password length is now limited to minimum of 8 characters and the other properties no longer allow negative values (192bc08, e0f912b, 9b424a6).
  • Fixed improper calendar Low Code page block responsiveness which caused it to appear cropped when it was added. The bug was fixed by manually tweaking the calendar’s elements for layout changes (cf66f22).
  • Fixed Low Code charts not showing any data when the ${record} or ${recordID} pre-filter variables were used. The issue was caused because records were incorrectly resolved and not available in time (ec33de1).
  • Fixed Record field’s options when using a nested Record field where data is duplicated. The fix now correctly resolves duplicated records and correctly displays option labels (b954f59).
  • Fixed record list’s display where only one column is shown. The issue was resolved by adjusting the columns for the “metadata” (the checkbox and the action buttons) (2671c5d)
  • Fixed record page preview when accessing without a record. The page no longer infinitely loads and generally prevents access if there is no record (21c4f04, 924934e).
  • Fixed a visual bug with multi-value Record fields where the last selected record would be shown as the placeholder even if removed from the list of selected records. The fix now opts out of using the last selected record as the placeholder but falls back to a generic label (491bc19).
  • Fixed a display error for report tables when a joined data source provided no data. The table column now properly handles this edge-cases and constructs the table appropriately (953556a)
  • Fixed an error when trying to mark a role as contextual. The error was caused by an invalid internal state and is now resolved (b14e4e7)
  • Fixed failing index creation for Corteza Discovery caused by an unsupported data type. The fix changes the used data type for the cases which caused the index to fail. The error was caused by identifier indexes such as module ID, namespace ID, and record ID (25ebf75)
  • Fixed invalid time produced by the Date Time field when time, past/future, and relative output options were selected. The date-time logic now properly handles this option combination and properly handles the value (a4bbbab).
  • Fix improper resource translations for Low Code charts when looking up specific charts (b8ad97e), module fields when looking up specific modules (5ccd682)
  • Fixed improper record list and chart pre-filter evaluation which caused a pre-filter with ${recordID} to display no data when creating new records (6da48a0)
  • Fixed invalid counter when exporting records from a record list (d837e9e).
  • Added SonarQube GitHub build action to Corteza server (5999c70).

View the full changelog.

How to install Corteza

You can follow the local setup instructions for a local development or demonstration instance of Corteza. If you are looking for setting up a live deployment, check out the extensive production setup instructions. If you have questions, you can engage with other community members on the Corteza forum.

How to upgrade your Corteza instance

To upgrade your instance to the latest version of Corteza, follow our Upgrade Guide.

About Planet Crust

Planet Crust is the creator of and driving force behind Corteza, a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. For more information or to try Corteza on the cloud, please visit www.planetcrust.com.

About Corteza

Corteza is a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. Corteza comes with an Apache 2.0 license and all code is published and can be reviewed at https://github.com/cortezaproject. All Corteza code is contributed to the Commons Conservancy Software Foundation. To stay up-to-date on the project, follow @CortezaProject on Twitter.

Planet Crust has released a new update of Corteza, including new features and a long list of changes and fixes:

Release notes:

  • Added support for workflow prompts to Corteza One and Admin web applications (Low Code already supports prompts). Some web applications don’t show certain prompt types such as “redirect to record page” (#76e4410, #c74fe70, #f95d26f, 6e835bc, #c62f9fe, #2909ca3).
  • Added a print layout to assist with print to PDF browser features. This feature helps produce nicer output PDF document without the unneeded UI navigation and other resource management elements (#ed8ee8b, #d980c0b, #c71e1f0, #f005b62, d582560).
  • Added support for provisioning JSON system setting values when running the provisioning step. The support was added to allow provision YAML files configure record toolbar button visibility (#05b97ee). An example of this would be compose.ui.record-toolbar: { "hideBack": true }.
  • Changed Low Code user interface UX by adding spinners to indicate data loading (#11c7cf8), changing calendar event cursor to pointer (#75cc346), added additional exceptions for record list sorting and filtering to avoid strange behavior (#70c6277, #6826d19), added a small delay when processing Record fields (#b6e722d).
  • Changed chart font family to Poppins-Regular to make them consistent with the rest of the Corteza design (#0349363).
  • Changed user authentication session and access token logic as well as updating corresponding .env variables and their descriptions (#7f84994). Changed the authentication session and corresponding cookie to expire on session end when using “log in”, and after the specified lifetime when using “login and remember me” (#5fd5b93). Changed the “login and remember me” button to not show if the AUTH_SESSION_PERM_LIFETIME .env variable is set to 0 (disabling the feature) (#ad53ea9).
  • Changed the Corteza Low Code sidebar to show the link to all namespaces at the top of the dropdown. This change allows the link to be visible even with many namespaces present (#15ca4000).
  • Changed and standardized name and handle input value validation across all web apps. The change was made to provide a more consistent user experience across Corteza web applications. The inputs now properly display if the provided value is a valid name/handle or not (#e3bbec7, #cae73df, #1b1d165).
  • Changed the module field kinds to be sorted alphabetically when editing the module. The change was made to provide a more consistent user experience when configuring Low Code modules (#8378e73).
  • Removed the AUTH_JWT_EXPIRY .env variable because it is replaced by the AUTH_OAUTH2_ACCESS_TOKEN_LIFETIME .env variable (#e626bcd).
  • Fixed broken Low Code module export which caused Record fields to become unconfigurable after the module was imported (#1219112).
  • Fixed invalid RBAC rule migration where a rule could use wildcards between resource IDs (invalid state). A new migration step attempts to correct the broken RBAC rules (563a73c6).
  • Fixed improper workflow prompt handling when user has multiple Corteza instances (tabs) open at the same time. Corteza web applications improved communication on what prompts are already resolved and where the prompts should be shown (#40e5416).
  • Fixed improper number and text setting value decoding by covering edge-cases (#ced2daf).
  • Fixed invalid valid JSONL files being rejected when importing records by adding additional fallback content-type checks to the preprocessing logic (#f726d3f).
  • Fixed improper record access control rule migration due to invalid paging (#b6d13d9).
  • Fixed infinite loop webconsole alerts when offline (#d8e57b1).
  • Fixed improper Federation URI node generation by including the API base URL (#798c31e).
  • Fixed system healthcheck panic when Corredor connection is not available (#2ff1108).
  • Fixed broken module field value expressions where the old record reference was used. The issue occurred because the value was never provided (#7135903).
  • Fixed improper credential validation on user registration causing the user to be created even when invalid credentials (mainly the password) was provided. The fix moves the password validation step to the earlier stage of the sign up flow (#c1500df).
  • Fixed improper record count for grouped reports where multi-value fields are involved. The fix, for some cases, omits duplicate values (#416a7ec).
  • Fixed page blocks resetting to their default positions when the changes are saved (#efe24c3).
  • Fixed improper resource translation user interface content parsing which caused some of the paste events to clear out the contents or block the editor (#6a195df)
  • Fixed and assured that multi-value delimiters are properly displayed when viewing the record value (#a211af6)
  • Fixed duplicate resource translations when exporting the Low Code namespace. The fix applies extra pre-processing and validations before the resource translations are outputted to the archive (#dcef397).
  • Fixed custom field validation error messages not showing based on the user’s language. The value validator now utilizes i18n capabilities to provide appropriate error messages (#f9e9433).
  • Fixed improper RBAC rule correction migration procedure caused by an unrestricted data fetch overloading the database. The procedure now gradually fetches the required data thus avoiding the issue (#f310442).
  • Fixed failed workflow prompts from not being dismissible (#ff3d0e6).
  • Including the web console bundle into the built corteza-server (#54fffd0).
  • Defined a new resource utility structure which helps improve operation performance by performing smarter indexing strategies. The structure was applied to current RBAC access control service, the RBAC rule export and resource translations export services (#0466ffe, #e7c1fe1, #a68ddf1, #aef3171).

View the full changelog.

 

How to install Corteza

You can follow the local setup instructions for a local development or demonstration instance of Corteza. If you are looking for setting up a live deployment, check out the extensive production setup instructions. If you have questions, you can engage with other community members on the Corteza forum.

How to upgrade your Corteza instance

To upgrade your instance to the latest version of Corteza, follow our Upgrade Guide.

About Planet Crust

Planet Crust is the creator of and driving force behind Corteza, a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. For more information or to try Corteza on the cloud, please visit www.planetcrust.com.

About Corteza

Corteza is a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. Corteza comes with an Apache 2.0 license and all code is published and can be reviewed at https://github.com/cortezaproject. All Corteza code is contributed to the Commons Conservancy Software Foundation. To stay up-to-date on the project, follow @CortezaProject on Twitter.

Corteza 2021.9.11 has been released. It includes the following fixes:

  • Fixed improper credential validation on user registration causing the user to be created even when invalid credentials (mainly the password) was provided. The fix moves the password validation step to the earlier stage of the sign up flow (#ff13912).
  • Fixed improper record count for grouped reports where multi-value fields are involved. The fix, for some cases, omits duplicate values (7546dbb).

Read more

Corteza 2021.9.11 has been released. It includes the following fixes:

  • Fixed improper PostgreSQL formatting for ISO timestamp templates by adding an edge-case exception (#034a7f9).
  • Fixed improper number and text setting value decoding by covering edge-cases (#ced2daf).
  • Fixed improper module field resource translation encoding, decoding, and store persistance causing the field description and hint field to get mixed up by fixing invalid value mapping and removing translations from the DB (#0422e5f, #e7ea299, #6c2dd28).
  • Fixed improper workflow prompt handling when user has multiple Corteza instances (tabs) open at the same time. Corteza web applications improved communication on what prompts are already resolved and where the prompts should be shown (#ef238df).
  • Fixed broken module field value expressions where the old record reference was used. The issue occurred because the value was never provided (#993cd22).

Read more

Planet Crust has released a new update of Corteza with several new features, such as record list filter preservation in the local browser storage. Additionally, a list of changes and fixes is included.

Release notes:

    • Added an empty check for module field name validation (d3c33a6).
    • Added more descriptive tab titles based on what page the user is currently on (d6bb352, a7f36e5).
    • Added record list filter preservation in the local browser storage (52ff728, bc2dd98). Note that the saved filters are only available on the browser they were saved in.
    • Changed static translations for Low Code modules (5efb7c9) and integration gateway filters (98f8e4b).
    • Changed resource configuration input states to be more consistent (2ef02c5).
    • Changed date-time record filter format template to ignore seconds (fc2eab1, 07c409e).
    • Changed resource activity log store definitions to be more restrictive and less flexible (e7ed1d8).
    • Changed record module fields to show a user-friendly label of the nested user field instead of the user ID (0d4d74b).
    • Changed chart configuration by hiding the “add metric” button when no module is selected (a3177bc).
    • Fixed queue search on the Admin web application (98a5d95, e6a0b0f).
    • Fixed integration gateway route search on the Admin web application (f821dd8, 5ddddf8).
    • Fixed broken resource translation migration when the related resource was deleted (1786eda).
    • Fixed chart configuration’s improper error handling (d4bf472) and improper state handling when a new chart was created (41b0a15).
    • Fixed improper resource translation handling for Low Code module field’s hint and description properties. The two properties were flipped (q7fbaf94, 1c6b793), incorrectly removed from resource translations when removed in the field configuration popup (d4c9243), and not reflected on the web application (18de72f).
    • Fixed charts failing to load in cases of incorrect state management (629d306).
    • Fixed record list filter not resetting when deleting filter rows (00b491d).
    • Fixed improper authentication scenarios loading when running the in development mode (d280fc7).
    • Fixed improper refresh token expiration. When new refresh tokens got issued they did not adjust the expiration timestamps (e7d3df1).
    • Fixed new Low Code record pages failing to load due to missing button definitions (b135287).
    • Fixed item selection lists (primarily module fields) where the item would get duplicated (9a33368).
    • Fixed the system crashing once user attempts to exchange invalid credentials by redirecting them to the login page (0c49832e).
    • Fixed improper peer-closed connection error handling which needlessly spammed error tracking systems (ab248fe1).

View the full changelog.

 

How to install Corteza

You can follow the local setup instructions for a local development or demonstration instance of Corteza. If you are looking for setting up a live deployment, check out the extensive production setup instructions. If you have questions, you can engage with other community members on the Corteza forum.

How to upgrade your Corteza instance

To upgrade your instance to the latest version of Corteza, follow our Upgrade Guide.

About Planet Crust

Planet Crust is the creator of and driving force behind Corteza, a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. For more information or to try Corteza on the cloud, please visit www.planetcrust.com.

About Corteza

Corteza is a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. Corteza comes with an Apache 2.0 license and all code is published and can be reviewed at https://github.com/cortezaproject. All Corteza code is contributed to the Commons Conservancy Software Foundation. To stay up-to-date on the project, follow @CortezaProject on Twitter.

Planet Crust has released a new update of Corteza including new features, such as additional Geometry field options and persistent storage on record filters. Additionally, an extensive list of fixes, such as a memory leak fix, have been included. With this release, the stability, speed and User Experience of Corteza have improved significantly.

Release notes:

  • Added deleted resources to Discovery indexing and searching (09d69f124)
  • Added JWT token duration option to the CLI command (679af2f55).
  • Added additional Geometry field configuration options such as default zoom-level (a8534ed, b7ab3e47, 97d1aed3, 98cf01b8).
  • Added processing indicator to record organizer for improved UX (0e85fbca).
  • Added support for translating system Low Code module fields (623adaf3).
  • Added persistent storage to record list filters allowing you to reuse previously used filters (e18267fd).
  • Added Discovery web application to the make webapp make command
  • Added pagination to search responses improving web application performance for large responses (e046f12, 7cb2d64)
  • General UI/UX improvements on Corteza Low Code, Corteza Admin, Corteza One, and Corteza Workflow.
  • Changed Low Code deletion to also remove the related record page 0ceade66
  • Fixed File upload for CSV files where the server incorrectly detected the MimeType 195c2bb13
  • Fixed invalid workflow resource iterator management where larger datasets crashed execution due to improper resource limitation implementation (0792c0a17).
  • Fixed improper workflow execution tracing where the workflow execution logic ignored the workflow trace parameter (41667a7da).
  • Fixed data race errors for pkg/locale (345050990), pkg/corredor healthcheck (a797c847b), pkg/healtcheck (662f5155b), WebSockets (e8cd7d37d), and pkg/scheduler (4a75778c1).
  • Fixed time transformation expression functions erroring out when valid string encoded time values were used (5b40f7875).
  • Fixed memory leak errors causing performance degradation on WebSockets (c64116fc8), content sanitization (9346b5702), Workflow loading (fa614c7ac), and expression processing (adee67f6b).
  • Fixed workflow attachment uploading for all supported types (Reader, Bytes, and String) (6fd2288df).
  • Fixed prompt duplication by preventing prompts from being resent over web sockets (SERVER_COMMIT_BASE)9c0026462[9c0026462].
  • Fixed Workflow HTTP request function basic authentication header preparation 2898e1b8c
  • Fixed CInputDateTime responsiveness (b0c6422).
  • Fixed CSidebarNavItems behavior (7c7b708).
  • Fixed missing report page block display elements (1625d1fc)
  • Fix Low Code failing to load due to read-only parameter assignment (ce5cd504).
  • Fixed system field translations in record page blocks (fa7e6808).
  • Fixed overflowing record list notification indicating there are no records to show (12b9fc7f).
  • Fixed inline record list saving (f54452c7).
  • Fixed system fields not appearing in record page blocks (de874a8b).
  • Fixed record list footer overflowing page block (9cb2d923)
  • Fixed field expression documentation link (301a1de8).
  • Fixed dropdown selects overflowing the screen (8e37e2b8).
  • Fixed feed indexing for deleted resources (f5cfb6c).
  • Improved E2E testing by adding data-test-id tags to specific UI components (56af630c0, 3bb8fe59).

View the full changelog.

 

How to install Corteza

You can follow the local setup instructions for a local development or demonstration instance of Corteza. If you are looking for setting up a live deployment, check out the extensive production setup instructions. If you have questions, you can engage with other community members on the Corteza forum.

How to upgrade your Corteza instance

To upgrade your instance to the latest version of Corteza, follow our Upgrade Guide.

About Planet Crust

Planet Crust is the creator of and driving force behind Corteza, a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. For more information or to try Corteza on the cloud, please visit www.planetcrust.com.

About Corteza

Corteza is a 100% open-source low-code rapid application development, business process management and integration platform for software vendors, system integrators and internal development teams. Corteza comes with an Apache 2.0 license and all code is published and can be reviewed at https://github.com/cortezaproject. All Corteza code is contributed to the Commons Conservancy Software Foundation. To stay up-to-date on the project, follow @CortezaProject on Twitter.