#103338 - 08/13/04 05:19 AM
Re: OT:Remedy Annoyances
[Re: Waldo]
|
enthusiast
Registered: 03/11/04
Posts: 398
|
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?
Regards, Saby
|
|
Top
|
|
|
|
|
#103339 - 08/13/04 06:19 AM
Re: OT:Remedy Annoyances
[Re: Waldo]
|
journeyman
Registered: 04/20/04
Posts: 79
|
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
|
|
Top
|
|
|
|
|
#103340 - 08/13/04 06:35 AM
Re: OT:Remedy Annoyances
[Re: Waldo]
|
Old Hand
   
Registered: 07/03/01
Posts: 2984
|
** ...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
|
|
Top
|
|
|
|
|
#103341 - 08/13/04 06:35 AM
Re: OT:Remedy Annoyances
[Re: Waldo]
|
Old Hand
   
Registered: 07/03/01
Posts: 2984
|
** ** ...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
|
|
Top
|
|
|
|
|
#103342 - 08/13/04 07:49 PM
Re: OT:Remedy Annoyances
[Re: Waldo]
|
old hand
Registered: 06/28/04
Posts: 736
|
Hello,
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
|
|
Top
|
|
|
|
|
#103343 - 08/13/04 09:15 PM
Re: OT:Remedy Annoyances
[Re: Waldo]
|
old hand
Registered: 06/28/04
Posts: 736
|
Hi,
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
|
|
Top
|
|
|
|
|
#103344 - 08/15/04 08:11 PM
Re: OT:Remedy Annoyances
[Re: Waldo]
|
old hand
Registered: 06/28/04
Posts: 736
|
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
|
|
Top
|
|
|
|
|
#103345 - 08/16/04 04:13 AM
Re: OT:Remedy Annoyances
[Re: Waldo]
|
enthusiast
Registered: 03/11/04
Posts: 306
|
** >>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
|
|
Top
|
|
|
|
|
#103346 - 08/16/04 04:26 AM
Re: OT:Remedy Annoyances
[Re: Waldo]
|
journeyman
Registered: 03/11/04
Posts: 84
|
** 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.
This posting was submitted via the Web interface
|
|
Top
|
|
|
|
|
#103347 - 08/16/04 05:19 AM
Re: OT:Remedy Annoyances
[Re: Waldo]
|
enthusiast
Registered: 03/11/04
Posts: 306
|
** 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
|
|
Top
|
|
|
|
|
|
|