Hi,

As per your business requirement, i would recommend the below rule pattern design;

On submit clicked()

{

// excute these two rules parallely -- concurrent---

              Check duplicate entry at DataBase();

              Check duplicate entry in SharePoint library();

}                             - end of the above executuion blok, you must have stored the output result of both the rules on hidden fields, lets say DBcheckFlag and SPCheckFlag.

IF Advanced condition (DBCheckFlag is not empty AND SPCheckFlag is not empty)

{

        Show MessageBox(duplicate entry exist);

}

ELSE

{

       Call Custom SmartObject to create a entry into GP and generates Invoice Number();

}

With this approach you can reduce number of advanced conditions and multiple ELSE execution blocks!

Hope it helps !

Cheers,

Prajwal Shambhu

Thank you for your suggestion. Since these rules are defined in the smartform rules using K2 designer. I dnot know how to handle rules pattern design in K2 designer tool. Can you please give me some idea ?

IPO, 

When I start working with something of this complexity, I create unbound rules. I never trust 'else' and I don't like nesting rules. 

Create unbound rules for your nested rules.

Call the unbound rule from your main rule. 

That will make the logic a bit easier to follow, and when you need to change the location of 1 rule, it won't get caugt in a "Am I nested in an Else statement?" or the Else statement needs at least one rule. 

Hi,

I standy by Chadg reply, i dont use ELSE specially when there is complex rule implementation. As Chadg suggested we can make use of unbound rules and call them inside any rules.

Cheers,

Prajwal Shambhu