AnsweredAssumed Answered

Inactivating vs Locking Resources in Admin

Question asked by Robert Ensinger on Jan 12, 2015
Latest reply on Dec 14, 2015 by Robert Ensinger

Hi all.

   Other than what the bookshelf has to offer (locking a resource disables the user's ability to log in), are there any other functional differentiations/benefits to locking a resource vs inactivation? (example: user with scheduled reports - would be nice if 'lock' cleared all of the resource's scheduled reports and jobs)


   We have resource administration 'clean up' jobs that inactive resources as required, but I'm wondering if I shouldn't lock them as well. If there was some additional functionality to the lock this would add value to locking.


   Operationally, how do others use locking vs inactivation?