Details about this thread
  • State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 322 subscribers
  • Views 178 views
  • Users 0 members are here

BPM Not Triggering "Accès mkp" Field After Lead Conversion

Phuong Trinh

Hi everyone, Blush

I need help resolving an issue with a Business Process Management (BPM) automation that checks the "Accès marketplace" field in the Contacts module based on the "OFFRES" field value in the Accounts module.

Current Behavior:
Working Scenario (Non-Converted Leads): 

My BPM correctly checks "Accès marketplace" in Contacts when :

- The associated Account has "OFFRES" = ACHAT or ACHAT SUR MESURE.
- This works when the Account already exists in Sugar or Account is created before the creating of a new contact.

BPM Configuration Details:
Target Module: Contacts

Trigger: On record creation of "Contact"

Condition: Checks Accounts. OFFRES for values ACHAT or ACHAT SUR MESURE.

Action: Updates the "Accès marketplace" checkbox.


Broken Scenario (During Lead Conversion): 

When a Lead is converted:

- The Contact record is created first.
- The Account record is created afterward.
The BPM fails to check "Accès marketplace" because: At the time of Contact creation, the Account does not yet exist, so the BPM cannot evaluate the "OFFRES" field.


Could you please help me to modify the BPM logic to handle the Lead conversion scenario? Specifically:

Ensure the BPM evaluates the "OFFRES" field after the Account is linked during conversion.

Suggest whether a delayed execution (e.g., via hook/job queue) or a secondary BPM on the Accounts module would be more reliable.

Thank you for your guidance! Pray

Parents
  • 0

    Hi  ,

    If the value should consistently be calculated based on the related account, then  's recommendation is best. If you are looking to only designate an initial value and need the ability to edit the field later on, then your approach with SugarBPM is more suitable. For the use case you are trying to achieve, I recommend inserting a gateway immediately after your start event to see if there is a related account by evaluating whether the account name is empty or not. If the account name is empty, then the gateway should proceed to an event-based gateway that waits for the first of 2 events to happen:

    1. An account is related to the contact
    2. An amount of time elapses where no contact remains unrelated to an account

    If the account is related to the contact, it cycles back through the initial gateway and proceeds to the remainder of your process. Here is what the process definition looks like with that strategy:

    I hope this helps!

    Chris

    Co-Founder | SugarCRM's 2024 Global Outfitters Partner of the Year

Reply
  • 0

    Hi  ,

    If the value should consistently be calculated based on the related account, then  's recommendation is best. If you are looking to only designate an initial value and need the ability to edit the field later on, then your approach with SugarBPM is more suitable. For the use case you are trying to achieve, I recommend inserting a gateway immediately after your start event to see if there is a related account by evaluating whether the account name is empty or not. If the account name is empty, then the gateway should proceed to an event-based gateway that waits for the first of 2 events to happen:

    1. An account is related to the contact
    2. An amount of time elapses where no contact remains unrelated to an account

    If the account is related to the contact, it cycles back through the initial gateway and proceeds to the remainder of your process. Here is what the process definition looks like with that strategy:

    I hope this helps!

    Chris

    Co-Founder | SugarCRM's 2024 Global Outfitters Partner of the Year

Children
No Data