The method Crystal describes is how I've had to do it as well. Though I'm
able to do it through the Mid Tier, you just have to use the ctrl-alt-enter
hotkey combo as a search button. As I type this though I suppose I could
just make it easy on myself and add a search button.

Levi Lippincott
(402) 216-6396
[email protected]
https://www.facebook.com/levi.lippincott

"Talent is a Gift; But Character is a Choice." -Matt Grotewold-

On Thu, Jul 27, 2017 at 9:04 AM, CRENSHAW, CRYSTAL <
[email protected]> wrote:

> **
>
> Hey Brian,
>
>
>
> We have done this by removing the user validation from the rules.  On the
> RBE:Action form search for the rule incident create and delete Validate
> Sender between the <auth></auth> Action Parameters and save.  Repeat for
> any other rules you wish to not validate users on.  (*We had to do this
> thru the User Tool and not the midtier.)
>
>
>
> Thanks,
>
>
> Crystal
>
>
>
> Crystal Crenshaw
>
> Service Management Senior Systems Analyst
>
> Project Services – Service Management
>
> (919)508-0546 <(919)%20508-0546>
>
>
>
>
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> [email protected]] *On Behalf Of *Brian Pancia
> *Sent:* Thursday, July 27, 2017 9:45 AM
> *To:* [email protected]
> *Subject:* Public Users and RBE
>
>
>
> **
>
> We are trying to implement the RBE to create/update tickets.  Looking
> through the documentation the users need to have an email address and login
> id in Remedy in order to use the RBE.  There is also a way to add users to
> the trusted email list that don't have a login id.  However, we can have
> users from outside our organization that will email into the system.
> Without a people record, email address, and login id the RBE does not
> process the emails.  It would become an administrative nightmare to keep up
> with all the outside email addresses.  For a good percentage of them we
> know the domain they are coming from (ie gmail.com).  It would be nice to
> be able to add trusted domains.  I'm sure we can work around this with some
> minor customizations.  Has anyone ran in to this and what was the solution
> they used?
>
>
>
> Thanks,
>
>
>
> Brian
>
>
>
> DISCLAIMER: The information contained in this e-mail and its attachments
> contain confidential information belonging to the sender, which is legally
> privileged. The information is intended only for the use of the
> recipient(s) named above. If you are not the intended recipient, you are
> notified that any disclosure, copying, distribution or action in reliance
> upon the contents of the information transmitted is strictly prohibited. If
> you have received this information in error, please delete it immediately.
>
> _ARSlist: "Where the Answers Are" and have been for 20 years_
>
> This email may contain confidential and privileged material for the sole
> use of the intended recipient. If you are not the intended recipient,
> please contact the sender and delete all copies. Any review or distribution
> by others is strictly prohibited. Personal emails are restricted by policy
> of the State Employees' Credit Union (SECU).  Therefore SECU specifically
> disclaims any responsibility or liability for any personal information or
> opinions of the author expressed in this email.
>
> _ARSlist: "Where the Answers Are" and have been for 20 years_
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to