Re: Securing Sensitive WO Information

His statement is specific Support Group not separate companies. -Original Message- From: Deepak Pathak To: arslist Sent: Fri, Aug 18, 2017 3:52 pm Subject: Re: Securing Sensitive WO Information ** I believe that feature is called

Re: Securing Sensitive WO Information

I believe that feature is called Multi-Tenancy. On Fri, Aug 18, 2017 at 10:34 AM, Rackley, James A CIV < james.a.rack...@uscg.mil> wrote: > Oh Mighty Brain Trust, > > What is the recommended method to ensure that users with Work Order > permissions CANNOT see a specific subset of WOs via Global

Re: [Non-DoD Source] Re: Securing Sensitive WO Information

I would think you could do this with a multi-tenancy setup. It should go across multiple platforms (analytics, smart reporting, ect). We have one customer with almost 300 companies setup for this very purpose. It works well. From: Action Request System

Re: ARS Wikipedia page

If the sales person and the person writing the SOW (1) and the project manager (2) stayed within the package guidelines as we had it written, 1 & 2 were almost a no-brainer. The things almost sold themselves to small and midsized businesses. #3… You never knew. But back then, our stable

Re: ARS Wikipedia page

Yes they usually came back for services and they almost ALWAYS bought more licenses as the 5 that came with the base package just wasn’t enough. More licenses = more reoccurring support revenue. And it was popular. I stayed on the road almost 100% for right at 2 years doing nothing but RR

Re: [Non-DoD Source] Re: Securing Sensitive WO Information

My apologies; we're running 9.1. Regards, Jim -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Roger Justice Sent: Friday, August 18, 2017 12:03 PM To: arslist@ARSLIST.ORG Subject: [Non-DoD Source] Re: Securing

Re: ARS Wikipedia page

Since I did a Rapid Results at BMC it need three things to be successful. Was it sold properly Was there a good project plan As you stated was there a knowledgeable consultant doing the work. -Original Message- From: Lee Cullom To: arslist

Re: Securing Sensitive WO Information

Please provide the release you are working on. There is nothing in the base capability to do this. -Original Message- From: Rackley, James A CIV To: arslist Sent: Fri, Aug 18, 2017 11:35 am Subject: Securing Sensitive WO Information Oh

Securing Sensitive WO Information

Oh Mighty Brain Trust, What is the recommended method to ensure that users with Work Order permissions CANNOT see a specific subset of WOs via Global Search, WO Console, Overview, AR Reporting, Analytics, or Smart Reporting? Essentially, only users in a specific Support Group should be able

CSRA: Opportunity for a Remedy Administrator in Arlington, VA – Active TS Clearance

CSRA has an immediate staffing requirement for a Remedy Administrator to join our Mission Critical Cyber Team located in Arlington, VA. The National Cybersecurity Protection System (NCPS) is an integrated system of intrusion detection, analytics, intrusion prevention, and information sharing

Service Target Stop Qualification?

Hi List Question about service targets. When building a custom target (in this case a stop condition) should any field that's in the form work as a qualifier? For example, if I want a stop condition when a workinfo type is created ('z1D_Work Log Type' = "Email System"), should that work? Or is