Script Hellp!!

[vidishaagarwal5]

I need to Allow user to generate "Security Incident" via normal Incident record but we have to make sure that logged in user has access to "Security Incident" Table?

[Ravi Gaurav · Accepted solution]

Hi @vidishaagarwal5 

There are two methods to verify users access for any glide record.

1. Use GlideRecordSecure API while creating security incident. This API implicitly verifies if user passes ACL access on table.
2. Use canRead or canWrite function. These functions implicitly verifies if logged in user satisfies ACL access.

[Ravi Gaurav · Accepted solution]

or you can opt the below options:

Option 1: Use gs.hasRole() if specific role exists

If your instance uses a dedicated role like sn_si..special_access_write_manager or sn_si.admin, then your UI Action’s Condition field can simply check that:

gs.hasRole('sn_si..special_access_write_manage') || gs.hasRole('sn_si.admin')

This ensures only users with proper Security Incident access see or use the button.

---

Option 2: Use ACL-based table access check

If access is more dynamic (driven by ACLs rather than roles), then you can check access programmatically in your script.

Example (in your UI Action script):

if (!gs.hasRole('sn_si.admin')) { var canAccess = GlideTableDescriptor.get('sn_si_incident').canWrite(); if (!canAccess) { gs.addErrorMessage('You do not have permission to create a Security Incident.'); action.setRedirectURL(current); return; } } // Proceed to create the Security Incident var si = new GlideRecord('sn_si_incident'); si.initialize(); si.short_description = current.short_description; si.caller = current.caller; si.description = current.description; si.insert(); gs.addInfoMessage('Security Incident ' + si.number + ' has been created.'); action.setRedirectURL(si);

---

Option 3: Hide or disable the UI Action entirely

If you want the “Create Security Incident” button to only appear for users with access:

Set the Condition on the UI Action as:

GlideTableDescriptor.get('sn_si_incident').canCreate()

[GlideFather]

Hi @Ravi Gaurav, thank you for the documentation. I am aware of that and that's actually why I was curious about the role you mentioned >>> sn_si.security_incident_writer:

Can you please share where does sn_si.security_incident_writer come from?

Thank you

[GlideFather]

Please @Ravi Gaurav maybe you should inform @vidishaagarwal5 that you edited a reply which was originally accepted for the solution....

And when you edit your comment to hide the fact that you used non existing role, be careful about the formatting and two dots :)))

But it's really interesting that @vidishaagarwal5 asks a very general question, @Ravi Gaurav nor @Sarthak Kashyap need no further explanation of the issue, both answered a few minutes after posting a question and both deliver the exactly desired solution 😄 just wooooow! 

And the solution: @Ravi Gaurav replies with non existing roles and @Sarthak Kashyap with a custom field 😄 so none of your examples could work in real world... unless nobody even tried if it works but that wouldn't be nice, right? :))) 

[Sarthak Kashyap · Accepted solution]

Hi @vidishaagarwal5 ,

Please try below solution

Create a Before BR where table is Incident, After insert and advance checked and add below code 

(function executeRule(current, previous /*null when async*/) {

    var siGR = new GlideRecordSecure('sn_si_incident');
    if (!siGR.canCreate()) {
        gs.info('User does not have permission to create Security Incident.');
        return;
    }

    var si = new GlideRecord('sn_si_incident');
    si.initialize();
    si.short_description = current.short_description;
    si.description = current.description;
    si.caller = current.caller_id;
    si.source_incident = current.sys_id; 
    var newSI = si.insert();

    current.u_related_security_incident = newSI;

    gs.info('Security Incident created: ' + newSI);

})(current, previous);

Please mark my answer correct and helpful if this works for you

Thanks and Regards,

Sarthak

[GlideFather]

Hi @Sarthak Kashyap,

the following field is custom, no?

u_related_security_incident

How did you know that @vidishaagarwal5 uses a custom field without telling you about it? You can read minds? 😮 

[Sarthak Kashyap]

@GlideFather ,

I can create some custom feilds and store the reference, this is very general thing.