All topics
RAP_CDS_ODATAintermediate

Draft Handling

Learn RAP draft handling for Fiori-style transactional editing where users need intermediate state before activation. Cover draft ownership, edit/activate/discard behavior, side effects, validations, concurrent editing and when draft is unnecessary for stateless APIs.

Overview

Learn RAP draft handling for Fiori-style transactional editing where users need intermediate state before activation. Cover draft ownership, edit/activate/discard behavior, side effects, validations, concurrent editing and when draft is unnecessary for stateless APIs.

Lessons in this topic

Interview questions covered

  • When would you enable draft for a RAP BO, and when not?
  • After adding a field to a draft-enabled BO, activation fails and Fiori shows errors. What is the likely cause?
  • What is draft in RAP, why is it needed, and how are draft and active instances distinguished?
  • Walk through the draft lifecycle actions: Edit, Resume, Prepare, Activate and Discard.
  • Users report 'Save does nothing' in a draft app. How do you investigate?
  • How do the exclusive lock and the total ETag work together in draft scenarios?
  • An hourly integration sets statuses via API, but long-running drafts later reset them. Why, and how do you prevent it?
  • How does draft change where you put determinations and validations?
  • A user says a purchase request has been 'locked' for two days. Support wants to delete the draft table rows. What do you do?
  • You inherit a draft-enabled RAP BO. What do you review?

Related topics

Interview questions on this topic