User Admin - Option for 24 hour access - BATCH Processing Impacted

[doran.george]

*** Added 30 day impact because of lack of a 24 hour work window for BATCH UserIDs.                           


The CHORUS BPM 'User' Screen allows an 'In By' and 'Out By' time window.  The values can be set to '00:00:00' and '23:59:59' respectively; but is NOT 24 hour window.

There are two holes, the second before midnight and the second after midnight.  The two seconds may not seem like much, but, if you are engaged in BATCH processing using REST Calls at midnight, incoming work will fail to be created or updated.  This is causing out-of-synch issues.  This impacts ALL versions of Chorus and AWD.   Customer Support informed me that In By and Out By are working as designed.  We now have REST services that stay true to time ranges and cannot process for 24 hours.    We need a 24 hour option for BATCH Users.
This is impacting clients every day, data updates are lost.  Please help.
There are two errors in LOG Files:
User cannot logon this early
User cannot logon this late

[Karen_Hunter]

Digital Workers and Systems Jobs should have different guard rails than the "logon between these two times".  This requirement is covered in our upcoming Admin modernization project which fundamentally addresses the similarities and differences between human and digital workers..

[Karen_Hunter]

We are evaluating options to support current user base before admin modernization.