Insights & Information Design

The repeat loop is principally a quick function which only becomes noticeably slower after a few thousand processes. The current arcplan realization at allocation (as mandatory with the numerator [OBJx] := [OBJx] +1), however, results in the increase of the running time upon allocation of values  in relation to the aggregate amount of the objects of the opened documents. (This is a problem of the fundamental programming of arcplan Enterprise when identifying the object in the object stack which contains all objects of all open documents). In case of complex applications, the running time of the repeat loop is therefore much higher so that it may be running for seconds, rather than milliseconds, even in case of only few entries. Therefore, if possible, all functionalities should be implemented without repeat loop in order to ensure a good performance.

Subsequently, we provide an example which is frequently realized with the repeat loop even though there is an implementation option with other formulas.

The new functions READMETADATA() and PLACEMETADATA() offer a range of quite new possibilities to the arcplan designer. As shown in the arcCorporation Demo, data queries can be dynamically set up and modified via drag & drop.

The set-up of such a query is described below.

A background report to connect to databases enables the user to login to all required systems with one single loginin the background; there is no need for the user to explicitly login to each connection upon its first access. The requirement is, of course, that the user exists in all systems with the same access data.
In addition, logins to systems which are not personalized but operate with a technical user can be performed.

If there is no such background report, a login dialog popup appearswhen a report with database reference is opened. This function enables the user to login to the respective database.If several databases are used, several dialogs will open up. One for each database.