Forced to sign of JDE each time a DBA is revised in order for the change to take effect

Hello,

When developing DBAs, I thoroughly test them one by one as I create them, by using the Interim check functionality.

Now, on different client machines as well as on different E1 versions (9.0, 9.1, 9.2) in the past three or four years, I always encountered this annoying situation described hereafter:

Let say that you create a DBA;

a) you attach the DBA to an employee, the Group/Union, or maybe you have set it up as a DBA that calculates for ALL employees, that does not matter;

b) you run an interim check for the selected employee in order to check DBA results;