The Improved Field Organiser

Modified on Mon, 9 Sep at 3:00 PM

We have recently improved the Field Organiser to present options more concisely, allow better fine-tuning of when to ignore problems, display warnings, or fail execution, and remove certain limitations that previously caused the block to cancel workflow execution when the set of fields was modified upstream.


This new feature is available from build 2024.3 onwards. Field Organisers in existing workflows are automatically updated to the new version. These blocks will function exactly as they did before, so no manual action is required. New workflows using the improved Field Organiser will also work seamlessly in older versions of Omniscope that only support the previous Field Organiser.



Upon entering the Field Organiser, users are shown a list of fields, just as in the previous version:



Any changes made to the set of fields upstream are instantly reflected in the list of fields displayed in the Field Organiser. A key difference from the old version is that the order of the fields is no longer fixed. Any upstream change to the order of fields will be reflected in the Field Organiser, unless a custom order is applied.





Block Failure Fine-Tuning


One notable change is the removal of the checkboxes at the bottom of the dialog, and the addition of a "Freeze" button at the top. When reconfiguring a field, dropdown menus appear at the bottom, enabling fine-tuning of how the block handles situations where it should ignore issues, show warnings, or fail execution.




On Missing Customised Field:

This dropdown allows you to fine-tune what happens when a field configured in the Field Organiser is later removed from the upstream workflow.


For example, consider an Issue Date field that was changed from Date to Text. If a block upstream alters the set of fields so that Issue Date is no longer included, the field would be missing, and the reconfiguration of the field could no longer be applied.



On Missing Deleted Field:

Similar to the above example, if a field is deleted and later removed upstream, you can now define how the Field Organiser should respond.

We opted to create two separate dropdowns because the severity of a missing configured field typically differs from that of a deleted field.




Freeze


A new "Freeze" button is available at the top of the dialog. Pressing this button freezes the current set of fields, ensuring they remain in this exact order in the block’s output. Two new options at the bottom control what happens if the set of fields changes upstream: one is a dropdown for handling missing listed fields, and the other is a checkbox for additional fields.




On Missing Listed Field:

This dropdown controls how the block behaves if any of the listed fields are removed upstream.


Include Other Input Fields:

When checked, any additional field not listed in the Field Organiser will be included in its output.





Apply custom field order


When you change the order of fields in the Field Organiser, a "Reset order" button appears.



Reordering fields creates a custom order. Once a custom order is set, any upstream changes to the order of fields will not affect the Field Organiser’s output. The order of all fields is locked when one field is moved. To remove the custom order, simply click "Reset order", and the block will once again display the fields in the order they arrive from upstream.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article