Is the external system creating the record?  That’s the key to the
create/modify using a read license.

Dave

On Wed, May 23, 2018 at 2:29 PM Joey Neff <remedy0...@gmail.com> wrote:

> Thanks Dave, but my concern is how to handle updates from external systems
> rather than simple updates.
>
> On Wed, May 23, 2018 at 10:04 AM, Dave Shellman <adshell...@gmail.com>
> wrote:
>
>> Custom applications can be created with the ability to submit records
>> using a Read license.
>>
>> My guess is that the ITSM Suite is also configured for submitters to
>> create records with a Read license.
>>
>> Dave
>>
>> On Wed, May 23, 2018 at 12:04 PM Joey Neff <remedy0...@gmail.com> wrote:
>>
>>> From BMC’s End User License Agreement:
>>>
>>> *BMC Remedy Products*:  Customer man not bypass or delay, in any way,
>>> the consumption of a concurrent or named user license to perform and
>>> activity that requires a user license (including, without limitation,
>>> submitting a ticket to a parallel form and then using workflow to perform
>>> and update without a license).
>>>
>>>
>>>
>>> Does BMC consider a User license to be an actual person or can the User
>>> License represent an external system that interfaces with Remedy?
>>>
>>> If a user license can represent an interfacing system such as Netcool
>>> or an externally customer facing portal, then how does that not violate
>>> the above restriction since a single “system” user could be performing
>>> updates that represent multiple users in that external system?
>>>
>>>
>>>
>>> Under Units of Measure, there is this statement:
>>>
>>> *Per third-party software: *A license is required for each installation
>>> of the third-party software product that interfaces with the Product.
>>>
>>>
>>>
>>> Is this referring to any external system interfacing with Remedy or for
>>> those applications developed and registered with BMC by an ISV?
>>>
>>> If this is referring to any external system interfacing with Remedy,
>>> then can it be assumed that if you provide that “user” with a fixed or
>>> floating license, that it can perform the same update functions that a
>>> person user could?
>>>
>>> --
>>> ARSList mailing list
>>> ARSList@arslist.org
>>> https://mailman.rrr.se/cgi/listinfo/arslist
>>>
>>
>> --
>> ARSList mailing list
>> ARSList@arslist.org
>> https://mailman.rrr.se/cgi/listinfo/arslist
>>
>>
> --
> ARSList mailing list
> ARSList@arslist.org
> https://mailman.rrr.se/cgi/listinfo/arslist
>
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

Reply via email to