We have recently made some changes to the Submitted By gadget due to issues being reported in Kuali Build and feedback submitted by customers.
Some of these issues and feedback include the following. There were some instances where data contained in the gadget did not populate despite the document's metadata holding the correct value. Additionally, customers reported being confused when seeing submittedBy versus meta.submittedBy in notification variable lists and in other areas in the system.
Our hope is that these changes will reduce confusion and streamline the way metadata is used in Kuali Build applications.
We have changed the Submitted By gadget to use the value contained in the metadata. This change prevents issues with the gadget not being populated when data exists. A side effect of this change is that the gadget itself no longer has a data value, which impacts the following scenarios:
- Conditional Visibility using the Submitted By gadget data will no longer have data to read. Customers will need to update any Conditional Visibility rules to use meta.submittedBy when referencing the submitter moving forward.
- Notifications using the Submitted By gadget data will no longer have data to read. Customers should update variables used in notifications to read off the meta.SubmittedBy data rather than the Submitted By gadget.
- PDFs generated shortly after the fix will have blank Submitted By fields. Moving forward PDFs will generate correctly. Any PDFs that have blank Submitted By fields should be regenerated.
- Anywhere where "Submitter" or "Creator" were listed to refer to the submitter will now read "Submitter - Display Name" in some areas of the system.
We have pushed out fixes for these problems, and with those fixes we have also migrated impacted data to ensure that the correct value shows up throughout customer forms. Please let us know if you have any questions regarding these changes.