LIFECYCLE EVENT and DRAFTS not connecting

[Nadine Wighton]

We have a lifecycle event that facilitates a promotion process. This requires different personas to complete tasks in various phases (per normal lifecycle event/journey behaviour).

We have enabled the ability to create a draft on a record producer (Report) that is linked to the Lifecycle Event.  Observation is that the draft is created successfully, but once submitted, it becomes an independent case, and it doesn't mark the originating task in the Lifecycle Event as complete.  The task remains in a ready state.  There seems to be a disconnect between drafts and Lifecycle Event tasks.  Trying to understand if this is undesirable out-of-the-box behaviour, or if we need to write business rules to connect the two.

Additionally, the draft list ends up with the same description line for all drafts. Therefore, if you have lots of applicants to write reports for, you cannot easily identify which draft relates to which applicant.  Both problems make it a poor user experience.

Has anyone had a similar experience with Lifecycle Events and drafting record producers or have any ideas on how to resolve this?

[Wessel van Enk]

Hi Nadine,

If I understand correctly, you are submitting a record producer as part of a task in an Lifecycle Event?
Out of the box the behavior is then correct that from the record producer it creates a new case/record, besides the lifecycle event, as that's the standard behavior of the record producer. 

You can relate both records via a script or business rule once the new record has been created via the child case option. So if you add your lifecycle event case as the parent of the new created case, you should have the relation.