Hi @pooja.arora like Andrei mentions you can achieve this in flows.

There are different ways to approach this objective. What is right for your org will depend on your data model within Salesforce for relating accounts. In this example we are using the ParentId relationship on the account record object.

When the entry criteria for this flow is met (a check box “screen child account” is set to true on the parent record), we look up the related child records using the “Get Records” action, and then use a “Loop” action to cycle through the results calling the Automate Screening Apex action for each one before ending the process. This example is going to create the screening events for the parent and the child accounts at the same time.

The flow could look something like this:

Hello @pooja.arora

Thank you for reaching out to us. I am contacting the World-Check/Screening team to look into your question.

I will give you more updates as soon as I receive any information from the team.

Hi @pooja.arora,

To perform multiple screenings at the same time, this endpoint - "SEQ-case-save-and-screen-cases: Save and screen multiple cases" can be used. However, all of the cases would be treated as separate cases and there would be no concept of parent and associated cases between them. If this relationship needs to be maintained, another endpoint - "[SEQ-linked-cases-create-links]: Create links between cases" can be used. I have also attached a link to our documentation for your reference - Refinitiv World-Check One API. Please revert to me in case of any questions. Thank you.

Regards,

Ssneha Balasubramanian.

Hey Ssneha, Just to clarify I am not using code to run this automation. Earlier I was using process builder and now flow since Salesforce is retiring process builder and workfkow rules. So I need to understand the solution that I can implement in a flow. I am not sure if this documentation can help me with that. It'll be much quicker if we can have a call scheduled. thanks.

Hi @pooja.arora,

Please send me an invite between 9 a.m. - 6 p.m. IST and I'd be happy to discuss this. Thank you.

Regards,

Ssneha Balasubramanian.

Hi Ssneha, I don't have your email. My email is pooja.arora@bp.com

Either send me your email or send me an invite for 6pm IST. That would be 8:30 am my time.

Thanks,

Pooja

Hi @pooja.arora,
you can accomplish your goal in the flow. In the flow you need to get all Accounts (using Get Record block) that need to be screened and using iterator (Loop block) for example call the same apex class - "Automate Screening" and input three parameters as you did for one record. It's one of the option that should work for you.

Continued....

GET RECORDS

You are going to want to limit the records that you are fetching, e.g. where parent ID = the record ID of the account initiating the flow. Remember there are API limits that no more than 1000 records can go through the API in one go via real time trigger. If you have a very large hierarchy you would need to consider the impact of this limit in your flow.

LOOP:

You then loop the records in the collection

@pooja.arora please do add any clarifications that you need but I hope this answered your question more fully.

Hi @pooja.arora try referencing { Loop_throught_each_Affinity_Account.Id} I am not quite clear what your Assignment actions are trying to do.

This is a screenshot from my org why I reference my loopname.id.

@Hannah.Quinn Thanks Hannah.

Thanks Hannah,

I did try to add the collection variable/list that I created after looping through all the affinity accounts but the input variable in the apex action clearly says: recordId. Looks like it’s expecting only one id and not the collection. Can you please verify why it isn't taking a collection variable? Does it have anytihng to do with the apex class itself?

@Hannah.Quinn @Karolina.Wisniewska

Can you please respond. This has been open for way too long. I am not sure what's the hold-up. But I would like to escalate this ticket.

Hi @pooja.arora,

Inside the flow, we work with all related child accounts. But since in our case the method (Invocable method) inside the apex class only supports passing one account at a time (RecordId), we have to pass accounts one at a time in a loop.

Second option we can write the logic in apex trigger that will looks like below that will pass collection:

trigger AccountTrigger on Account (after insert) {

if(trigger.isInsert){

List<tr_wc1.tr_automateScreening.automateScreeningVars> sCaseVars = new

List<tr_wc1.tr_automateScreening.automateScreeningVars>();

for (Account acc : Trigger.new){

tr_wc1.tr_automateScreening.automateScreeningVars item = new

tr_wc1.tr_automateScreening.automateScreeningVars();

item.enableMonitoring = false;

item.objectType = 'Account';

item.recordId = acc.Id;

sCaseVars.add(item);

}

tr_wc1.tr_BulkCreateAndScreenCases batch = new

tr_wc1.tr_BulkCreateAndScreenCases(sCaseVars);

Database.executeBatch(batch, 30);

}

}