Fields under table field group are not getting created for Document Extraction CapabilityDescriptionUsers are unable to view or proceed with field group creation when no description is provided. The system blocks the action unexpectedly, even though descriptions are not expected to be mandatory for field groups.Steps to Reproduce Navigate to Now Assist Admin -> features.Click on Platform ->Document Intelligence.Select Document Extraction.Create a use case UC1.Under the use case (UC1) create 2 individual fields.Fields are displaying under UC1.Create a table field group under the same use case and create some fields under that field group.Expected Behaviour:Fields created under the table field group should be displayed within the use case.Actual Behaviour:Fields inside the table field group are not displayed.WorkaroundTo prevent installation or workflow issues, the mandatory description check for field groups has been temporarily disabled. The following code lines in the business rule responsible for field/field group creation and updating have been commented out: For Field/Field Group Creation: //Description is a mandatory key // Temporarily commented out the description field check to prevent workflow errors. /* if (isGenAITask && capability == "doc_data_extractor" && (!current.getValue('description') || current.getValue('description').trim().length === 0)) { gs.warn("Required field(s) is/are missing. Aborting updation"); gs.addErrorMessage(gs.getMessage("Details are missing.")); current.setAbortAction(true); return; } */ For Field/Field Group Updating: //Description is a mandatory key // Temporarily commented out the description field check to prevent workflow errors. /* if (isGenAITask && capability == "doc_data_extractor" && (!current.getValue('description') || current.getValue('description').trim().length === 0)) { gs.warn("Required field(s) is/are missing. Aborting updation"); gs.addErrorMessage(gs.getMessage("Details are missing.")); current.setAbortAction(true); return; } */ Next Steps A permanent fix is under review to refine the business rule logic and ensure that the description is required only where applicable (i.e., fields but not field groups). Once finalised, the code will be updated accordingly.Related Problem: PRB1846148