Posts

Corteza 2021.9.8 released

Corteza 2021.9.8 has been released. It includes the following updates, improvements and changes.

  1. Changed default background colour to white in MetricConfigurator (49a525a).
  1. Fixed count expression function to properly handle the no argument case when typed values are being used (usually when invoked via workflow expressions) (5d7d3aa3).
  2. Fixed improper page blockID assignment on page create (95065f8e7).
  3. Fixed improper page blockID assignment on page create (95065f8e7).
  4. Fixed role management on external auth providers (d679a59).
  5. Append custom args when executing Corredor scripts via Compose REST handlers (2741e3577).
  6. Fixed improper handling of unresolved (type any) values (5ff68c414).
  7. Hide refresh data button when no data is present in MetricConfigurator (8fc446c).
  8. Increase z-index for PageBuilder to avoid toolbar with icons appearing below the Block’s title and description (667a9b0).
  9. Translate messages in errors component (acd5473, 1e933b2, 0af18b1).
  10. Reminders of other people showing up (63b3efe).
  11. Translations of field configurators and calendars (d4a379e, 5f00980).
  12. Relative values with charts (eb5c4c7, 025cfd5).
  13. Fix number of record to be exported in ExporterModal (eb5c4c7, 5f36917).
  14. Add missing input string to integration gateway namespace for admin (eb5c4c7, 64d27e1).
  15. Fixed cumulative funnel chart value calculations (0fbce36).
  16. Fixed improper reporter funnel chart display due to invalid data type conversion (c7ca7d1).
  1. Strengthen reset-password flow with rate limiting and invalidation of existing tokens(d2d0245d5).
  2. Improve attachment validation on size and type for compose uploads (6f19f00b2).
  3. Sanitize back-link on logout page (XSS) (8c0a62284).
  4. Refactor delete all session of user from auth page (23a8b757ee).

Read more

Corteza 2021.9.7 released

Corteza 2021.9.7 has been released. It includes the following updates, improvements and changes.

  • Fixed set expression function to properly handle types provided by workflow execution (f42d707).
  • Fixed OIDC provider scope string issue (b1572e1).
  • Fixed workflow issues with invoker/runner (c4d80b88).
  • Fixed resource translations for content and automation page blocks (8a8cf42e).
  • Fixed inconsistent NULL order for different DB engines causing paging cursor issues (2be460ee).

Read more

Corteza 2021.9.6 released

Corteza 2021.9.6 has been released. It includes the following updates, improvements and changes.

  • Added support for RTL direction.
  • Added support for additional arguments when invoking automation scripts via API (91eb88d2).
  • Added support for resource translation on select field options (c72902a8).
  • Added support for SAML signed requests (5e4486c7, 7ec02f6e).
  • Added support for SAML HTTP binding (717cae5c0b, 5cf0597b40)
  • Added option to hide the import button on the record list (cd982a8, 9c85d0b, 874e0b2).
  • Added support for version specific DB_DSN .env variable, simplifying development (c3516dd).
  • Added find and has expression functions (86deaea9).
  • Added sort expr function (be6b572)
  • Added support for multi-value filtering on record lists (d0213cb).
  • Added processing indicator when deleting records in record list (6d47c1b)
  • Refactored workflow execution and fixed runner/invoker logic (92224360).
  • Fixed improper attachment upload permission checks due to partial request parameters (#309, #346).
  • Fixed improper QL argument transformations based on the used database (#308).
  • Fix broken docker container health check on Corredor server (dce30ba).
  • Changed federation locales (91094e44).
  • Refactored minio store and fixed invalid bucket name issue (23a2446).
  • Fixed scrolling when only one pageBlock is added (88f3e72).
  • Fixed translations on password reset (87f08d8).
  • Fixed RBAC rules and workflows not applying after being imported via namespace import (ff6cadc0).
  • Fixed improper handling of empty resource translation strings (resource-translations) (4b264798, 043588f1).
  • Fixed external OIDC for Corteza flow (398242b).
  • Fixed percentage calculation for all types of charts (2b7c949).
  • Fixed field picker system field translations (fa80ade, 485187e).
  • Fixed namespace importing — additional request validation (ca178714b), improve internal resource identification (00dd86fb9, d247ec678, and 8be8be96d).
  • Fixed improper API request content parsing when Content-Type defines character set (d0154cc1b).
  • Fixed improper error handling for the upload component (a0a1ac0).
  • Fixed role-security setting for external providers (05a40ca).
  • Fixed issue with OIDC provider removal (c078808).
  • Fixed queue name matching on workflow onMessage event (79d8a842)
  • Fixed calendar event display for events that span multiple months (4d2f824)
  • Fixed record list filter for number and id fields (3b421a1)
  • Fixed namespace selector overflowing sidebar (b9aa41e)
  • Fixed metric page block field selector options (cb69c80)
  • Fixed chart rendering edge case where the canvas did not yet exist (1b965f8).
  • Fixed centering for the empty record list label (f467e0f)
  • Fixed inline record editor not checking permissions for deletion (f74d398)
  • Fixed improper reminder handling, causing them to sometimes not show (94247f0)
  • Fixed invalid membership fetch for closed roles (88955eb)
  • Fixed column order not persisting for ColumnPicker component (9659d9f, 2b7c949, b53bc6b).
  • Make default value not required for multi fields (aae3f6f)
  • Prefill inline record editor related values (c457679)
  • Disable page deletion if it has sub-pages (67c3b2c)

Read more

Corteza 2021.9.5 released

Corteza 2021.9.5 has been released. It includes a long list of updates and improvements.

  • The record import via the import CLI command requires you to provide module field definitions along with the record import definitions. The constraint will be lifted in future patch releases.
  • Role security (forbidden, permitted, forced) on external authentication providers (91eb88d2).
  • Workflow functions for attachment management (8a8c7685).
  • OIDC support for corteza (a2091db).
  • Integration Gateway json response postfilter and http request to scope (b0590d2f).
  • JWT generate workflow function (eecf8670).
  • Unix strftime support to gval functions (d5001341).
  • Integer caster to gval functions (3473a267).
  • Added support for role permission cloning (0564fe7, d06cd41, 9bd530a).
  • Added custom processing button (6ec4157).
  • Translations for reporter webapp (6e26d5a, 931011c).
  • Added additional string manipulation functions to reporter expressions (a45c914e).
  • Added support for record import via the import CLI command (96556f54).
  • Translatable content (modules, names, pages, namespaces) is now sent with current language (5bd3bd37).
  • Improve slow performance in some casses with wf-loops by increesing workflow session state flushing from 10 to 1000 (486a5752).
  • Prevent table display elements from crashing if an empty join frame is recieved (f244b7b2).
  • Fixed improper report route bindings (d250827b).
  • Added missing type definition to the report filter perser registry (08ef5ab10).
  • Fixed panicking report filter marshaling when invalid (59ef8da1a).
  • Fixed improper handling of automation page blocks which define buttons with no references (047b647af).
  • Prevent text from exiting container in EditorToolbox (147dcd7).
  • Fixed improper date manipulation functions for reporter expressions (46372f55).
  • Fixed persistent run-as workflow issue after trigger removal (87f08d8b).
  • Fix access control checks on UI (e902382).
  • Fix user role membership picker (cadb6e1).
  • Fix module field order changing when you navigated to all records (3525ef8).
  • Fix record and user selector editors not rendering properly (09bca49).
  • Fix display element configurator options form not resetting properly (6b33655).
  • Broken translations on password reset (87f08d8)
  • Prevent error message from being transformed by toLowerCase() 32e9325)
  • Changed chart display element configurator (b553f72).

Read more

Corteza 2021.9.4 released

Corteza 2021.9.4 has been released. It includes a long list of updates and improvements.

  • Added .env options to control OAuth2 access and refresh token lifetime

  • Added support for base password constraints

  • Added translations for webapp-workflow

  • Added custom processing button

  • Added multi select to workflow options prompts

  • Added warning when workflow triggers paths change

  • Added expandable expressions editor to workflows

  • Fixed improper report filter type casting for ID-like values

  • Fixed default record module field value validation setup

  • Boolean value (record field) sanitization

  • Uint64 JSON serialization in APP_AUTOMATION payloads

  • Fixed invalid data point labeling for radial charts

  • Fixed report table pagination

  • Fixed workflow help shortcut opening when inputting

  • Admin role membership management

  • Update Bluemonday & net packages

Read more

Corteza 2021.9.3 released

Corteza 2021.9.3 has been released. It includes a long list of updates and improvements.

  • All user’s access tokens are now removed after password change (01577191).
  • Fixed improper page block ref validation for yaml encode (5afc715f).
  • Fixed unstable RBAC check that was caused by more complex setup of roles and RBAC rules (a385fe1c).
  • Fixed multi value required field errors (a5e4fb21).
  • Fixed display elements configurator sometimes not loading correct information when switching between elements (b8121e5).

Read more

Salesforce vs. Corteza
Which Is Better?

Salesforce Sales CRM and the Salesforce Lightning Platform that underpins it are powerful tools for any business. But are they truly the best tools for what businesses and organizations need – or are they simply coasting on their market share and gargantuan marketing budget? And more importantly, is the high cost of Salesforce justified?

Salesforce vs. Corteza

Today we’re going to take an in-depth look at Salesforce CRM and compare it to Corteza CRM by Planet Crust.

Planet crust is the creator and driving force behind Corteza – a 100% fully open-source, UX-driven, standards-based low-code platform that comes with pre-built CRM and Case Management solutions. Other solutions are also possible, such as Integration Hub, Smart Cities, Supply Chain Management, Patient Management, Disaster Relief Management. Basically, any data-based solution you can think of, you can build on Corteza, which is one of its strongest selling points.

By contrast, Salesforce comes with a large library of existing solutions, including Analytics, Commerce, CRM, Marketing, Healthcare, Service and more. If anything, it’s this suite of products that is one of Salesforce’s selling points, though you do have to pay separately for each solution.

But in this article, we’re going to focus on Salesforce’s and Corteza’s respective CRMs and the low-code platforms they’re built on so you can decide which platform is better for you and your organization. Read more

Four Challenges Low-Code Platforms Face

How to counter the challenges of customizability, data standardization, vendor lock-in and shadow IT.

By now, most technology leaders have come to recognize the value of low-code development in the rapid deployment of business-critical applications and the alleviation of technical debt. In fact, Gartner predicts that two-thirds of software development will be low-code by 2024. The market is also expected to grow by 23% by the end of the year.

Yet despite this rapid growth, several significant challenges remain. These difficulties continue to discourage some businesses from fully realizing the benefits of using low code development platforms (LCDP). Some of the most oft-cited challenges include a lack of customizability, the risk of vendor lock-in, and the rise of shadow IT.

While it is easy to think of these challenges as inherent limitations of the low-code approach, it is important to remember that, just like any platform, not all LCDPs are made equal. Hybrid low-code development environments and fully open-source platforms are just a couple of the alternatives to the relatively inflexible closed-source industry standards.

In this article, we will look at how these alternatives can help businesses overcome the common limitations of low-code. Read more

Crust Technology Rebrands as Planet Crust

When my partners and I at Crust Technology finally launched our Corteza platform in 2019, we already had a larger vision in mind and a product strategy to achieve that vision.

Crust

The idea for Crust first took shape in my mind when I was working as a commercial consultant to open source businesses. In that work, I experienced firsthand how the open-source industry regularly fails to create high-quality, user-friendly products with truly open standards, applications and business models. So our first objective was to create a truly open-source product with as few limitations as technologically, operationally, fiscally and legally possible that also delivered a stellar user experience along with a powerful set of features.

We also wanted to create a product that was not only a viable but in fact a better alternative, to the low-code and structured data management platforms of some of the world’s leading business software clouds, such as Microsoft, SAP and Salesforce. And so Corteza was born – a 100% open-source, 100% API-centric low-code platform.

But why open-source?

The answer to that speaks to our long-term vision. A vision based on the belief that, in order for the world to deliver the sustainable economies it requires, we need to break down the barriers that prevent people and organizations from getting the information they need to, ultimately, create greater value with less strain.

Corteza

The first of those barriers is the one to creating critical business and operational applications. Low-code platforms eliminate the need for costly software developers and put the power directly into the hands of the organizations and business functions that use them. But this is simply the first step.

The next step is breaking down the barrier to the technology itself. Proprietary platforms such as Salesforce and SAP are not affordable for many organizations. And not all platforms are fully internationalized and completely accessible. To be a truly global software platform, it needs to be free and accessible in all respects and needs to belong to the world and every organization in it.

Then there is the deployment barrier, i.e. whether the platform can be deployed either locally or internationally, on the cloud or on an organization’s own servers, and where the data is held.

Finally, there is the ownership barrier. That is, who has ownership rights to the apps an organization builds on the platform and how easy is it to migrate those apps to another platform?

It was to break down these barriers that we released Corteza as an open-source platform. And this is why we issue it with a friendly Apache v2.0 license and put governing Corteza in the hands of an independent foundation project. It’s also why we implemented standards in every corner of Corteza – from i18n internationalization and WCAG 2.1 Accessibility to BPMN 2.0 compliant Workflows and OpenAPI. So every organization in the world has access to Corteza and is never isolated. Making Corteza free forever is the best way to ensure its qualities are adopted. 

All this – delivering Corteza as a standardized global software platform – was the foundational step and was encompassed in our founding name and brand: Crust Technologies.

Breaking the Data Barrier

But now we’re embarking on the next step of our journey towards achieving our vision. Which brings us the next barrier – the data barrier.

Every data gathering tool, every data application uses its own data standard and getting those standards to talk to each other and work with each other is a technological mess. The result is that businesses and other organizations can’t consolidate data from different parts of their operations, let alone from outside sources. Business processes slow down or malfunction. Cities are slow to respond to situations ranging from live parking and traffic situations to utility needs and supplies to accidents and emergencies because they don’t have the centralized, real-time reporting apps they need. National disaster relief agencies not being able to share data with their counterpart agencies across borders due to incompatible data and security concerns.

Corteza can connect with and accept data from any third-party software platform or cloud. It then transforms it to a common, reusable format for the purposes of building applications or to process further. This makes standardized collaboration possible across any organization or even between organizations, be they business enterprises, local governments, NGOs, emergency response units or disaster relief organizations.

Beyond this, Corteza can also federate on a many-to-many basis, allowing organizations to share selected data at scale in near real-time to stay ahead of problems or to accelerate innovation. Corteza ensures that no organization’s activity is locked in a silo, but can instead extend to a global scale as desired. Businesses can operate and cooperate more efficiently. Cities can respond to situations and emergencies faster and with the right resources. Disaster relief agencies can share data and innovate solutions without bumping into security protocols.

This breaking of the data barrier and extending the potential and reach of Corteza is represented by our new name and brand – Planet Crust.

Planet Crust

But this is just the beginning. Very soon, Corteza will enable search within data federations and even between them. This will help us to find the information we need to collaborate, solve problems or grow together, whether we are research institutes, industrial affiliates, smart cities or public health authorities.

All data stored in Corteza will be Linked Data. It will have its own portal building capabilities, but will also serve as a data backend to popular, mass-adopted CMS technology such as WordPress and Drupal.

Additionally, we will address the key question of data ownership with a state-of-the-art privacy management infrastructure that will allow end-users or organizations to visualize where their data is stored anywhere in Corteza federations across the world and manage that data from a single point of entry.

These steps will serve to harmonize all the data of the organizations that use Corteza. And as more and more organizations adopt Corteza, so too will the world in general move towards global data harmony.

This will allow us as a global people to catalog and measure our finite resources and build this data into our supply chains. It will also allow us to overlay what we know about how to exploit those resources and the social implications of doing so. And it will make it possible for our leaders, whether in the public or private sector, to make ethical decisions that lead to circular, sustainable economies.

This is our vision at Planet Crust.

Planet Crust is the creator and driving force behind Corteza, a 100% open-source low-code software development platform that lets you import data from any source and use intuitive drag-and-drop tools to create custom applications for your unique business needs. Get started for free today.

Corteza 2021.9.2 released

Corteza 2021.9.2 has been released. It includes a long list of updates and improvements.

Important upgrade notes: if you wish to enable functions for workflow – action log interaction, the ACTIONLOG_ENABLE_WORKFLOW_FUNCTIONS .env variable must be set.

  • Added a user interface to configure SMTP setting; such configuration does not require server restart (0b69d1a2, 20a85d8).
  • Added support for workflow – action log interaction (search, create) (1014f53a).
  • Added support for server plugins (614d2b30).
  • Added workflow import note (9d98170).
  • Compose module fields no longer accept reserved system names — recordID, ownedBy, createdBy, createdAt, updatedBy, updatedAt, deletedBy, and deletedAt (20757e58, 20a85d8).
  • Resource translations no longer fallback to base language in case of a missing translations (4cd54a58).
  • Compose webapp now sends Content-Language and `Accept-Language HTTP headers (f8427346).
  • Server source is now built with -trimpath and without -mod=readonly flags (0b02535c).
  • Namespace export no longer preserves logo/icon references (dab413ece).
  • Initial documentation site redesign (14550adf).
  • Fixed boot-level workflow initialization logic which crashed the server if an enabled workflow defined an invalid trigger configuration (415982c8).
  • Fixed workflow saving when the configuration sidebar was opened (6d8796e).
  • Fixed improper Low Code Checkbox labels representation for false values (0330e31, aef1a14).
  • Fixed accent & HTML escaping in translated strings (556ffc5e).
  • Fixed resource translation issues for current language, accents, and escaped HTML (05178c2b).
  • Hide pages if the parent page is marked as not visible (957a9de2).
  • Fixed broken permission setting from Low Code admin panel on module for fields & records (8ae2a48d).
  • Fixed RenderOptions expr value assignment via selectors (445f0ed5).
  • Fixed RBAC rule migration crash on duplicate rules (e8bc6141).
  • Docker container healthcheck (9d7cf23c).
  • Fixed compose false value label (6da6989).
  • Fixed sidebar shadow (4a02d90).
  • Fixed reporter table column reordering (6b25473).
  • Fixed Low Code error when the automation scripts are not loaded (bb94645).
  • Disabled the load button in chart editor (6912fcd).
  • Fixed improper prefilter handling in the chart editor (aeceb35).

Read more