Lesson 17 Practice — Draft-Enable the Support Issue Application

Your Support Issue application already has:

managed persistence
RAP behavior
validations
messages
actions
feature control
authorization
projection
OData V4 UI service

Now add:

persistent draft editing

Target architecture:

Fiori Elements
      ↓
OData V4
      ↓
ZC_ISSUE_###
      ↓
Draft-enabled ZR_ISSUE_###
   ┌───────────────┐
   ↓               ↓
ZISSUE_###      ZDISSUE_###
Active           Draft

---

Practice information

Time	About 3 hours
Prerequisite	Lesson 17 teacher-led work
Base BO	ZR_ISSUE_###
Active table	ZISSUE_###
Draft table	ZDISSUE_###
Projection	ZC_ISSUE_###
Service	Existing Lesson 16 OData V4 UI service

---

1. Verify prerequisites

Confirm these activate:

ZISSUE_###
ZR_ISSUE_###
base DCL
base BDEF
ZBP_R_ISSUE_###
ZC_ISSUE_###
projection DCL
projection BDEF
ZUI_ISSUE_###
OData V4 UI binding

Repair Lesson 16 defects first.

---

2. Keep draft separate from Issue Status

Issue business status remains:

O = Open
I = In Progress
C = Closed

Do not add:

D = Draft

RAP Draft is not a business status.

---

3. Harden ResponsibleUser

Change:

ResponsibleUser

from:

read-only on update

to:

fully read-only

The BO will assign ownership automatically.

---

4. Add owner determination

Create:

setResponsibleUser

Requirements:

on modify
trigger = create
current technical user
only fill when ResponsibleUser is initial
provider-side local-mode EML

Do not let the external UI type the technical owner.

---

5. Verify existing initial Status determination

You should already have:

setInitialStatus

Rule:

new Issue
→ Status = O

Both determinations should now run during new-draft creation:

Status = O
ResponsibleUser = current user

---

6. Add with draft

Open the base Issue BDEF.

Add:

with draft;

in the BDEF header.

---

7. Declare draft table

Use:

ZDISSUE_###

as the draft-table name.

Add it to the root entity's behavior definition after the active persistence table.

---

8. Generate draft table

Place the cursor on:

ZDISSUE_###

Use:

Ctrl+1

Generate the draft table.

Do not manually build its technical draft administration.

Activate it.

---

9. Choose total ETag field

Use the field equivalent to:

LastChangedAt

that is semantically the active instance's last-change timestamp.

Add it as:

total etag

after the lock-master declaration.

Keep:

LocalLastChangedAt

as the existing ETag master.

---

10. Explain both ETags

Complete:

Local ETag field:
____________________

Purpose:
____________________

Total ETag field:
____________________

Purpose:
____________________

---

11. Add draft actions

Declare:

Edit
Activate optimized
Discard
Resume
Prepare

Use actual RAP draft-action syntax.

---

12. Connect validations to Prepare

Your Issue BO already has:

validateTitle
validateReportedOn
validateCost

Assign all three to:

draft determine action Prepare

Do not create duplicate draft-specific validation methods.

---

13. Prepare target

Your source should contain a block equivalent to:

draft determine action Prepare
{
  validation validateTitle;
  validation validateReportedOn;
  validation validateCost;
}

---

14. Preserve business actions

Keep:

startProcessing
close

They remain business actions.

Do not confuse them with:

Edit
Activate
Discard
Resume
Prepare

---

15. Adapt global authorization

Your Lesson 15 global authorization must now recognize update-style draft requests.

Treat:

%update
%action-Edit

according to the same training global update permission.

Fill only requested components in the global result structure. Keep the existing %create and %delete handling.

Prepare is a draft determine action. It has no independently generated authorization component, so do not check or populate authorization fields for it.

Do not use feature-control constants.

---

16. Adapt instance authorization

Your owner-based instance authorization must consider:

%update
%action-Edit

as requiring the same ownership check.

Rule remains:

ResponsibleUser = current user
→ authorized

Return auth-unauthorized when the owner does not match. Keep the existing Lesson 15 %delete classroom cleanup policy.

get_instance_authorizations returns a result table. For each instance read through local-mode EML, append a row with its full %tky, then fill the requested components on that row. Do not assign components directly on the table as if it were the global result structure.

---

17. Explain Activate authorization

Why does the practice not invent:

a new independent "Activate privilege"

?

Your answer must refer to:

underlying create/update
active persistence

---

18. Draft-enable the projection BDEF

Open:

ZC_ISSUE_###

projection behavior.

Add:

use draft;

after:

projection
strict ( 2 )

---

19. Reuse all draft actions

Add:

use action Edit
use action Activate
use action Discard
use action Resume
use action Prepare

Keep:

use action startProcessing
use action close

---

20. Projection behavior target

Equivalent shape:

projection;
strict ( 2 );
use draft;

define behavior for ZC_Issue_### alias Issue
use etag
{
  use create;
  use update;
  use delete;

  use action Edit;
  use action Activate;
  use action Discard;
  use action Resume;
  use action Prepare;

  use action startProcessing;
  use action close;
}

---

21. Service artifacts

Do not create a second:

Service Definition
Service Binding

Reuse the Lesson 16 OData V4 UI service.

Activate changed artifacts.

Refresh/reopen the Fiori Elements preview.

---

Test A — New Draft

22. Create a new Issue in Fiori preview

Choose:

Create

Enter values equivalent to:

IssueNo        = 99110001
Title          = Draft issue test
Description    = New draft lifecycle
RequesterEmail = draft.issue@example.com
Priority       = H
ReportedOn     = today
EstimatedCost  = 250.00
CurrencyCode   = EUR

Do not enter:

Status
ResponsibleUser
Uuid
admin fields

---

23. Do not Save yet

Remain in draft editing.

Expected derived values:

Status = O
ResponsibleUser = current user

---

24. Inspect active table

Open:

ZISSUE_###

Use Table Data Preview.

Expected for:

99110001

no active row yet

---

25. Inspect draft table

Open:

ZDISSUE_###

Expected:

draft row for 99110001 exists

Inspect but do not modify the technical draft columns.

---

26. Save

Return to the UI.

Choose:

Save

Expected lifecycle:

Prepare
→ validations
→ Activate
→ active CREATE
→ draft removed

---

27. Verify activation

Expected:

ZISSUE_###
→ 99110001 exists

ZDISSUE_###
→ corresponding draft removed

---

Test B — Edit and Discard

28. Edit active Issue

Open:

99110001

Choose:

Edit

Change:

Description

to:

This change will be discarded

Do not Save.

---

29. Compare active and draft

Active table:

old Description

Draft table:

new unsaved Description

Record both values.

---

30. Discard

Choose:

Cancel / Discard

Expected:

draft removed
active Description unchanged

---

Test C — Validation Blocks Activation

31. Edit again

Set:

ReportedOn = tomorrow

This violates your Lesson 13 validation.

---

32. Save invalid draft

Choose:

Save

Expected:

Prepare invokes validateReportedOn
error message returned
Activate does not complete
draft remains
active row unchanged

---

33. Correct the draft

Set:

ReportedOn = today

Save again.

Expected:

activation succeeds
draft removed
active row updated

---

Test D — Business Actions Remain Separate

34. Check current business Status

After activation:

Status = O

Business action:

startProcessing

is conceptually separate from:

Edit / Activate

---

35. Execute business action

Use the service UI to execute:

startProcessing

Expected:

O → I

Verify the active business Status changed.

---

36. Explain the distinction

Complete:

Activate means:
____________________

startProcessing means:
____________________

The answers must not be the same.

---

Draft Reasoning

37. New draft vs edit draft

Complete:

Question	New Draft	Edit Draft
Active row already exists?
How is it started?
What does Activate do?
What does Discard do?

---

38. Active vs draft table

Explain:

Why can a draft row contain values
that the active table does not yet contain?

Use:

work in progress
activation

in your answer.

---

39. Why invalid draft data can exist

A user may temporarily type:

invalid ReportedOn

while editing.

Why is that acceptable in the draft table but not in the active table?

---

40. Why Prepare exists

Explain why:

on-save validation
+
draft Prepare

are connected.

What would be the risk if the relevant validations were never assigned to Prepare?

---

41. Why total ETag matters

Explain this scenario:

draft created from active version A
active data changes to version B
user later tries to resume/save old draft

What must RAP detect?

---

42. Why Resume exists

Explain:

durable draft
vs
short-lived exclusive database lock

Do not wait for a real timeout.

---

Repair Exercises

43. Repair — no draft table

Remove or break the draft-table declaration temporarily.

Use syntax check.

Restore it and explain why Draft needs separate persistence.

---

44. Repair — no total ETag

Temporarily remove:

total etag

Run syntax check.

Restore it.

Explain why local ETag alone is not the complete draft concurrency model.

---

45. Repair — missing Prepare validation

Temporarily omit:

validateReportedOn

from Prepare.

Explain why this weakens pre-activation checking.

Restore it.

---

46. Repair — no use draft

Imagine the base BO is draft-enabled but the projection BDEF is not.

Explain why the OData UI projection would not expose the intended draft lifecycle.

Restore:

use draft

---

47. Repair — missing use action Edit

Remove it temporarily in strict projection behavior.

Run syntax check.

Restore it.

---

48. Repair — owner not derived

Imagine ResponsibleUser remains blank on a new draft.

Explain potential problems with:

DCL
instance authorization
UI continuity

Restore the owner determination.

---

49. Repair — draft authorization not updated

Imagine Lesson 15 authorization handles:

%update

but ignores:

%action-Edit

Explain why Edit can be denied unexpectedly, then adapt both authorization handlers to apply the update-style policy to Edit.

Explain why adding authorization fields for Prepare would cause a syntax error: it is a draft determine action, and those components do not exist in the generated authorization structures.

Check that the instance handler appends result rows keyed by %tky and fills only requested components on each row.

---

50. Repair — direct SQL draft manipulation

Do not execute this:

DELETE FROM ZDISSUE_###

Explain why draft persistence must be owned by the RAP runtime.

---

Certification-Style Mini Task

51. Draft repair challenge

Without looking at the guided Reservation BDEF, repair a deliberately incomplete draft setup with:

with draft present
draft table missing
total ETag missing
Prepare empty
projection lacks use draft

Required outcome:

draft table generated
total ETag correct
validations assigned to Prepare
projection draft enabled
draft actions explicitly reused
UI Create/Edit/Save works

---

52. State audit

Complete from actual runtime tests:

Stage	Active row?	Draft row?	Business Status
New draft before Save
New draft after Save
Edit draft before Discard
After Discard
Invalid edit after failed Save
Corrected edit after Save

---

53. Draft-action audit

Draft action	Purpose
Edit
Activate
Discard
Resume
Prepare

---

54. Submission checklist

• ResponsibleUser fully read-only.
• Owner determination exists.
• Owner defaults to current technical user.
• with draft added.
• ZDISSUE_### declared.
• Draft table generated with Quick Fix.
• Draft table active.
• Correct total ETag configured.
• Existing local ETag retained.
• Edit declared.
• Activate optimized declared.
• Discard declared.
• Resume declared.
• Prepare declared.
• validateTitle assigned to Prepare.
• validateReportedOn assigned to Prepare.
• validateCost assigned to Prepare.
• Global auth handles Edit alongside create/update/delete.
• Instance auth checks ownership for update/Edit and retains delete handling.
• Instance auth appends one result row per %tky.
• Prepare is not referenced as an authorization component.
• Projection uses draft.
• Projection reuses all draft actions.
• Existing OData V4 UI service reused.
• New draft exists only in draft table before Save.
• Save creates active row and removes draft.
• Edit draft leaves active row unchanged.
• Discard removes draft only.
• Invalid Save is blocked.
• Invalid draft remains for correction.
• Corrected draft activates.
• Business action still works separately from draft actions.

---

55. End-of-practice explanation

Explain without notes:

A RAP draft is persisted work in progress.

The active table stores active business data.

The draft table stores intermediate editing state.

Edit creates an edit draft.

Create in the draft UI creates a new draft.

Prepare runs the validations needed before activation.

Activate transfers valid draft state to active persistence.

Discard removes draft work without deleting the active object.

Resume continues a durable draft after lock expiry.

Total ETag protects the relationship between
a longer-lived draft and its active version.

Draft state is not business Status.

If you can prove each statement through your Issue service and tables, you are ready for Lesson 18 compositions.