Update UI Action - Create Change

[becks_kirk]

I have a request from our change team to look into this issue.

When an incident has been identified to require a Change to resolve the incident, the "Create Change" UI Action link under Related Lists is usually what the user will click to get the change request started. This is OK, the problem is the record is inserted on the table and we have mandatory fields that need to be filled in as part of submitting a change request that cannot be auto populated from the Incident. Since the change record is saved through the UI Action that runs, the mandatory fields not filled in continue to show as required, but because the record has already been inserted on the change request table, a user can navigate away from the CR without filling in these details. The change team then pulls teeth (insert all the complaints here about empty change requests) to find out the rest of the CR detials. Turns out most of the time the users 'didn't mean' to click on the link and navigate away instead of canceling their false change request.

Is there a way to keep the link, but not save the record immediately to the change request table? I still want to pull in the data that auto populates, I just don't want the record to auto save so that users have to fill in the info if the CR is legit.

This is what my current UI   Action record for Create Change looks like... what are your recommendations?

[Michael Fry1]

What if you put a Confirmation message on the UI Action. Something like: Are you sure you want to create a Change Request? then if they click cancel, nothing is created.

[becks_kirk]

That would probably be ideal. Thank you for the suggestion.

[souren0071]

Hi everyone,

It's a very intersting requirement. Even if we put a confirmation while

raising the request, user might confirm and raise the change and record

will be inserted. So assign rule will work during the insertion of the

ticket and get assigned to respective teams without putting the mandatory

fields which were not mapped from the incident.

I'm looking for a solution like this. If anyone use the related link which

will open up a new change request form with the fields populated from

incident but don't get inserted. So user must have to put the mandatory

fields in order to submit or save the form.

It's little difficult to mapp field from other table client side. We need

to find out some other solution to achive it.

Regards,

Souren

On 19 Oct 2017 12:25 am, "becks_kirk" <community-no-reply@servicenow.com>

[GoBucks]

Any luck with this request?  I was looking to achieve the same thing.  I do not like how the "Create Change" UI action inserts a record without giving one the opportunity to make field modifications first, prior to a potential insert.