CLIP 5.04.00, May 2016
We're pleased to present CLIP V5.04.00
High Availability (HA) and Scalability for CLIP
CLIP V5.04 extends previous HA capabilities by adding a new, clustered deployment model that allows for
- High Availability : HA is achieved by replicating CLIP instances and run it in a HA cluster
- Automatic failover: failover does not require any manual intervention
- Automatic recovery: should a failed CLIP instance come up again, it is available instantly and automatically performs a recovery procedure
- Scalability: all requests can be distributed among the CLIP instances of the cluster, the cluster can run in Active/Active or Active/Passive mode
CLIP for HP BSM for ServiceNow: New option for direct integration without "Update Set"
In former versions, CLIP for HP BSM required the upload of a ServiceNow "Update Set" or the installation of AppLink's "Scoped App" for CLIP from the ServiceNow AppStore. These contain the Web Service endpoint, transform map, business rules, scripts, menus etc. used by CLIP to create incidents and trigger incident updates to be reported back to HP BSM.
Even though the use of the "Update Set" / "Scoped App" is still the recommended option for the integration, CLIP V5.04 now offers a "direct" integration into ServiceNow without use of an "Update Set" or "Scoped App"– incidents can be created directly in the ServiceNow Incidents table. Using this mode, CLIP actively polls for changes of incidents to update the OMi events accordingly.
This option can be used if
- company policies refuse to apply additional configurations to your ServiceNow instance for the integration into HP BSM
- a more simple approach is favored - no maintenance is necessary on ServiceNow release changes
CLIP for HP BSM for Salesforce: New integration to RemedyForce and the salesforce.com platform
CLIP V5.04 includes an integration module to integrate with the salesforce.com platform. Utilizing the new CLIP module for salesforce.com, CLIP provides an out-of-the-box standard integrations into BMC RemedyForce.
Extended CLIP variable scopes
CLIP supports extended access to attributes of related events and incidents in the rules to update events and incidents. Example use cases for this feature include:
- on incident creation, CLIP can auto assign the event to OMi operators and groups dependant of the submission type and only after initial submission by evaluating event and incident attributes
- update the incident state dependant dependant of event state and other event attributes and the current incident state by lookup of the current incident state, e.g. an incident can be closed if the event is closed but only if the current incident state is "New" so it was not yet assigned
CLIP for HP BSM OMi: CLIP can do various kind of OMi event manipulations to show data of an related incident in the "forwarding tab", custom attributes, annotations, change state, severity and priority etc. The current CLIP version also allows to auto assign an event to an OMi user and group using the attributes "assigned_user" and "assigned_group" in ClipConfig.xml.
For changed features and issues fixed, please refer to the ReleaseNotes in the "Downloads" area under "Information & Documentation" as a registered and logged in user.