Skip to content
← GLM & SLM Idea Lab

How can we improve GLM and SLM? Search or submit ideas below.

GLM & SLM Idea Lab: Batch

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Batch Assign Evaluations - Remove the Limit!

I have commented on this elsewhere, but this is something I really feel is worth looking at.

When assigning evaluations for several hundred requests in a process, it would be most helpful to not limit it to 25 requests at a time. When assigning hundreds of requests I have to do these assignments in stages, so to go in and individually select 25 requests, scroll to the bottom, assign the evaluation and do this 15 or so times is exhausting.

Please remove the limit, or make the limit at least 100!

I am not clear on why there is a limit, and would hope that removing such a limit would not have negative consequences on other foundations.

If you have another work around, I am all ears!

4 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Dana Jeffery shared this idea  ·   ·  Report…  ·  Admin →
Comments are closed An error occurred while saving the comment
  • Vonda Carr commented  ·   ·  Report

    This is a great suggestion. I ran into this problem this morning when assigning my Evaluator 2 group.

  • Dana Jeffery commented  ·   ·  Report

    Thanks Chris, it is helpful to understand the current limitations. If this can be planned within the next year, we would be very happy.

    Thanks for taking the time to explain.

  • Chris Dahl commented  ·   ·  Report

    Hi Dana,

    The limit exists because - as you kind of anticipated - removing it (or increasing it) could have negative impacts performance-wise on other users. I'm not sure how many evaluators you have, but some clients have over 10 evaluators for a given process / stage. So letting them assign 100 evaluations would mean that the system would have to deal with 1,000+ submissions in a very short amount of time. This would consume quite a few system resources, and I couldn't guarantee that this request would be completed in less time than it would take for your browser to say you "timed out".

    But ... as we continue looking at more resource-intensive functionality, we'll be looking at a variety of ways to deal with more processing in a way that doesn't impact other users. I can't put a time frame on it, but I'd anticipate some improvements in the next 9-15 months. I know that seems like a long way out, but there are a number of things we need to do to lay the foundation for those types of changes (not to mention that there are a lot of other things that are being requested). Bottom line is that we'll be doing our best to work toward a more performant solution.

    Thanks for taking time to add this suggestion,
    -chris