Lifecycle Question - Adding Additional Info to Existing Lifecycle Case

[maxstnr]

Hello, we are designing / drafting a Corrective Action process as a lifecycle event. The lifecycle will follow each step of the corrective action process from our first step of verbal warning up to termination. One of our requirements is to allow the opened for user to generate each step of the process. For example, if the employee already had a verbal warning, the opened for user could then generate the next step, a written warning. For this, what is the best practice for the opened for user to provide additional information? Meaning, when they go to generate the next step of the process (we currently have that set up as a task), they should be able to provide their reasoning as to why they're generating the written warning, which we're hoping can then be mapped to the existing lifecycle case.

[Sandeep Rajput]

@maxstnr In your lifecycle event you can have following setup of the activity set.

1. Activity set: Raise verbal warning

Activity type: HR Task

Assigned to: Opened for

Trigger Immediately

2. Activity set: Raise written warning

Activity type: HR Task

Assigned to: Opened for

Trigger: After Raise verbal warning activity set

Both of these HR tasks will be record producer based tasks which will allow the Opened for to share their inputs after the submission of the record producer the entered data will be mapped to the parent case.

Hope this helps.

[Msteiner94]

Thanks, Sandeep. For those record producer based tasks, what is the best method to map the data back to the parent case? Via the record producer script?

[Sandeep Rajput · Accepted solution]

@Msteiner94 The data can be mapped via the record producer script on the parent HR Case.

[maxstnr]

Thank you! I ended up using a slightly different method w/ a flow but this otherwise answered my question