Hi Guys, Gals,
 
I have a bit of a question and (damn) it's a snowy weekend and I should be
skiing instead.  
 
I noticed (with a protection exception in an error situation while trying to
get a schema dump of ITSM 7.6) that AR_ENUM_STYLE_QUERY is now in use.
Introduced in the 5.12 API, there have been no Remedy Administrators that
offered the facility (until now presumably).
 
There are a few forms in ITSM 7.6 that use this.
 
My questions are rather simple.  
 
Do I have to perform the query myself?  Or is there a convenient function
that I can call to give me the appropriate set or single num/text (for my
locale in ar_control - of-course).    How is any server reference resolved?
I may not match it against any servers I have and I may not even be signed
on to it.  (I don't copy user/pwd info in multiple ar_controls or sessions).
 
And just how dynamic is this?  Does the concept of a "set" make sense here?
For example, can the query include fields from a user's "working record" or
gotten record?   Must I run the query each time I need a value / text check?
(We may need an attribute like refreshcode from ARGetCharMenu() - why not in
the CharMenu struct?).  
 
Menus do have a f() "Expand" for which I have this q() as well:  How do I
supply a set of fields/values for the queries?  
 
When I have an assignment to a record's enum I may have a variety of records
gotten or even no records at all - as in Assign "xxxxx" to an enum field.
 
It's obviously the way to go for a "data driven", "data customisable" app
like ITSM (it's interesting to add association types etc to ITSM 7x).  I
would hope some expansion f()s are included with its use.  
 
I'm sure I'll have a bit more to ask as I delve a bit deeper into fleshing
out this area.
 
Looking forward to your responses.
 
Cheers
Ben Chernys
www.softwaretoolhouse.com
 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

Reply via email to