Re: Google Chrome and Advanced Search error

[LJ LongWing]

Tauf,
I think the issue he's dealing with is not a blocking, but a
truncating.more than likely he will find that if he uses something like
Fiddler to look at the backchannel calls that are being made, his Chrome is
not allowing the full URL to be played out to the Mid-Tier server whereas
the other browsers are, and that's what's causing the issue at hand.

On Fri, Feb 9, 2018 at 3:51 PM, Tauf Chowdhury  wrote:

> It actually sounds like the Chrome build you are using is blocking an HTTP
> request causing the 404 error. You can try disabling some security features
> to see if that works.
>
> Sent from my iPhone
>
> On Feb 9, 2018, at 5:20 PM, Joel D Sender  wrote:
>
> I usually see that message when a slow server appears to have timed-out,
> or after a long period of inactivity (on my part).
>
> You can wait for the server to respond, or hit refresh.
>
> HTH,
>
> *Joel*
>
> Joel Sender  *   jdsen...@earthlink.net
>
>
>
> *From:* ARSList [mailto:arslist-boun...@arslist.org
> ] *On Behalf Of *Fawver, Dustin
> *Sent:* Friday, February 9, 2018 1:30 PM
> *To:* arslist@ARSLIST.ORG
> *Subject:* Google Chrome and Advanced Search error
>
>
>
> Greetings!
>
>
>
> I’m sending this out to see if anyone else has encountered this.  Part of
> what I have to do involves long strings in the Advanced Search field.
> Normally this is not a problem.  Recently I’ve encountered this error in
> Google Chrome when trying to run a search with a string that’s a little
> over 1k characters long.
>
>
>
> 
>
>
>
> Firefox and MS Edge have no issues with processing the string.  Before
> this error occurs, there’s an empty pop-up window that hangs there for
> about 5 seconds.  Right now I have a single AR and Mid-Tier server, so the
> load balancing things that I saw when searching wouldn’t apply.  Nothing’s
> changed on the server aside from Windows updates.  Fortunately this really
> isn’t affecting anyone else but me and of course there’s an easy workaround.
>
>
>
> Thanks!
>
> Dustin Fawver
>
> Sr. Help Desk Technician
>
> Information Technology Services
>
>
>
> P: 423-439-4648 <(423)%20439-4648>
>
> itsh...@etsu.edu
>
>  
>
>
>
>
> 
>  Virus-free.
> www.avast.com
> 
> <#m_-6331059606662127474_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> --
> ARSList mailing list
> ARSList@arslist.org
> https://mailman.rrr.se/cgi/listinfo/arslist
>
>
> --
> ARSList mailing list
> ARSList@arslist.org
> https://mailman.rrr.se/cgi/listinfo/arslist
>
>
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

Re: Google Chrome and Advanced Search error

[Tauf Chowdhury]

It actually sounds like the Chrome build you are using is blocking an HTTP 
request causing the 404 error. You can try disabling some security features to 
see if that works. 

Sent from my iPhone

> On Feb 9, 2018, at 5:20 PM, Joel D Sender  wrote:
> 
> I usually see that message when a slow server appears to have timed-out, or 
> after a long period of inactivity (on my part).
> You can wait for the server to respond, or hit refresh.
> HTH,
> Joel
> Joel Sender  *   jdsen...@earthlink.net 
>  
> From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Fawver, Dustin
> Sent: Friday, February 9, 2018 1:30 PM
> To: arslist@ARSLIST.ORG
> Subject: Google Chrome and Advanced Search error
>  
> Greetings!
>  
> I’m sending this out to see if anyone else has encountered this.  Part of 
> what I have to do involves long strings in the Advanced Search field.  
> Normally this is not a problem.  Recently I’ve encountered this error in 
> Google Chrome when trying to run a search with a string that’s a little over 
> 1k characters long.
>  
> 
>  
> Firefox and MS Edge have no issues with processing the string.  Before this 
> error occurs, there’s an empty pop-up window that hangs there for about 5 
> seconds.  Right now I have a single AR and Mid-Tier server, so the load 
> balancing things that I saw when searching wouldn’t apply.  Nothing’s changed 
> on the server aside from Windows updates.  Fortunately this really isn’t 
> affecting anyone else but me and of course there’s an easy workaround.
>  
> Thanks!
> Dustin Fawver
> Sr. Help Desk Technician
> Information Technology Services
>  
> P: 423-439-4648
> itsh...@etsu.edu
> 
>  
> 
>   Virus-free. www.avast.com
> -- 
> ARSList mailing list
> ARSList@arslist.org
> https://mailman.rrr.se/cgi/listinfo/arslist
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

RE: Google Chrome and Advanced Search error

[Joel D Sender]

I usually see that message when a slow server appears to have timed-out, or
after a long period of inactivity (on my part).

You can wait for the server to respond, or hit refresh.

HTH,

Joel

Joel Sender  * jdsen...@earthlink.net  

 

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Fawver,
Dustin
Sent: Friday, February 9, 2018 1:30 PM
To: arslist@ARSLIST.ORG
Subject: Google Chrome and Advanced Search error

 

Greetings!

 

I'm sending this out to see if anyone else has encountered this.  Part of
what I have to do involves long strings in the Advanced Search field.
Normally this is not a problem.  Recently I've encountered this error in
Google Chrome when trying to run a search with a string that's a little over
1k characters long.

 



 

Firefox and MS Edge have no issues with processing the string.  Before this
error occurs, there's an empty pop-up window that hangs there for about 5
seconds.  Right now I have a single AR and Mid-Tier server, so the load
balancing things that I saw when searching wouldn't apply.  Nothing's
changed on the server aside from Windows updates.  Fortunately this really
isn't affecting anyone else but me and of course there's an easy workaround.

 

Thanks!

Dustin Fawver

Sr. Help Desk Technician

Information Technology Services

 

P: 423-439-4648

itsh...@etsu.edu

  itslogo

 



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

Google Chrome and Advanced Search error

[Fawver, Dustin]

Greetings!

I'm sending this out to see if anyone else has encountered this.  Part of what 
I have to do involves long strings in the Advanced Search field.  Normally this 
is not a problem.  Recently I've encountered this error in Google Chrome when 
trying to run a search with a string that's a little over 1k characters long.

[cid:image001.png@01D3A1C2.E7E1F930]

Firefox and MS Edge have no issues with processing the string.  Before this 
error occurs, there's an empty pop-up window that hangs there for about 5 
seconds.  Right now I have a single AR and Mid-Tier server, so the load 
balancing things that I saw when searching wouldn't apply.  Nothing's changed 
on the server aside from Windows updates.  Fortunately this really isn't 
affecting anyone else but me and of course there's an easy workaround.

Thanks!
Dustin Fawver
Sr. Help Desk Technician
Information Technology Services

P: 423-439-4648
itsh...@etsu.edu
[itslogo]

-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

RE: [EXTERNAL] Re: Reporting on Incidents that have re-opened

[Arner, Todd]

Thanks Dustin, I appreciate the input.  We did think about that same thing.  It 
will work moving forward but doesn’t help with past Incidents.  Right now we 
are trying to get a percentage of incidents that were re-opened for the past 
year.

Todd

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Fawver, Dustin
Sent: Friday, February 09, 2018 11:04 AM
To: ARSList
Subject: RE: [EXTERNAL] Re: Reporting on Incidents that have re-opened

I was also thinking of a filter that could do it on Modify, depending on how 
you want to be notified.  Maybe an email or a message.  Have the Run If clause 
of:

(‘DB.Status’ = “Resolved”) AND (‘TR.Status’ < “Resolved”)

I’m just using regular ARS 9.1.2, if that plays any part in how things are set 
up.

I hope this helps.

Dustin Fawver
Sr. Help Desk Technician
Information Technology Services

P: 423-439-4648
itsh...@etsu.edu
[itslogo]

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of LJ LongWing
Sent: Friday, February 09, 2018 11:47 AM
To: ARSList >
Subject: [EXTERNAL] Re: Reporting on Incidents that have re-opened


*** This email does NOT originate from an ETSU person or service. ***
Todd,
How about something a bit more novel.  Look for records that have a Resolved 
Status history Date/User who's status is < Resolved

On Fri, Feb 9, 2018 at 8:55 AM, Arner, Todd 
> wrote:
Hi Crystal,
Thanks for the help.   We are still seeing at least one  Incident that has  
been re-opened that does not have a date in the re-opened date field.  Have you 
ran into any issues like that?  The re-open date field definitely looks more 
useful the Kick_Back Count field.

Thanks,
Todd

From: ARSList 
[mailto:arslist-boun...@arslist.org] On 
Behalf Of CRENSHAW, CRYSTAL
Sent: Friday, February 09, 2018 8:48 AM
To: arslist@ARSLIST.ORG
Subject: RE: Reporting on Incidents that have re-opened

Todd,

There is a hidden field on HPD:Help Desk called ‘Re-Opened Date’.  If that 
field has a vaule, then it has been reopened at least once.


This is a query for active Incidents that have been previously resolved:

'Re-Opened Date' != $NULL$ AND 'Status*' < "Resolved"

Hope that helps.


Thanks,

Crystal Crenshaw
Service Management Senior Systems Analyst
Project Services – Service Management
(919)508-0546

[cid:image002.gif@01D3A1AF.F60185C0]

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Arner, Todd
Sent: Friday, February 09, 2018 9:14 AM
To: arslist@ARSLIST.ORG
Subject: Reporting on Incidents that have re-opened

Wondering if anyone can help us figure out how to query for Incidents that have 
been re-opened.  We thought we could do this by using the Kick_Back Count field 
but it seems to reset the count after the Incident is closed and we also get 
strange results were incidents we would expect to match the query do not.  
Anyway, wondering if anyone has a better way to find incidents that have been 
re-opened.  We are using version 9.1.3.  Basically we want to run a query 
against all incidents that will list any that have been resolved and then moved 
back to an active status.  I appreciate any tips you can provide. ☺

Todd Arner
Systems Administrator III
Great Lakes Educational Loan Services, Inc.


The information contained in this communication may be confidential, is 
intended only for the use of the recipient(s) named above, and may be protected 
under state or federal law. If the reader of this message is not the intended 
recipient, you are hereby notified that any dissemination, distribution, or 
copying of this communication, or any of its contents, is strictly prohibited. 
If you have received this communication in error, please forward the 
communication to no...@glhec.org immediately and 
destroy or delete the original message and any copy of it from your computer 
system. If you have any questions concerning this message, please contact the 
sender.
This email may contain confidential and privileged material for the sole use of 
the intended recipient. If you are not the intended recipient, please contact 
the sender and delete all copies. Any review or distribution by others is 
strictly prohibited. Personal emails are restricted by policy of the State 
Employees' Credit Union (SECU). Therefore SECU specifically disclaims any 
responsibility or liability for any personal information or opinions of the 
author expressed in this email.

--
ARSList mailing list
ARSList@arslist.org

Re: Reporting on Incidents that have re-opened

[LJ LongWing]

that's the only problem with status history, you only get the 'last' time
something happened, so if it was reopened, then re-closed, you loose that
data...so you wouldn't be able to use thatso, workflow is the best way
to do that, as was suggested before db.status = resolved and status <
resolved, set a flag, increment a value, etcI thought something similar
to that already existed, but it might not in the version you are using.

On Fri, Feb 9, 2018 at 12:06 PM, Arner, Todd  wrote:

> Hi LJ,
>
> Thanks for your response but I am not following what you mean.  Could you
> provide more detail?
>
>
>
> Thanks,
>
> Todd
>
>
>
> *From:* ARSList [mailto:arslist-boun...@arslist.org] *On Behalf Of *LJ
> LongWing
> *Sent:* Friday, February 09, 2018 10:47 AM
> *To:* ARSList
> *Subject:* Re: Reporting on Incidents that have re-opened
>
>
>
> Todd,
>
> How about something a bit more novel.  Look for records that have a
> Resolved Status history Date/User who's status is < Resolved
>
>
>
> On Fri, Feb 9, 2018 at 8:55 AM, Arner, Todd  wrote:
>
> Hi Crystal,
>
> Thanks for the help.   We are still seeing at least one  Incident that has
>  been re-opened that does not have a date in the re-opened date field.
> Have you ran into any issues like that?  The re-open date field definitely
> looks more useful the Kick_Back Count field.
>
>
>
> Thanks,
>
> Todd
>
>
>
> *From:* ARSList [mailto:arslist-boun...@arslist.org] *On Behalf Of *CRENSHAW,
> CRYSTAL
> *Sent:* Friday, February 09, 2018 8:48 AM
> *To:* arslist@ARSLIST.ORG
> *Subject:* RE: Reporting on Incidents that have re-opened
>
>
>
> Todd,
>
>
>
> There is a hidden field on HPD:Help Desk called ‘Re-Opened Date’.  If that
> field has a vaule, then it has been reopened at least once.
>
>
>
>
>
> This is a query for active Incidents that have been previously resolved:
>
>
>
> 'Re-Opened Date' != $NULL$ AND 'Status*' < "Resolved"
>
>
>
> Hope that helps.
>
>
>
>
>
> Thanks,
>
>
>
> Crystal Crenshaw
>
> Service Management Senior Systems Analyst
>
> Project Services – Service Management
>
> (919)508-0546 <(919)%20508-0546>
>
>
>
>
>
> *From:* ARSList [mailto:arslist-boun...@arslist.org
> ] *On Behalf Of *Arner, Todd
> *Sent:* Friday, February 09, 2018 9:14 AM
> *To:* arslist@ARSLIST.ORG
> *Subject:* Reporting on Incidents that have re-opened
>
>
>
> Wondering if anyone can help us figure out how to query for Incidents that
> have been re-opened.  We thought we could do this by using the Kick_Back
> Count field but it seems to reset the count after the Incident is closed
> and we also get strange results were incidents we would expect to match the
> query do not.  Anyway, wondering if anyone has a better way to find
> incidents that have been re-opened.  We are using version 9.1.3.  Basically
> we want to run a query against all incidents that will list any that have
> been resolved and then moved back to an active status.  I appreciate any
> tips you can provide. J
>
>
>
> Todd Arner
>
> Systems Administrator III
>
> Great Lakes Educational Loan Services, Inc.
>
>
> --
>
> The information contained in this communication may be confidential, is
> intended only for the use of the recipient(s) named above, and may be
> protected under state or federal law. If the reader of this message is not
> the intended recipient, you are hereby notified that any dissemination,
> distribution, or copying of this communication, or any of its contents, is
> strictly prohibited. If you have received this communication in error,
> please forward the communication to no...@glhec.org immediately and
> destroy or delete the original message and any copy of it from your
> computer system. If you have any questions concerning this message, please
> contact the sender.
>
> This email may contain confidential and privileged material for the sole
> use of the intended recipient. If you are not the intended recipient,
> please contact the sender and delete all copies. Any review or distribution
> by others is strictly prohibited. Personal emails are restricted by policy
> of the State Employees' Credit Union (SECU). Therefore SECU specifically
> disclaims any responsibility or liability for any personal information or
> opinions of the author expressed in this email.
>
>
> --
> ARSList mailing list
> ARSList@arslist.org
> https://mailman.rrr.se/cgi/listinfo/arslist
> 
>
>
>
> --
> ARSList mailing list
> ARSList@arslist.org
> https://mailman.rrr.se/cgi/listinfo/arslist
>
>
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

RE: Reporting on Incidents that have re-opened

[Arner, Todd]

LJ,
I think I understand what you are getting at but that will only solve the query 
for those incidents that are still open.  How can we find out if a Closed 
incident was re-opened during its life?

Thanks,
Todd

From: Arner, Todd
Sent: Friday, February 09, 2018 1:06 PM
To: 'ARSList'
Subject: RE: Reporting on Incidents that have re-opened

Hi LJ,
Thanks for your response but I am not following what you mean.  Could you 
provide more detail?

Thanks,
Todd

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of LJ LongWing
Sent: Friday, February 09, 2018 10:47 AM
To: ARSList
Subject: Re: Reporting on Incidents that have re-opened

Todd,
How about something a bit more novel.  Look for records that have a Resolved 
Status history Date/User who's status is < Resolved

On Fri, Feb 9, 2018 at 8:55 AM, Arner, Todd 
> wrote:
Hi Crystal,
Thanks for the help.   We are still seeing at least one  Incident that has  
been re-opened that does not have a date in the re-opened date field.  Have you 
ran into any issues like that?  The re-open date field definitely looks more 
useful the Kick_Back Count field.

Thanks,
Todd

From: ARSList 
[mailto:arslist-boun...@arslist.org] On 
Behalf Of CRENSHAW, CRYSTAL
Sent: Friday, February 09, 2018 8:48 AM
To: arslist@ARSLIST.ORG
Subject: RE: Reporting on Incidents that have re-opened

Todd,

There is a hidden field on HPD:Help Desk called ‘Re-Opened Date’.  If that 
field has a vaule, then it has been reopened at least once.


This is a query for active Incidents that have been previously resolved:

'Re-Opened Date' != $NULL$ AND 'Status*' < "Resolved"

Hope that helps.


Thanks,

Crystal Crenshaw
Service Management Senior Systems Analyst
Project Services – Service Management
(919)508-0546

[cid:image001.gif@01D3A1A7.F1F67E70]

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Arner, Todd
Sent: Friday, February 09, 2018 9:14 AM
To: arslist@ARSLIST.ORG
Subject: Reporting on Incidents that have re-opened

Wondering if anyone can help us figure out how to query for Incidents that have 
been re-opened.  We thought we could do this by using the Kick_Back Count field 
but it seems to reset the count after the Incident is closed and we also get 
strange results were incidents we would expect to match the query do not.  
Anyway, wondering if anyone has a better way to find incidents that have been 
re-opened.  We are using version 9.1.3.  Basically we want to run a query 
against all incidents that will list any that have been resolved and then moved 
back to an active status.  I appreciate any tips you can provide. ☺

Todd Arner
Systems Administrator III
Great Lakes Educational Loan Services, Inc.


The information contained in this communication may be confidential, is 
intended only for the use of the recipient(s) named above, and may be protected 
under state or federal law. If the reader of this message is not the intended 
recipient, you are hereby notified that any dissemination, distribution, or 
copying of this communication, or any of its contents, is strictly prohibited. 
If you have received this communication in error, please forward the 
communication to no...@glhec.org immediately and 
destroy or delete the original message and any copy of it from your computer 
system. If you have any questions concerning this message, please contact the 
sender.
This email may contain confidential and privileged material for the sole use of 
the intended recipient. If you are not the intended recipient, please contact 
the sender and delete all copies. Any review or distribution by others is 
strictly prohibited. Personal emails are restricted by policy of the State 
Employees' Credit Union (SECU). Therefore SECU specifically disclaims any 
responsibility or liability for any personal information or opinions of the 
author expressed in this email.

--
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

RE: Reporting on Incidents that have re-opened

[Arner, Todd]

Hi LJ,
Thanks for your response but I am not following what you mean.  Could you 
provide more detail?

Thanks,
Todd

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of LJ LongWing
Sent: Friday, February 09, 2018 10:47 AM
To: ARSList
Subject: Re: Reporting on Incidents that have re-opened

Todd,
How about something a bit more novel.  Look for records that have a Resolved 
Status history Date/User who's status is < Resolved

On Fri, Feb 9, 2018 at 8:55 AM, Arner, Todd 
> wrote:
Hi Crystal,
Thanks for the help.   We are still seeing at least one  Incident that has  
been re-opened that does not have a date in the re-opened date field.  Have you 
ran into any issues like that?  The re-open date field definitely looks more 
useful the Kick_Back Count field.

Thanks,
Todd

From: ARSList 
[mailto:arslist-boun...@arslist.org] On 
Behalf Of CRENSHAW, CRYSTAL
Sent: Friday, February 09, 2018 8:48 AM
To: arslist@ARSLIST.ORG
Subject: RE: Reporting on Incidents that have re-opened

Todd,

There is a hidden field on HPD:Help Desk called ‘Re-Opened Date’.  If that 
field has a vaule, then it has been reopened at least once.


This is a query for active Incidents that have been previously resolved:

'Re-Opened Date' != $NULL$ AND 'Status*' < "Resolved"

Hope that helps.


Thanks,

Crystal Crenshaw
Service Management Senior Systems Analyst
Project Services – Service Management
(919)508-0546

[cid:image001.gif@01D3A1A6.C4BB03F0]

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Arner, Todd
Sent: Friday, February 09, 2018 9:14 AM
To: arslist@ARSLIST.ORG
Subject: Reporting on Incidents that have re-opened

Wondering if anyone can help us figure out how to query for Incidents that have 
been re-opened.  We thought we could do this by using the Kick_Back Count field 
but it seems to reset the count after the Incident is closed and we also get 
strange results were incidents we would expect to match the query do not.  
Anyway, wondering if anyone has a better way to find incidents that have been 
re-opened.  We are using version 9.1.3.  Basically we want to run a query 
against all incidents that will list any that have been resolved and then moved 
back to an active status.  I appreciate any tips you can provide. ☺

Todd Arner
Systems Administrator III
Great Lakes Educational Loan Services, Inc.


The information contained in this communication may be confidential, is 
intended only for the use of the recipient(s) named above, and may be protected 
under state or federal law. If the reader of this message is not the intended 
recipient, you are hereby notified that any dissemination, distribution, or 
copying of this communication, or any of its contents, is strictly prohibited. 
If you have received this communication in error, please forward the 
communication to no...@glhec.org immediately and 
destroy or delete the original message and any copy of it from your computer 
system. If you have any questions concerning this message, please contact the 
sender.
This email may contain confidential and privileged material for the sole use of 
the intended recipient. If you are not the intended recipient, please contact 
the sender and delete all copies. Any review or distribution by others is 
strictly prohibited. Personal emails are restricted by policy of the State 
Employees' Credit Union (SECU). Therefore SECU specifically disclaims any 
responsibility or liability for any personal information or opinions of the 
author expressed in this email.

--
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

RE: [EXTERNAL] Re: Reporting on Incidents that have re-opened

[Fawver, Dustin]

I was also thinking of a filter that could do it on Modify, depending on how 
you want to be notified.  Maybe an email or a message.  Have the Run If clause 
of:

(‘DB.Status’ = “Resolved”) AND (‘TR.Status’ < “Resolved”)

I’m just using regular ARS 9.1.2, if that plays any part in how things are set 
up.

I hope this helps.

Dustin Fawver
Sr. Help Desk Technician
Information Technology Services

P: 423-439-4648
itsh...@etsu.edu
[itslogo]

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of LJ LongWing
Sent: Friday, February 09, 2018 11:47 AM
To: ARSList 
Subject: [EXTERNAL] Re: Reporting on Incidents that have re-opened


*** This email does NOT originate from an ETSU person or service. ***
Todd,
How about something a bit more novel.  Look for records that have a Resolved 
Status history Date/User who's status is < Resolved

On Fri, Feb 9, 2018 at 8:55 AM, Arner, Todd 
> wrote:
Hi Crystal,
Thanks for the help.   We are still seeing at least one  Incident that has  
been re-opened that does not have a date in the re-opened date field.  Have you 
ran into any issues like that?  The re-open date field definitely looks more 
useful the Kick_Back Count field.

Thanks,
Todd

From: ARSList 
[mailto:arslist-boun...@arslist.org] On 
Behalf Of CRENSHAW, CRYSTAL
Sent: Friday, February 09, 2018 8:48 AM
To: arslist@ARSLIST.ORG
Subject: RE: Reporting on Incidents that have re-opened

Todd,

There is a hidden field on HPD:Help Desk called ‘Re-Opened Date’.  If that 
field has a vaule, then it has been reopened at least once.


This is a query for active Incidents that have been previously resolved:

'Re-Opened Date' != $NULL$ AND 'Status*' < "Resolved"

Hope that helps.


Thanks,

Crystal Crenshaw
Service Management Senior Systems Analyst
Project Services – Service Management
(919)508-0546

[cid:image003.gif@01D3A19E.13860010]

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Arner, Todd
Sent: Friday, February 09, 2018 9:14 AM
To: arslist@ARSLIST.ORG
Subject: Reporting on Incidents that have re-opened

Wondering if anyone can help us figure out how to query for Incidents that have 
been re-opened.  We thought we could do this by using the Kick_Back Count field 
but it seems to reset the count after the Incident is closed and we also get 
strange results were incidents we would expect to match the query do not.  
Anyway, wondering if anyone has a better way to find incidents that have been 
re-opened.  We are using version 9.1.3.  Basically we want to run a query 
against all incidents that will list any that have been resolved and then moved 
back to an active status.  I appreciate any tips you can provide. ☺

Todd Arner
Systems Administrator III
Great Lakes Educational Loan Services, Inc.


The information contained in this communication may be confidential, is 
intended only for the use of the recipient(s) named above, and may be protected 
under state or federal law. If the reader of this message is not the intended 
recipient, you are hereby notified that any dissemination, distribution, or 
copying of this communication, or any of its contents, is strictly prohibited. 
If you have received this communication in error, please forward the 
communication to no...@glhec.org immediately and 
destroy or delete the original message and any copy of it from your computer 
system. If you have any questions concerning this message, please contact the 
sender.
This email may contain confidential and privileged material for the sole use of 
the intended recipient. If you are not the intended recipient, please contact 
the sender and delete all copies. Any review or distribution by others is 
strictly prohibited. Personal emails are restricted by policy of the State 
Employees' Credit Union (SECU). Therefore SECU specifically disclaims any 
responsibility or liability for any personal information or opinions of the 
author expressed in this email.

--
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

Re: Reporting on Incidents that have re-opened

[LJ LongWing]

Todd,
How about something a bit more novel.  Look for records that have a
Resolved Status history Date/User who's status is < Resolved

On Fri, Feb 9, 2018 at 8:55 AM, Arner, Todd  wrote:

> Hi Crystal,
>
> Thanks for the help.   We are still seeing at least one  Incident that has
>  been re-opened that does not have a date in the re-opened date field.
> Have you ran into any issues like that?  The re-open date field definitely
> looks more useful the Kick_Back Count field.
>
>
>
> Thanks,
>
> Todd
>
>
>
> *From:* ARSList [mailto:arslist-boun...@arslist.org] *On Behalf Of *CRENSHAW,
> CRYSTAL
> *Sent:* Friday, February 09, 2018 8:48 AM
> *To:* arslist@ARSLIST.ORG
> *Subject:* RE: Reporting on Incidents that have re-opened
>
>
>
> Todd,
>
>
>
> There is a hidden field on HPD:Help Desk called ‘Re-Opened Date’.  If that
> field has a vaule, then it has been reopened at least once.
>
>
>
>
>
> This is a query for active Incidents that have been previously resolved:
>
>
>
> 'Re-Opened Date' != $NULL$ AND 'Status*' < "Resolved"
>
>
>
> Hope that helps.
>
>
>
>
>
> Thanks,
>
>
>
> Crystal Crenshaw
>
> Service Management Senior Systems Analyst
>
> Project Services – Service Management
>
> (919)508-0546 <(919)%20508-0546>
>
>
>
>
>
> *From:* ARSList [mailto:arslist-boun...@arslist.org
> ] *On Behalf Of *Arner, Todd
> *Sent:* Friday, February 09, 2018 9:14 AM
> *To:* arslist@ARSLIST.ORG
> *Subject:* Reporting on Incidents that have re-opened
>
>
>
> Wondering if anyone can help us figure out how to query for Incidents that
> have been re-opened.  We thought we could do this by using the Kick_Back
> Count field but it seems to reset the count after the Incident is closed
> and we also get strange results were incidents we would expect to match the
> query do not.  Anyway, wondering if anyone has a better way to find
> incidents that have been re-opened.  We are using version 9.1.3.  Basically
> we want to run a query against all incidents that will list any that have
> been resolved and then moved back to an active status.  I appreciate any
> tips you can provide. J
>
>
>
> Todd Arner
>
> Systems Administrator III
>
> Great Lakes Educational Loan Services, Inc.
>
>
> --
>
> The information contained in this communication may be confidential, is
> intended only for the use of the recipient(s) named above, and may be
> protected under state or federal law. If the reader of this message is not
> the intended recipient, you are hereby notified that any dissemination,
> distribution, or copying of this communication, or any of its contents, is
> strictly prohibited. If you have received this communication in error,
> please forward the communication to no...@glhec.org immediately and
> destroy or delete the original message and any copy of it from your
> computer system. If you have any questions concerning this message, please
> contact the sender.
>
> This email may contain confidential and privileged material for the sole
> use of the intended recipient. If you are not the intended recipient,
> please contact the sender and delete all copies. Any review or distribution
> by others is strictly prohibited. Personal emails are restricted by policy
> of the State Employees' Credit Union (SECU). Therefore SECU specifically
> disclaims any responsibility or liability for any personal information or
> opinions of the author expressed in this email.
>
> --
> ARSList mailing list
> ARSList@arslist.org
> https://mailman.rrr.se/cgi/listinfo/arslist
>
>
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

RE: Reporting on Incidents that have re-opened

[Arner, Todd]

Hi Crystal,
Thanks for the help.   We are still seeing at least one  Incident that has  
been re-opened that does not have a date in the re-opened date field.  Have you 
ran into any issues like that?  The re-open date field definitely looks more 
useful the Kick_Back Count field.

Thanks,
Todd

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of CRENSHAW, 
CRYSTAL
Sent: Friday, February 09, 2018 8:48 AM
To: arslist@ARSLIST.ORG
Subject: RE: Reporting on Incidents that have re-opened

Todd,

There is a hidden field on HPD:Help Desk called 'Re-Opened Date'.  If that 
field has a vaule, then it has been reopened at least once.


This is a query for active Incidents that have been previously resolved:

'Re-Opened Date' != $NULL$ AND 'Status*' < "Resolved"

Hope that helps.


Thanks,

Crystal Crenshaw
Service Management Senior Systems Analyst
Project Services - Service Management
(919)508-0546

[cid:image001.gif@01D3A18B.F21AB900]

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Arner, Todd
Sent: Friday, February 09, 2018 9:14 AM
To: arslist@ARSLIST.ORG
Subject: Reporting on Incidents that have re-opened

Wondering if anyone can help us figure out how to query for Incidents that have 
been re-opened.  We thought we could do this by using the Kick_Back Count field 
but it seems to reset the count after the Incident is closed and we also get 
strange results were incidents we would expect to match the query do not.  
Anyway, wondering if anyone has a better way to find incidents that have been 
re-opened.  We are using version 9.1.3.  Basically we want to run a query 
against all incidents that will list any that have been resolved and then moved 
back to an active status.  I appreciate any tips you can provide. :)

Todd Arner
Systems Administrator III
Great Lakes Educational Loan Services, Inc.


The information contained in this communication may be confidential, is 
intended only for the use of the recipient(s) named above, and may be protected 
under state or federal law. If the reader of this message is not the intended 
recipient, you are hereby notified that any dissemination, distribution, or 
copying of this communication, or any of its contents, is strictly prohibited. 
If you have received this communication in error, please forward the 
communication to no...@glhec.org immediately and 
destroy or delete the original message and any copy of it from your computer 
system. If you have any questions concerning this message, please contact the 
sender.
This email may contain confidential and privileged material for the sole use of 
the intended recipient. If you are not the intended recipient, please contact 
the sender and delete all copies. Any review or distribution by others is 
strictly prohibited. Personal emails are restricted by policy of the State 
Employees' Credit Union (SECU). Therefore SECU specifically disclaims any 
responsibility or liability for any personal information or opinions of the 
author expressed in this email.
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

RE: Reporting on Incidents that have re-opened

[CRENSHAW, CRYSTAL]

Todd,

There is a hidden field on HPD:Help Desk called 'Re-Opened Date'.  If that 
field has a vaule, then it has been reopened at least once.


This is a query for active Incidents that have been previously resolved:

'Re-Opened Date' != $NULL$ AND 'Status*' < "Resolved"

Hope that helps.


Thanks,

Crystal Crenshaw
Service Management Senior Systems Analyst
Project Services - Service Management
(919)508-0546

[cid:image001.gif@01D3A18A.C18A6E30]

From: ARSList [mailto:arslist-boun...@arslist.org] On Behalf Of Arner, Todd
Sent: Friday, February 09, 2018 9:14 AM
To: arslist@ARSLIST.ORG
Subject: Reporting on Incidents that have re-opened

Wondering if anyone can help us figure out how to query for Incidents that have 
been re-opened.  We thought we could do this by using the Kick_Back Count field 
but it seems to reset the count after the Incident is closed and we also get 
strange results were incidents we would expect to match the query do not.  
Anyway, wondering if anyone has a better way to find incidents that have been 
re-opened.  We are using version 9.1.3.  Basically we want to run a query 
against all incidents that will list any that have been resolved and then moved 
back to an active status.  I appreciate any tips you can provide. :)

Todd Arner
Systems Administrator III
Great Lakes Educational Loan Services, Inc.


The information contained in this communication may be confidential, is 
intended only for the use of the recipient(s) named above, and may be protected 
under state or federal law. If the reader of this message is not the intended 
recipient, you are hereby notified that any dissemination, distribution, or 
copying of this communication, or any of its contents, is strictly prohibited. 
If you have received this communication in error, please forward the 
communication to no...@glhec.org immediately and 
destroy or delete the original message and any copy of it from your computer 
system. If you have any questions concerning this message, please contact the 
sender.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. If you are not the intended recipient, please contact 
the sender and delete all copies. Any review or distribution by others is 
strictly prohibited. Personal emails are restricted by policy of the State 
Employees' Credit Union (SECU).  Therefore SECU specifically disclaims any 
responsibility or liability for any personal information or opinions of the 
author expressed in this email.
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

Reporting on Incidents that have re-opened

[Arner, Todd]

Wondering if anyone can help us figure out how to query for Incidents that have 
been re-opened.  We thought we could do this by using the Kick_Back Count field 
but it seems to reset the count after the Incident is closed and we also get 
strange results were incidents we would expect to match the query do not.  
Anyway, wondering if anyone has a better way to find incidents that have been 
re-opened.  We are using version 9.1.3.  Basically we want to run a query 
against all incidents that will list any that have been resolved and then moved 
back to an active status.  I appreciate any tips you can provide. :)

Todd Arner
Systems Administrator III
Great Lakes Educational Loan Services, Inc.

--
The information contained in this communication may be confidential, is 
intended only for the use of the recipient(s) named above, and may be protected 
under state or federal law. If the reader of this message is not the intended 
recipient, you are hereby notified that any dissemination, distribution, or 
copying of this communication, or any of its contents, is strictly prohibited. 
If you have received this communication in error, please forward the 
communication to no...@glhec.org immediately and destroy or delete the original 
message and any copy of it from your computer system. If you have any questions 
concerning this message, please contact the sender.
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist