Fields going blank when using new "Save as Draft" feature
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2024 07:55 PM - edited ‎11-06-2024 08:25 PM
We recently updated our instance and we now have the new "Save as Draft" feature on our catalog forms. However, when using this feature, we've noticed that one of our fields always goes blank when we open a saved draft. The field is in a variable set, however, we have two variable sets on the form, and the fields on the other variable set are fine when saved as draft. The first variable set is at the start of the form, whereas the variable set with the blank field is at the end, in case that makes any difference.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-19-2025 12:21 PM
I am also having a very similar issue. However, it is only happening on fields that are conditionally made visible and mandatory on the Record Producer based upon input in another field using a Catalog UI Policy / Policy Action. The fields that are conditionally displayed and made mandatory are the ones that do not retain the value when doing Save as Draft. On the Catalog UI Policy, the Catalog UI Policy Action had a Value Action set to Clear Value. Setting the Value Action to Leave alone seemed to do the trick. I hope this helps!