In the development point of view I think that would be pretty useful too... something
like a REM in a batch file or some programming code... would be neat to have...

In light of another infamous thread thats not yet seen its death, I think a warning for
developers that they are using an Admin tool of the wrong version would also be a
pretty good idea... it might have saved Roger Nall's day when he did what he did...

Regards

Joe

--- Rick Cook wrote:

> OK, here's something I would like to see. How about the ability to disable
> individual actions in an AL or Filter, for debug purposes? It's a minor thing, but
> would be nice sometimes to not have to delete and then reconstruct certain actions.
>
> Rick
>
>
>
> From: strauss
> Sent: Thu 8/12/2004 9:15 AM
> To: ARSLIST@ARSLIST.ORG
> Subject: Re: OT:Remedy Annoyances
>
>
> We have already begun enforcing strong password security on the LDAP
> server, which directly affects all AREA authentication, but that has no
> effect on those support staff who set a LOCAL password in the User form
> - which we have encouraged since they can still login and create tickets
> when the LDAP server IS THE PROBLEM. eDir has been more reliable of
> late, but every time they patch it or change the OS (was on Solaris,
> then Linux, then NetWare - which has been the most stable) it has
> hiccups that CANNOT be allowed to interfere with helpdesk staff entering
> tickets, especially since when eDir breaks so many campus systems stop
> working at once that the helpdesk telephones all explode! So, I need
> similar controls on passwords in the User form, as will any site that is
> not able to use external authentication for one reason or another.
>
> The ability to set a login banner in the User Tool might be solved
> through the Init-Form or ARS 6 Home Page (whenever we migrate to ARS
> 6.x), but in each case we are having to do custom application
> development to work around a basic system limitation that COULD be
> solved in the client-server application. My to-do list (Change Request
> queue) is already overfull implementing and maintaining the ITSM apps
> without having to develop basic security and system features as well.
>
> Christopher Strauss, MSLS
> Remedy Database Administrator
> University of North Texas Computing Center
> http://remedy.unt.edu/
>
> -----Original Message-----
> From: Covert, Jack [mailto:Jack.Covert@MCKESSON.COM]
> Sent: Thursday, August 12, 2004 10:50 AM
> To: ARSLIST@ARSLIST.ORG
> Subject: Re: OT:Remedy Annoyances
>
> You could use Init-Form to bring a dialog up every time somebody logs
> in.
> Then on close go to the Support form (or whatever yours may be).
> Regarding passwords, I think the movement will be to use AREA/LDAP.
> There is no need to keep all this information in silos all over the
> place.
>
> Jack
>
> -----Original Message-----
> From: strauss [mailto:strauss@REMEDY.ACS.UNT.EDU]
> Sent: Thursday, August 12, 2004 7:27 AM
> To: ARSLIST@ARSLIST.ORG
> Subject: Re: OT:Remedy Annoyances
>
>
> Let me second this motion. The state auditors are demanding strong
> passwords, password aging, previous password prevention, etc., etc., and
> while this is easy enough to implement at the OS level, many
> applications (Remedy for one) do not support these restrictions in the
> base product. I also need to be able to present an authorized user
> security warning at login - easy on mid-tier but not on the User Tool
> where you would have to hack the executable. We need to be able to set
> these sorts of things on the AR Server, and let the clients enforce
> them.
>
> Christopher Strauss, MSLS
> Remedy Database Administrator
> University of North Texas Computing Center http://remedy.unt.edu/=20
>
> -----Original Message-----
> From: Joe DeSouza [mailto:joeremedy@YAHOO.COM]=20
> Sent: Thursday, August 12, 2004 12:42 AM
> To: ARSLIST@ARSLIST.ORG
> Subject: Re: OT:Remedy Annoyances
>
> Hello all,
>
> While we are still on this topic of discussing our wish-list, a internal
> Remedy User password management system is something I'm sure a lot would
> have wanted in the event that the user authentication is internal... I
> know that there are some real slick apps available built by the likes of
> Bruce to achieve this but if this feature was 'built-in' I think I would
> have liked that at least...
>
> Regards
>
>
> =3D=3D=3D=3D=3D
> Joe DeSouza,
> Remedy Technical Consultant,
> CyberMAK Information Systems,
> Kuwait.
> Phone :- 00965 484 7068
> Mobile :- 00965 940 6129
>
>
>
>
>
>
>
>
> Do you Yahoo!?
> Yahoo! Mail is new and improved - Check it out!
> http://promotions.yahoo.com/newmail
>
>
>
> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
> (Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
> SERVICES at www.QMXS.com
>
>
>
>
> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
> (Support:
> mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES
> at www.QMXS.com
>
>
>
> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
> (Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
> SERVICES at www.QMXS.com
>
>
> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
> mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
> www.QMXS.com
>
>
> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
> mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
> www.QMXS.com
>


=====
Joe DeSouza,
Remedy Technical Consultant,
CyberMAK Information Systems,
Kuwait.
Phone :- 00965 484 7068
Mobile :- 00965 940 6129









Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/newmail

**
I agree with you, Rick. However, I have a workaround - I disable the original, File|Save As the object, and delete the annoying action - then I can switch between the two by enabling/disabling them.

Later
Stephen

Rick Cook wrote:

**
OK, here's something I would like to see. How about the ability to disable individual actions in an AL or Filter, for debug purposes? It's a minor thing, but would be nice sometimes to not have to delete and then reconstruct certain actions.

Rick
This posting was submitted via the Web interface







Post your free ad now! Yahoo! Canada Personals

That would be sweet! How about allowing you to "move" menu items rather
than just add after/before/modify/delete?

-----Original Message-----
From: Rick Cook [mailto:rcook@DENALIAI.COM]
Sent: Thursday, August 12, 2004 9:30 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances


--54C842DE-05A2-40B0-B2CC-99163D8A590D
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

OK, here's something I would like to see. How about the ability to disable=
individual actions in an AL or Filter, for debug purposes? It's a minor t=
hing, but would be nice sometimes to not have to delete and then reconstruc=
t certain actions.

Rick



From: strauss
Sent: Thu 8/12/2004 9:15 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances


We have already begun enforcing strong password security on the LDAP
server, which directly affects all AREA authentication, but that has no
effect on those support staff who set a LOCAL password in the User form
- which we have encouraged since they can still login and create tickets
when the LDAP server IS THE PROBLEM. eDir has been more reliable of
late, but every time they patch it or change the OS (was on Solaris,
then Linux, then NetWare - which has been the most stable) it has
hiccups that CANNOT be allowed to interfere with helpdesk staff entering
tickets, especially since when eDir breaks so many campus systems stop
working at once that the helpdesk telephones all explode! So, I need
similar controls on passwords in the User form, as will any site that is
not able to use external authentication for one reason or another.

The ability to set a login banner in the User Tool might be solved
through the Init-Form or ARS 6 Home Page (whenever we migrate to ARS
6.x), but in each case we are having to do custom application
development to work around a basic system limitation that COULD be
solved in the client-server application. My to-do list (Change Request
queue) is already overfull implementing and maintaining the ITSM apps
without having to develop basic security and system features as well.

Christopher Strauss, MSLS
Remedy Database Administrator
University of North Texas Computing Center
http://remedy.unt.edu/=20

-----Original Message-----
From: Covert, Jack [mailto:Jack.Covert@MCKESSON.COM]=20
Sent: Thursday, August 12, 2004 10:50 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances

You could use Init-Form to bring a dialog up every time somebody logs
in.
Then on close go to the Support form (or whatever yours may be).
Regarding passwords, I think the movement will be to use AREA/LDAP.
There is no need to keep all this information in silos all over the
place.

Jack

-----Original Message-----
From: strauss [mailto:strauss@REMEDY.ACS.UNT.EDU]
Sent: Thursday, August 12, 2004 7:27 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances


Let me second this motion. The state auditors are demanding strong
passwords, password aging, previous password prevention, etc., etc., and
while this is easy enough to implement at the OS level, many
applications (Remedy for one) do not support these restrictions in the
base product. I also need to be able to present an authorized user
security warning at login - easy on mid-tier but not on the User Tool
where you would have to hack the executable. We need to be able to set
these sorts of things on the AR Server, and let the clients enforce
them.

Christopher Strauss, MSLS
Remedy Database Administrator
University of North Texas Computing Center http://remedy.unt.edu/=3D20

-----Original Message-----
From: Joe DeSouza [mailto:joeremedy@YAHOO.COM]=3D20
Sent: Thursday, August 12, 2004 12:42 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances

Hello all,

While we are still on this topic of discussing our wish-list, a internal
Remedy User password management system is something I'm sure a lot would
have wanted in the event that the user authentication is internal... I
know that there are some real slick apps available built by the likes of
Bruce to achieve this but if this feature was 'built-in' I think I would
have liked that at least...

Regards


=3D3D=3D3D=3D3D=3D3D=3D3D
Joe DeSouza,
Remedy Technical Consultant,
CyberMAK Information Systems,
Kuwait.
Phone :- 00965 484 7068
Mobile :- 00965 940 6129








Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/newmail



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
SERVICES at www.QMXS.com




UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
(Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES
at www.QMXS.com



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
SERVICES at www.QMXS.com

=

UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support: =
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at w=
ww.QMXS.com



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
www.QMXS.com

--54C842DE-05A2-40B0-B2CC-99163D8A590D
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

**







UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
www.QMXS.com This posting was submitted via the Web interface

--54C842DE-05A2-40B0-B2CC-99163D8A590D--

Stephen,

you COULD consider adding your external users to your LDAP system for
validation purposes. After all, these users *ARE* using your resources.
But even then you'd need a way to let them change their passwords.

--
Michiel

-----Oorspronkelijk bericht-----
Van: lilly remedy [mailto:arslistlilly@YAHOO.CA]
Verzonden: donderdag 12 augustus 2004 18:49
Aan: ARSLIST@ARSLIST.ORG
Onderwerp: Re: [ARSLIST] OT:Remedy Annoyances


**
The problem with using the Init-Form is that the user has to successfully
log in first. One of our requirements is to lock out a user after three bad
attempts.
As for LDAP - we are not in a position to make use of that because a good
number of our users are external and they don't have accounts anywhere else.
And finally, although it's makes life simpler for users, having one password
to get into Everything" is never a good idea.

Later
Stephen


"Covert, Jack" wrote:

You could use Init-Form to bring a dialog up every time somebody logs in.
Then on close go to the Support form (or whatever yours may be). Regarding
passwords, I think the movement will be to use AREA/LDAP. There is no need
to keep all this information in silos all over the place.

Jack

-----Original Message-----
From: strauss [mailto:strauss@REMEDY.ACS.UNT.EDU]
Sent: Thursday, August 12, 2004 7:27 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances


Let me second this motion. The state auditors are demanding strong
passwords, password aging, previous password prevention, etc., etc., and
while this is easy enough to implement at the OS level, many
applications (Remedy for one) do not support these restrictions in the
base product. I also need to be able to present an authorized user
security warning at login - easy on mid-tier but not on the User Tool
where you would have to hack the executable. We need to be able to set
these sorts of things on the AR Server, and let the clients enforce
them.

Christopher Strauss, MSLS
Remedy Database Administrator
University of North Texas Computing Center
http://remedy.unt.edu/=20

-----Original Message-----
From: Joe DeSouza [mailto:joeremedy@YAHOO.COM]=20
Sent: Thursday, August 12, 2004 12:42 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances

Hello all,

While we are still on this topic of discussing our wish-list, a internal
Remedy User password management system is something I'm sure a lot would
have wanted in the event that the user authentication is internal... I
know that there are some real slick apps available built by the likes of
Bruce to achieve this but if this feature was 'built-in' I think I would
have liked that at least...

Regards


=3D=3D=3D=3D=3D
Joe DeSouza,
Remedy Technical Consultant,
CyberMAK Information Systems,
Kuwait.
Phone :- 00965 484 7068
Mobile :- 00965 940 6129








Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/newmail



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
SERVICES at www.QMXS.com



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES

UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
SERVICES at www.QMXS.com This posting was submitted via the Web interface at
www.QMXS.com



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
www.QMXS.com







Post your free ad now! Yahoo! Canada
Personals

See below

-----Original Message-----
From: lilly remedy [mailto:arslistlilly@YAHOO.CA]
Sent: Thursday, August 12, 2004 9:30 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances


--0-2141087365-1092328177=:61787
Content-Type: text/plain; charset=us-ascii

The problem with using the Init-Form is that the user has to successfully
log in first. One of our requirements is to lock out a user after three bad
attempts. - That is a good point...

As for LDAP - we are not in a position to make use of that because a good
number of our users are external and they don't have accounts anywhere else.
- We have the same issue here. We are building an enterprise-directory with
a separate data source for external people so that we can still use the
functionality (there are a couple of other groups that need the same info,
so it makes sense to do).

And finally, although it's makes life simpler for users, having one password
to get into Everything" is never a good idea. Agreed. But I'd guess that
Remedy is one of the less sensative areas to worry about this. I suppose it
depends on what you are using it for of course.

Later
Stephen


"Covert, Jack" wrote:
You could use Init-Form to bring a dialog up every time somebody logs in.
Then on close go to the Support form (or whatever yours may be). Regarding
passwords, I think the movement will be to use AREA/LDAP. There is no need
to keep all this information in silos all over the place.

Jack

-----Original Message-----
From: strauss [mailto:strauss@REMEDY.ACS.UNT.EDU]
Sent: Thursday, August 12, 2004 7:27 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances


Let me second this motion. The state auditors are demanding strong
passwords, password aging, previous password prevention, etc., etc., and
while this is easy enough to implement at the OS level, many
applications (Remedy for one) do not support these restrictions in the
base product. I also need to be able to present an authorized user
security warning at login - easy on mid-tier but not on the User Tool
where you would have to hack the executable. We need to be able to set
these sorts of things on the AR Server, and let the clients enforce
them.

Christopher Strauss, MSLS
Remedy Database Administrator
University of North Texas Computing Center
http://remedy.unt.edu/=20

-----Original Message-----
From: Joe DeSouza [mailto:joeremedy@YAHOO.COM]=20
Sent: Thursday, August 12, 2004 12:42 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances

Hello all,

While we are still on this topic of discussing our wish-list, a internal
Remedy User password management system is something I'm sure a lot would
have wanted in the event that the user authentication is internal... I
know that there are some real slick apps available built by the likes of
Bruce to achieve this but if this feature was 'built-in' I think I would
have liked that at least...

Regards


=3D=3D=3D=3D=3D
Joe DeSouza,
Remedy Technical Consultant,
CyberMAK Information Systems,
Kuwait.
Phone :- 00965 484 7068
Mobile :- 00965 940 6129








Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/newmail



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
SERVICES at www.QMXS.com



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
www.QMXS.com



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
www.QMXS.com



---------------------------------
Post your free ad now! Yahoo! Canada Personals



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
www.QMXS.com

--0-2141087365-1092328177=:61787
Content-Type: text/html; charset=us-ascii

**

The problem with using the Init-Form is that the user has to
successfully log in first.  One of our requirements is to lock out a
user after three bad attempts.

As for LDAP - we are not in a position to make use of that because a
good number of our users are external and they don't have accounts anywhere
else.

And finally, although it's makes life simpler for users, having one
password to get into Everything" is never a good idea.

 

Later

Stephen 

"Covert, Jack" <Jack.Covert@MCKESSON.COM>
wrote:

You could use Init-Form to bring a dialog up
every time somebody logs in.
Then on close go to the Support form (or
whatever yours may be). Regarding
passwords, I think the movement will be
to use AREA/LDAP. There is no need
to keep all this information in silos
all over the place.

Jack

-----Original Message-----
From:
strauss [mailto:strauss@REMEDY.ACS.UNT.EDU]
Sent: Thursday, August 12,
2004 7:27 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy
Annoyances


Let me second this motion. The state auditors are
demanding strong
passwords, password aging, previous password prevention,
etc., etc., and
while this is easy enough to implement at the OS level,
many
applications (Remedy for one) do not support these restrictions in
the
base product. I also need to be able to present an authorized
user
security warning at login - easy on
mid-tier but not on the User Tool
where you would have to hack the
executable. We need to be able to set
these sorts of things on the AR
Server, and let the clients enforce
them.

Christopher Strauss,
MSLS
Remedy Database Administrator
University of North Texas Computing
Center
http://remedy.unt.edu/=20

-----Original
Message-----
From: Joe DeSouza [mailto:joeremedy@YAHOO.COM]=20
Sent:
Thursday, August 12, 2004 12:42 AM
To: ARSLIST@ARSLIST.ORG
Subject:
Re: OT:Remedy Annoyances

Hello all,

While we are still on this
topic of discussing our wish-list, a internal
Remedy User password
management system is something I'm sure a lot would
have wanted in the
event that the user authentication is internal... I
know that there are
some real slick apps available built by the likes of
Bruce to achieve
this but if this feature was 'built-in' I think I would
have liked that
at
least...

Regards


=3D=3D=3D=3D=3D
Joe
DeSouza,
Remedy Technical Consultant,
CyberMAK Information
Systems,
Kuwait.
Phone :- 00965 484 7068
Mobile :- 00965 940
6129








Do
you Yahoo!?
Yahoo! Mail is new and improved - Check it
out!
http://promotions.yahoo.com/newmail




UNSUBSCRIBE
or access ARSList Archives at http://www.ARSLIST.org
(Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
SERVICES at
www.QMXS.com




UNSUBSCRIBE or access ARSList Archives at
http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is
hosted by QMX SUPPORT SERVICES


UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
www.QMXS.com This posting was submitted via the Web interface

at
www.QMXS.com



UNSUBSCRIBE or access ARSList Archives at
http://www.ARSLIST.org (Support: mailto:support@arslist.org ) ARSList is
hosted by QMX SUPPORT SERVICES at www.QMXS.com

size=1>Post your free ad now! href="http://ca.personals.yahoo.com/">Yahoo! Canada Personals

--0-2141087365-1092328177=:61787--

Another nice debug feature; a log4j "look-a-like" where you can specify what kind of loglevel you want on filter-logs.

Levels like; INFO, DEBUG, ALL, etc....

And built-in logging into a logform.


Regards,
Jarl


-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG]On Behalf Of Rick Cook
Sent: 12. august 2004 18:30
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances


**
OK, here's something I would like to see. How about the ability to disable individual actions in an AL or Filter, for debug purposes? It's a minor thing, but would be nice sometimes to not have to delete and then reconstruct certain actions.

Rick



From: strauss
Sent: Thu 8/12/2004 9:15 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances


We have already begun enforcing strong password security on the LDAP
server, which directly affects all AREA authentication, but that has no
effect on those support staff who set a LOCAL password in the User form
- which we have encouraged since they can still login and create tickets
when the LDAP server IS THE PROBLEM. eDir has been more reliable of
late, but every time they patch it or change the OS (was on Solaris,
then Linux, then NetWare - which has been the most stable) it has
hiccups that CANNOT be allowed to interfere with helpdesk staff entering
tickets, especially since when eDir breaks so many campus systems stop
working at once that the helpdesk telephones all explode! So, I need
similar controls on passwords in the User form, as will any site that is
not able to use external authentication for one reason or another.

The ability to set a login banner in the User Tool might be solved
through the Init-Form or ARS 6 Home Page (whenever we migrate to ARS
6.x), but in each case we are having to do custom application
development to work around a basic system limitation that COULD be
solved in the client-server application. My to-do list (Change Request
queue) is already overfull implementing and maintaining the ITSM apps
without having to develop basic security and system features as well.

Christopher Strauss, MSLS
Remedy Database Administrator
University of North Texas Computing Center
http://remedy.unt.edu/

-----Original Message-----
From: Covert, Jack [mailto:Jack.Covert@MCKESSON.COM]
Sent: Thursday, August 12, 2004 10:50 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances

You could use Init-Form to bring a dialog up every time somebody logs
in.
Then on close go to the Support form (or whatever yours may be).
Regarding passwords, I think the movement will be to use AREA/LDAP.
There is no need to keep all this information in silos all over the
place.

Jack

-----Original Message-----
From: strauss [mailto:strauss@REMEDY.ACS.UNT.EDU]
Sent: Thursday, August 12, 2004 7:27 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances


Let me second this motion. The state auditors are demanding strong
passwords, password aging, previous password prevention, etc., etc., and
while this is easy enough to implement at the OS level, many
applications (Remedy for one) do not support these restrictions in the
base product. I also need to be able to present an authorized user
security warning at login - easy on mid-tier but not on the User Tool
where you would have to hack the executable. We need to be able to set
these sorts of things on the AR Server, and let the clients enforce
them.

Christopher Strauss, MSLS
Remedy Database Administrator
University of North Texas Computing Center http://remedy.unt.edu/=20

-----Original Message-----
From: Joe DeSouza [mailto:joeremedy@YAHOO.COM]=20
Sent: Thursday, August 12, 2004 12:42 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances

Hello all,

While we are still on this topic of discussing our wish-list, a internal
Remedy User password management system is something I'm sure a lot would
have wanted in the event that the user authentication is internal... I
know that there are some real slick apps available built by the likes of
Bruce to achieve this but if this feature was 'built-in' I think I would
have liked that at least...

Regards


=3D=3D=3D=3D=3D
Joe DeSouza,
Remedy Technical Consultant,
CyberMAK Information Systems,
Kuwait.
Phone :- 00965 484 7068
Mobile :- 00965 940 6129








Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/newmail



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
SERVICES at www.QMXS.com




UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
(Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES
at www.QMXS.com



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
SERVICES at www.QMXS.com






This posting was submitted via the Web interface

You could also enforce this when accessing any of the ITSM consoles. In
the user form, you can store a password history (encrypted), password
expiration and so on.

Kind Regards,
Axton Grams
New York Life
Remedy Solutions
Provider

Mobile: 404.861.7273
Work: 770.406.4415
Email: AxtonWGrams@NewYorkLife.com






|---------+---------------------------->
| | "Covert, Jack" |
| | | | SSON.COM> |
| | Sent by: "Action |
| | Request System |
| | discussion |
| | list(ARSList)" |
| | | | ORG> |
| | |
| | |
| | 08/12/2004 11:49 |
| | AM |
| | Please respond to|
| | arslist |
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
| |
| To: ARSLIST@ARSLIST.ORG |
| cc: |
| Subject: Re: OT:Remedy Annoyances |
>------------------------------------------------------------------------------------------------------------------------------|




You could use Init-Form to bring a dialog up every time somebody logs in.
Then on close go to the Support form (or whatever yours may be). Regarding
passwords, I think the movement will be to use AREA/LDAP. There is no need
to keep all this information in silos all over the place.

Jack

-----Original Message-----
From: strauss [mailto:strauss@REMEDY.ACS.UNT.EDU]
Sent: Thursday, August 12, 2004 7:27 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances


Let me second this motion. The state auditors are demanding strong
passwords, password aging, previous password prevention, etc., etc., and
while this is easy enough to implement at the OS level, many
applications (Remedy for one) do not support these restrictions in the
base product. I also need to be able to present an authorized user
security warning at login - easy on mid-tier but not on the User Tool
where you would have to hack the executable. We need to be able to set
these sorts of things on the AR Server, and let the clients enforce
them.

Christopher Strauss, MSLS
Remedy Database Administrator
University of North Texas Computing Center
http://remedy.unt.edu/=20

-----Original Message-----
From: Joe DeSouza [mailto:joeremedy@YAHOO.COM]=20
Sent: Thursday, August 12, 2004 12:42 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances

Hello all,

While we are still on this topic of discussing our wish-list, a internal
Remedy User password management system is something I'm sure a lot would
have wanted in the event that the user authentication is internal... I
know that there are some real slick apps available built by the likes of
Bruce to achieve this but if this feature was 'built-in' I think I would
have liked that at least...

Regards


=3D=3D=3D=3D=3D
Joe DeSouza,
Remedy Technical Consultant,
CyberMAK Information Systems,
Kuwait.
Phone :- 00965 484 7068
Mobile :- 00965 940 6129








Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/newmail



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
SERVICES at www.QMXS.com




UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
www.QMXS.com



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
www.QMXS.com

The one feature I'd like to see is the ability to create variables/keywords. It is simply silly how many forms have 20+ "zTmpxxxxxx" fields that are used only for data processing.

It would be nice if you had the ability during form creation to define admin-created keywords specific to that form (globally would be nice too but that's a whole other ball of wax).

So, instead of creating a field "zTmpHeresMyFieldForFlaggingStuff" I could define a keyword $TEMPFIELD1$, along with a default value. This has two benefits. First, you don't have to place the field on the form and make sure it is or is not in 15 different views. Secondly, it takes it out of the list selection.

AND, it makes it more like "normal" programming.

In a perfect dream world, these would allow arrays, list variables, etc...but I'm not that optimisitic :)

See comments below.

Kind Regards,
Axton Grams
New York Life
Remedy Solutions
Provider

Mobile: 404.861.7273
Work: 770.406.4415
Email: AxtonWGrams@NewYorkLife.com






|---------+---------------------------->
| | William Rentfrow |
| | | | COMINC.COM> |
| | Sent by: "Action |
| | Request System |
| | discussion |
| | list(ARSList)" |
| | | | ORG> |
| | |
| | |
| | 08/12/2004 01:27 |
| | PM |
| | Please respond to|
| | arslist |
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
| |
| To: ARSLIST@ARSLIST.ORG |
| cc: |
| Subject: Re: OT:Remedy Annoyances |
>------------------------------------------------------------------------------------------------------------------------------|




The one feature I'd like to see is the ability to create
variables/keywords. It is simply silly how many forms have 20+
"zTmpxxxxxx" fields that are used only for data processing.

** This is the idea behind a display-only field. No db overhead.

It would be nice if you had the ability during form creation to define
admin-created keywords specific to that form (globally would be nice too
but that's a whole other ball of wax).

** This can be accomplished using global fields if they are static to a
given session(regular) or a given window(window-scoped).

So, instead of creating a field "zTmpHeresMyFieldForFlaggingStuff" I could
define a keyword $TEMPFIELD1$, along with a default value. This has two
benefits. First, you don't have to place the field on the form and make
sure it is or is not in 15 different views. Secondly, it takes it out of
the list selection.

** Fields can be removed from the list selection (for reporting and QBE)
for end users by removing it from the view. Maybe you are referring to the
list selection in the admin tool.

AND, it makes it more like "normal" programming.

In a perfect dream world, these would allow arrays, list variables,
etc...but I'm not that optimisitic :)

** The idea of an array type for fields is a good one. Instead of having
zTmpInt1, zTmpInt2, you could have zTmpInt[x]. Even a reserved range for
Remedy where x>1 and x<1000, and all others are free game. This could
allow for a standard set of array fields for all forms per data type for
processing, though the naming/understanding would get increasingly
confusing as the usage of a given array expanded.



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
www.QMXS.com

One thing that I've always wanted to see was some way to put comments in
an Active-Link or Filter at a per-item basis (like a comment for the
run-if qual, comment for each action, etc). This way you could properly
document each individual component of the workflow to make it easier for
troubleshooting, similar to how you would in a conventional programming
language. As it is, you have one big "Help Text" field for you to put
everything in. It is not very easy to explain why you did what you did
for each piece of the workflow in one big text field. Does anyone have
any ideas for how they are doing this now?


James Scott
Contractor, IST
Mary Kay Inc.
972-687-5204 (w)
817-800-8457 (c)
james.scott@mkcorp.com



-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:ARSLIST@ARSLIST.ORG] On Behalf Of
lars.j.pettersson@VATTENFALL.COM
Sent: Thursday, August 12, 2004 1:27 PM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances


I have one dream, create a unique dbid, like 536970412 and set a flag as
'master'

Then u can use this dbid in 100 regular forms, and set a flag as
'relation to masterid'

If u change the value for the masterid 536970412 from A to B, all other
forms with this id will be updated, without having to build wf for that
update, let ars take care of that ...

I think a timecomsuming part building a large arssystem is to keep
fields 'up to date' with push field action and so.

I know ARS not is build like Access as a relational databasesystem,
advantages and disadvantages ...

L ars

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:ARSLIST@ARSLIST.ORG] On Behalf Of William Rentfrow
Sent: Thursday, August 12, 2004 7:27 PM
To: ARSLIST@ARSLIST.ORG
Subject: Re: OT:Remedy Annoyances

The one feature I'd like to see is the ability to create
variables/keywords. It is simply silly how many forms have 20+
"zTmpxxxxxx" fields that are used only for data processing.

It would be nice if you had the ability during form creation to define
admin-created keywords specific to that form (globally would be nice too
but that's a whole other ball of wax).

So, instead of creating a field "zTmpHeresMyFieldForFlaggingStuff" I
could define a keyword $TEMPFIELD1$, along with a default value. This
has two benefits. First, you don't have to place the field on the form
and make sure it is or is not in 15 different views. Secondly, it takes
it out of the list selection.

AND, it makes it more like "normal" programming.

In a perfect dream world, these would allow arrays, list variables,
etc...but I'm not that optimisitic :)



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
SERVICES at www.QMXS.com



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
SERVICES at www.QMXS.com