10 Replies Latest reply: Sep 2, 2012 3:17 PM by Aditya Sharma RSS

Esclation on the form

Manish Verma

Hi All,

 

We have created an Esclation to run on a form and make changes in the searched entry.

But we are not able to search more then 5000 entries using the esclation as we have done a setting "Max-Entries-Per-Query: 5000" in the ar.cfg file to restrict the user from pulling large reports.

 

please suggest can we make the esclation to override this setting.

 

Thanks,

Manish

  • 1. Re: Esclation on the form
    LJ LongWing

    Nope, you need to make the setting as large as you need it to be

  • 2. Re: Esclation on the form
    Laurent Matheo

    That could be a good RFE though.

    Though I guess it's possible to cheat in a server group environments. On the "admin" ARS Server it could be unlimited and since escalations run on the admin server the problem wouldn't rise.

    The ARS "clients" would have a limit though of course.

  • 3. Re: Esclation on the form
    Manish Verma

    Thanks all for the reply.

     

    we are not using the server group, so we would look into the option to increase the setting.

     

    Thanks

    Manish

  • 4. Re: Esclation on the form
    Misi Mladoniczky

    Hi,

     

    Escalations should not be limited by that setting.

     

    But if an escalation performs a Push-Fields to a form, this Push-Fields should be subject to this.

     

    So what are you doing here? Are you really doing this:


    Escalation:

      Run If: matches 5000+ records

      Action:

        Set-Fields: CURRENT TRANSACTION

           FieldA = "New value"

     

    Or do you do this:

    Escalation:

      Run If: matches 5000+ records

      Run If: match 1 record

        Push-Fields: to form which matches 5000+ records

          FieldA = "New value"

     

    The last example will not work, but the first one should work fine.

     

            Best Regards - Misi, RRR AB, http://rrr.se

  • 5. Re: Esclation on the form
    Manish Verma

    Thanks Misi for explaining the esclation processing.

     

    we are using the esclation according to the second example, to update the form with 5000+ records.

    Please suggest if we delete the entries from the second form using a workflow, then will the esclation able to process more then 5000 records.

     

    Thanks

    Manish

  • 6. Re: Esclation on the form
    Misi Mladoniczky

    Hi,

     

    You should change your design to use the first example.

     

    Escalation:

      Run If: matches 5000+ records

      Action:

        Set-Fields: CURRENT TRANSACTION

           FieldA = "New value"

     

    This is how you do it without hitting the limit.

     

    The other problem is that if you use the second option everything will be treated as a single database transaction, which can cause performance issues and other problems.

     

            Best Regards - Misi, RRR AB, http://rrr.se

  • 7. Re: Esclation on the form
    LJ LongWing

    Misi,

    Why would an escalation not be limited by the search record max?  I remember in the past that if you set the value to say, 1000, that you wouldn't be able to pull up all active links in the system....why would an escalation be able to perform a search on a form > maxCount and process all of them?

  • 8. Re: Esclation on the form
    Misi Mladoniczky

    Hi,

     

    I think you are wrong.

     

    The max-entries does not apply to either ACTL-listings or Escalations. It never has.

     

            Best Regards - Misi, RRR AB, http://rrr.se

  • 9. Re: Esclation on the form
    LJ LongWing

    Misi,

    You are correct...I was wrong....I know for a fact, at some point back with the Admin Tool (Before Dev Studio), there were people complaining in the ARSList about inability to pull up all AL's because of this limit...apparently a bug that was fixed at some point in the past

  • 10. Re: Esclation on the form
    Aditya Sharma

    Yes Escalations query is independent of Max-Entries-Per-Query parameter. Operation will be performed for all the records irrespective of parameter value.

     

    Regards,

    Aditya