Claire,
If you have Cross Authentication Blank Password set, you can just manually
designate a password for the users in the User form. Remedy will
authenticate to that password instead of trying to authenticate to LDAP.
Thanks,
Jared
-Original Message-
From: Action Request System
I believe you just delete the object. For example, if you have an overlay
active link in dev studio and you delete it, the original reappears. This
should work the same on all objects as long as you're in Best Practices
view.
-Original Message-
From: Action Request System discussion
We integrate with Alarmpoint (now called xMatters), which is a third-party
tool. It's worked well for us.
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Mike Tomasiewicz (ConAgra Foods)
Sent: Wednesday, October 05, 2011
I've had the identical issue happen to me importing through Dev Studio; I
haven't tried Migrator. I tried importing both origin and overlay and
importing just the overlay for CTM:People and COM:Company and could never get
it to work, always getting the error described below. I was able to
Couple things I forgot to mention...this was importing into an SP1 environment
and things got so messed up after a while I could see the unmodified
COM:Company field as well as the Overlaid at the same time in Best Practices
mode. That was the point I decided to restore the database and
Saji,
I believe you can configure Orion to call a perl script that sends a SOAP
message into a Remedy web service. From there you can have custom staging
form that pulls in data from other forms (i.e. product category info from
CMDB on the affected asset to do automatic assignment) and then
6 matches
Mail list logo
