**
Yes I know that but then you have to use your time to query either through workflow you have already built or through SQL, to find it.. Having it on the Admin tool you could open the schema you want as soon as you find it by ID if the ID is the identifying factor that you had for wanting to open that schema..
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED]On Behalf Of Robert Molenda
Sent: Saturday, October 21, 2006 8:03 AM
To: [email protected]
Subject: Re: Enhancement: Schema ID on AR Admin tool...

**

Sometimes yes, but only for specific purposes (looking at a raw SQL log, or performance profiler SQL queries realtime).

 

Just build a ‘read-only’ view for arschema table.

 

Thanks-n-advance;

HDT Platform Incident / Problem Manager & Architect
Robert Molenda
IT OS PA
Tel: +1 408 501 6310
Fax: +1 408 501 2410
Mobile: +1 408 472 8097
[EMAIL PROTECTED]

Quality begins with your actions.

 


From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: Friday, October 20, 2006 9:51 AM
To: [email protected]
Subject: Enhancement: Schema ID on AR Admin tool...

 

How many of you would think that having the SchemaID displayed on the form list returned on the AR Admin tool would be useful?

 

I know we can build a view to the arschema table on the admin tool if we need to view the schemaid that a form corresponds to or find a form that corresponds to a particular schemaid, but my question is if we have that available as a part of the details on the form list we could do a sort on the schemaid and open a form by schemaid if that was ever required...

 

How many of you might find this useful.. the task I'm performing right now I would find that mighty useful...

 

Cheers
 

Joe D'Souza

Remedy Developer / Consultant,

Shyle Networks,

New Jersey.

 

__20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___
__20060125_______________________This posting was submitted with HTML in it___

Reply via email to