Entity as a input to Subflow in post automation - Australia release

[Sunil25]

Hello all,

We are on Australia release and I wanted to create control record from Smart Assessment Engine post automation once the assessment is submitted by Assessor. I have created a flow to trigger smart assessment when an entity is created or updated.

Also, I have created subflow to create control and it requires inputs such as Entity and Control Objective. I will be passing Control Objective as hard coded, but entity should be passed from Smart Assessment as on which trigger has raised against the entity. So I am trying to pass the entity from the smart assessment template, but it is not available.

Can you guide me how to pass smart assessment template input inside the subflow which triggers during post automation.

Summary what I am trying below:

1) Created Smart assessment with questions and answers

2) Created flow to trigger the assessment when the entity is created/updated

3) Created subflow to create control

4) Selected the subflow from step (3) in Automation

Challenge: I want to pass the Entity so that Control will be created on that entity.

Please let me know if anyone have tried this approach. 

Thanks, Sunil Safare

[Sunil25]

One more question!

Is there a way how many control records are created through smart assessment automation. I mean any m2m table in the system where we can know control and smart assessment are related.

[Matthias Ferstl]

As you ususally us assessments to assess controls instead of creating them, there is no OOB m2m table fot that.
But you can build your own and create the entries in your subflow.

[surajsengar]

@Sunil25 - Instead of trying to pass the Entity directly from the Post Automation configuration, pass an available assessment context object (such as the Assessment Instance or Assessment Result, depending on what is exposed to your subflow) and then retrieve the associated Entity within the subflow logic.

Typical flow:

1. Entity created/updated
2. Flow launches Smart Assessment
3. Assessment completed
4. Post-assessment automation calls Subflow
5. Subflow receives assessment context
6. Subflow queries the assessment record to determine the source Entity
7. Create Control against that Entity

Verify Available Data Pills

In your subflow definition:

• Add an input for the assessment context record (if available).
• Check the data pills exposed by Post Assessment Actions.
• Often the triggering entity is stored as a reference on the assessment instance/subject record and can be retrieved in a Flow Designer action or Script step.

Important Check

Make sure the subflow is properly linked to the Template Category, otherwise only limited inputs/actions may be exposed in the automation configuration. ServiceNow specifically requires subflows to be linked to the template category before they can be used in Post-Assessment Actions. [github.com], [servicenow.com]

If Entity Is Not Available at All

A workaround is to:

• Pass the Assessment Instance ID into the subflow.
• Use a "Look Up Record" step or Script step.
• Read the entity reference from the assessment instance table.
• Use that Entity sys_id when creating the Control record.