Infrastructure methods and systems for extending customer relationship management platform
Systems and methods are disclosed with respect to extending customer relationship management platform, in particular, providing purpose made components to provide desired functionality. Embodiments are disclosed herein for translation multi-category data requests into single category requests; blocking or controlling browser operation; implementing security access and control over customer data requests; and file management functionality. The systems and methods may be implemented in a user system to extend the functionality of a customer relationship management platform.
1 . A computer-implemented method for handling requests of a first type from a user system and converting them to a second type for a customer relationship management system, the method comprising:
receiving, at one or more processors, a customer data request in a multi-category format from the user system,
wherein the customer data request: (i) includes a request to manipulate customer data stored at the customer relationship management system, and (ii) is based on a data flow software design pattern; and
wherein the multi-category format structures data requests to be handled by a model-view-controller designed system;
determining, at the one or more processors, a type for the customer data request based on the multi-category format,
wherein the type for the customer data request based on the multi-category format is based on a different software design pattern;
converting, at the one or more processors, the customer data request in the multi-category format to a single category format corresponding to the customer relationship management system,
wherein the converting includes determining, via a translation engine including a request handler and a translation generator, if the customer data request needs to be translated and generating, when the customer data request needs to be translated, a translation of the data request,
wherein converting the customer data request in the multi-category format to the single category format corresponding to the customer relationship management system does not change the user system, and
wherein converting the customer data request in the multi-category format to the single category format corresponding to the customer relationship management system includes converting the customer data request into a single web page architecture executable by the customer relationship management system; and
generating, at the one or more processors, a set of access controls for the user based on validating a security level of the user;
transmitting, at the one or more processors, the customer data request including the set of access controls to another computing system.
2 . The computer-implemented method of claim 1 , wherein the user system is a customer management system for an insurance agent.
3 . The computer-implemented method of claim 1 , wherein receiving the customer data request further comprises:
transmitting, at the one or more processors, the customer data request to the translation engine.
4 . The computer-implemented method of claim 1 , wherein determining the type for the customer data request further comprises:
transmitting, at the one or more processors, the customer data request to the request handler.
5 . The computer-implemented method of claim 1 , wherein determining the type for the customer data request further comprises:
determining, at the one or more processors, the request to manipulate customer data stored at the customer relationship management system; and
determining, at the one or more processors, a set of subsequent operations to be taken based on the request to manipulate.
6 . The computer-implemented method of claim 5 , wherein converting the customer data request in the multi-category format to a single category format further comprises:
generating, at the one or more processors, a single category format data request corresponding to the type for the customer data request; and
augmenting, at the one or more processors, the single category format data request with a set of user data and the determined set of subsequent operations.
7 . The computer-implemented method of claim 3 , wherein converting the customer data request in the multi-category format to a single category format further comprises:
transmitting, at the one or more processors, the customer data request to the translation generator.
8 . The computer-implemented method of claim 1 , wherein converting the customer data request in the multi-category format to a single category format further comprises:
generating, at the one or more processors, a single category format data request corresponding to the type for the customer data request; and
augmenting, at the one or more processors, the single category format data request with a set of user data and a set of requested operations from the customer data request.
9 . The computer-implemented method of claim 1 , further comprising:
monitoring, at one or more processors, a user system for an application start event;
determining, at the one or more processors, a type of application that has been opened based on the application start event;
generating, at the one or more processors, a custom cross-site scripting object based on the type of application; and
transmitting, at the one or more processors, the custom cross-site scripting object to a browser application corresponding to the application start event.
10 . The computer-implemented method of claim 9 , further comprising:
preventing, at the one or more processors, access to a customer relationship management system when the custom cross-site scripting object is successfully instantiated at a web page received at the browser application.
11 . The computer-implemented method of claim 9 , wherein the application start event includes data indicative of a software application beginning operation.
12 . The computer-implemented method of claim 9 , wherein determining a type of application that has been opened, further comprises:
transmitting, at the one or more processors, the application start event to a browser monitor.
13 . The computer-implemented method of claim 9 , wherein the type of application to be identified is a browser application.
14 . The computer-implemented method of claim 9 , wherein the custom cross-site scripting object is a JavaScript object.
15 . The computer-implemented method of claim 9 , wherein generating a custom JavaScript object, further comprises:
transmitting, at the one or more processors, the type of application to an object generator.
16 . The computer-implemented method of claim 15 , further comprising:
receiving, at the one or more processors, a cross-site scripting object from the object generator.
17 . The computer-implemented method of claim 9 , wherein transmitting the custom cross-site scripting object to a browser application, further comprises:
instantiating, at the one or more processors, the cross-site scripting object based on a web page received at the browser application.
18 . The computer-implemented method of claim 1 , further comprising:
receiving, at one or more processors, a customer data request from a user, wherein the user has a dataset indicative of an agent profile;
determining, at the one or more processors, a security level for the user based on the agent profile;
validating, at the one or more processors, the security level for the user based on the agent profile;
generating, at the one or more processors, a set of access controls for the user based on the validation; and
transmitting, at the one or more processors, the customer data request augmented with the set of access controls to a customer relationship management platform.