1. Too many copies of the same data. When will Remedy implement a healthy balance between a relational and copy model. There are situations where one is definitely a better choice over the other, so why not give the option? 2. When will login names be internally represented as a GUID so login names can be changed without requiring 4 trillion data elements to be updated. (This in part goes back to my first annoyance) 3. Better db utilization. Throw the C programmers and dba's in the same room until they come up with a product that takes advantage of the features offered by each db. Much of this could even be done while staying inside the ANSI standards. (Again, this in part goes back to my first annoyance)
Kind Regards, Axton Grams New York Life Remedy Solutions Provider
With Version 6.x poised on the horizon I have to wonder about some annoyances still in the "core" application like:
1. Checkboxes (don't get me started) 2. Delimiter for a Menu (when append menu selection allowed, i.e. a semicolon or etc.) 3. Control of an Integer field (i.e. do NOT roll down to -1, -2, etc.) 4. MENU validation (i.e. allowing us to choose a MENU from a SQL lookup and etc.) 5. Controlling a window size in the Mid-Tier (please no Java) 6. Comparing a Date to a Date Time field 7. AR Admin Tool - how about a progress meter when importing ? 8. AR Admin Tool - Deleting forms with associations, once I select delete DELETE ? 9. AR Admin Tool - minimize the tool during import and (Windows) and it takes the task manager to restore the window ?
While I am all for the next latest and greatest, have any of these been fixed, repaired or etc.
Anyone have anything to add to this list ?
Regards?Gidd
Glidden L. Calden BUOYANT SOLUTIONS, INC. "Keeping business afloat ...in a Sea of Solutions"
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
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
Of course this is not a problem when you have custom apps :)
You are correct on healthy balance. I have a couple of systems (not Remedy) that I have to pull data from that overkill on normalization. i.e. The state code in an address is in a separate table and all that is stored with the address is a pointer to the correct row in the master list. I mean how many times has the government changed the abbreviation for a state? Why waste 4 (or more) bytes of space for a 2 byte character?
Fred
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of Axton W Grams/NYLIC Sent: Tuesday, August 10, 2004 3:30 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
1. Too many copies of the same data. When will Remedy implement a healthy balance between a relational and copy model. There are situations where one is definitely a better choice over the other, so why not give the option? 2. When will login names be internally represented as a GUID so login names can be changed without requiring 4 trillion data elements to be updated. (This in part goes back to my first annoyance) 3. Better db utilization. Throw the C programmers and dba's in the same room until they come up with a product that takes advantage of the features offered by each db. Much of this could even be done while staying inside the ANSI standards. (Again, this in part goes back to my first annoyance)
Kind Regards, Axton Grams New York Life Remedy Solutions Provider
With Version 6.x poised on the horizon I have to wonder about some annoyances still in the "core" application like:
1. Checkboxes (don't get me started) 2. Delimiter for a Menu (when append menu selection allowed, i.e. a semicolon or etc.) 3. Control of an Integer field (i.e. do NOT roll down to -1, -2, etc.) 4. MENU validation (i.e. allowing us to choose a MENU from a SQL lookup and etc.) 5. Controlling a window size in the Mid-Tier (please no Java) 6. Comparing a Date to a Date Time field 7. AR Admin Tool - how about a progress meter when importing ? 8. AR Admin Tool - Deleting forms with associations, once I select delete DELETE ? 9. AR Admin Tool - minimize the tool during import and (Windows) and it takes the task manager to restore the window ?
While I am all for the next latest and greatest, have any of these been fixed, repaired or etc.
Anyone have anything to add to this list ?
Regards?Gidd
Glidden L. Calden BUOYANT SOLUTIONS, INC. "Keeping business afloat ...in a Sea of Solutions"
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
1) Not to beat a dead horse - but the group list field in the user record. Causes me no end of problems. 2) Drag & Drop migration for workflow in the admin tool between servers. Wouldn't always want to use it, but when you have one or two filters to move...it would be nice. 3) More time in the day to do remedy development :)
Bill Estep ---------------------- http://www.clubreading.com An online community for the avid book reader. On Aug 10, 2004, at 12:39 PM, Gidd Calden wrote:
** ** Listers,
With Version 6.x poised on the horizon I have to wonder about some annoyances still in the "core" application like:
1. Checkboxes (don't get me started) 2. Delimiter for a Menu (when append menu selection allowed, i.e. a semicolon or etc.) 3. Control of an Integer field (i.e. do NOT roll down to -1, -2, etc.) 4. MENU validation (i.e. allowing us to choose a MENU from a SQL lookup and etc.) 5. Controlling a window size in the Mid-Tier (please no Java) 6. Comparing a Date to a Date Time field 7. AR Admin Tool - how about a progress meter when importing ? 8. AR Admin Tool - Deleting forms with associations, once I select delete DELETE ? 9. AR Admin Tool - minimize the tool during import and (Windows) and it takes the task manager to restore the window ?
While I am all for the next latest and greatest, have any of these been fixed, repaired or etc.
Anyone have anything to add to this list ?
Regards...Gidd
Glidden L. Calden BUOYANT SOLUTIONS, INC. “Keeping business afloat ..in a Sea of Solutions”
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
This posting was submitted via the Web interface This posting was submitted via the Web interface
1) Not to beat a dead horse - but the group list field in the user =20 record. Causes me no end of problems. 2) Drag & Drop migration for workflow in the admin tool between =20 servers. Wouldn't always want to use it, but when you have one or two =20=
filters to move...it would be nice. 3) More time in the day to do remedy development :)
Bill Estep ---------------------- http://www.clubreading.com An online community for the avid book reader. On Aug 10, 2004, at 12:39 PM, Gidd Calden wrote:
> ** ** > Listers, > =A0 > With Version 6.x=A0poised on the horizon I have to wonder > about some annoyances still in the "core" application like: > =A0 > 1. Checkboxes (don't get me started) > 2.=A0Delimiter for a Menu (when append menu selection allowed, i.e. a =20=
> semicolon or etc.) > 3. Control of an Integer field (i.e. do NOT roll down to -1, -2, etc.) > 4. MENU validation (i.e. allowing us to choose a MENU from a SQL =20 > lookup and etc.) > 5. Controlling a window size in the Mid-Tier (please no Java) > 6. Comparing a Date to a Date Time field > 7. AR Admin Tool - how about a progress meter when importing ? > 8. AR Admin Tool - Deleting forms with associations, once I select =20 > delete DELETE ? > 9. AR Admin Tool - minimize the tool during import and (Windows) and =20=
> it takes the task > manager to restore the window ? > =A0 > =A0 > While I am all for the next latest and greatest, have any of these =20 > been fixed, repaired > or etc. > =A0 > Anyone have anything to add to this list ?=A0 > =A0 > =A0 > > Regards=85Gidd > > =A0 > > Glidden L. Calden > BUOYANT SOLUTIONS, INC. > =A0 =93Keeping business afloat > =A0=A0=A0=A0=A0=A0 ..in a Sea of Solutions=94 > > =A0 > > =A0 > > Office=A0 =A0( 916.334.0599 > > Cell=A0=A0=A0=A0 =A0=A0( 916.761.3095 > Web =A0=A0=A0 =A08 =A0http://www.buoyantsolutions.net > E-mail=A0 =A0+ mailto:gidd@buoyantsolutions.net > Fax=A0=A0=A0=A0=A0 =A0=A0=FE =A0916.339.2915 > > =A0 > > This message and any attachments are intended only for the use of the =20=
> addressee and may contain information that is privileged and =20 > confidential. If the reader of the message is not the intended =20 > recipient or an authorized representative of the intended recipient, =20=
> you are hereby notified that any dissemination of this communication =20=
> is strictly prohibited. If you have received this communication in =20 > error, please notify us immediately by e-mail and delete the message =20=
> and any attachments from your system. > > =A0 > =A0 > =20 > = =20=
> UNSUBSCRIBE or access ARSList Archives at =20 > http://www.ARSLIST.org (Support: mailto:support@arslist.org ) ARSList =20=
> is hosted by QMX SUPPORT SERVICES at www.QMXS.com This posting was =20 > submitted via the Web interface =20 > = =20=
> UNSUBSCRIBE or access ARSList Archives at =20 > http://www.ARSLIST.org (Support: mailto:support@arslist.org ) ARSList =20=
> is hosted by QMX SUPPORT SERVICES at www.QMXS.com This posting was =20 > submitted via the Web interface=
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
1) Not to beat a dead horse - but the group list field in the user record. Causes me no end of problems.
2) Drag & Drop migration for workflow in the admin tool between servers. Wouldn't always want to use it, but when you have one or two filters to move...it would be nice.
3) More time in the day to do remedy development :)
Bill Estep
----------------------
http://www.clubreading.com
An online community for the avid book reader.
On Aug 10, 2004, at 12:39 PM, Gidd Calden wrote:
** ** =20
= ArialListers,
=A0
ArialWith Version 6.x=A0poised on the horizon I have to wonder
Arial about some annoyances still in the "core" application like:
=A0
Arial1. Checkboxes (don't get me started)
Arial2.=A0Delimiter for a Menu (when append menu selection allowed, i.e. a semicolon or = etc.)
Arial3. Control of an Integer field (i.e. do NOT roll down to -1, -2, etc.)
Arial4. MENU validation (i.e. allowing us to choose a MENU from a SQL lookup and = etc.)
Arial5. Controlling a window size in the Mid-Tier (please no Java)
Arial6. Comparing a Date to a Date Time field
Arial7. AR Admin Tool - how about a progress meter when importing ?
Arial8. AR Admin Tool - Deleting forms with associations, once I select delete DELETE = ?
Arial9. AR Admin Tool - minimize the tool during import and (Windows) and it takes the = task
Arial manager to restore the window ?
=A0
=A0
ArialWhile I am all for the next latest and greatest, have any of these been fixed, = repaired
Arialor etc.
Arial=A0
ArialAnyone have anything to add to this list ?=A0
Arial=A0
=A0
= Regards=85GiddAria= l =
Arial=A0
Glidden L. CaldenArial =
BUOYANT SOLUTIONS, INC.Arial =
=A0 =93Keeping business afloatArial
Arial =A0=A0=A0=A0=A0= =A0 ..in a Sea of Solutions=94Arial =
Arial=A0
Arial=A0
Office=A0=20 = Wingdings=A0Luc= ida Grande( = Arial916.334.0= 599
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
Arial=A0
=A0
= =
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 = =
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=
How about not being able to expand the puny Advanced Search bar window when searching?
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of Covert, Jack Sent: Wednesday, August 11, 2004 9:43 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
Ability to log into multiple servers in one window using different passwords. Like SQL Enterprise Manager.
-----Original Message----- From: Bill Estep [mailto:bestep@CLUBREADING.COM] Sent: Tuesday, August 10, 2004 4:29 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
1) Not to beat a dead horse - but the group list field in the user =20 record. Causes me no end of problems. 2) Drag & Drop migration for workflow in the admin tool between =20 servers. Wouldn't always want to use it, but when you have one or two =20=
filters to move...it would be nice. 3) More time in the day to do remedy development :)
Bill Estep ---------------------- http://www.clubreading.com An online community for the avid book reader. On Aug 10, 2004, at 12:39 PM, Gidd Calden wrote:
> ** ** > Listers, > =A0 > With Version 6.x=A0poised on the horizon I have to wonder about some > annoyances still in the "core" application like: > =A0 > 1. Checkboxes (don't get me started) > 2.=A0Delimiter for a Menu (when append menu selection allowed, i.e. a > =20=
> semicolon or etc.) > 3. Control of an Integer field (i.e. do NOT roll down to -1, -2, etc.)
> 4. MENU validation (i.e. allowing us to choose a MENU from a SQL =20 > lookup and etc.) 5. Controlling a window size in the Mid-Tier (please > no Java) 6. Comparing a Date to a Date Time field 7. AR Admin Tool - > how about a progress meter when importing ? > 8. AR Admin Tool - Deleting forms with associations, once I select =20
> delete DELETE ? > 9. AR Admin Tool - minimize the tool during import and (Windows) and > =20=
> it takes the task > manager to restore the window ? > =A0 > =A0 > While I am all for the next latest and greatest, have any of these =20
> been fixed, repaired or etc. > =A0 > Anyone have anything to add to this list ?=A0 =A0 =A0 > > Regards=85Gidd > > =A0 > > Glidden L. Calden > BUOYANT SOLUTIONS, INC. > =A0 =93Keeping business afloat > =A0=A0=A0=A0=A0=A0 ..in a Sea of Solutions=94 > > =A0 > > =A0 > > Office=A0 =A0( 916.334.0599 > > Cell=A0=A0=A0=A0 =A0=A0( 916.761.3095 Web =A0=A0=A0 =A08 > =A0http://www.buoyantsolutions.net > E-mail=A0 =A0+ mailto:gidd@buoyantsolutions.net Fax=A0=A0=A0=A0=A0 > =A0=A0=FE =A0916.339.2915 > > =A0 > > This message and any attachments are intended only for the use of the > =20=
> addressee and may contain information that is privileged and =20 > confidential. If the reader of the message is not the intended =20 > recipient or an authorized representative of the intended recipient, > =20=
> you are hereby notified that any dissemination of this communication > =20=
> is strictly prohibited. If you have received this communication in =20
> error, please notify us immediately by e-mail and delete the message > =20=
> and any attachments from your system. > > =A0 > =A0 > =20 > = = 20=
> UNSUBSCRIBE or access ARSList Archives at =20 > http://www.ARSLIST.org (Support: mailto:support@arslist.org ) ARSList > =20=
> is hosted by QMX SUPPORT SERVICES at www.QMXS.com This posting was =20
> submitted via the Web interface =20 = = 20=
> UNSUBSCRIBE or access ARSList Archives at =20 > http://www.ARSLIST.org (Support: mailto:support@arslist.org ) ARSList =20=
> is hosted by QMX SUPPORT SERVICES at www.QMXS.com This posting was =20 > submitted via the Web interface=
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
1) Not to beat a dead horse - but the group list field in the user record. Causes me no end of problems.
2) Drag & Drop migration for workflow in the admin tool between servers. Wouldn't always want to use it, but when you have one or two filters to move...it would be nice.
3) More time in the day to do remedy development :)
Bill Estep
----------------------
http://www.clubreading.com
An online community for the avid book reader.
On Aug 10, 2004, at 12:39 PM, Gidd Calden wrote:
** ** =20
= ArialListers,
=A0
ArialWith Version 6.x=A0poised on the horizon I have to wonder
Arial about some annoyances still in the "core" application like:
=A0
Arial1. Checkboxes (don't get me started)
Arial2.=A0Delimiter for a Menu (when append menu selection allowed, i.e. a semicolon or = etc.)
Arial3. Control of an Integer field (i.e. do NOT roll down to -1, -2, etc.)
Arial4. MENU validation (i.e. allowing us to choose a MENU from a SQL lookup and = etc.)
Arial5. Controlling a window size in the Mid-Tier (please no Java)
Arial6. Comparing a Date to a Date Time field
Arial7. AR Admin Tool - how about a progress meter when importing ?
Arial8. AR Admin Tool - Deleting forms with associations, once I select delete DELETE = ?
Arial9. AR Admin Tool - minimize the tool during import and (Windows) and it takes the = task
Arial manager to restore the window ?
=A0
=A0
ArialWhile I am all for the next latest and greatest, have any of these been fixed, = repaired
Arialor etc.
Arial=A0
ArialAnyone have anything to add to this list ?=A0
Arial=A0
=A0
= Regards=85GiddAr ia= l =
Arial=A0
Glidden L. CaldenArial =
BUOYANT SOLUTIONS, INC.Arial =
=A0 =93Keeping business afloatArial
Arial =A0=A0=A0=A0=A0= =A0 ..in a Sea of Solutions=94Arial =
Arial=A0
Arial=A0
Office=A0=20 = Wingdings=A0L uc= ida Grande( = Arial916.334 .0= 599
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
Arial=A0
=A0
=
=
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 =
=
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=
--Apple-Mail-1-56725704--
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 email is intended only for the use of the individual or entity named above and may contain information that is confidential and privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. When addressed to our clients, any opinions or advice contained in this Email are subject to the terms and conditions expressed in the governing KPMG client engagement letter. If you have received this Email in error, please notify us immediately by return email or telephone +61 2 93357000 and destroy the original message. Thank You. **********************************************************************M
> 1) Not to beat a dead horse - but the group list field in the user > record. Causes me no end of problems. > 2) Drag & Drop migration for workflow in the admin tool between servers. > Wouldn't always want to use it, but when you have one or two filters to > move...it would be nice. > 3) More time in the day to do remedy development :)
4) How's about a native client for Linux, or a client written in Java?
I have a lot of non-Windows users here, and something like that would make my life a lot easier, since Mid Tier is somewhat fussy about browser types and Java installs, which makes Linux use rather problematic (having overly-fussy users doesn't help, though!).
-- Dr Dan Holdsworth Remedy ARS Administrator, Manchester Computing daniel.r.holdsworth@man.ac.uk 0161 275 0606
1. Too many copies of the same data. When will Remedy implement a healthy balance between a relational and copy model. There are situations where one is definitely a better choice over the other, so why not give the option? 2. When will login names be internally represented as a GUID so login names can be changed without requiring 4 trillion data elements to be updated (This in part goes back to my first annoyance) 3. Better db utilization. Throw the C programmers and dba's in the same room until they come up with a product that takes advantage of the features offered by each db. Much of this could even be done while staying inside the ANSI standards. (Again, this in part goes back to my first annoyance)
Kind Regards, Axton Grams New York Life Remedy Solutions Provider
With Version 6.x poised on the horizon I have to wonder about some annoyances still in the "core" application like:
1. Checkboxes (don't get me started) 2. Delimiter for a Menu (when append menu selection allowed, i.e. a semicolon or etc.) 3. Control of an Integer field (i.e. do NOT roll down to -1, -2, etc.) 4. MENU validation (i.e. allowing us to choose a MENU from a SQL lookup and etc.) 5. Controlling a window size in the Mid-Tier (please no Java) 6. Comparing a Date to a Date Time field 7. AR Admin Tool - how about a progress meter when importing ? 8. AR Admin Tool - Deleting forms with associations, once I select delete DELETE ? 9. AR Admin Tool - minimize the tool during import and (Windows) and it takes the task manager to restore the window ?
While I am all for the next latest and greatest, have any of these been fixed, repaired or etc.
Anyone have anything to add to this list ?
Regards?Gidd
Glidden L. Calden BUOYANT SOLUTIONS, INC. "Keeping business afloat ...in a Sea of Solutions"
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
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
The real reason to use a separate table to store state information (or similar static data) is to prevent users from making the following kinds of entries; VA, va, Va, vA, VG, VI, etc for Virginia. The problem isn't how often the states have changed its how many ways will a user enter the data. In the example above a search for all Virginia related items would be a nightmare. The trouble saved is well worth the 4 bytes.
Anthony O. Burkholder AOC Weapons System Database Administrator Dynamics Research Corporation (757) 225-7110 / DSN 575-7110 Email: anthony.burkholder@langley.af.mil SIPR Email: anthony.burkholder@c2fs.acc.af.smil.mil
-----Original Message----- From: Grooms, Frederick W [mailto:frederick.w.grooms@XO.COM] Sent: Tuesday, August 10, 2004 6:09 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
Of course this is not a problem when you have custom apps :)
You are correct on healthy balance. I have a couple of systems (not Remedy) that I have to pull data from that overkill on normalization. i.e. The state code in an address is in a separate table and all that is stored with the address is a pointer to the correct row in the master list. I mean how many times has the government changed the abbreviation for a state? Why waste 4 (or more) bytes of space for a 2 byte character?
Fred
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of Axton W Grams/NYLIC Sent: Tuesday, August 10, 2004 3:30 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
1. Too many copies of the same data. When will Remedy implement a healthy balance between a relational and copy model. There are situations where one is definitely a better choice over the other, so why not give the option? 2. When will login names be internally represented as a GUID so login names can be changed without requiring 4 trillion data elements to be updated. (This in part goes back to my first annoyance) 3. Better db utilization. Throw the C programmers and dba's in the same room until they come up with a product that takes advantage of the features offered by each db. Much of this could even be done while staying inside the ANSI standards. (Again, this in part goes back to my first annoyance)
Kind Regards, Axton Grams New York Life Remedy Solutions Provider
With Version 6.x poised on the horizon I have to wonder about some annoyances still in the "core" application like:
1. Checkboxes (don't get me started) 2. Delimiter for a Menu (when append menu selection allowed, i.e. a semicolon or etc.) 3. Control of an Integer field (i.e. do NOT roll down to -1, -2, etc.) 4. MENU validation (i.e. allowing us to choose a MENU from a SQL lookup and etc.) 5. Controlling a window size in the Mid-Tier (please no Java) 6. Comparing a Date to a Date Time field 7. AR Admin Tool - how about a progress meter when importing ? 8. AR Admin Tool - Deleting forms with associations, once I select delete DELETE ? 9. AR Admin Tool - minimize the tool during import and (Windows) and it takes the task manager to restore the window ?
While I am all for the next latest and greatest, have any of these been fixed, repaired or etc.
Anyone have anything to add to this list ?
Regards?Gidd
Glidden L. Calden BUOYANT SOLUTIONS, INC. "Keeping business afloat ...in a Sea of Solutions"
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
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
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
That might be the cause of a lot of issues. If we can somehow avoid having users that would solve most of my problems. Of course being without a job would be a minor setback :)
-----Original Message----- From: Action Request System discussion list(ARSList) [ mailto:ARSLIST@ARSLIST.ORG]On Behalf Of Dan Holdsworth Sent: 11 August 2004 10:48 To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
Bill Estep wrote:
> 1) Not to beat a dead horse - but the group list field in the user > record. Causes me no end of problems. > 2) Drag & Drop migration for workflow in the admin tool between servers. > Wouldn't always want to use it, but when you have one or two filters to > move...it would be nice. > 3) More time in the day to do remedy development :)
4) How's about a native client for Linux, or a client written in Java?
I have a lot of non-Windows users here, and something like that would make my life a lot easier, since Mid Tier is somewhat fussy about browser types and Java installs, which makes Linux use rather problematic (having overly-fussy users doesn't help, though!).
-- Dr Dan Holdsworth Remedy ARS Administrator, Manchester Computing daniel.r.holdsworth@man.ac.uk 0161 275 0606
How about making saved Diary field data available to workflow.
Dwayne Martin James Madison University
---- Original message ---- >Date: Tue, 10 Aug 2004 12:39:45 -0700 >From: Gidd Calden >Subject: OT:Remedy Annoyances >To: ARSLIST@ARSLIST.ORG > > ** ** > Listers, > > With Version 6.x poised on the horizon I have to > wonder > about some annoyances still in the "core" > application like: > > 1. Checkboxes (don't get me started) > 2. Delimiter for a Menu (when append menu selection > allowed, i.e. a semicolon or etc.) > 3. Control of an Integer field (i.e. do NOT roll > down to -1, -2, etc.) > 4. MENU validation (i.e. allowing us to choose a > MENU from a SQL lookup and etc.) > 5. Controlling a window size in the Mid-Tier (please > no Java) > 6. Comparing a Date to a Date Time field > 7. AR Admin Tool - how about a progress meter when > importing ? > 8. AR Admin Tool - Deleting forms with associations, > once I select delete DELETE ? > 9. AR Admin Tool - minimize the tool during import > and (Windows) and it takes the task > manager to restore the window ? > > > While I am all for the next latest and greatest, > have any of these been fixed, repaired > or etc. > > Anyone have anything to add to this list ? > > > > Regards...Gidd > > > > Glidden L. Calden > BUOYANT SOLUTIONS, INC. > “Keeping business afloat > ..in a Sea of Solutions” > > > > > > Office ( 916.334.0599 > > Cell ( 916.761.3095 > Web 8 http://www.buoyantsolutions.net > E-mail + mailto:gidd@buoyantsolutions.net > Fax ? 916.339.2915 > > > > This message and any attachments are intended only > for the use of the addressee and may contain > information that is privileged and confidential. If > the reader of the message is not the intended > recipient or an authorized representative of the > intended recipient, you are hereby notified that any > dissemination of this communication is strictly > prohibited. If you have received this communication > in error, please notify us immediately by e-mail and > delete the message and any attachments from your > system. > > > > >
> 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 >
> 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
Dwayne Martin Computing Support James Madison University
My vote goes to having the "Else" tab in active links/filter setup be a different color if there actually *is* an else action.
How often have you done a "save as" because the bit of workflow was *almost* what you wanted and then changed it and several weeks and strange effects later realised the copy had an "Else" attached which you forgot to check for :-)
And I am pretty sure I put it in as an enhancement yonks ago.
My vote goes to having the "Else" tab in active links/filter setup be a different color if there actually *is* an else action.
How often have you done a "save as" because the bit of workflow was *almost* what you wanted and then changed it and several weeks and strange effects later realised the copy had an "Else" attached which you forgot to check for :-)
And I am pretty sure I put it in as an enhancement yonks ago.
-- Regards
Dave Saville
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
6.00.01 has the number of actions listed on each tab so you can tell quickly if you have an if action.
>>> dave@DEEZEE.ORG Aug 11, 2004 5:57:56 AM >>> My vote goes to having the "Else" tab in active links/filter setup be a different color if there actually *is* an else action.
How often have you done a "save as" because the bit of workflow was *almost* what you wanted and then changed it and several weeks and strange effects later realised the copy had an "Else" attached which you forgot to check for :-)
And I am pretty sure I put it in as an enhancement yonks ago.
-- Regards
Dave Saville
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
Why not set the field to be call caps, then all you have to worry about is typos. Shelia
-----Original Message----- From: Burkholder Anthony O Contr 83 CS/SCZA [ mailto:Anthony.Burkholder@LANGLEY.AF.MIL] Sent: Wednesday, August 11, 2004 5:49 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
My 2 cents,
The real reason to use a separate table to store state information (or similar static data) is to prevent users from making the following kinds of entries; VA, va, Va, vA, VG, VI, etc for Virginia. The problem isn't how often the states have changed its how many ways will a user enter the data. In the example above a search for all Virginia related items would be a nightmare. The trouble saved is well worth the 4 bytes.
Anthony O. Burkholder AOC Weapons System Database Administrator Dynamics Research Corporation (757) 225-7110 / DSN 575-7110 Email: anthony.burkholder@langley.af.mil SIPR Email: anthony.burkholder@c2fs.acc.af.smil.mil
-----Original Message----- From: Grooms, Frederick W [ mailto:frederick.w.grooms@XO.COM] Sent: Tuesday, August 10, 2004 6:09 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
Of course this is not a problem when you have custom apps :)
You are correct on healthy balance. I have a couple of systems (not Remedy) that I have to pull data from that overkill on normalization. i.e. The state code in an address is in a separate table and all that is stored with the address is a pointer to the correct row in the master list. I mean how many times has the government changed the abbreviation for a state? Why waste 4 (or more) bytes of space for a 2 byte character?
Fred
-----Original Message----- From: Action Request System discussion list(ARSList) [ mailto:ARSLIST@ARSLIST.ORG] On Behalf Of Axton W Grams/NYLIC Sent: Tuesday, August 10, 2004 3:30 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
1. Too many copies of the same data. When will Remedy implement a healthy balance between a relational and copy model. There are situations where one is definitely a better choice over the other, so why not give the option? 2. When will login names be internally represented as a GUID so login names can be changed without requiring 4 trillion data elements to be updated. (This in part goes back to my first annoyance) 3. Better db utilization. Throw the C programmers and dba's in the same room until they come up with a product that takes advantage of the features offered by each db. Much of this could even be done while staying inside the ANSI standards. (Again, this in part goes back to my first annoyance)
Kind Regards, Axton Grams New York Life Remedy Solutions Provider
With Version 6.x poised on the horizon I have to wonder about some annoyances still in the "core" application like:
1. Checkboxes (don't get me started) 2. Delimiter for a Menu (when append menu selection allowed, i.e. a semicolon or etc.) 3. Control of an Integer field (i.e. do NOT roll down to -1, -2, etc.) 4. MENU validation (i.e. allowing us to choose a MENU from a SQL lookup and etc.) 5. Controlling a window size in the Mid-Tier (please no Java) 6. Comparing a Date to a Date Time field 7. AR Admin Tool - how about a progress meter when importing ? 8. AR Admin Tool - Deleting forms with associations, once I select delete DELETE ? 9. AR Admin Tool - minimize the tool during import and (Windows) and it takes the task manager to restore the window ?
While I am all for the next latest and greatest, have any of these been fixed, repaired or etc.
Anyone have anything to add to this list ?
Regards?Gidd
Glidden L. Calden BUOYANT SOLUTIONS, INC. "Keeping business afloat ...in a Sea of Solutions"
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
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
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
** Actually I validate with a $MENU$ check. I just don't store the record ID of the validation record in my address, I keep the real state code. Fred
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of Palermo, Shelia D ERDC-ITL-MS Contractor Sent: Wednesday, August 11, 2004 8:29 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
**
Why not set the field to be call caps, then all you have to worry about is typos. Shelia
-----Original Message----- From: Burkholder Anthony O Contr 83 CS/SCZA [ mailto:Anthony.Burkholder@LANGLEY.AF.MIL] Sent: Wednesday, August 11, 2004 5:49 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
My 2 cents,
The real reason to use a separate table to store state information (or similar static data) is to prevent users from making the following kinds of entries; VA, va, Va, vA, VG, VI, etc for Virginia. The problem isn't how often the states have changed its how many ways will a user enter the data. In the example above a search for all Virginia related items would be a nightmare. The trouble saved is well worth the 4 bytes.
Anthony O. Burkholder AOC Weapons System Database Administrator Dynamics Research Corporation (757) 225-7110 / DSN 575-7110 Email: anthony.burkholder@langley.af.mil SIPR Email: anthony.burkholder@c2fs.acc.af.smil.mil
-----Original Message----- From: Grooms, Frederick W [ mailto:frederick.w.grooms@XO.COM] Sent: Tuesday, August 10, 2004 6:09 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
Of course this is not a problem when you have custom apps :)
You are correct on healthy balance. I have a couple of systems (not Remedy) that I have to pull data from that overkill on normalization. i.e. The state code in an address is in a separate table and all that is stored with the address is a pointer to the correct row in the master list. I mean how many times has the government changed the abbreviation for a state? Why waste 4 (or more) bytes of space for a 2 byte character?
Fred
-----Original Message----- From: Action Request System discussion list(ARSList) [ mailto:ARSLIST@ARSLIST.ORG] On Behalf Of Axton W Grams/NYLIC Sent: Tuesday, August 10, 2004 3:30 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
1. Too many copies of the same data. When will Remedy implement a healthy balance between a relational and copy model. There are situations where one is definitely a better choice over the other, so why not give the option? 2. When will login names be internally represented as a GUID so login names can be changed without requiring 4 trillion data elements to be updated. (This in part goes back to my first annoyance) 3. Better db utilization. Throw the C programmers and dba's in the same room until they come up with a product that takes advantage of the features offered by each db. Much of this could even be done while staying inside the ANSI standards. (Again, this in part goes back to my first annoyance)
Kind Regards, Axton Grams New York Life Remedy Solutions Provider
With Version 6.x poised on the horizon I have to wonder about some annoyances still in the "core" application like:
1. Checkboxes (don't get me started) 2. Delimiter for a Menu (when append menu selection allowed, i.e. a semicolon or etc.) 3. Control of an Integer field (i.e. do NOT roll down to -1, -2, etc.) 4. MENU validation (i.e. allowing us to choose a MENU from a SQL lookup and etc.) 5. Controlling a window size in the Mid-Tier (please no Java) 6. Comparing a Date to a Date Time field 7. AR Admin Tool - how about a progress meter when importing ? 8. AR Admin Tool - Deleting forms with associations, once I select delete DELETE ? 9. AR Admin Tool - minimize the tool during import and (Windows) and it takes the task manager to restore the window ?
While I am all for the next latest and greatest, have any of these been fixed, repaired or etc.
Anyone have anything to add to this list ?
Regards?Gidd
Glidden L. Calden BUOYANT SOLUTIONS, INC. "Keeping business afloat ...in a Sea of Solutions"
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
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
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
And if you're using a search menu validating via $MENU$ you have eratic results ... sometimes it will do it ... sometimes not. And when NOT you have to build a series of 3 filters to accomplish what the $MENU$ is supposed to do. For instance with CTI or State/Prov dependent on Country.
And I have a very simple request, filed as an enhancement request years ago and brought up at each RUG Engineering night. On the Reports screen, let us make the columns the width we want and have it REMEMBER it like it does on other forms.
I also want the enlarged Advanced search bar or an expand button.
Why can't you open the Run If on two pieces of workflow at the same time?
I want an audit field as part of the core fields.
I know I want more things ..... lol
Susan
--- "Grooms, Frederick W" wrote:
> Actually I validate with a $MENU$ check. I just > don't store the record ID of the validation record > in my address, I keep the real state code. > Fred > > -----Original Message----- > From: Action Request System discussion > list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] On Behalf > Of Palermo, Shelia D ERDC-ITL-MS Contractor > Sent: Wednesday, August 11, 2004 8:29 AM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > > ** > > Why not set the field to be call caps, then > all you have to worry about is typos. > Shelia > > > -----Original Message----- > From: Burkholder Anthony O Contr 83 CS/SCZA > [mailto:Anthony.Burkholder@LANGLEY.AF.MIL] > Sent: Wednesday, August 11, 2004 5:49 AM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > > My 2 cents, > > The real reason to use a separate table to > store state information (or > similar static data) is to prevent users > from making the following kinds of > entries; VA, va, Va, vA, VG, VI, etc for > Virginia. The problem isn't how > often the states have changed its how many > ways will a user enter the data. > In the example above a search for all > Virginia related items would be a > nightmare. The trouble saved is well worth > the 4 bytes. > > > Anthony O. Burkholder > AOC Weapons System Database Administrator > Dynamics Research Corporation > (757) 225-7110 / DSN 575-7110 > Email: anthony.burkholder@langley.af.mil > SIPR Email: > anthony.burkholder@c2fs.acc.af.smil.mil > > > -----Original Message----- > From: Grooms, Frederick W > [mailto:frederick.w.grooms@XO.COM] > Sent: Tuesday, August 10, 2004 6:09 PM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > Of course this is not a problem when you > have custom apps :) > > You are correct on healthy balance. I have > a couple of systems (not Remedy) > that I have to pull data from that overkill > on normalization. i.e. The > state code in an address is in a separate > table and all that is stored with > the address is a pointer to the correct row > in the master list. I mean how > many times has the government changed the > abbreviation for a state? Why > waste 4 (or more) bytes of space for a 2 > byte character? > > Fred > > -----Original Message----- > From: Action Request System discussion > list(ARSList) > [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of > Axton W Grams/NYLIC > Sent: Tuesday, August 10, 2004 3:30 PM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > > 1. Too many copies of the same data. When > will Remedy implement a healthy > balance between a relational and copy model. > There are situations where one > is definitely a better choice over the > other, so why not give the option? 2. > When will login names be internally > represented as a GUID so login names can > be changed without requiring 4 trillion data > elements to be updated. (This > in part goes back to my first annoyance) 3. > Better db utilization. Throw > the C programmers and dba's in the same room > until they come up with a > product that takes advantage of the features > offered by each db. Much of > this could even be done while staying inside > the ANSI standards. (Again, > this in part goes back to my first > annoyance) > > > Kind Regards, > Axton Grams > New York Life > Remedy Solutions > Provider > > Mobile: 404.861.7273 > Work: 770.406.4415 > Email: > AxtonWGrams@NewYorkLife.com > > > > > > > |---------+----------------------------> > | | Gidd Calden | > | | > | | TIONS.NET> | > | | Sent by: "Action | > | | Request System | > | | discussion | > | | list(ARSList)" | > | | > | | ORG> | > | | | > | | | > | | 08/10/2004 03:39 | > | | PM | > | | Please respond to| > | | arslist | > | | | > |---------+----------------------------> > > > >--------------------------------------------------------------------------- > > > ---------------------------------------------------| > > | > | > | To: ARSLIST@ARSLIST.ORG > | > | cc: > | > | Subject: OT:Remedy Annoyances > | > > > >--------------------------------------------------------------------------- > > > ---------------------------------------------------| > > > > > > ** > Listers, > > With Version 6.x poised on the horizon I > have to wonder > about some annoyances still in the "core" > application like: > > 1. Checkboxes (don't get me started) > 2. Delimiter for a Menu (when append menu > selection allowed, i.e. a > semicolon or etc.) 3. Control of an Integer > field (i.e. do NOT roll down to > -1, -2, etc.) 4. MENU validation (i.e. > allowing us to choose a MENU from a > SQL lookup and > etc.) > 5. Controlling a window size in the Mid-Tier > (please no Java) 6. Comparing a > Date to a Date Time field 7. AR Admin Tool - > how about a progress meter when > importing ? 8. AR Admin Tool - Deleting > forms with associations, once I > select delete DELETE ? 9. AR Admin Tool - > minimize the tool during import > and (Windows) and it takes the task manager > to restore the window ? > > > While I am all for the next latest and > greatest, have any of these been > fixed, repaired or etc. > > Anyone have anything to add to this list ? > > > > > Regards?Gidd > > > > > > Glidden L. Calden > BUOYANT SOLUTIONS, INC. > "Keeping business afloat > ...in a Sea of Solutions" > > > > > > > > > Office ( 916.334.0599 > > > Cell ( 916.761.3095 > Web 8 http://www.buoyantsolutions.net > E-mail + mailto:gidd@buoyantsolutions.net > Fax ? 916.339.2915 > > > > > > This message and any attachments are > intended only for the use of the > addressee and may contain information that > is privileged and confidential. > If the reader of the message is not the > intended recipient or an authorized > representative of the intended recipient, > you are hereby notified that any > dissemination of this communication is > strictly prohibited. If you have > received this communication in error, please > notify us immediately by e-mail > and delete the message and any attachments > from your system. > > > > > > > >
> > > 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 > > > > >
> > > 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 This posting > was submitted via the Web interface > > >
> 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 >
Or create a charmeny, with $MENU$ as pattern. But ..likely not the best solution if You often have to make changes to the list, add, delete entries, then a regular form with filtervalidating the data should be a better alternative, changes can be handled within the usertool. I try to avoid using hardcoded charmenues for that reson.
L ars
-----Ursprungligt meddelande----- Fran: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG]For Palermo, Shelia D ERDC-ITL-MS Contractor Skickat: den 11 augusti 2004 15:29 Till: ARSLIST@ARSLIST.ORG Amne: Re: OT:Remedy Annoyances
Why not set the field to be call caps, then all you have to worry about is typos. Shelia
-----Original Message----- From: Burkholder Anthony O Contr 83 CS/SCZA [ mailto:Anthony.Burkholder@LANGLEY.AF.MIL] Sent: Wednesday, August 11, 2004 5:49 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
My 2 cents,
The real reason to use a separate table to store state information (or similar static data) is to prevent users from making the following kinds of entries; VA, va, Va, vA, VG, VI, etc for Virginia. The problem isn't how often the states have changed its how many ways will a user enter the data. In the example above a search for all Virginia related items would be a nightmare. The trouble saved is well worth the 4 bytes.
Anthony O. Burkholder AOC Weapons System Database Administrator Dynamics Research Corporation (757) 225-7110 / DSN 575-7110 Email: anthony.burkholder@langley.af.mil SIPR Email: anthony.burkholder@c2fs.acc.af.smil.mil
-----Original Message----- From: Grooms, Frederick W [ mailto:frederick.w.grooms@XO.COM] Sent: Tuesday, August 10, 2004 6:09 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
Of course this is not a problem when you have custom apps :)
You are correct on healthy balance. I have a couple of systems (not Remedy) that I have to pull data from that overkill on normalization. i.e. The state code in an address is in a separate table and all that is stored with the address is a pointer to the correct row in the master list. I mean how many times has the government changed the abbreviation for a state? Why waste 4 (or more) bytes of space for a 2 byte character?
Fred
-----Original Message-----
From: Action Request System discussion list(ARSList)
99% of all my menus are Search menus. As long as the values in the menu do not rely on any other fields on the form the $MENU$ works. If they do rely on other fields then I use a 2 filter method of validating.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of lars.j.pettersson@VATTENFALL.COM Sent: Wednesday, August 11, 2004 9:23 AM To: ARSLIST@ARSLIST.ORG Subject: SV: OT:Remedy Annoyances
**
Or create a charmeny, with $MENU$ as pattern. But ..likely not the best solution if You often have to make changes to the list, add, delete entries, then a regular form with filtervalidating the data should be a better alternative, changes can be handled within the usertool. I try to avoid using hardcoded charmenues for that reson.
L ars
-----Ursprungligt meddelande----- Fran: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG]For Palermo, Shelia D ERDC-ITL-MS Contractor Skickat: den 11 augusti 2004 15:29 Till: ARSLIST@ARSLIST.ORG Amne: Re: OT:Remedy Annoyances
Why not set the field to be call caps, then all you have to worry about is typos. Shelia
-----Original Message----- From: Burkholder Anthony O Contr 83 CS/SCZA [ mailto:Anthony.Burkholder@LANGLEY.AF.MIL] Sent: Wednesday, August 11, 2004 5:49 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
My 2 cents,
The real reason to use a separate table to store state information (or similar static data) is to prevent users from making the following kinds of entries; VA, va, Va, vA, VG, VI, etc for Virginia. The problem isn't how often the states have changed its how many ways will a user enter the data. In the example above a search for all Virginia related items would be a nightmare. The trouble saved is well worth the 4 bytes.
Anthony O. Burkholder AOC Weapons System Database Administrator Dynamics Research Corporation (757) 225-7110 / DSN 575-7110 Email: anthony.burkholder@langley.af.mil SIPR Email: anthony.burkholder@c2fs.acc.af.smil.mil
-----Original Message----- From: Grooms, Frederick W [ mailto:frederick.w.grooms@XO.COM] Sent: Tuesday, August 10, 2004 6:09 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
Of course this is not a problem when you have custom apps :)
You are correct on healthy balance. I have a couple of systems (not Remedy) that I have to pull data from that overkill on normalization. i.e. The state code in an address is in a separate table and all that is stored with the address is a pointer to the correct row in the master list. I mean how many times has the government changed the abbreviation for a state? Why waste 4 (or more) bytes of space for a 2 byte character?
Fred
-----Original Message-----
From: Action Request System discussion list(ARSList)
Frederick, seemes that we have designed the system in the same way. My dream is that user not are allows to write in fields with a menu attached if I have set a 'flag for this', sometimes free text can be useful, and the menu is just basevalues. But often we just want to accept the menuvalues, would skip 2 filters, hope Remedy will do something in coming versons.
L ars
-----Ursprungligt meddelande----- Fran: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG]For Grooms, Frederick W Skickat: den 11 augusti 2004 17:15 Till: ARSLIST@ARSLIST.ORG Amne: Re: OT:Remedy Annoyances
99% of all my menus are Search menus. As long as the values in the menu do not rely on any other fields on the form the $MENU$ works. If they do rely on other fields then I use a 2 filter method of validating.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of lars.j.pettersson@VATTENFALL.COM Sent: Wednesday, August 11, 2004 9:23 AM To: ARSLIST@ARSLIST.ORG Subject: SV: OT:Remedy Annoyances
**
Or create a charmeny, with $MENU$ as pattern. But ..likely not the best solution if You often have to make changes to the list, add, delete entries, then a regular form with filtervalidating the data should be a better alternative, changes can be handled within the usertool. I try to avoid using hardcoded charmenues for that reson.
L ars
-----Ursprungligt meddelande----- Fran: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG]For Palermo, Shelia D ERDC-ITL-MS Contractor Skickat: den 11 augusti 2004 15:29 Till: ARSLIST@ARSLIST.ORG Amne: Re: OT:Remedy Annoyances
Why not set the field to be call caps, then all you have to worry about is typos. Shelia
-----Original Message----- From: Burkholder Anthony O Contr 83 CS/SCZA [ mailto:Anthony.Burkholder@LANGLEY.AF.MIL] Sent: Wednesday, August 11, 2004 5:49 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
My 2 cents,
The real reason to use a separate table to store state information (or similar static data) is to prevent users from making the following kinds of entries; VA, va, Va, vA, VG, VI, etc for Virginia. The problem isn't how often the states have changed its how many ways will a user enter the data. In the example above a search for all Virginia related items would be a nightmare. The trouble saved is well worth the 4 bytes.
Anthony O. Burkholder AOC Weapons System Database Administrator Dynamics Research Corporation (757) 225-7110 / DSN 575-7110 Email: anthony.burkholder@langley.af.mil SIPR Email: anthony.burkholder@c2fs.acc.af.smil.mil
-----Original Message----- From: Grooms, Frederick W [ mailto:frederick.w.grooms@XO.COM] Sent: Tuesday, August 10, 2004 6:09 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
Of course this is not a problem when you have custom apps :)
You are correct on healthy balance. I have a couple of systems (not Remedy) that I have to pull data from that overkill on normalization. i.e. The state code in an address is in a separate table and all that is stored with the address is a pointer to the correct row in the master list. I mean how many times has the government changed the abbreviation for a state? Why waste 4 (or more) bytes of space for a 2 byte character?
Fred
-----Original Message-----
From: Action Request System discussion list(ARSList)
Yes...agree..."I also want the enlarged Advanced search bar or an expand button" Long data on ASB now is difficult to edit. Have sent an enh reg about this. And also ..if many windows are open for one form, You can only se Form, form, form ...I would like to select one field/form as 'show in windowmode',
Requestid, name or so, much more easy for users with many open windows to navigate to the right window
Form - Smith Jones Form - Mueller Carla
Many of 'my users' complain about this issue, should be rather easy fo Remedy to implement this.
L ars
-----Ursprungligt meddelande----- Fran: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG]For Susan Palmer Skickat: den 11 augusti 2004 16:47 Till: ARSLIST@ARSLIST.ORG Amne: Re: OT:Remedy Annoyances
And if you're using a search menu validating via $MENU$ you have eratic results ... sometimes it will do it ... sometimes not. And when NOT you have to build a series of 3 filters to accomplish what the $MENU$ is supposed to do. For instance with CTI or State/Prov dependent on Country.
And I have a very simple request, filed as an enhancement request years ago and brought up at each RUG Engineering night. On the Reports screen, let us make the columns the width we want and have it REMEMBER it like it does on other forms.
I also want the enlarged Advanced search bar or an expand button.
Why can't you open the Run If on two pieces of workflow at the same time?
I want an audit field as part of the core fields.
I know I want more things ..... lol
Susan
--- "Grooms, Frederick W" wrote:
> Actually I validate with a $MENU$ check. I just > don't store the record ID of the validation record > in my address, I keep the real state code. > Fred > > -----Original Message----- > From: Action Request System discussion > list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] On Behalf > Of Palermo, Shelia D ERDC-ITL-MS Contractor > Sent: Wednesday, August 11, 2004 8:29 AM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > > ** > > Why not set the field to be call caps, then > all you have to worry about is typos. > Shelia > > > -----Original Message----- > From: Burkholder Anthony O Contr 83 CS/SCZA > [mailto:Anthony.Burkholder@LANGLEY.AF.MIL] > Sent: Wednesday, August 11, 2004 5:49 AM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > > My 2 cents, > > The real reason to use a separate table to > store state information (or > similar static data) is to prevent users > from making the following kinds of > entries; VA, va, Va, vA, VG, VI, etc for > Virginia. The problem isn't how > often the states have changed its how many > ways will a user enter the data. > In the example above a search for all > Virginia related items would be a > nightmare. The trouble saved is well worth > the 4 bytes. > > > Anthony O. Burkholder > AOC Weapons System Database Administrator > Dynamics Research Corporation > (757) 225-7110 / DSN 575-7110 > Email: anthony.burkholder@langley.af.mil > SIPR Email: > anthony.burkholder@c2fs.acc.af.smil.mil > > > -----Original Message----- > From: Grooms, Frederick W > [mailto:frederick.w.grooms@XO.COM] > Sent: Tuesday, August 10, 2004 6:09 PM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > Of course this is not a problem when you > have custom apps :) > > You are correct on healthy balance. I have > a couple of systems (not Remedy) > that I have to pull data from that overkill > on normalization. i.e. The > state code in an address is in a separate > table and all that is stored with > the address is a pointer to the correct row > in the master list. I mean how > many times has the government changed the > abbreviation for a state? Why > waste 4 (or more) bytes of space for a 2 > byte character? > > Fred > > -----Original Message----- > From: Action Request System discussion > list(ARSList) > [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of > Axton W Grams/NYLIC > Sent: Tuesday, August 10, 2004 3:30 PM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > > 1. Too many copies of the same data. When > will Remedy implement a healthy > balance between a relational and copy model. > There are situations where one > is definitely a better choice over the > other, so why not give the option? 2. > When will login names be internally > represented as a GUID so login names can > be changed without requiring 4 trillion data > elements to be updated. (This > in part goes back to my first annoyance) 3. > Better db utilization. Throw > the C programmers and dba's in the same room > until they come up with a > product that takes advantage of the features > offered by each db. Much of > this could even be done while staying inside > the ANSI standards. (Again, > this in part goes back to my first > annoyance) > > > Kind Regards, > Axton Grams > New York Life > Remedy Solutions > Provider > > Mobile: 404.861.7273 > Work: 770.406.4415 > Email: > AxtonWGrams@NewYorkLife.com > > > > > > > |---------+----------------------------> > | | Gidd Calden | > | | > | | TIONS.NET> | > | | Sent by: "Action | > | | Request System | > | | discussion | > | | list(ARSList)" | > | | > | | ORG> | > | | | > | | | > | | 08/10/2004 03:39 | > | | PM | > | | Please respond to| > | | arslist | > | | | > |---------+----------------------------> > > > >--------------------------------------------------------------------------- > > > ---------------------------------------------------| > > | > | > | To: ARSLIST@ARSLIST.ORG > | > | cc: > | > | Subject: OT:Remedy Annoyances > | > > > >--------------------------------------------------------------------------- > > > ---------------------------------------------------| > > > > > > ** > Listers, > > With Version 6.x poised on the horizon I > have to wonder > about some annoyances still in the "core" > application like: > > 1. Checkboxes (don't get me started) > 2. Delimiter for a Menu (when append menu > selection allowed, i.e. a > semicolon or etc.) 3. Control of an Integer > field (i.e. do NOT roll down to > -1, -2, etc.) 4. MENU validation (i.e. > allowing us to choose a MENU from a > SQL lookup and > etc.) > 5. Controlling a window size in the Mid-Tier > (please no Java) 6. Comparing a > Date to a Date Time field 7. AR Admin Tool - > how about a progress meter when > importing ? 8. AR Admin Tool - Deleting > forms with associations, once I > select delete DELETE ? 9. AR Admin Tool - > minimize the tool during import > and (Windows) and it takes the task manager > to restore the window ? > > > While I am all for the next latest and > greatest, have any of these been > fixed, repaired or etc. > > Anyone have anything to add to this list ? > > > > > Regards?Gidd > > > > > > Glidden L. Calden > BUOYANT SOLUTIONS, INC. > "Keeping business afloat > ...in a Sea of Solutions" > > > > > > > > > Office ( 916.334.0599 > > > Cell ( 916.761.3095 > Web 8 http://www.buoyantsolutions.net > E-mail + mailto:gidd@buoyantsolutions.net > Fax ? 916.339.2915 > > > > > > This message and any attachments are > intended only for the use of the > addressee and may contain information that > is privileged and confidential. > If the reader of the message is not the > intended recipient or an authorized > representative of the intended recipient, > you are hereby notified that any > dissemination of this communication is > strictly prohibited. If you have > received this communication in error, please > notify us immediately by e-mail > and delete the message and any attachments > from your system. > > > > > > > >
> > > 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 > > > > >
> > > 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 This posting > was submitted via the Web interface > > >
> 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 >
Does that same feature apply to search menus that are dependent on the previous choice, like CTI.
Thanks, Susan
--- "Watson, Matthew (Melbourne)" wrote:
> Lars, > > In version 6, you can make character fields with > menus attached to them display like a drop down list > - the end user cannot type anything into the field > and is forced to choose something from the menu. > > It is a really nice enhancement that's been a long > time coming. You can still have the option of having > the menu attached as per normal so that the user can > type into the field if they want, it's just a simple > flag that gets changed in the field properties to > control how it displays. > > Cheers, > Matt > > -----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 3:54 AM > To: ARSLIST@ARSLIST.ORG > Subject: SV: OT:Remedy Annoyances > > Frederick, seemes that we have designed the system > in the same way. My dream is that user not are > allows to write in fields with a menu attached if I > have set a 'flag for this', sometimes free text can > be useful, and the menu is just basevalues. But > often we just want to accept the menuvalues, would > skip 2 filters, hope Remedy will do something in > coming versons. > > L ars > > -----Ursprungligt meddelande----- > Fran: Action Request System discussion list(ARSList) > [mailto:ARSLIST@ARSLIST.ORG]For Grooms, Frederick W > Skickat: den 11 augusti 2004 17:15 > Till: ARSLIST@ARSLIST.ORG > Amne: Re: OT:Remedy Annoyances > > > 99% of all my menus are Search menus. As long as > the values in the menu do not rely on any other > fields on the form the $MENU$ works. If they do > rely on other fields then I use a 2 filter method of > validating. > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of > lars.j.pettersson@VATTENFALL.COM > Sent: Wednesday, August 11, 2004 9:23 AM > To: ARSLIST@ARSLIST.ORG > Subject: SV: OT:Remedy Annoyances > > > ** > > Or create a charmeny, with $MENU$ as pattern. But > ..likely not the best solution if You often have to > make changes to the list, add, delete entries, then > a regular form with filtervalidating the data should > be a better alternative, changes can be handled > within the usertool. I try to avoid using hardcoded > charmenues for that reson. > > > > L ars > > > > -----Ursprungligt meddelande----- > Fran: Action Request System discussion list(ARSList) > [mailto:ARSLIST@ARSLIST.ORG]For Palermo, Shelia D > ERDC-ITL-MS Contractor > Skickat: den 11 augusti 2004 15:29 > Till: ARSLIST@ARSLIST.ORG > Amne: Re: OT:Remedy Annoyances > > > > Why not set the field to be call caps, then all you > have to worry about is typos. > Shelia > > > > -----Original Message----- > From: Burkholder Anthony O Contr 83 CS/SCZA [ > > mailto:Anthony.Burkholder@LANGLEY.AF.MIL] > Sent: Wednesday, August 11, 2004 5:49 AM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > > > My 2 cents, > > The real reason to use a separate table to store > state information (or similar static data) is to > prevent users from making the following kinds of > entries; VA, va, Va, vA, VG, VI, etc for Virginia. > The problem isn't how often the states have changed > its how many ways will a user enter the data. > In the example above a search for all Virginia > related items would be a nightmare. The trouble > saved is well worth the 4 bytes. > > > > Anthony O. Burkholder > AOC Weapons System Database Administrator > Dynamics Research Corporation > (757) 225-7110 / DSN 575-7110 > Email: anthony.burkholder@langley.af.mil > SIPR Email: anthony.burkholder@c2fs.acc.af.smil.mil > > > > > -----Original Message----- > From: Grooms, Frederick W [ > > mailto:frederick.w.grooms@XO.COM] > Sent: Tuesday, August 10, 2004 6:09 PM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > Of course this is not a problem when you have custom > apps :) > > You are correct on healthy balance. I have a couple > of systems (not Remedy) > that I have to pull data from that overkill on > normalization. i.e. The > state code in an address is in a separate table and > all that is stored with the address is a pointer to > the correct row in the master list. I mean how > many times has the government changed the > abbreviation for a state? Why > waste 4 (or more) bytes of space for a 2 byte > character? > > Fred > > -----Original Message----- > >
> 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 > From: Action Request System discussion list(ARSList) > > >
> 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 email is intended only for the use of the > individual or entity > named above and may contain information that is > confidential and > privileged. If you are not the intended recipient, > you are hereby notified that any dissemination, > distribution or copying of this Email is strictly > prohibited. When addressed to our clients, any > opinions or advice contained in this Email are > subject to the terms and conditions expressed in the > governing KPMG client engagement letter. If you have > received this Email in error, please notify us > immediately by return email or telephone +61 2 > 93357000 and destroy the original message. Thank > You. > **********************************************************************M > >
> 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 >
In version 6, you can make character fields with menus attached to them display like a drop down list - the end user cannot type anything into the field and is forced to choose something from the menu.
It is a really nice enhancement that's been a long time coming. You can still have the option of having the menu attached as per normal so that the user can type into the field if they want, it's just a simple flag that gets changed in the field properties to control how it displays.
Cheers, Matt
-----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 3:54 AM To: ARSLIST@ARSLIST.ORG Subject: SV: OT:Remedy Annoyances
Frederick, seemes that we have designed the system in the same way. My dream is that user not are allows to write in fields with a menu attached if I have set a 'flag for this', sometimes free text can be useful, and the menu is just basevalues. But often we just want to accept the menuvalues, would skip 2 filters, hope Remedy will do something in coming versons.
L ars
-----Ursprungligt meddelande----- Fran: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG]For Grooms, Frederick W Skickat: den 11 augusti 2004 17:15 Till: ARSLIST@ARSLIST.ORG Amne: Re: OT:Remedy Annoyances
99% of all my menus are Search menus. As long as the values in the menu do not rely on any other fields on the form the $MENU$ works. If they do rely on other fields then I use a 2 filter method of validating.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of lars.j.pettersson@VATTENFALL.COM Sent: Wednesday, August 11, 2004 9:23 AM To: ARSLIST@ARSLIST.ORG Subject: SV: OT:Remedy Annoyances
**
Or create a charmeny, with $MENU$ as pattern. But ..likely not the best solution if You often have to make changes to the list, add, delete entries, then a regular form with filtervalidating the data should be a better alternative, changes can be handled within the usertool. I try to avoid using hardcoded charmenues for that reson.
L ars
-----Ursprungligt meddelande----- Fran: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG]For Palermo, Shelia D ERDC-ITL-MS Contractor Skickat: den 11 augusti 2004 15:29 Till: ARSLIST@ARSLIST.ORG Amne: Re: OT:Remedy Annoyances
Why not set the field to be call caps, then all you have to worry about is typos. Shelia
-----Original Message----- From: Burkholder Anthony O Contr 83 CS/SCZA [ mailto:Anthony.Burkholder@LANGLEY.AF.MIL] Sent: Wednesday, August 11, 2004 5:49 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
My 2 cents,
The real reason to use a separate table to store state information (or similar static data) is to prevent users from making the following kinds of entries; VA, va, Va, vA, VG, VI, etc for Virginia. The problem isn't how often the states have changed its how many ways will a user enter the data. In the example above a search for all Virginia related items would be a nightmare. The trouble saved is well worth the 4 bytes.
Anthony O. Burkholder AOC Weapons System Database Administrator Dynamics Research Corporation (757) 225-7110 / DSN 575-7110 Email: anthony.burkholder@langley.af.mil SIPR Email: anthony.burkholder@c2fs.acc.af.smil.mil
-----Original Message----- From: Grooms, Frederick W [ mailto:frederick.w.grooms@XO.COM] Sent: Tuesday, August 10, 2004 6:09 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
Of course this is not a problem when you have custom apps :)
You are correct on healthy balance. I have a couple of systems (not Remedy) that I have to pull data from that overkill on normalization. i.e. The state code in an address is in a separate table and all that is stored with the address is a pointer to the correct row in the master list. I mean how many times has the government changed the abbreviation for a state? Why waste 4 (or more) bytes of space for a 2 byte character?
Fred
-----Original Message-----
From: Action Request System discussion list(ARSList)
********************************************************************** This email is intended only for the use of the individual or entity named above and may contain information that is confidential and privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. When addressed to our clients, any opinions or advice contained in this Email are subject to the terms and conditions expressed in the governing KPMG client engagement letter. If you have received this Email in error, please notify us immediately by return email or telephone +61 2 93357000 and destroy the original message. Thank You. **********************************************************************M
Any search menu. The behavior is a little different on the web though (floating values as opposed to the drop down feel), and the arrows look a little different; but the feature is nice.
Axton
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of Susan Palmer Sent: Wednesday, August 11, 2004 6:39 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
Matthew ...
Does that same feature apply to search menus that are dependent on the previous choice, like CTI.
Thanks, Susan
--- "Watson, Matthew (Melbourne)" wrote:
> Lars, > > In version 6, you can make character fields with > menus attached to them display like a drop down list > - the end user cannot type anything into the field > and is forced to choose something from the menu. > > It is a really nice enhancement that's been a long > time coming. You can still have the option of having > the menu attached as per normal so that the user can > type into the field if they want, it's just a simple > flag that gets changed in the field properties to > control how it displays. > > Cheers, > Matt > > -----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 3:54 AM > To: ARSLIST@ARSLIST.ORG > Subject: SV: OT:Remedy Annoyances > > Frederick, seemes that we have designed the system > in the same way. My dream is that user not are > allows to write in fields with a menu attached if I > have set a 'flag for this', sometimes free text can > be useful, and the menu is just basevalues. But > often we just want to accept the menuvalues, would > skip 2 filters, hope Remedy will do something in > coming versons. > > L ars > > -----Ursprungligt meddelande----- > Fren: Action Request System discussion list(ARSList) > [mailto:ARSLIST@ARSLIST.ORG]Fvr Grooms, Frederick W > Skickat: den 11 augusti 2004 17:15 > Till: ARSLIST@ARSLIST.ORG > Dmne: Re: OT:Remedy Annoyances > > > 99% of all my menus are Search menus. As long as > the values in the menu do not rely on any other > fields on the form the $MENU$ works. If they do > rely on other fields then I use a 2 filter method of > validating. > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of > lars.j.pettersson@VATTENFALL.COM > Sent: Wednesday, August 11, 2004 9:23 AM > To: ARSLIST@ARSLIST.ORG > Subject: SV: OT:Remedy Annoyances > > > ** > > Or create a charmeny, with $MENU$ as pattern. But > ..likely not the best solution if You often have to > make changes to the list, add, delete entries, then > a regular form with filtervalidating the data should > be a better alternative, changes can be handled > within the usertool. I try to avoid using hardcoded > charmenues for that reson. > > > > L ars > > > > -----Ursprungligt meddelande----- > Fren: Action Request System discussion list(ARSList) > [mailto:ARSLIST@ARSLIST.ORG]Fvr Palermo, Shelia D > ERDC-ITL-MS Contractor > Skickat: den 11 augusti 2004 15:29 > Till: ARSLIST@ARSLIST.ORG > Dmne: Re: OT:Remedy Annoyances > > > > Why not set the field to be call caps, then all you > have to worry about is typos. > Shelia > > > > -----Original Message----- > From: Burkholder Anthony O Contr 83 CS/SCZA [ > > mailto:Anthony.Burkholder@LANGLEY.AF.MIL] > Sent: Wednesday, August 11, 2004 5:49 AM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > > > My 2 cents, > > The real reason to use a separate table to store > state information (or similar static data) is to > prevent users from making the following kinds of > entries; VA, va, Va, vA, VG, VI, etc for Virginia. > The problem isn't how often the states have changed > its how many ways will a user enter the data. > In the example above a search for all Virginia > related items would be a nightmare. The trouble > saved is well worth the 4 bytes. > > > > Anthony O. Burkholder > AOC Weapons System Database Administrator > Dynamics Research Corporation > (757) 225-7110 / DSN 575-7110 > Email: anthony.burkholder@langley.af.mil > SIPR Email: anthony.burkholder@c2fs.acc.af.smil.mil > > > > > -----Original Message----- > From: Grooms, Frederick W [ > > mailto:frederick.w.grooms@XO.COM] > Sent: Tuesday, August 10, 2004 6:09 PM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > Of course this is not a problem when you have custom > apps :) > > You are correct on healthy balance. I have a couple > of systems (not Remedy) > that I have to pull data from that overkill on > normalization. i.e. The > state code in an address is in a separate table and > all that is stored with the address is a pointer to > the correct row in the master list. I mean how > many times has the government changed the > abbreviation for a state? Why > waste 4 (or more) bytes of space for a 2 byte > character? > > Fred > > -----Original Message----- > >
> 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 > From: Action Request System discussion list(ARSList) > > >
> 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 email is intended only for the use of the > individual or entity > named above and may contain information that is > confidential and > privileged. If you are not the intended recipient, > you are hereby notified that any dissemination, > distribution or copying of this Email is strictly > prohibited. When addressed to our clients, any > opinions or advice contained in this Email are > subject to the terms and conditions expressed in the > governing KPMG client engagement letter. If you have > received this Email in error, please notify us > immediately by return email or telephone +61 2 > 93357000 and destroy the original message. Thank > You. > **********************************************************************M > >
> 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
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
===== 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
Hi, I found /thanks Doug) that this is possible even in pre ver 6, set 'display as text' for the field, then the menybutton is still there, but it's not possible to write in the field, only select data using the menubutton. The data is displayed as 'plain text', not in a field, but it works! I have tried with searchnmenus, suppose there is no limitation/menutypes, but I have to test more.
L ars
-----Ursprungligt meddelande----- Fran: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] For Axton Grams Skickat: den 12 augusti 2004 00:58 Till: ARSLIST@ARSLIST.ORG Amne: Re: OT:Remedy Annoyances
Any search menu. The behavior is a little different on the web though (floating values as opposed to the drop down feel), and the arrows look a little different; but the feature is nice.
Axton
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of Susan Palmer Sent: Wednesday, August 11, 2004 6:39 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
Matthew ...
Does that same feature apply to search menus that are dependent on the previous choice, like CTI.
Thanks, Susan
--- "Watson, Matthew (Melbourne)" wrote:
> Lars, > > In version 6, you can make character fields with > menus attached to them display like a drop down list > - the end user cannot type anything into the field > and is forced to choose something from the menu. > > It is a really nice enhancement that's been a long > time coming. You can still have the option of having > the menu attached as per normal so that the user can > type into the field if they want, it's just a simple > flag that gets changed in the field properties to > control how it displays. > > Cheers, > Matt > > -----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 3:54 AM > To: ARSLIST@ARSLIST.ORG > Subject: SV: OT:Remedy Annoyances > > Frederick, seemes that we have designed the system > in the same way. My dream is that user not are > allows to write in fields with a menu attached if I > have set a 'flag for this', sometimes free text can > be useful, and the menu is just basevalues. But > often we just want to accept the menuvalues, would > skip 2 filters, hope Remedy will do something in > coming versons. > > L ars > > -----Ursprungligt meddelande----- > Fren: Action Request System discussion list(ARSList) > [mailto:ARSLIST@ARSLIST.ORG]Fvr Grooms, Frederick W > Skickat: den 11 augusti 2004 17:15 > Till: ARSLIST@ARSLIST.ORG > Dmne: Re: OT:Remedy Annoyances > > > 99% of all my menus are Search menus. As long as > the values in the menu do not rely on any other > fields on the form the $MENU$ works. If they do > rely on other fields then I use a 2 filter method of > validating. > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of > lars.j.pettersson@VATTENFALL.COM > Sent: Wednesday, August 11, 2004 9:23 AM > To: ARSLIST@ARSLIST.ORG > Subject: SV: OT:Remedy Annoyances > > > ** > > Or create a charmeny, with $MENU$ as pattern. But > ..likely not the best solution if You often have to > make changes to the list, add, delete entries, then > a regular form with filtervalidating the data should > be a better alternative, changes can be handled > within the usertool. I try to avoid using hardcoded > charmenues for that reson. > > > > L ars > > > > -----Ursprungligt meddelande----- > Fren: Action Request System discussion list(ARSList) > [mailto:ARSLIST@ARSLIST.ORG]Fvr Palermo, Shelia D > ERDC-ITL-MS Contractor > Skickat: den 11 augusti 2004 15:29 > Till: ARSLIST@ARSLIST.ORG > Dmne: Re: OT:Remedy Annoyances > > > > Why not set the field to be call caps, then all you > have to worry about is typos. > Shelia > > > > -----Original Message----- > From: Burkholder Anthony O Contr 83 CS/SCZA [ > > mailto:Anthony.Burkholder@LANGLEY.AF.MIL] > Sent: Wednesday, August 11, 2004 5:49 AM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > > > My 2 cents, > > The real reason to use a separate table to store > state information (or similar static data) is to > prevent users from making the following kinds of > entries; VA, va, Va, vA, VG, VI, etc for Virginia. > The problem isn't how often the states have changed > its how many ways will a user enter the data. > In the example above a search for all Virginia > related items would be a nightmare. The trouble > saved is well worth the 4 bytes. > > > > Anthony O. Burkholder > AOC Weapons System Database Administrator > Dynamics Research Corporation > (757) 225-7110 / DSN 575-7110 > Email: anthony.burkholder@langley.af.mil > SIPR Email: anthony.burkholder@c2fs.acc.af.smil.mil > > > > > -----Original Message----- > From: Grooms, Frederick W [ > > mailto:frederick.w.grooms@XO.COM] > Sent: Tuesday, August 10, 2004 6:09 PM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > Of course this is not a problem when you have custom > apps :) > > You are correct on healthy balance. I have a couple > of systems (not Remedy) > that I have to pull data from that overkill on > normalization. i.e. The > state code in an address is in a separate table and > all that is stored with the address is a pointer to > the correct row in the master list. I mean how > many times has the government changed the > abbreviation for a state? Why > waste 4 (or more) bytes of space for a 2 byte > character? > > Fred > > -----Original Message----- > >
> 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 > From: Action Request System discussion list(ARSList) > > >
> 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 email is intended only for the use of the > individual or entity > named above and may contain information that is > confidential and > privileged. If you are not the intended recipient, > you are hereby notified that any dissemination, > distribution or copying of this Email is strictly > prohibited. When addressed to our clients, any > opinions or advice contained in this Email are > subject to the terms and conditions expressed in the > governing KPMG client engagement letter. If you have > received this Email in error, please notify us > immediately by return email or telephone +61 2 > 93357000 and destroy the original message. Thank > You. > **********************************************************************M > >
> 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
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/
-----Original Message----- From: Joe DeSouza [mailto:joeremedy@YAHOO.COM] 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
===== 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
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
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
** 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
** 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 This posting was submitted via the Web interface at www.QMXS.com
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
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
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
OK, here's somet= hing 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 th= ing, 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:Re= medy Annoyances
We have already begun enforcing s= trong 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 This posting was submitted via the Web interface
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
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
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
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
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
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 :)
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
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 :)
I agree this is the idea behind a display only field - and that is what I was referring to (but did not say directly).
However, display only fields have a definite purpose when designing GUI's and using them essentially as variables seems (IMHO) like an afterthought. I rather doubt they were originally intende for what we all use them for.
I'd prefer more of a traditional variable-like mechanism, and keywords would be right up that alley. Remedy has them already. Expanding their functionality would be a simple step for current users to learn and administer.
As far as the list selection - yes, I was referring to the admin tool.
-----Original Message----- From: Action Request System discussion list(ARSList) on behalf of Axton W Grams/NYLIC Sent: Thu 8/12/2004 1:09 PM To: ARSLIST@ARSLIST.ORG Cc: Subject: Re: OT:Remedy Annoyances
See comments below.
Kind Regards, Axton Grams New York Life Remedy Solutions Provider
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
I have done this with good results. I have also gone as far as to put a box behind the field to make it look like a read only field :)
Mark
----- Original Message ----- From: To: Sent: Thursday, August 12, 2004 2:23 AM Subject: SV: OT:Remedy Annoyances
Hi, I found /thanks Doug) that this is possible even in pre ver 6, set 'display as text' for the field, then the menybutton is still there, but it's not possible to write in the field, only select data using the menubutton. The data is displayed as 'plain text', not in a field, but it works! I have tried with searchnmenus, suppose there is no limitation/menutypes, but I have to test more.
L ars
-----Ursprungligt meddelande----- Fran: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] For Axton Grams Skickat: den 12 augusti 2004 00:58 Till: ARSLIST@ARSLIST.ORG Amne: Re: OT:Remedy Annoyances
Any search menu. The behavior is a little different on the web though (floating values as opposed to the drop down feel), and the arrows look a little different; but the feature is nice.
Axton
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of Susan Palmer Sent: Wednesday, August 11, 2004 6:39 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
Matthew ...
Does that same feature apply to search menus that are dependent on the previous choice, like CTI.
Thanks, Susan
--- "Watson, Matthew (Melbourne)" wrote:
> Lars, > > In version 6, you can make character fields with > menus attached to them display like a drop down list > - the end user cannot type anything into the field > and is forced to choose something from the menu. > > It is a really nice enhancement that's been a long > time coming. You can still have the option of having > the menu attached as per normal so that the user can > type into the field if they want, it's just a simple > flag that gets changed in the field properties to > control how it displays. > > Cheers, > Matt > > -----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 3:54 AM > To: ARSLIST@ARSLIST.ORG > Subject: SV: OT:Remedy Annoyances > > Frederick, seemes that we have designed the system > in the same way. My dream is that user not are > allows to write in fields with a menu attached if I > have set a 'flag for this', sometimes free text can > be useful, and the menu is just basevalues. But > often we just want to accept the menuvalues, would > skip 2 filters, hope Remedy will do something in > coming versons. > > L ars > > -----Ursprungligt meddelande----- > Fren: Action Request System discussion list(ARSList) > [mailto:ARSLIST@ARSLIST.ORG]Fvr Grooms, Frederick W > Skickat: den 11 augusti 2004 17:15 > Till: ARSLIST@ARSLIST.ORG > Dmne: Re: OT:Remedy Annoyances > > > 99% of all my menus are Search menus. As long as > the values in the menu do not rely on any other > fields on the form the $MENU$ works. If they do > rely on other fields then I use a 2 filter method of > validating. > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of > lars.j.pettersson@VATTENFALL.COM > Sent: Wednesday, August 11, 2004 9:23 AM > To: ARSLIST@ARSLIST.ORG > Subject: SV: OT:Remedy Annoyances > > > ** > > Or create a charmeny, with $MENU$ as pattern. But > ..likely not the best solution if You often have to > make changes to the list, add, delete entries, then > a regular form with filtervalidating the data should > be a better alternative, changes can be handled > within the usertool. I try to avoid using hardcoded > charmenues for that reson. > > > > L ars > > > > -----Ursprungligt meddelande----- > Fren: Action Request System discussion list(ARSList) > [mailto:ARSLIST@ARSLIST.ORG]Fvr Palermo, Shelia D > ERDC-ITL-MS Contractor > Skickat: den 11 augusti 2004 15:29 > Till: ARSLIST@ARSLIST.ORG > Dmne: Re: OT:Remedy Annoyances > > > > Why not set the field to be call caps, then all you > have to worry about is typos. > Shelia > > > > -----Original Message----- > From: Burkholder Anthony O Contr 83 CS/SCZA [ > > mailto:Anthony.Burkholder@LANGLEY.AF.MIL] > Sent: Wednesday, August 11, 2004 5:49 AM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > > > My 2 cents, > > The real reason to use a separate table to store > state information (or similar static data) is to > prevent users from making the following kinds of > entries; VA, va, Va, vA, VG, VI, etc for Virginia. > The problem isn't how often the states have changed > its how many ways will a user enter the data. > In the example above a search for all Virginia > related items would be a nightmare. The trouble > saved is well worth the 4 bytes. > > > > Anthony O. Burkholder > AOC Weapons System Database Administrator > Dynamics Research Corporation > (757) 225-7110 / DSN 575-7110 > Email: anthony.burkholder@langley.af.mil > SIPR Email: anthony.burkholder@c2fs.acc.af.smil.mil > > > > > -----Original Message----- > From: Grooms, Frederick W [ > > mailto:frederick.w.grooms@XO.COM] > Sent: Tuesday, August 10, 2004 6:09 PM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > Of course this is not a problem when you have custom > apps :) > > You are correct on healthy balance. I have a couple > of systems (not Remedy) > that I have to pull data from that overkill on > normalization. i.e. The > state code in an address is in a separate table and > all that is stored with the address is a pointer to > the correct row in the master list. I mean how > many times has the government changed the > abbreviation for a state? Why > waste 4 (or more) bytes of space for a 2 byte > character? > > Fred > > -----Original Message----- > >
> 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 > From: Action Request System discussion list(ARSList) > > >
> 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 email is intended only for the use of the > individual or entity > named above and may contain information that is > confidential and > privileged. If you are not the intended recipient, > you are hereby notified that any dissemination, > distribution or copying of this Email is strictly > prohibited. When addressed to our clients, any > opinions or advice contained in this Email are > subject to the terms and conditions expressed in the > governing KPMG client engagement letter. If you have > received this Email in error, please notify us > immediately by return email or telephone +61 2 > 93357000 and destroy the original message. Thank > You. > **********************************************************************M > >
> 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
But why not also have the option to have a change in value in that field on any form update all the other records.
Susan
--- lars.j.pettersson@VATTENFALL.COM wrote:
> 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 >
I remember Doug talking about the desire to have global data elements a couple of years ago, but I don't know what the status of that is. Just wanted you to know that they ARE thinking about things like that.
Susan's wish seems more like a normalized DB structure. For a number of reasons, I don't see them going there.
Rick
From: Action Request System discussion list(ARSList) on behalf of Susan Palmer Sent: Thu 8/12/2004 4:43 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
What a great idea ...
But why not also have the option to have a change in value in that field on any form update all the other records.
Susan
--- lars.j.pettersson@VATTENFALL.COM wrote:
> 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 >
Hmmm... not sure if the following has already been mentioned - basically the idea is, to get more out of the Admin client, making it more compareable to a "real" coding editors.
You know, such little things as little as coloring brackets for example. Being able to drag n' drop actions from one AL to another, converting AL's to filters, more debugging and real time monitoring of variables - also like the log file telling you "qualificaton of AL xxx failed" - yeah, nice. But failed why ? What part ? ... and so on :-)
Basically I think that the whole idea of having those little own windows for single AL's and such may perhaps be something that could get improved, or taking another direction basically, like more diplaying those flat like code snippets too, where you can modify per text directly and copy n paste even or such things.
Well, not really annoyances those are. I think the Admin Client is real good - but I think that there is room for improvements too.
Cheers from Germany - tgif - Robert
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of Rick Cook Sent: Friday, August 13, 2004 3:25 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
I remember Doug talking about the desire to have global data elements a couple of years ago, but I don't know what the status of that is. Just wanted you to know that they ARE thinking about things like that.
Susan's wish seems more like a normalized DB structure. For a number of reasons, I don't see them going there.
Rick
From: Action Request System discussion list(ARSList) on behalf of Susan Palmer Sent: Thu 8/12/2004 4:43 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
What a great idea ...
But why not also have the option to have a change in value in that field on any form update all the other records.
Susan
--- lars.j.pettersson@VATTENFALL.COM wrote:
> 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 >
I submitted and enhancement request (RFE 2620) in September 1999 on this topic. This particular RFE has a status of 'Retired'. I resubmitted it in November 2002 (RFE 6182). It has the status of 'Assigned'.
Perhaps if more people were to request this enhancement then Remedy may look into it.
Nyall
Quoting Rick Cook :
> 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. >
Not sure how useful everyone would find this, but a lot of times I have to create several change field actions for fields that I need to change the display attributes like making a whole bunch of fields hidden or read-only. It would be nice if the change field action would allow you to (if required) select multiple fields and specify read-only or hidden or other appropriate actions rather than have to add the Change field action individually for each field. This sometimes leads to creating more than one AL if you have more than 24 fields for which you are changing the display property of the fields. Maybe something similar like how the set fields actions work.
Also how about an additional execute on for "Mouse Over" in addition to gain and lose focus in the execute on in AL's?
Regards, Saby
--- "Kern Robert (SBA)" wrote:
> Hmmm... not sure if the following has already been > mentioned - basically the idea is, to get more out > of the Admin client, making it more compareable to a > "real" coding editors. > > You know, such little things as little as coloring > brackets for example. Being able to drag n' drop > actions from one AL to another, converting AL's to > filters, more debugging and real time monitoring of > variables - also like the log file telling you > "qualificaton of AL xxx failed" - yeah, nice. But > failed why ? What part ? ... and so on :-) > > Basically I think that the whole idea of having > those little own windows for single AL's and such > may perhaps be something that could get improved, or > taking another direction basically, like more > diplaying those flat like code snippets too, where > you can modify per text directly and copy n paste > even or such things. > > Well, not really annoyances those are. I think the > Admin Client is real good - but I think that there > is room for improvements too. > > > Cheers from Germany - tgif - Robert > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of Rick Cook > Sent: Friday, August 13, 2004 3:25 AM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > > I remember Doug talking about the desire to have > global data elements a couple of years ago, but I > don't know what the status of that is. Just wanted > you to know that they ARE thinking about things like > that. > > Susan's wish seems more like a normalized DB > structure. For a number of reasons, I don't see > them going there. > > Rick > > > > From: Action Request System discussion list(ARSList) > on behalf of Susan Palmer > Sent: Thu 8/12/2004 4:43 PM > To: ARSLIST@ARSLIST.ORG > Subject: Re: OT:Remedy Annoyances > > > > What a great idea ... > > But why not also have the option to have a change in > value in that field on any form update all the other > records. > > Susan > > > > > > --- lars.j.pettersson@VATTENFALL.COM wrote: > > > 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 > > > >
> 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 >
Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/newmail
I have submitted an eng req long time ago, to populate a field when You are creating a 'display a list AL'. Enter a text in the field 'Select the Statecode from the list' for example, its not always so easy for users to understand what ldisplaylist really shows, should be rather easy to set this text as head instead of the standard selection list ..I also want columheaders in the selection list. Much more userfrienly.. I wonder if there is any meaning leaving enh req on Remedys site - I expected some form of email back when they change status of an entry. Hopefylly Remedy are reading all we have written about on the list the last week, and maybe implement something in coming releases ..
L ars
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of Nyall McCavitt Sent: Friday, August 13, 2004 8:55 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
Hi,
I submitted and enhancement request (RFE 2620) in September 1999 on this topic. This particular RFE has a status of 'Retired'. I resubmitted it in November 2002 (RFE 6182). It has the status of 'Assigned'.
Perhaps if more people were to request this enhancement then Remedy may look into it.
Nyall
Quoting Rick Cook :
> 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. >
I like the Change field idea ... and I believe it crosses my mind everytime I have to do that because it never seems to be just one field.
Why couldn't it work like a set field where you pick the field and then you could pick what you want to happen to that field, hidden or visible etc.
Susan
--- Sabyson Fernandes wrote:
> All, > > Not sure how useful everyone would find this, but a > lot of times I have to create several change field > actions for fields that I need to change the display > attributes like making a whole bunch of fields > hidden > or read-only. It would be nice if the change field > action would allow you to (if required) select > multiple fields and specify read-only or hidden or > other appropriate actions rather than have to add > the > Change field action individually for each field. > This > sometimes leads to creating more than one AL if you > have more than 24 fields for which you are changing > the display property of the fields. Maybe something > similar like how the set fields actions work. > > Also how about an additional execute on for "Mouse > Over" in addition to gain and lose focus in the > execute on in AL's? > > Regards, > Saby > > --- "Kern Robert (SBA)" > wrote: > > > Hmmm... not sure if the following has already been > > mentioned - basically the idea is, to get more out > > of the Admin client, making it more compareable to > a > > "real" coding editors. > > > > You know, such little things as little as coloring > > brackets for example. Being able to drag n' drop > > actions from one AL to another, converting AL's to > > filters, more debugging and real time monitoring > of > > variables - also like the log file telling you > > "qualificaton of AL xxx failed" - yeah, nice. But > > failed why ? What part ? ... and so on :-) > > > > Basically I think that the whole idea of having > > those little own windows for single AL's and such > > may perhaps be something that could get improved, > or > > taking another direction basically, like more > > diplaying those flat like code snippets too, where > > you can modify per text directly and copy n paste > > even or such things. > > > > Well, not really annoyances those are. I think the > > Admin Client is real good - but I think that there > > is room for improvements too. > > > > > > Cheers from Germany - tgif - Robert > > > > > > -----Original Message----- > > From: Action Request System discussion > list(ARSList) > > [mailto:ARSLIST@ARSLIST.ORG] On Behalf Of Rick > Cook > > Sent: Friday, August 13, 2004 3:25 AM > > To: ARSLIST@ARSLIST.ORG > > Subject: Re: OT:Remedy Annoyances > > > > > > I remember Doug talking about the desire to have > > global data elements a couple of years ago, but I > > don't know what the status of that is. Just > wanted > > you to know that they ARE thinking about things > like > > that. > > > > Susan's wish seems more like a normalized DB > > structure. For a number of reasons, I don't see > > them going there. > > > > Rick > > > > > > > > From: Action Request System discussion > list(ARSList) > > on behalf of Susan Palmer > > Sent: Thu 8/12/2004 4:43 PM > > To: ARSLIST@ARSLIST.ORG > > Subject: Re: OT:Remedy Annoyances > > > > > > > > What a great idea ... > > > > But why not also have the option to have a change > in > > value in that field on any form update all the > other > > records. > > > > Susan > > > > > > > > > > > > --- lars.j.pettersson@VATTENFALL.COM wrote: > > > > > 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 > > > > > > > >
> > 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 > > > > > > > > Do you Yahoo!? > New and Improved Yahoo! Mail - Send 10MB messages! > 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 >
I was just thinking of that one the other day. Make it like a set fields dialog or something (select a field, set a change, have it show up as field name and change)
How about being able to modify common attributes of fields. So I can do a box around 4 fields, click properties and select hidden or permissions and it will apply to all of them. If features aren't available for all of the fields, disable the field until that feature is available for all fields.
How about Ctrl+Z!
Good stuff guys, keep at it!
Jack
-----Original Message----- From: Sabyson Fernandes [mailto:sebyritz@YAHOO.COM] Sent: Friday, August 13, 2004 1:15 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
All,
Not sure how useful everyone would find this, but a lot of times I have to create several change field actions for fields that I need to change the display attributes like making a whole bunch of fields hidden or read-only. It would be nice if the change field action would allow you to (if required) select multiple fields and specify read-only or hidden or other appropriate actions rather than have to add the Change field action individually for each field. This sometimes leads to creating more than one AL if you have more than 24 fields for which you are changing the display property of the fields. Maybe something similar like how the set fields actions work.
Also how about an additional execute on for "Mouse Over" in addition to gain and lose focus in the execute on in AL's?
On Thu, 12 Aug 2004 12:29:37 -0400, lilly remedy wrote:
>And finally, although it's makes life simpler for users, having one password to get into Everything" is never a good idea.
Except they are likely to remember one password, more than that and they will be on post it notes around the terminal.
Which is also the problem with all this "strong" passwords, ageing etc. If you have to change a dozen passwords every 30 days - of *course* one is going to write them down. Really secure that.
** ...as once again, theoretical, rushing forward like Homer Simpson at a buffet table, butts head-on into a nasty practical... One must never forget that we are working with carbon units who think that sticky notes and digital watches are still pretty cool, and that the "computer" is what we know as the display. The salt of the earth...people of the common cubicle...you know - morons.
(Did I say that? - hey, it's Friday, and I only said what we all think). 8P
Rick
From: Dave Saville Sent: Fri 8/13/2004 9:19 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
On Thu, 12 Aug 2004 12:29:37 -0400, lilly remedy wrote:
>And finally, although it's makes life simpler for users, having one password to get into Everything" is never a good idea.
Except they are likely to remember one password, more than that and they will be on post it notes around the terminal.
Which is also the problem with all this "strong" passwords, ageing etc. If you have to change a dozen passwords every 30 days - of *course* one is going to write them down. Really secure that.
** ** ...as once again, theoretical, rushing forward like Homer Simpson at a buffet table, butts head-on into a nasty practical... One must never forget that we are working with carbon units who think that sticky notes and digital watches are still pretty cool, and that the "computer" is what we know as the display. The salt of the earth...people of the common cubicle...you know - morons.
(Did I say that? - hey, it's Friday, and I only said what we all think). 8P
Rick
From: Dave Saville Sent: Fri 8/13/2004 9:19 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
On Thu, 12 Aug 2004 12:29:37 -0400, lilly remedy wrote:
>And finally, although it's makes life simpler for users, having one password to get into Everything" is never a good idea.
Except they are likely to remember one password, more than that and they will be on post it notes around the terminal.
Which is also the problem with all this "strong" passwords, ageing etc. If you have to change a dozen passwords every 30 days - of *course* one is going to write them down. Really secure that.
-- Regards
Dave Saville
This posting was submitted via the Web interface This posting was submitted via the Web interface
Kerns idea of having colored brackets kind of inspired another thought.. so I think he should take the credit for this...
Didn't the MS-SQL Query Analyzer look better when the queries written in them dsiplayed a different color for field names, another for field values, another for constructs and conditions, another for keywords... I think that is a good visual feature for viewing ones query so one could 'visually' edit their queries as sometimes those colors in MS-SQL's QA does tell you if you have something missing somewhere... Being a sucker for esthetics I would love this at least...
Joe
--- "Kern Robert (SBA)" wrote:
> Hmmm... not sure if the following has already been mentioned - basically the idea is, > to get more out of the Admin client, making it more compareable to a "real" coding > editors. > > You know, such little things as little as coloring brackets for example. Being able > to drag n' drop actions from one AL to another, converting AL's to filters, more > debugging and real time monitoring of variables - also like the log file telling you > "qualificaton of AL xxx failed" - yeah, nice. But failed why ? What part ? ... and so > on :-) > > Basically I think that the whole idea of having those little own windows for single > AL's and such may perhaps be something that could get improved, or taking another > direction basically, like more diplaying those flat like code snippets too, where you > can modify per text directly and copy n paste even or such things. > > Well, not really annoyances those are. I think the Admin Client is real good - but I > think that there is room for improvements too. > > > Cheers from Germany - tgif - Robert
===== 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
I like it too.. It would be even nicer if you have a 'range' of field ID's to pick from to run these Change field actions against, something like you choose the change field action and have a radio button, 1) Single Field 2) Field Range - () To () ** And if possible to select this range values using workflow** 3) Multiple Fields (Saby's idea) (List of fields with check boxes)
Having the field range for this action would be encouraging to developers who structure their applications by 'assigning' field ID's themselves, thus having a related data set of field with ID's that fall within a range... This would also mean that if another field of the same type of information is added within that range, this action would automatically associate itself with that new field... Wouldn't that be cool?
Another little something I wished I could have had from ages, is to find a field (especially on a form that has 100 + fields - eg. HPD:HelpDesk if you are using the ITSM product Remedy Helpdesk) from a drop list of field ID's on the tool bar sorted by field ID's... I would find this especially useful to trouble shoot errors when the error message returned is on the field ID... To do so now I have to run queries against the database to find the offending field name... This is an enhancement request I had put forth a few years ago, but it was closed without any action...
Regards
Joe
--- Susan Palmer wrote:
I like the Change field idea ... and I believe it crosses my mind everytime I have to do that because it never seems to be just one field.
Why couldn't it work like a set field where you pick the field and then you could pick what you want to happen to that field, hidden or visible etc.
Susan
--- Sabyson Fernandes wrote:
All,
Not sure how useful everyone would find this, but a lot of times I have to create several change field actions for fields that I need to change the display attributes like making a whole bunch of fields hidden or read-only. It would be nice if the change field action would allow you to (if required) select multiple fields and specify read-only or hidden or other appropriate actions rather than have to add the Change field action individually for each field. This sometimes leads to creating more than one AL if you have more than 24 fields for which you are changing the display property of the fields. Maybe something similar like how the set fields actions work.
Also how about an additional execute on for "Mouse Over" in addition to gain and lose focus in the execute on in AL's?
Regards, Saby
--- "Kern Robert (SBA)" wrote:
Hmmm... not sure if the following has already been mentioned - basically the idea is, to get more out of the Admin client, making it more compareable to a "real" coding editors.
You know, such little things as little as coloring brackets for example. Being able to drag n' drop actions from one AL to another, converting AL's to filters, more debugging and real time monitoring of variables - also like the log file telling you "qualificaton of AL xxx failed" - yeah, nice. But failed why ? What part ? ... and so on :-)
Basically I think that the whole idea of having those little own windows for single AL's and such may perhaps be something that could get improved, or taking another direction basically, like more diplaying those flat like code snippets too, where you can modify per text directly and copy n paste even or such things.
Well, not really annoyances those are. I think the Admin Client is real good - but I think that there is room for improvements too.
Cheers from Germany - tgif - Robert
===== 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 - Send 10MB messages! http://promotions.yahoo.com/newmail
Just thought I'd run an update with the group about some of the things that I suggested here on this thread that I already raised with Remedy...
ARS Server 1) Password maintenance 2) Color coding of Run If's and other queries 3) Locate a field on a form via its database Field ID 4) Lock out a subset of users...
The 4th one I thought would be useful for Application developers as well as Administrators is locking out a subset of users instead of having just the generic lockout of all non Admin users (Administrator Mode Only - off course this is useful in some circumstances too).
The reason I would have wished to have a subset of users locked out is if I was developing or migrating changes to just one application which is not used enterprize wide but just by a set of users say the 'Software' group, then it is sometimes pointless to deny access to groups other than 'Software'. I know that these things are usually done during non-productive hours, but sometimes it becomes necessary to have such lockouts during production hours and it doesn't make sense locking the whole organization out when you could have locked just a set of users and performed the task you wanted...
Would this feature be appealing to any of you???
I've also asked for enhancement on the ARS Email Engine for the following: 1) Support the Secured Password Authentication feature of MS-Exchange
I haven't logged any of the other suggestions as I thought it would be appropriate for persons who thought of them to log them.
Regards
===== 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
** >>Lock out a subset of users... >>Would this feature be appealing to any of you??? I have already implemented this for our system. You need to add a field to every form and some functionality that runs on Window Open/Window Loaded. Basically, I have a form accessible only by the Admin and on it is a field to indicate what application you want restricted and even what message you want the user to see. We use it for exactly the reason you mentioned - we want to restrict access to one app but not the other. If anyone is interested in more detail, just ask.
Later Stephen
Joe DeSouza wrote:
Hello,
Just thought I'd run an update with the group about some of the things that I suggested here on this thread that I already raised with Remedy...
ARS Server 1) Password maintenance 2) Color coding of Run If's and other queries 3) Locate a field on a form via its database Field ID 4) Lock out a subset of users...
The 4th one I thought would be useful for Application developers as well as Administrators is locking out a subset of users instead of having just the generic lockout of all non Admin users (Administrator Mode Only - off course this is useful in some circumstances too).
The reason I would have wished to have a subset of users locked out is if I was developing or migrating changes to just one application which is not used enterprize wide but just by a set of users say the 'Software' group, then it is sometimes pointless to deny access to groups other than 'Software'. I know that these things are usually done during non-productive hours, but sometimes it becomes necessary to have such lockouts during production hours and it doesn't make sense locking the whole organization out when you could have locked just a set of users and performed the task you wanted...
Would this feature be appealing to any of you???
I've also asked for enhancement on the ARS Email Engine for the following: 1) Support the Secured Password Authentication feature of MS-Exchange
I haven't logged any of the other suggestions as I thought it would be appropriate for persons who thought of them to log them.
Regards
===== Joe DeSouza, Remedy Technical Consultant, CyberMAK Information Systems, Kuwait. Phone :- 00965 484 7068 Mobile :- 00965 940 6129
Do you This posting was submitted via the Web interface Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/newmail
** Wouldn't it be just as easy to remove permissions on the Form? Make the changes and then set permissions back?
-----Original Message----- From: lilly remedy [mailto:arslistlilly@YAHOO.CA] Sent: Monday, August 16, 2004 9:14 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
** >>Lock out a subset of users... >>Would this feature be appealing to any of you??? I have already implemented this for our system. You need to add a field to every form and some functionality that runs on Window Open/Window Loaded. Basically, I have a form accessible only by the Admin and on it is a field to indicate what application you want restricted and even what message you want the user to see. We use it for exactly the reason you mentioned - we want to restrict access to one app but not the other. If anyone is interested in more detail, just ask.
Later Stephen
Joe DeSouza wrote:
Hello,
Just thought I'd run an update with the group about some of the things that I suggested here on this thread that I already raised with Remedy...
ARS Server 1) Password maintenance 2) Color coding of Run If's and other queries 3) Locate a field on a form via its database Field ID 4) Lock out a subset of users...
The 4th one I thought would be useful for Application developers as well as Administrators is locking out a subset of users instead of having just the generic lockout of all non Admin users (Administrator Mode Only - off course this is useful in some circumstances too).
The reason I would have wished to have a subset of users locked out is if I was developing or migrating changes to just one application which is not used enterprize wide but just by a set of users say the 'Software' group, then it is sometimes pointless to deny access to groups other than 'Software'. I know that these things are usually done during non-productive hours, but sometimes it becomes necessary to have such lockouts during production hours and it doesn't make sense locking the whole organization out when you could have locked just a set of users and performed the task you wanted...
Would this feature be appealing to any of you???
I've also asked for enhancement on the ARS Email Engine for the following: 1) Support the Secured Password Authentication feature of MS-Exchange
I haven't logged any of the other suggestions as I thought it would be appropriate for persons who thought of them to log them.
Regards
===== Joe DeSouza, Remedy Technical Consultant, CyberMAK Information Systems, Kuwait. Phone :- 00965 484 7068 Mobile :- 00965 940 6129
Do you This posting was submitted via the Web interface Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/newmail
Post your free ad now! Yahoo! Canada Personals
NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.
** It's not intended for application changes/maintenance. Those are migrated over during off-peak hours. This is when we need to restrict access to an application without locking out all the users to all the other apps as well. And since our apps are typically 15-20+ forms, this is much faster and easier - I open one record, modify a couple of fields and hit save.
Later Stephen
"Dunn, Eric" wrote:
** Wouldn't it be just as easy to remove permissions on the Form? Make the changes and then set permissions back?
-----Original Message----- From: lilly remedy [mailto:arslistlilly@YAHOO.CA] Sent: Monday, August 16, 2004 9:14 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
** >>Lock out a subset of users... >>Would this feature be appealing to any of you??? I have already implemented this for our system. You need to add a field to every form and some functionality that runs on Window Open/Window Loaded. Basically, I have a form accessible only by the Admin and on it is a field to indicate what application you want restricted and even what message you want the user to see. We use it for exactly the reason you mentioned - we want to restrict access to one app but not the other. If anyone is interested in more detail, just ask.
Later Stephen
Joe DeSouza wrote:
Hello,
Just thought I'd run an update with the group about some of the things that I suggested here on this thread that I already raised with Remedy...
ARS Server 1) Password maintenance 2) Color coding of Run If's and other queries 3) Locate a field on a form via its database Field ID 4) Lock out a subset of users...
The 4th one I thought would be useful for Application developers as well as Administrators is locking out a subset of users instead of having just the generic lockout of all non Admin users (Administrator Mode Only - off course this is useful in some circumstances too).
The reason I would have wished to have a subset of users locked out is if I was developing or migrating changes to just one application which is not used enterprize wide but just by a set of users say the 'Software' group, then it is sometimes pointless to deny access to groups other than 'Software'. I know that these things are usually done during non-productive hours, but sometimes it becomes necessary to have such lockouts during production hours and it doesn't make sense locking the whole organization out when you could have locked just a set of users and performed the task you wanted...
Would this feature be appealing to any of you???
I've also asked for enhancement on the ARS Email Engine for the following: 1) Support the Secured Password Authentication feature of MS-Exchange
I haven't logged any of the other suggestions as I thought it would be appropriate for persons who thought of them to log them.
Regards
===== Joe DeSouza, Remedy Technical Consultant, CyberMAK Information Systems, Kuwait. Phone :- 00965 484 7068 Mobile :- 00965 940 6129
Do you This posting was submitted via the Web interface Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/newmail
Post your free ad now! Yahoo! Canada Personals
This posting was submitted via the Web interface
NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.
Why restrict to window open/loaded? I have something similar, a ‘lockform’, if a button is set to YES in this form, then a filter checks this value on modify/submit in the other form – and set a tmpfield, if this field is YES, then message – ‘this form is locked at the moment , please try again later ...’or a more friendy messages, depending on the reason why u want to lock a form ...this is in fact the same as enabling a filter in Admintool on submit/modify – errormessage, but the advantage is that u can handle this within the Usertool, lock/unlock without logging in to RA.
L ars
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG]On Behalf Of lilly remedy Sent: Monday, August 16, 2004 5:19 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
**
It's not intended for application changes/maintenance. Those are migrated over during off-peak hours. This is when we need to restrict access to an application without locking out all the users to all the other apps as well. And since our apps are typically 15-20+ forms, this is much faster and easier - I open one record, modify a couple of fields and hit save.
Later
Stephen
"Dunn, Eric" wrote:
**
Wouldn't it be just as easy to remove permissions on the Form? Make the changes and then set permissions back?
-----Original Message----- From: lilly remedy [mailto:arslistlilly@YAHOO.CA] Sent: Monday, August 16, 2004 9:14 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
**
>>Lock out a subset of users...
>>Would this feature be appealing to any of you??? I have already implemented this for our system. You need to add a field to every form and some functionality that runs on Window Open/Window Loaded. Basically, I have a form accessible only by the Admin and on it is a field to indicate what application you want restricted and even what message you want the user to see.
We use it for exactly the reason you mentioned - we want to restrict access to one app but not the other.
If anyone is interested in more detail, just ask.
Later
Stephen
Joe DeSouza wrote:
Hello,
Just thought I'd run an update with the group about some of the things that I suggested here on this thread that I already raised with Remedy...
ARS Server 1) Password maintenance 2) Color coding of Run If's and other queries 3) Locate a field on a form via its database Field ID 4) Lock out a subset of users...
The 4th one I thought would be useful for Application developers as well as Administrators is locking out a subset of users instead of having just the generic lockout of all non Admin users (Administrator Mode Only - off course this is useful in some circumstances too).
The reason I would have wished to have a subset of users locked out is if I was developing or migrating changes to just one application which is not used enterprize wide but just by a set of users say the 'Software' group, then it is sometimes pointless to deny access to groups other than 'Software'. I know that these things are usually done during non-productive hours, but sometimes it becomes necessary to have such lockouts during production hours and it doesn't make sense locking the whole organization out when you could have locked just a set of users and performed the task you wanted...
Would this feature be appealing to any of you???
I've also asked for enhancement on the ARS Email Engine for the following: 1) Support the Secured Password Authentication feature of MS-Exchange
I haven't logged any of the other suggestions as I thought it would be appropriate for persons who thought of them to log them.
Regards
===== Joe DeSouza, Remedy Technical Consultant, CyberMAK Information Systems, Kuwait. Phone :- 00965 484 7068 Mobile :- 00965 940 6129
Do you This posting was submitted via the Web interface Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/newmail
Post your free ad now! Yahoo! Canada Personals
This posting was submitted via the Web interface
NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.
I don't think he needs to use the admin tool either. Seems to me it would be good to display a warning message on window loaded and then an error on submit/modify.
Jack
-----Original Message----- From: lars.j.pettersson@VATTENFALL.COM [mailto:lars.j.pettersson@VATTENFALL.COM] Sent: Monday, August 16, 2004 8:37 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
Why restrict to window open/loaded? I have something similar, a = 'lockform', if a button is set to YES in this form, then a filter checks = this value on modify/submit in the other form - and set a tmpfield, if = this field is YES, then message - 'this form is locked at the moment , = please try again later ...'or a more friendy messages, depending on the = reason why u want to lock a form ...this is in fact the same as enabling = a filter in Admintool on submit/modify - errormessage, but the advantage = is that u can handle this within the Usertool, lock/unlock without = logging in to RA. =20 L ars =20 -----Original Message----- From: Action Request System discussion list(ARSList) = [mailto:ARSLIST@ARSLIST.ORG]On Behalf Of lilly remedy Sent: Monday, August 16, 2004 5:19 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances =20 **=20 It's not intended for application changes/maintenance. Those are = migrated over during off-peak hours. This is when we need to restrict = access to an application without locking out all the users to all the = other apps as well. And since our apps are typically 15-20+ forms, this = is much faster and easier - I open one record, modify a couple of fields = and hit save. =20 Later Stephen
"Dunn, Eric" wrote: **=20 Wouldn't it be just as easy to remove permissions on the Form? Make the = changes and then set permissions back? =20 =20 -----Original Message----- From: lilly remedy [mailto:arslistlilly@YAHOO.CA] Sent: Monday, August 16, 2004 9:14 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances **=20 >>Lock out a subset of users... >>Would this feature be appealing to any of you??? I have already implemented this for our system. You need to add a field = to every form and some functionality that runs on Window Open/Window = Loaded. Basically, I have a form accessible only by the Admin and on it = is a field to indicate what application you want restricted and even = what message you want the user to see. =20 We use it for exactly the reason you mentioned - we want to restrict = access to one app but not the other. If anyone is interested in more detail, just ask. =20 Later Stephen
Joe DeSouza wrote: Hello,
Just thought I'd run an update with the group about some of the things = that I suggested here on this thread that I already raised with Remedy...
ARS Server 1) Password maintenance 2) Color coding of Run If's and other queries 3) Locate a field on a form via its database Field ID 4) Lock out a subset of users...
The 4th one I thought would be useful for Application developers as well = as Administrators is locking out a subset of users instead of having just = the generic lockout of all non Admin users (Administrator Mode Only - off course = this is useful in some circumstances too).
The reason I would have wished to have a subset of users locked out is = if I was developing or migrating changes to just one application which is not = used enterprize wide but just by a set of users say the 'Software' group, then it is = sometimes pointless to deny access to groups other than 'Software'. I know that = these things are usually done during non-productive hours, but sometimes it becomes = necessary to have such lockouts during production hours and it doesn't make sense locking = the whole organization out when you could have locked just a set of users and = performed the task you wanted...
Would this feature be appealing to any of you???
I've also asked for enhancement on the ARS Email Engine for the = following: 1) Support the Secured Password Authentication feature of MS-Exchange
I haven't logged any of the other suggestions as I thought it would be = appropriate for persons who thought of them to log them.
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 = = 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 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 =20 =20
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 This posting was submitted via the Web = interface=20 NOTICE: This electronic mail transmission may contain confidential = information and is intended only for the person(s) named. Any use, = copying or disclosure by any other person is strictly prohibited. If you = have received this transmission in error, please notify the sender via = e-mail.
= 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=20 =20 =20
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
color=3Dnavy face=3DArial>lang=3DEN-GB = style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial; mso-ansi-language:EN-GB'>Why restrict to window open/loaded? I have = something similar, a ‘lockform’, if a button is set to YES in this = form, then a filter checks this value on modify/submit in the other form – and set a = tmpfield, if this field is YES, then message – ‘this form is locked at = the moment , please try again later …’or a more friendy messages, depending on = the reason why u want to lock a form …this is in fact the same as enabling a filter = in Admintool on submit/modify – errormessage, but the advantage is that u can = handle this within the Usertool, lock/unlock without logging in to = RA.
face=3D"Times New Roman">style=3D'font-size:12.0pt;mso-ansi-language: EN-GB'>!supportEmptyParas]>
color=3Dblack face=3D"Times New Roman">style=3D'font-size:12.0pt;color:black; mso-ansi-language:EN-GB'>** lang=3DEN-GB style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
color=3Dblack face=3D"Times New Roman">style=3D'font-size:12.0pt;color:black; mso-ansi-language:EN-GB'>It's not intended for application changes/maintenance. Those are migrated over during off-peak = hours. This is when we need to restrict access to an application without = locking out all the users to all the other apps as well. And since our apps = are typically 15-20+ forms, this is much faster and easier - I open one = record, modify a couple of fields and hit save.color=3Dblack>lang=3DEN-GB = style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
color=3Dblack face=3D"Times New Roman">style=3D'font-size:12.0pt;color:black; mso-ansi-language:EN-GB'> lang=3DEN-GB = style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
color=3Dblack face=3D"Times New Roman">style=3D'font-size:12.0pt;color:black; mso-ansi-language:EN-GB'>Laterlang=3DEN-GB style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
color=3Dblack face=3D"Times New Roman">style=3D'font-size:12.0pt;color:black; mso-ansi-language:EN-GB'>Stephen
style=3D'margin-right:36.0pt;mso-margin-top-alt:auto; mso-margin-bottom-alt:auto;margin-left:68.95pt;border:none;mso-border-lef= t-alt: solid #1010FF 1.5pt;padding:0cm;mso-padding-alt:0cm 0cm 0cm 4.0pt'>size=3D2 color=3Dpurple face=3D"Bookman Old Style">style=3D'font-size: 10.0pt;font-family:"Bookman Old = Style";color:purple;mso-ansi-language:EN-GB'>Wouldn't it be just as easy to remove permissions on the Form? Make the changes = and then set permissions back?lang=3DEN-GB style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
style=3D'margin-right:72.0pt;mso-margin-top-alt:auto; mso-margin-bottom-alt:auto;margin-left:104.95pt;border:none;mso-border-le= ft-alt: solid #1010FF 1.5pt;padding:0cm;mso-padding-alt:0cm 0cm 0cm 4.0pt'>size=3D3 color=3Dblack face=3D"Times New Roman">style=3D'font-size: 12.0pt;color:black;mso-ansi-language:EN-GB'>>>Lock out a subset of users...style=3D'color:black; mso-color-alt:windowtext;mso-ansi-language:EN-GB'>t>
style=3D'margin-right:72.0pt;mso-margin-top-alt:auto; mso-margin-bottom-alt:auto;margin-left:104.95pt;border:none;mso-border-le= ft-alt: solid #1010FF 1.5pt;padding:0cm;mso-padding-alt:0cm 0cm 0cm 4.0pt'>size=3D3 color=3Dblack face=3D"Times New Roman">style=3D'font-size: 12.0pt;color:black;mso-ansi-language:EN-GB'>>>Would this feature = be appealing to any of you???
I have already implemented this for our system. You need to = add a field to every form and some functionality that runs on Window = Open/Window Loaded. Basically, I have a form accessible only by the Admin and = on it is a field to indicate what application you want restricted and = even what message you want the user to see. color=3Dblack>lang=3DEN-GB = style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
style=3D'margin-right:72.0pt;mso-margin-top-alt:auto; mso-margin-bottom-alt:auto;margin-left:104.95pt;border:none;mso-border-le= ft-alt: solid #1010FF 1.5pt;padding:0cm;mso-padding-alt:0cm 0cm 0cm 4.0pt'>size=3D3 color=3Dblack face=3D"Times New Roman">style=3D'font-size: 12.0pt;color:black;mso-ansi-language:EN-GB'>We use it for exactly the = reason you mentioned - we want to restrict access to one app but not the = other.color=3Dblack>style=3D'color:black;mso-color-alt:windowtext; mso-ansi-language:EN-GB'>
style=3D'margin-right:72.0pt;mso-margin-top-alt:auto; mso-margin-bottom-alt:auto;margin-left:104.95pt;border:none;mso-border-le= ft-alt: solid #1010FF 1.5pt;padding:0cm;mso-padding-alt:0cm 0cm 0cm 4.0pt'>size=3D3 color=3Dblack face=3D"Times New Roman">style=3D'font-size: 12.0pt;color:black;mso-ansi-language:EN-GB'>If anyone is interested in = more detail, just ask.style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
Just thought I'd run an update with the group about some of the things = that I suggested
here on this thread that I already raised with Remedy...
ARS Server
1) Password maintenance
2) Color coding of Run If's and other queries
3) Locate a field on a form via its database Field ID
4) Lock out a subset of users...
The 4th one I thought would be useful for Application developers as well = as
Administrators is locking out a subset of users instead of having just = the generic
lockout of all non Admin users (Administrator Mode Only - off course = this is useful in
some circumstances too).
The reason I would have wished to have a subset of users locked out is = if I was
developing or migrating changes to just one application which is not = used enterprize
wide but just by a set of users say the 'Software' group, then it is = sometimes
pointless to deny access to groups other than 'Software'. I know that = these things are
usually done during non-productive hours, but sometimes it becomes = necessary to have
such lockouts during production hours and it doesn't make sense locking = the whole
organization out when you could have locked just a set of users and = performed the task
you wanted...
Would this feature be appealing to any of you???
I've also asked for enhancement on the ARS Email Engine for the = following:
1) Support the Secured Password Authentication feature of = MS-Exchange
I haven't logged any of the other suggestions as I thought it would be appropriate for
persons who thought of them to log them.
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 =
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 = 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.comstyle=3D'color:black; mso-color-alt:windowtext;mso-ansi-language:EN-GB'>t>
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 = color=3Dblack>style=3D'color:black;mso-color-alt:windowtext; mso-ansi-language:EN-GB'>
style=3D'margin-right:36.0pt;margin-left:68.95pt;border:none;mso-border-l= eft-alt: solid #1010FF 1.5pt;padding:0cm;mso-padding-alt:0cm 0cm 0cm = 4.0pt'>size=3D2 color=3Dblack face=3DArial>style=3D'font-size:10.0pt; font-family:Arial;color:black;mso-ansi-language:EN-GB;font-weight:bold'>N= OTICE: This electronic mail transmission may contain confidential information = and is intended only for the person(s) named. Any use, copying or disclosure by = any other person is strictly prohibited. If you have received this = transmission in error, please notify the sender via e-mail.color=3Dblack>lang=3DEN-GB = style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
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 = color=3Dblack>style=3D'color:black;mso-color-alt:windowtext; mso-ansi-language:EN-GB'>
face=3D"Times New Roman">lang=3DEN-GB = style=3D'font-size:12.0pt;color:black;mso-ansi-language:EN-GB'>!supportEmptyParas]> color=3Dblack>style=3D'color:black;mso-color-alt:windowtext; mso-ansi-language:EN-GB'>
style=3D'margin-left:65.2pt;text-align:center'>size=3D3 color=3Dblack face=3D"Times New Roman">style=3D'font-size:12.0pt; color:black'>
color=3Dblack face=3D"Times New Roman">style=3D'font-size:12.0pt;color:black; mso-ansi-language:EN-GB'>Post your free ad now! href=3D"http://ca.personals.yahoo.com/">style=3D'font-weight:bold'>Yahoo! Canada Personalsstyle=3D'color: black;mso-color-alt:windowtext'>
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
I don't think he needs to use the admin tool either. Seems to me it would be good to display a warning message on window loaded and then an error on submit/modify.
Jack
-----Original Message----- From: lars.j.pettersson@VATTENFALL.COM [mailto:lars.j.pettersson@VATTENFALL.COM] Sent: Monday, August 16, 2004 8:37 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
Why restrict to window open/loaded? I have something similar, a = 'lockform', if a button is set to YES in this form, then a filter checks = this value on modify/submit in the other form - and set a tmpfield, if = this field is YES, then message - 'this form is locked at the moment , = please try again later ...'or a more friendy messages, depending on the = reason why u want to lock a form ...this is in fact the same as enabling = a filter in Admintool on submit/modify - errormessage, but the advantage = is that u can handle this within the Usertool, lock/unlock without = logging in to RA. =20 L ars =20 -----Original Message----- From: Action Request System discussion list(ARSList) = [mailto:ARSLIST@ARSLIST.ORG]On Behalf Of lilly remedy Sent: Monday, August 16, 2004 5:19 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances =20 **=20 It's not intended for application changes/maintenance. Those are = migrated over during off-peak hours. This is when we need to restrict = access to an application without locking out all the users to all the = other apps as well. And since our apps are typically 15-20+ forms, this = is much faster and easier - I open one record, modify a couple of fields = and hit save. =20 Later Stephen
"Dunn, Eric" wrote: **=20 Wouldn't it be just as easy to remove permissions on the Form? Make the = changes and then set permissions back? =20 =20 -----Original Message----- From: lilly remedy [mailto:arslistlilly@YAHOO.CA] Sent: Monday, August 16, 2004 9:14 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances **=20 >>Lock out a subset of users... >>Would this feature be appealing to any of you??? I have already implemented this for our system. You need to add a field = to every form and some functionality that runs on Window Open/Window = Loaded. Basically, I have a form accessible only by the Admin and on it = is a field to indicate what application you want restricted and even = what message you want the user to see. =20 We use it for exactly the reason you mentioned - we want to restrict = access to one app but not the other. If anyone is interested in more detail, just ask. =20 Later Stephen
Joe DeSouza wrote: Hello,
Just thought I'd run an update with the group about some of the things = that I suggested here on this thread that I already raised with Remedy...
ARS Server 1) Password maintenance 2) Color coding of Run If's and other queries 3) Locate a field on a form via its database Field ID 4) Lock out a subset of users...
The 4th one I thought would be useful for Application developers as well = as Administrators is locking out a subset of users instead of having just = the generic lockout of all non Admin users (Administrator Mode Only - off course = this is useful in some circumstances too).
The reason I would have wished to have a subset of users locked out is = if I was developing or migrating changes to just one application which is not = used enterprize wide but just by a set of users say the 'Software' group, then it is = sometimes pointless to deny access to groups other than 'Software'. I know that = these things are usually done during non-productive hours, but sometimes it becomes = necessary to have such lockouts during production hours and it doesn't make sense locking = the whole organization out when you could have locked just a set of users and = performed the task you wanted...
Would this feature be appealing to any of you???
I've also asked for enhancement on the ARS Email Engine for the = following: 1) Support the Secured Password Authentication feature of MS-Exchange
I haven't logged any of the other suggestions as I thought it would be = appropriate for persons who thought of them to log them.
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 = = 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 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 =20 =20
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 This posting was submitted via the Web = interface=20 NOTICE: This electronic mail transmission may contain confidential = information and is intended only for the person(s) named. Any use, = copying or disclosure by any other person is strictly prohibited. If you = have received this transmission in error, please notify the sender via = e-mail.
= 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=20 =20 =20
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
color=3Dnavy face=3DArial>lang=3DEN-GB = style=3D'font-size:10.0pt;mso-bidi-font-size:12.0pt;font-family:Arial; mso-ansi-language:EN-GB'>Why restrict to window open/loaded? I have = something similar, a ‘lockform’, if a button is set to YES in this = form, then a filter checks this value on modify/submit in the other form – and set a = tmpfield, if this field is YES, then message – ‘this form is locked at = the moment , please try again later …’or a more friendy messages, depending on = the reason why u want to lock a form …this is in fact the same as enabling a filter = in Admintool on submit/modify – errormessage, but the advantage is that u can = handle this within the Usertool, lock/unlock without logging in to = RA.
face=3D"Times New Roman">style=3D'font-size:12.0pt;mso-ansi-language: EN-GB'>!supportEmptyParas]>
color=3Dblack face=3D"Times New Roman">style=3D'font-size:12.0pt;color:black; mso-ansi-language:EN-GB'>** lang=3DEN-GB style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
color=3Dblack face=3D"Times New Roman">style=3D'font-size:12.0pt;color:black; mso-ansi-language:EN-GB'>It's not intended for application changes/maintenance. Those are migrated over during off-peak = hours. This is when we need to restrict access to an application without = locking out all the users to all the other apps as well. And since our apps = are typically 15-20+ forms, this is much faster and easier - I open one = record, modify a couple of fields and hit save.color=3Dblack>lang=3DEN-GB = style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
color=3Dblack face=3D"Times New Roman">style=3D'font-size:12.0pt;color:black; mso-ansi-language:EN-GB'> lang=3DEN-GB = style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
color=3Dblack face=3D"Times New Roman">style=3D'font-size:12.0pt;color:black; mso-ansi-language:EN-GB'>Laterlang=3DEN-GB style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
color=3Dblack face=3D"Times New Roman">style=3D'font-size:12.0pt;color:black; mso-ansi-language:EN-GB'>Stephen
style=3D'margin-right:36.0pt;mso-margin-top-alt:auto; mso-margin-bottom-alt:auto;margin-left:68.95pt;border:none;mso-border-lef= t-alt: solid #1010FF 1.5pt;padding:0cm;mso-padding-alt:0cm 0cm 0cm 4.0pt'>size=3D2 color=3Dpurple face=3D"Bookman Old Style">style=3D'font-size: 10.0pt;font-family:"Bookman Old = Style";color:purple;mso-ansi-language:EN-GB'>Wouldn't it be just as easy to remove permissions on the Form? Make the changes = and then set permissions back?lang=3DEN-GB style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
style=3D'margin-right:72.0pt;mso-margin-top-alt:auto; mso-margin-bottom-alt:auto;margin-left:104.95pt;border:none;mso-border-le= ft-alt: solid #1010FF 1.5pt;padding:0cm;mso-padding-alt:0cm 0cm 0cm 4.0pt'>size=3D3 color=3Dblack face=3D"Times New Roman">style=3D'font-size: 12.0pt;color:black;mso-ansi-language:EN-GB'>>>Lock out a subset of users...style=3D'color:black; mso-color-alt:windowtext;mso-ansi-language:EN-GB'>t>
style=3D'margin-right:72.0pt;mso-margin-top-alt:auto; mso-margin-bottom-alt:auto;margin-left:104.95pt;border:none;mso-border-le= ft-alt: solid #1010FF 1.5pt;padding:0cm;mso-padding-alt:0cm 0cm 0cm 4.0pt'>size=3D3 color=3Dblack face=3D"Times New Roman">style=3D'font-size: 12.0pt;color:black;mso-ansi-language:EN-GB'>>>Would this feature = be appealing to any of you???
I have already implemented this for our system. You need to = add a field to every form and some functionality that runs on Window = Open/Window Loaded. Basically, I have a form accessible only by the Admin and = on it is a field to indicate what application you want restricted and = even what message you want the user to see. color=3Dblack>lang=3DEN-GB = style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
style=3D'margin-right:72.0pt;mso-margin-top-alt:auto; mso-margin-bottom-alt:auto;margin-left:104.95pt;border:none;mso-border-le= ft-alt: solid #1010FF 1.5pt;padding:0cm;mso-padding-alt:0cm 0cm 0cm 4.0pt'>size=3D3 color=3Dblack face=3D"Times New Roman">style=3D'font-size: 12.0pt;color:black;mso-ansi-language:EN-GB'>We use it for exactly the = reason you mentioned - we want to restrict access to one app but not the = other.color=3Dblack>style=3D'color:black;mso-color-alt:windowtext; mso-ansi-language:EN-GB'>
style=3D'margin-right:72.0pt;mso-margin-top-alt:auto; mso-margin-bottom-alt:auto;margin-left:104.95pt;border:none;mso-border-le= ft-alt: solid #1010FF 1.5pt;padding:0cm;mso-padding-alt:0cm 0cm 0cm 4.0pt'>size=3D3 color=3Dblack face=3D"Times New Roman">style=3D'font-size: 12.0pt;color:black;mso-ansi-language:EN-GB'>If anyone is interested in = more detail, just ask.style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
Just thought I'd run an update with the group about some of the things = that I suggested
here on this thread that I already raised with Remedy...
ARS Server
1) Password maintenance
2) Color coding of Run If's and other queries
3) Locate a field on a form via its database Field ID
4) Lock out a subset of users...
The 4th one I thought would be useful for Application developers as well = as
Administrators is locking out a subset of users instead of having just = the generic
lockout of all non Admin users (Administrator Mode Only - off course = this is useful in
some circumstances too).
The reason I would have wished to have a subset of users locked out is = if I was
developing or migrating changes to just one application which is not = used enterprize
wide but just by a set of users say the 'Software' group, then it is = sometimes
pointless to deny access to groups other than 'Software'. I know that = these things are
usually done during non-productive hours, but sometimes it becomes = necessary to have
such lockouts during production hours and it doesn't make sense locking = the whole
organization out when you could have locked just a set of users and = performed the task
you wanted...
Would this feature be appealing to any of you???
I've also asked for enhancement on the ARS Email Engine for the = following:
1) Support the Secured Password Authentication feature of = MS-Exchange
I haven't logged any of the other suggestions as I thought it would be appropriate for
persons who thought of them to log them.
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 =
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 = 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.comstyle=3D'color:black; mso-color-alt:windowtext;mso-ansi-language:EN-GB'>t>
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 = color=3Dblack>style=3D'color:black;mso-color-alt:windowtext; mso-ansi-language:EN-GB'>
style=3D'margin-right:36.0pt;margin-left:68.95pt;border:none;mso-border-l= eft-alt: solid #1010FF 1.5pt;padding:0cm;mso-padding-alt:0cm 0cm 0cm = 4.0pt'>size=3D2 color=3Dblack face=3DArial>style=3D'font-size:10.0pt; font-family:Arial;color:black;mso-ansi-language:EN-GB;font-weight:bold'>N= OTICE: This electronic mail transmission may contain confidential information = and is intended only for the person(s) named. Any use, copying or disclosure by = any other person is strictly prohibited. If you have received this = transmission in error, please notify the sender via e-mail.color=3Dblack>lang=3DEN-GB = style=3D'color:black;mso-color-alt:windowtext;mso-ansi-language:EN-GB'>:p>
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 = color=3Dblack>style=3D'color:black;mso-color-alt:windowtext; mso-ansi-language:EN-GB'>
face=3D"Times New Roman">lang=3DEN-GB = style=3D'font-size:12.0pt;color:black;mso-ansi-language:EN-GB'>!supportEmptyParas]> color=3Dblack>style=3D'color:black;mso-color-alt:windowtext; mso-ansi-language:EN-GB'>
style=3D'margin-left:65.2pt;text-align:center'>size=3D3 color=3Dblack face=3D"Times New Roman">style=3D'font-size:12.0pt; color:black'>
color=3Dblack face=3D"Times New Roman">style=3D'font-size:12.0pt;color:black; mso-ansi-language:EN-GB'>Post your free ad now! href=3D"http://ca.personals.yahoo.com/">style=3D'font-weight:bold'>Yahoo! Canada Personalsstyle=3D'color: black;mso-color-alt:windowtext'>
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
Why restrict to window open/loaded? I have something similar, a ‘lockform’, if a button is set to YES in this form, then a filter checks this value on modify/submit in the other form – and set a tmpfield, if this field is YES, then message – ‘this form is locked at the moment , please try again later ...’or a more friendy messages, depending on the reason why u want to lock a form ...this is in fact the same as enabling a filter in Admintool on submit/modify – errormessage, but the advantage is that u can handle this within the Usertool, lock/unlock without logging in to RA.
L ars
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:ARSLIST@ARSLIST.ORG]On Behalf Of lilly remedy Sent: Monday, August 16, 2004 5:19 PM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
**
It's not intended for application changes/maintenance. Those are migrated over during off-peak hours. This is when we need to restrict access to an application without locking out all the users to all the other apps as well. And since our apps are typically 15-20+ forms, this is much faster and easier - I open one record, modify a couple of fields and hit save.
Later
Stephen
"Dunn, Eric" wrote:
**
Wouldn't it be just as easy to remove permissions on the Form? Make the changes and then set permissions back?
-----Original Message----- From: lilly remedy [mailto:arslistlilly@YAHOO.CA] Sent: Monday, August 16, 2004 9:14 AM To: ARSLIST@ARSLIST.ORG Subject: Re: OT:Remedy Annoyances
**
>>Lock out a subset of users...
>>Would this feature be appealing to any of you??? I have already implemented this for our system. You need to add a field to every form and some functionality that runs on Window Open/Window Loaded. Basically, I have a form accessible only by the Admin and on it is a field to indicate what application you want restricted and even what message you want the user to see.
We use it for exactly the reason you mentioned - we want to restrict access to one app but not the other.
If anyone is interested in more detail, just ask.
Later
Stephen
Joe DeSouza wrote:
Hello,
Just thought I'd run an update with the group about some of the things that I suggested here on this thread that I already raised with Remedy...
ARS Server 1) Password maintenance 2) Color coding of Run If's and other queries 3) Locate a field on a form via its database Field ID 4) Lock out a subset of users...
The 4th one I thought would be useful for Application developers as well as Administrators is locking out a subset of users instead of having just the generic lockout of all non Admin users (Administrator Mode Only - off course this is useful in some circumstances too).
The reason I would have wished to have a subset of users locked out is if I was developing or migrating changes to just one application which is not used enterprize wide but just by a set of users say the 'Software' group, then it is sometimes pointless to deny access to groups other than 'Software'. I know that these things are usually done during non-productive hours, but sometimes it becomes necessary to have such lockouts during production hours and it doesn't make sense locking the whole organization out when you could have locked just a set of users and performed the task you wanted...
Would this feature be appealing to any of you???
I've also asked for enhancement on the ARS Email Engine for the following: 1) Support the Secured Password Authentication feature of MS-Exchange
I haven't logged any of the other suggestions as I thought it would be appropriate for persons who thought of them to log them.
Regards
===== Joe DeSouza, Remedy Technical Consultant, CyberMAK Information Systems, Kuwait. Phone :- 00965 484 7068 Mobile :- 00965 940 6129
Do you This posting was submitted via the Web interface Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/newmail
Post your free ad now! Yahoo! Canada Personals
This posting was submitted via the Web interface
NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.
This posting was submitted via the Web interface
Post your free ad now! Yahoo! Canada Personals
This posting was submitted via the Web interface This posting was submitted via the Web interface
I agree you can achieve this with a bit of customized functionality, but I thought it would be good to have it as a feature instead of having to build it. Customizing this might mean (depending on how dynamic you can get when trying to build a custom feature), that you might need to revisit the workflow whenever a new group is added to use the application. It would be possible to make these changes transparent with a good use of the EXTERNAL feature while building quailifications to construct this feature...
Rgds
Joe
--- lilly remedy wrote:
> >>Lock out a subset of users... > >>Would this feature be appealing to any of you??? > I have already implemented this for our system. You need to add a field to every > form and some functionality that runs on Window Open/Window Loaded. Basically, I > have a form accessible only by the Admin and on it is a field to indicate what > application you want restricted and even what message you want the user to see. > We use it for exactly the reason you mentioned - we want to restrict access to one > app but not the other. > If anyone is interested in more detail, just ask. > > Later > Stephen > > Joe DeSouza wrote: > Hello, > > Just thought I'd run an update with the group about some of the things that I > suggested > here on this thread that I already raised with Remedy... > > ARS Server > 1) Password maintenance > 2) Color coding of Run If's and other queries > 3) Locate a field on a form via its database Field ID > 4) Lock out a subset of users... > > The 4th one I thought would be useful for Application developers as well as > Administrators is locking out a subset of users instead of having just the generic > lockout of all non Admin users (Administrator Mode Only - off course this is useful > in > some circumstances too). > > The reason I would have wished to have a subset of users locked out is if I was > developing or migrating changes to just one application which is not used enterprize > wide but just by a set of users say the 'Software' group, then it is sometimes > pointless to deny access to groups other than 'Software'. I know that these things > are > usually done during non-productive hours, but sometimes it becomes necessary to have > such lockouts during production hours and it doesn't make sense locking the whole > organization out when you could have locked just a set of users and performed the > task > you wanted... > > Would this feature be appealing to any of you??? > > I've also asked for enhancement on the ARS Email Engine for the following: > 1) Support the Secured Password Authentication feature of MS-Exchange > > I haven't logged any of the other suggestions as I thought it would be appropriate > for > persons who thought of them to log them. > > Regards > > > ===== > 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
Previous Topic
Index