Different types of licenses in bmc rmedy

The end user interface for this module allows viewing of the repository via the Remedy User tool with methods to view: Information collected in the repository includes:Дefinition of object at the time of change The user interface for repository access is accomplished using standard Remedy forms. Server events are communicated to ARSOH through a configurable polling interval. ARSOH will compensate for name changes to workflow objects using the ARSystem server events feature. The strain ID persists from the time of object creation to the time of object deletion. A strain ID will be created for each object to uniquely identify each object. The Object Audit Daemon captures changes to ARSystem workflow objects and stores the definition in a central repository. The main object audit daemon has the following characteristics: This does not include flashboards, flashboards data sources, flashboard variables, flashboard alarms, DSO mappings, or DSO pools. This includes forms, fields, form views, active links, filters, escalations, containers (active link guides, filter guides, applications, and packing lists), and menus. Target operating systems for the first release include all platforms that support java.ДЄRSOH is capable of supporting all ARSystem workflow objects for which a Remedy server event is generated. The daemon is capable of listening to events from multiple ARServer instances. ARSOH is a filter plugin which enables Remedy administrators and developers to maintain a running history of changes to ARSystem workflow objects in a centralized repository.

Different types of licenses in bmc rmedy