Is it possible to use draft only on a child entity and not on root entity using RAP?

[Andreas_M]

Dear community,

is it possible to use draft only on a child entity and not on root entity using RAP. I didn't find anything about that and what would be best practice to implement such a scenario? At the moment I have a structure, like Root->Child1->Child2 and I only want draft on Child2. My idea is to split it into Root->Child1 and make Child2 an own root Entity on which I will activate draft. Therefore I connect the second root entity with child1 on my own. Would that be best practice in that case?

Thanks for your help and opinions.

Best regards
Andreas

[Andre_Fischer · Accepted solution]

It is planned to offer a feature called "collaborative draft". This will allow several users to work on one draft at the same time. You will even be able to see who is currently editing the document.

When you solution solved your requirement for the time being I don't see a problem.

[Andreas_M · Accepted solution]

Thanks for the information. Looking forward to that feature!

[Andre_Fischer]

Draft is only active for the complete business object, not for single entities.

What you can do is to create two projections for the same underlying RAP BO.

One would use the statement "use draft;" the other would not use that.

Not sure whether this would help you and maybe you can explain the business scenario in more detail which requires such a setup.

[Andreas_M]

Hey Andre,

thanks for your help and sorry for the late response. If I understand it correctly this won't work for our use case.

Our business scenario looks like the following. We have a simple workflow (Root Entity) which can contain several steps (Child Entity). Each of these steps can contain one or more articles (child entity of steps) which will be maintained by several users. As you already mentioned draft will be activated on the complete business object. The problem with that approach is, that the user can't work on their articles in parallel as the whole object got locked for draft. So each user should be working on their article in one step at the same time. Is it possible that RAP will support such use cases in the future? I talked with some colleagues of mine and one of them had a similarly problem for another business scenario. In my case I solved it that way, that articles is an root entity on which I activate draft and do the connection to the steps table on my own. There is some extra work I have to do in UI but I think that approach is ok so far. Do you consider it as best practice or what would your approach be? I'm using managed scenario if this is relevant.

Thanks for help.

Best regards

Andreas