My Business Architect wants to sort out the inconsistencies in how the Business Analysts have been capturing a process objects description, short description and remark/example attributes. So we've created a new Process Steps(L5) attribute to this end and now current attribute values/contents need to be set for the new "way of doing things". Current process object descriptions become the new process steps(L5), with current short descriptions and remark/examples becoming the new descriptions.
The above script logic is simple enough or so I thought as I need to update 17300 process objects and I'm hitting a magical 225 limit in the number of items I can update. I've tried various ways to get around this, running the process objects in batches of 100, closing the database and re-opening it again every 100 objects, clearing the database cache every 100 objects, removing all actual object references and only keeping attribute content and item GUIDS in the oProcessObjects array to only call the current process object to be updated via its GUID and then reset the object reference once its attributes have been updated. Again and again and again I just can't get past this magical 225 number, below is the code block I'm running. Maybe I'm missing something else, maybe I'm not seeing something or maybe I might just be wrong about all of this? Please enlighten me oh ARIS Community...
Klemens Hauk on
Hi,
there is no hard limit of 225 objects in ARIS Report scripting. Clear cache after 100 updates is not necessary. What really happens? Does the script terminate with an exception, become unresponsive, return false from setValue(), or simply stop updating attributes? Does it stop always exactly at the same GUID (maybe you then have an object issue)? You can log some data in the loop (GUID, result of both setValue etc.) to see what really happens.
Regards
Klemens