RFC-29: App Access Rule - Revised followup to New Data Access APIs

[AndreasEbert]

RFC-25 was (rightfully) closed, so I’d like to ask here on RFC-29 for feedback on my follow-up question regarding locked custom fields, (@AngelinaIgnatova, @JustinThirkell. Here my question on RFC-25:

RFC-25: [Superseded by RFC-29] App Access Rule - followup to New App Data Access APIs

@AngelinaIgnatova, thanks for the insight into locked custom fields. Indeed, internally we thought about this as a possible solution for App Access rules in regards to custom fields. Then at least it’s relatively clear to end-users, that a custom field “belongs” to an app, and indeally which app. So far, so good. But: I don’t see how we as an app can: create locked custom fields update an existing custom field as locked by our app I did found this docu where it says: When you install a Ji…

Thanks.