Ordering of Demographics
Some agencies need some Flow Value Collectors to be more strictly ordered in the output to external systems. Corti has introduced the Custom Property of key order to allow for more configurable options for how the metadata presents when output.
What to configure
Open Protocol Editor.
Find the Demographics component. You must edit the block prototypes for these three fields, not the instances on a canvas.
For each prototype, add a CustomProperty with
key orderand an integer value:Age prototype: order = 1
Age units prototype: order = 2
Sex prototype: order = 3
Save and publish your protocol.
What this changes
Smart comment output will sort blocks by the order value, lowest first, then join display values with " - ".
Blocks without order come after the ordered ones, in their original sequence.
If two blocks share the same order, their original sequence is kept.
Only integer values are treated as valid.
Notes for Flow Value Collector
If your Flow Value Collector pulls its values from the same block instances, it will reflect the same order automatically after you publish.
If you still see the old order in a specific collector view, check that those views are not hard-coded or filtered to a different block set.
Hide Organizational Settings
We have added a new organization feature flag called - organization-settings and it will be automatically enabled for all current organizations(customers). And we are adding new user permission, which is called Organization Settings (app:organization_settings) and it will be automatically added to all current user roles.
So,
if we want to hide Organization Settings only for few users, we need to remove Organization Settings (app:organization_settings) permission from their user roles
if we want to hide Organization Settings for all organization, we need to go to /admin-panel and remove organization-settings feature flag
Hide Support Option for Users
We have added a new organization feature flag called - support-ticket and it will be automatically enabled for all current organizations(customers). And we are adding new user permission, which is called Support Ticket (app:support_ticket) and it will be automatically added to all current user roles.
So,
if we want to hide Support only for few users, we need to remove Support (app:support_ticket) permission from their user roles
if we want to hide Support for all organization, we need to go to /admin-panel and remove support-ticket feature flag