Automatic association of accounts to templates using call back functions
Compatible for 14303 build
This KB is used when the user wants to associate the accounts to template automatically using callback functions. Below are the configuration steps to be followed in order associate an account to template.
STEPS:
1. Create a global function with
Function Name--> Get Configurations
Return type--> Map
API Name--> getconfigurationfor
Parameters--> configname - String
and save the content under filename Get Configurations.txt.
2. Create one more global function with
Function Name--> Generate Response
Return type--> Map
API Name--> generateresponse
Parameters-->
parameter_map - Map
method - String
configname - String
url - Stringand save the content under file name Generate Response.txt.
3. Create a callback function with
Function Name--> Update account of template
Return type--> Map
API Name--> updateaccount
Parameters-->
accountid - int
templateId - int and save the content under file Update account of template.txt
Once the custom call back function is saved, "URL to execute this Custom Function" will be generated.
How to invoke this custom call back function
Method : POST
URL : Copy paste from custom call back function
for example--> http:/abc.com/AppIntegrations?serviceName=callbackFunctions&api_name=updateaccount&auth_token=5d7ec0c8966a138c281265c16d118590d0e285379cf8bca665dcc2324b71933fe06107b4416146f2d84c2c0ed7bba722a5e3047adeae7a56ddcc2110107b9fbfdc3cd92e&PORTALID=1
Body form data
rawDataContent={"accountid":"901","templateId":"2401"}
Note: replace 901 with accountid, replace 2401 with templateid. For now only one accountid and templateId can be passed.New to ADSelfService Plus?
Related Articles
How to restrict automatic association of technicians to an account / sites ?
This article is applicable from 10600 builds. Scenario - At times the technicians will see extra Accounts / Sites in their login. Below is the reason and its solution : -> While creating an account, a common site will be automatically created by ...Hide templates from drop-down while using a specific template using FAFR
The below script can be used in the respective incident template under Form Load section of Field and Form Rules. if(["Application Crashes Frequently","New incident"].indexOf(jQuery("select#template_box").select2("data").text)==-1){ ...Disable Default Template - Using FAFR
1. Navigate to Admin>Incident Template>> Edit Default Template 2. Select Field & Form Rules Tab 3. Select On form Load 4. Make sure to select "Applies to Technicians" and set the action as Execute Script and paste the below script ...Account specific request template: Redirection to requester's account based template from default template using FAFR
Tested in builds 14000, 14200 and 14201 (Global FAFR): Step 1: In Global FAFR, on form load, configure an FAFR and execute the below script under Action as shown below, try{ $req.form.destroyForm(undefined, false); }catch(err){} ...Customize the category list/selection based on template.
The Category applies to all the templates in SDP-MSP. You can hide them using the field and form rules to make them unavailable for users. Under Admin >> Incident Template >> Edit the template in questions >> Field and Form Rules tab. You can create ...