Under Review
over 7 years ago

Turning off the "locks will be released" message upon closing a CSR

I would like to propose that we can choose whether or not to display the message regarding locks being released when a PeopleSoft CSR is moved to the closed status. I don't know if this is applicable to non-PeopleSoft CSRs or not, but I assume not.

 

As a Stat user since 2004, and having migrated to production and closed out close to 2,000 CSRs, I have seen this message way too often. For me, it provides no value and has not for years, since I am aware that closing a CSR will result in locks being released on the objects being maintained by that CSR. This pop-up message dialog, therefore, is nothing but an inconvenience to me, requiring me to dismiss it each time I move a CSR to a closed status in the workflow. It seems to me that any user of Stat for any length of time should be well aware that closing a CSR will release the associated locks.

 

Perhaps it is of value to other customers - I don't know. If so, then I would like to see an option added to selectively disable that message per service domain or globally. If it is not of value to other customers, perhpas it should be removed entirely.

 

Thank you for your consideration.

mheider@bgsu.edu
  • over 2 years ago

    Is there any chance this will ever get fixed? I originally posted this suggestion in 2016, so it has been nearly 5 years.  And, since the message was removed from the web client, it has been determined that it is not needed, yet it remains in the Windows client which no doubt nearly all of those who perform PeopleSoft migrations use.

    If there is some desire to keep this message as an option, simply add a “Display_Object_Release_Message” field on a convenient table, add the ability to change that flag via System Maintenance - Parameters, and then add one line of code to the client that states “if Display_Object_Release_Message = “y” then display object release dialog box. No need to even add an else to that statement.

    I realize this may not be a top priority, but someone went in years ago and fixed it in the web version but left the Windows client untouched.  It seems that sometime in the last 5 years this could have been squeezed into the schedule of code changes.

    And, for some reason this system will only let me post once every 15 minutes on this. I don't think this site is likely to be spammed since even actual Quest Stat customers rarely even use it so that seems a bit restrictive.

  • over 2 years ago

    I just came back to check on this, and see that there is a comment that this is resolved in the web client.

     

    Tutuapp 9Apps ShowBox

     

     

  • over 4 years ago in reply to mheider@bgsu.edu

    Apparently you can't hit enter while replying to get a new line or it submits what you have entered.  To continue: It seems that this method of suggesting changes is ineffective and simply allows ideas to languish. It is obvious that customers only come here when directed to do so to submit a request for a change, and rarely (if ever) come to see what ideas have been proposed and vote on them.  It seems the only votes that are done are when someone is here entering a request and then takes a moment to look at what else is out there, and then does not come back until the next request they want to suggest. I would prefer a more active approach where the idea is submitted as a service request, and some team from Quest would evaluate that request and provide a "we will do this" or "we will not do this" answer.  Granted, this would perhaps prevent feedback from other customers, but realistically they are not providing much of that anyway.  Plus, several new "features" have been implemented in Stat that were not well thought out changes in my estimation, and yet we have them in the current version, so it's not like we are really having much say anyway.

  • over 4 years ago in reply to mheider@bgsu.edu

    Does anyone from Quest ever check on ideas submitted via this community board?  This request is simple, has no negative comments, and has been unimplemented for many years now.   

  • over 4 years ago

    I just came back to check on this, and see that there is a comment that this is resolved in the web client.  I have never used the web client to close a CSR, since for PeopleSoft CSRs generally there is a migration that is needed that requires the use of the Windows client.  I guess I did not know that the message was also produced from the web client, but that is not the solution to this issue since it still happens in the latest 6.2 Hot fix E release of Stat when using the Windows client.  Please remove the message from the Windows version of Stat also.