Running Jobs as a SAM Admin

[oberlel]

Hi all,

How do SAM Admins run jobs? We are working on direct integrations which the SAM Admin has the ability to configure in the tool, but you need developer access to run a job. As a SAM Admin, I can see the jobs results but not run.

For Instance, Adobe Connector has two jobs:

SAM - Import Adobe User Subscriptions &  SAM - Optimize Adobe Subscriptions.

After configuring the connection, I would have to wait until Saturday to see if it worked and pulled in data, contact a developer and have them run the job, or work with a developer to change the date so that it runs more frequently.  The SAM Optimize only runs monthly which means after I pulled in all the data, I could potentially have to wait a month to see the optimization and after cleaning up those suggestions, wait another month to see how well it did.

I cannot be assigned a SAM Developer role, because I am not a developer and I wouldn't want those rights. SAM Admins should be able to run any job that is within the module ad hoc. 

Has anyone experienced this?  

[dbook]

Thanks @Taksh , I think there is a subtle difference that I hadn't quite registered. 

It is possible for a user with the sam_integrator role to execute Okta/Entra ID schedules under SSO Integration profiles. (Record is held in sam_sso_sysauto_script) 

It's Direct integration profiles where this is currently the gap and requires a system admin to execute on demand. (Record is held in sysauto_script) 

[Taksh]

Hi @dbook , yes, you're right. 
An enhancement idea can be submitted to bridge the gap of direct integration.

[oberlel]

Hi @dbook,

I already have the sam_integrator role. Unfortunately, that doesn't allow you to execute jobs on demand only setup the integrations. 

[dbook · Accepted solution]

This will require a change to the ACLs for 'sysauto_script', it's possible to configure this but would require your System Admin to perform, you need to have read access to the relevant records.