Skip to main content
Kinetic Community

Kinetic Sample Change Create

Creates an entry in the KS_SAMPLE_Change form based on information input by the end user. There is no processing that is done in this handler. All data is simply passed through and some values are hard coded in the node.xml.

Downloads

By downloading this file, you acknowledge that you agree to our Terms of Service

kinetic_sample_change_create_v2.zip

Detailed Description

The KS_SAMPLE_Change form is a sample Change Request form with a limited number
of fields on it.  This handler is designed to create a record in the
KS_SAMPLE_form by merely passing though the values input by the user as well as
setting some that are hard coded into the handler.  The two date fields on
KS_SAMPLE_Change require data in the ISO 8601 format so that must be supplied to
the handler.  The handler returns the Entry ID of the record that it creates.

Parameters

Name Description
Change Name A name given to the change request.
Description A description of what the change request is for.
Risk The Risk assigned to the change request.  The options are Minor, Standard and Critical.
Priority The Priority assigned to the change request.  The options are Minor, Standard and Critical.
Impact The Impact assigned to the change request.  The options are Low, Medium and High.
Start Date The date/time that the change request is supposed to start.  The field in Remedy that this pushes to is a Date/Time field.  These types of fields only take data passed to them in the ISO 8601 format.
End Date The date/time that the change request is supposed to end.  The field in Remedy that this pushes to is a Date/Time field.  These types of fields only take data passed to them in the ISO 8601 format.
Category The 'Category' element of the categorization of the change request.
Type The 'Type' element of the categorization of the change request.
Item The 'Item' element of the categorization of the change request.
Submitter The Submitter of the change request.

Sample Configuration

Parameter Example Configuration
Change Name <%=@answers['Change Name']%>
Description <%=@answers['Change Description']%>
Risk Minor
Priority Minor
Impact Low
Start Date <%=@answers['Start Date']%>
End Date <%=@answers['End Date']%>
Category Hardware
Type Server
Item Upgrade
Submitter <%=@answers['Req By']%>

Results

Name Description
Entry Id The 'Request ID' of the change request that gets created.

Change Log

Version Date Description
2 2014-03-07 This handler is safe to use in a subtree because it does not rely on any @base 
information to process. All data is passed into the handler as parameters.
1 2010-01-14 Initial version