2) Add Single-Selection/Multi-Selection field to table with some custom values defined in field property editor; 3) Add Single- Relational field to same table and map it to same table (as it set by default); 4) Add Sub-Relational field to same table and map it to previously configured Single-Relational field in same table and set Single-Selection/Multi-Selection field as Sub-Field;
Steps to reproduce 1) In SBM Composer, create a Single Selection field called "Field A". Add "x", "y" and "z" values 2) Create a Single Relational field called "Field B" and make it point to the current primary table
Form actions and rules used in form actions are not evaluating the "(None)" value in relational, multi-relational, and sub-relational fields as empty when checking "Is Field Empty".
1. Have two Process apps (A and B), A is referenced to B and has a Single-Relational and Sub-Relational field. 2. Have a form (Submit form ) on A process app with RestGrid that uses Sub-Relational field as a parameter 1. Try to submit an A item.
If you disable a multi- relational field on a transition form using a form action , transitioning the item will clear all selected values in the multi- relational field .
The submit transition is a called "Child Submit". " Set original item in new item's field" is set to a relational field that will hold the parent. All fields are mapped.
Sub-relational field value does not display value when updating from a relational field value that initially had no value in the sub-relational field ... Select a relational value where one of its sub-relational fields has a null or empty string value . ... Open the form again (via update) and select a different relational value . The sub-relational field that was empty before is now empty regardless of what you select for the Relational field
