Subject Date - DESC Rating Viewed Topic
Article Selected >> Considerations when setting up a service account to run utilities
What type of user should run the batch utilities at the command line or within an app that calls the iService web services?
There are a few things to consider when setting up accounts that will be running system processes (used to invoke web services, run the batch form submission utility at the command line, etc.). There is nothing unique about the user itself. iService sees its actions similar to any user that would be using the stock user interface.

(1) The account should not be used for interactive logon, because if a user logs out it could cause a process that is running under that userID to abort.

(2) The service account should have enough access rights to perform all the actions you are automating. Access rights are granted in the form of a) UserTypes and b) Segment Access. For instance, all agent userTypes (CSR, CSR Manager, Administrator, SuperUser) have the rights to perform contact searches, interaction searches, create notes, send agent emails, and create tickets. However, only CSR Managers and above by default have the rights to create new users or send mass mailings. The user should also have enough segment access to perform the actions desired. For instance, if the account is used to pull history for members it should likely have access to all segments (setup for the user in the Admin Tools - Agents - Details tab).

(3) You should consider using a userType that won't be accidentally downgraded or changed by another agent. Users can only change agent settings for people that are a level below themselves. So, only an administrator could change a CSR Manager and only a Superuser can downgrade an Administrator.

(4) There is a special consideration to consider when automating the import of new contacts. When a contact is created, it's assigned membership to all the segments to which the agent has access. This membership affects which agents can see their details when performing customer searches.

Using an administrator userType would ensure that only a superuser can change the account. If you are concerned about that account having too much access, you could probably use a CSR Manager if you are confident that your administrators know not to change it. However, it's very important to ensure that whatever userType you use has sufficient Segment Access to perform its actions.
Article DetailsSubscribe and Rate this article
Article ID:532473
Date Updated:7/3/2015 4:51:20 PM
# Views:2421
Article Creator:Scott Whitsitt
Article Topic:Batch Utility
Attachments:-- None --
Batch Utility Fields-update simple contact information 6/25/2010 11:09:01 PM None 1513 Batch Utility
Please Wait...