[go: up one dir, main page]

WO2019060618A1 - Systèmes et procédés de demande, de suivi et de rapport de modifications apportées à un enregistrement - Google Patents

Systèmes et procédés de demande, de suivi et de rapport de modifications apportées à un enregistrement Download PDF

Info

Publication number
WO2019060618A1
WO2019060618A1 PCT/US2018/052056 US2018052056W WO2019060618A1 WO 2019060618 A1 WO2019060618 A1 WO 2019060618A1 US 2018052056 W US2018052056 W US 2018052056W WO 2019060618 A1 WO2019060618 A1 WO 2019060618A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
records
record
action
logic
Prior art date
Application number
PCT/US2018/052056
Other languages
English (en)
Inventor
Doug RYBACKI
Natasha REID
Amy J. REAMS
Original Assignee
AppExtremes, LLC, d/b/a Conga
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US15/826,026 external-priority patent/US11182549B2/en
Application filed by AppExtremes, LLC, d/b/a Conga filed Critical AppExtremes, LLC, d/b/a Conga
Publication of WO2019060618A1 publication Critical patent/WO2019060618A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/107—Computer-aided management of electronic mailing [e-mailing]

Definitions

  • the present invention is generally directed toward systems and methods of selecting and modifying a record, by way of example, a record contained in a customer-relationship management (CRM) data repository. More particularly, the present invention relates to a system for requesting, tracking and reporting modifications to a record via automated, semi-automated and/or synchronous processes.
  • CRM customer-relationship management
  • Typical CR systems contain a variety of information displayed in a variety of different manners. However, the information is not easily visualized in a format that is efficient or convenient for a user to navigate, manage and act upon. In addition, the present limitations on these systems make it difficult, if not impossible, for a user to flag a record that requires further action and assign another user with the task of modifying that record, or reporting to one or more users that action has been taken on a record. Further, current CRM systems contain limitations with respect to tracking modifications once made by another user, or multiple users, over time. Thus, CRM systems presently suffer from a number of shortcomings with respect to managing information and/or modifying information contained within a data repository and accessible by multiple users.
  • a specific record may be modified several times by several different individual users.
  • action on a record may be requested by multiple users (referred to as "Requester(s)”), and in other embodiments may be assigned or requested of multiple users (referred to as “Requestee(s)").
  • the systems and methods described in detail herein may comprise one or more graphical displays for conveying the status of a request, whether the user is a requester, requestee or merely copied on the request.
  • the systems and methods also comprise graphical displays for notifying or alerting a user of an action or inaction made on one or more records.
  • graphical displays convey additional information to a user, such as the result of the action, the details of a modification, the synchronization or reconciliation of an action, or other discrete components or steps of the systems and methods described herein.
  • synchronization may be configured to occur automatically or semi-automatically. Synchronization may also occur amongst user displays, and records may be automatically or semi-automatically reconciled by way of the systems and methods described herein.
  • Messaging may take the form of a notification or an alert, and priorities for messaging/alerts may be preconfigured by one or more users.
  • a computer readable storage medium comprising processor executable instructions operable to utilize the system or perform the methods is provided.
  • each of the expressions “at least one of A, B and C”, “at least one of A, B, or C”, “one or more of A, B, and C", “one or more of A, B, or C" and "A, B, and/or C” means A alone, B alone, C alone, A and B together, A and C together, B and C together, or A, B and C together.
  • machine-readable media refers to any tangible storage medium that participates in providing instructions to a processor for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media.
  • Non-volatile media includes, for example, NVRAM, or magnetic or optical disks.
  • Volatile media includes dynamic memory, such as main memory.
  • Computer-readable media include, for example, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, magneto-optical medium, a CD-ROM, any other optical medium, a RAM, a PROM, an EPROM, a FLASH-EPROM, a solid state medium like a memory card, any other memory chip or cartridge, or any other medium from which a computer or like machine can read.
  • the computer-readable media is configured as a database
  • the database may be any type of database, such as relational, hierarchical, object-oriented, and/or the like. Accordingly, the invention is considered to include a tangible storage medium and prior art-recognized equivalents and successor media, in which the software implementations of the present invention are stored.
  • module refers to any known or later developed hardware, software, firmware, machine engine, artificial intelligence, fuzzy logic, or combination of hardware and software that is capable of performing the functionality associated with that element. Also, while the invention is described in terms of exemplary embodiments, it should be appreciated that individual aspects of the invention may be separately claimed.
  • FIG. 1 illustrates a display for reviewing and identifying records in accordance with a preferred embodiment of the present disclosure, including a menu containing the option to request an action taken with respect to one or more records;
  • FIG. 2 illustrates a display for identifying the Requestee(s) and providing instructions associated with the request for action in the embodiment of FIG. 1;
  • FIG. 3 illustrates a display for presenting the status of a previously initiated request for action from the viewpoint of the Requester
  • FIG. 4 illustrates a display for presenting the status of a request for action from the viewpoint of the Requestee.
  • the present disclosure in varying embodiments, relates to systems and methods for requesting action with respect to one or more records, such as a record contained in a CRM system, and monitoring and reporting action taken in connection with the request and the one or more records.
  • the present disclosure in embodiments includes systems and methods for tracking activity of a user(s) relative to the one or more records subject to a request.
  • the present disclosure also comprises systems and methods for monitoring the status and completion of action(s) taken with respect to one or more records, and reporting modifications made to one or more users.
  • These foregoing systems and methods are preferably associated with records contained in one or more data repositories, including but not limited to CRM data repositories.
  • systems and methods of the present disclosure provide the ability of a user to request action be taken on a particular record or records contained in a data repository. For example, a user may flag one or more records and request that a different user (or in certain embodiments, multiple other users) take action on the record(s) and modify the records accordingly. For example, certain information relating to a date may be missing or incomplete for a given record.
  • the user of the system may first identify the missing or incomplete fields and the associated records, and then assign a user or multiple users to complete the missing or incomplete fields.
  • the systems and methods further comprise notifications and alerts to the requesting user and other users, and further comprise automatic or semi-automatic reconciliation and/or synchronization, as described in detail herein.
  • the system and method may be implemented in connection with a data repository or database.
  • the data repository may be a CRM system, such as Salesforce, and comprise a variety of different records and record types.
  • different records and record types are routinely queried, searched, sorted, filtered, accessed, viewed, manipulated, modified, updated, added, deleted, recreated, revised, synchronized, reconciled and/or verified by multiple users during the course of a business day, week, month, etc.
  • one or more software modules may be employed by a user to search, access, view, manipulate, modify, update, sort, filter, organize, prioritize, reconcile and navigate through the various different records and record types.
  • the data repository or database may reside in a variety of locations, including on a storage medium local to or resident in one or more of computers. In one embodiment, the data repository or database may reside in a storage-area network ("SAN"), although any necessary files may be stored locally on one or more computers.
  • the data repository or database may be a relational database adapted to store, update, and retrieve data in response to SQL-formatted commands.
  • the database can be any storage mechanism, whether hardware and/or software, for storing and retrieving data, including by example but not limitation, a Hadoop architecture.
  • a database server is provided to communicate with the database and to manage the data within the database.
  • the database is a relational database and the database server is a SQL server.
  • One or more web servers are preferably provided to facilitate communication with user devices.
  • the web server preferably receives data or requests for data and communicates with the database server to store or retrieve the data.
  • the web server functions as an intermediary to put the data in the database into a usable form for viewing and manipulation via the user devices.
  • a software module (occasionally referred to herein as Conga Grid) may be employed in connection with the systems and methods described in this application.
  • the Conga Grid module is preferably used in conjunction with a CRM or other data repository, and permits a user to more efficiently manage, visualize and navigate data, which in many data repositories is displayed in a "list" view (and therefore difficult to organize, sort and manage).
  • the Conga Grid module may also be configured for use with data repositories that display data in a format other than a "list” view.
  • the Conga Grid module further allows a user to add fields or edit existing fields for certain records directly and without opening additional windows or forms in a separate application.
  • the editing capabilities of Conga Grid further comprise advanced filtering, such that records requiring action (or that have been neglected due to inaction) may be easily viewed and flagged by one or more users.
  • a display 100 is shown with multiple rows 110, columns 120 and column headings 130.
  • various fields and records may be displayed in a grid format, which permits a user to quickly search, sort, filter and locate a particular record or a particular field within a particular record.
  • one benefit of the systems and methods described herein is to provide a user with the ability to visualize one or more records and identify where information (i.e., fields) included in a record is missing or incomplete.
  • the records stored in the repository may be viewed in a database or spreadsheet format such that various information (i.e., fields) associated with the records are visible to, and in many embodiments readily identifiable by a user. This format permits a user to quickly recognize information that is missing or incomplete for a given record and take appropriate action.
  • the user is preferably provided with the ability to select a record 150, or a field 160 within a record 150, and prompt a menu 180 of options for further processing of information associated with the field 160/record 150.
  • this menu 180 may be in a pick list format. In other embodiments, this may appear as a dialog box or other display.
  • the user is provided with the option to request an action 190 be taken with respect to any one or multiple records.
  • the user may select more than one record 150 and/or field 160, if desired, and request multiple actions with respect to the same, as shown in Figure 1. If the user selects the Request Action 190 item from the menu 180, that step may prompt the user to supply more information, which is described below in connection with Figure 2.
  • a user who identifies the missing or incomplete record may provide the missing information directly. For example, a user may provide case comments, update opportunities or influence active or pending deadlines associated with a particular Salesforce record. Dialog boxes or other prompts may solicit this information directly from the user. A user may also update the status of a record or open and close records and/or sub-records associated with one or more records by providing input directly into those fields.
  • more than one user may be associated with a request (i.e., multiple Requesters). In certain embodiments, more than one user may be requested to take action on a record (i.e., multiple Requestees).
  • a display 200 is shown where the system prompts the Requester to identify the Requestee(s) 210 and provide specific instructions for modifying a record or records associated with the request for action.
  • the prompt is in the form of a dialog box, where the user is free to insert written instructions 220 to the identified Requestee(s) 210.
  • the instructions 220 may be selected from a pick list or prepopulated menu.
  • the instructions 220 may be automatically generated based on the nature of the missing information in the associated record(s).
  • the system is preferably unconstrained with respect to associating a request with one or several users, and in certain embodiments further comprises the ability to assign unique requests to specific users, each having a specific assignment to complete in order for the record to be successfully modified and thereby completed. Variations on this embodiment and the number of requests, Requesters and Requestees is contemplated with the systems and methods described herein.
  • the system may comprise one or more indicia to indicate that a field is missing or incomplete.
  • a cell in the grid or database formatted display may be highlighted or displayed in a different color than the remaining cells, such as in Figures 1 and 3-4.
  • the information contained in the cell, or in an associated row or column of the cell may be shown with a visual icon.
  • FIGs 3-4 multiple graphical displays are shown with the views of the records on which action has been requested from both the Requester and the Requestee' s perspective.
  • the Requester display now includes an icon 310 next to each of the records where that particular user requested an action be taken.
  • the icon 310 is in the form of a clock, although other icons 310 may be displayed and are described in greater detail herein.
  • the Requestee display includes a different set of icons 310 associated with the records that have been specifically requested of that user to modify.
  • the records that are subject to pending requests are also highlighted or painted in a different color than the non-requested records, which can assist the user in identifying the particular records requiring modification or other action.
  • the grid or database display may be automatically or manually configured to push all the missing or incomplete records to the forefront of a user's display. For example, those records that contain missing data (i.e., empty fields) may be automatically pushed to the top of the grid or database. Records that have some information but are incomplete may be pushed to the top but following the list of records that have empty fields.
  • the user may sort and filter one or more rows or columns of the grid display manually in order to identify those fields that are empty or incomplete.
  • the actions of sorting and filtering may be achieved through conditional formatting, and may be accomplished by sorting or filtering more than one field, column or row simultaneously.
  • a system for generating messaging between users for notifying either a request for action or a subsequent action taken in connection with a record.
  • This messaging may be manually initiated, but in a preferred embodiment occurs automatically once an action is requested or taken directly by a user.
  • messaging may be initiated at the point where a user has identified a missing or incomplete record and assigned an action to another user.
  • the messaging may be generated to appear in a variety of different formats, including direct messaging, text messaging, electronic mail messaging or equivalent messaging formats.
  • the messaging described herein may be achieved through a messaging framework comprising logic and/or instructions for sending notifications, alerts, instructions, etc. from one user of the system to at least one other user.
  • the messaging may be achieved through Salesforce chatter.
  • the messaging may be configured to automatically send a message from a Requester to a Requestee.
  • the Requestee may list one or multiple Requesters, and may identify one or multiple Requestees to receive the request, in which case the messaging would be received by each of the identified users.
  • the messaging function once initiated, remains active during the pendency of the assigned actions and is bi-directional (i.e., messaging may occur from the Requestee to the Requester as actions are completed).
  • messaging may also be generated to inform the associated users of the modification to the record(s) impacted by the request. For example, if Requestee is assigned the action of updating a date field associated with a particular record, and after viewing that request updates the record to include the relevant date, a message may be automatically generated to the Requester(s) from the Requestee to indicate that action has been taken. If the Requestee does not have all the information needed to take a complete action, in certain embodiments the Requestee may generate a new request and assign that action to a different user (i.e., a new Requestee).
  • the system may comprise a field listener function to automatically generate messaging post-action.
  • the field listener is preferably configured to listen for activity with respect to the field, and once a modification is made to that field automatically generate the messaging described herein.
  • the messaging is sent through Salesforce chatter messaging.
  • the system further comprises the ability to graphically display the status of a request for action, including actions initiated (i.e., outbound requests) by a Requester and actions received (i.e., inbound requests) by a Requestee, so that actions assigned by or to a user may be more easily reviewed and the status of those actions may be more efficiently managed.
  • the indicia or icon 310 described above may be applied to any of the fields or records associated with the data repository.
  • a specific icon 310 may be associated with a field, row or column of a particular record that indicates a request has been made by the user with respect to the record, or alternatively that a request has been received by the user with respect to the user, or both.
  • the icons 310 may further be contained in a separate field of the grid or database display and therefore more easily flagged, sorted or filtered relative to the other fields in the grid or database display.
  • the icon 310 may be configured to be removed once a certain action has been taken, or alternatively may change to a different icon 310 if the requested action is not made within a certain prescribed period of time, or if the assigned action increases or decreases in urgency.
  • the icon 310 assigned to an inbound request may appear in a certain color, and after the passage of time be automatically updated to appear in a different color to reflect that the action has been pending but not acted on for that period of time.
  • the Requester may assign the period of time.
  • the system assigns a default period of time based on the nature of the action requested. Variations on these concepts are contemplated for purposes of the present disclosure.
  • the system may further comprise the ability to hover over an icon 310 to view information associated with (1) the Requester, (2) the request, (3) the importance or urgency of the request, (4) the time limit or deadline associated with the request, or (5) the record or records impacted by the request.
  • a user may easily view information associated with a requested action to determine the information requested and the urgency of the request for any received requests in the user display. This information may appear, for example, when a user hovers a pointer (or equivalent) over the field where an icon 310 appears indicating a request, or alternatively over the field that has missing or incomplete information.
  • the application is also preferable configured to provide notifications or alerts.
  • Alerts may be provided via the module (e.g., notification upon login, push notification), email, messaging, or any other suitable method of communication to the user.
  • Alerts may be defined for certain conditions, for example, modification occurring to one or more particular records or fields. Alternately, alerts may be provided for continued modification or approval of an updated record by another user.
  • an alert may indicate a recommended course of action. For example, the alert may recommend that additional action be taken, or that a different Requestee be included in order to update the record.
  • the functionality described herein may be achieved by way of conditional formatting, which allows a module to display data in a Salesforce repository in an actionable, grid or database fashion. Additional functionality, such as the ability to dynamically filter and sort the information contained in rows or columns of the grid or database, further enhance the system and a user's ability to quickly identify fields with missing or incomplete information.
  • Methods for using the system and modifying a record are also provided.
  • the methods may comprise one or more of the following steps: (1) identifying one or more records located in a specific repository; (2) requesting action with respect to one or more records; (3) initiating the action requested with respect to one or more records; (4) tracking the action or inaction taken with respect to one or more records; (5) reporting modifications made to one or more records; and, in certain embodiments, (6) synchronizing or reconciling the action or inaction taken with respect to the one or more records within the specific data repository or another data repository.
  • the user initiates a method with the step of accessing a record.
  • the user selects the record and initiates a request for action on that record.
  • This step may entail identifying and selecting one or more Requestees, identifying and selecting additional Requesters, and providing instructions or comments to the users responsible for modifying the record(s).
  • the Requester completes the request for action and submits the request to the selected Requestees.
  • the step of initiating a request for action also initiates a method for messaging the users involved in the modification of the record.
  • the request for action may automatically initiate messaging to one or more users associated with the request, and once action is taken may generate additional messaging. This method may occur simultaneously or in near real-time to the actions being taken by the Requester and Requestee.
  • the messaging may be tied to the step of supplying a listening agent, which is configured to generate a message when a field the listening agent if directed towards experiences a change in status.
  • the listening agent may also be configured to generate additional messages when complete action has been taken and/or the requested action is closed.
  • the method also comprises a step of modifying the display of records to reflect that a request for action has been taken. This step may occur for both the Requester and the Requestee. In other embodiments, the display may also change as the progress or lack of progress is made with respect to the requested action. Examples of this method are described in greater detail above.
  • the methods described above may continuously flow in a loop, flow according to a timed event or sequence, or flow according to a change in status.
  • the method may be initiated or suspended by a user, such as a Requester, at various times during the method described above. Changes in status or actions taken by the Requester or Requestee may result in a step of changing the indicia associated with the record(s), and may further results in the step of generating an updated message to the users involved in the request for action.
  • Conga Grid as an add-on software module for use with Salesforce.
  • other modules whether or not associated with the functionality or advantages of Conga Grid, may still operate with the systems and methods described herein and otherwise enjoy the benefits of the present disclosure.
  • the systems and methods described in detail herein may comprise one or more graphical displays, in addition to those shown in Figures 1-4, for conveying the status of a request, whether the user is a requester, requestee or merely copied on the request.
  • the various graphical displays included with the applications incorporated herein are expressly included and form part of this disclosure.
  • the systems and methods may comprise graphical displays for notifying or alerting a user of an action or inaction made on one or more records.
  • graphical displays convey additional information to a user, such as the result of the action, the details of a modification, the synchronization or reconciliation of an action, or other discrete components or steps of the systems and methods described herein.
  • the graphical displays provide information regarding requests made by a user or missing information from one or more records so that a user may efficiently manage modifications and requested modifications to records.
  • a specific record may be modified several times by several different individual users and that activity displayed historically, graphically or otherwise to a user.
  • action on a record may be requested by multiple users, and that activity likewise displayed to a user via the graphical interface.
  • the systems and methods described above may further comprise an application or be provided via one or several modules.
  • the application/modules are designed to operate on a mobile device or mobile computer, and assist a user with managing requests for action and any subsequent action taken in connection with one or more records.
  • the application/modules may comprise one or more data sets, tables or databases, including one or more relational databases.
  • the application includes time and/or record-specific alerts and/or notifications.
  • the application/modules further permit a user to sort, search and modify records and thereby add or revise data associated therewith. In embodiments, one or more of these advantages of the system are automated, or performed at least semi-automatically.
  • the application is advantageously configured to receive and send information by, for example, a user's mobile device.
  • the application comprises one or more user interfaces and displays, such as the displays depicted in the applications incorporated herein by reference.
  • the application and associated user interfaces may be stored or operated on a computing environment, wherein the systems, devices, servers, modules, etc. may execute.
  • the computing environment preferably includes one or more user computers.
  • the computers may be general purpose personal computers (including, merely by way of example, personal computers, and/or laptop computers running various versions of Microsoft Corp.'s WindowsTM and/or Apple Corp.'s MacintoshTM operating systems) and/or workstation computers running any of a variety of commercially-available UNIXTM or UNIX-like operating systems.
  • These user computers may also have any of a variety of applications, including for example, database client and/or server applications, and web browser applications.
  • the user computers may be any other electronic device, such as a thin-client computer, Internet-enabled mobile telephone, and/or personal digital assistant, capable of communicating via a network and/or displaying and navigating web pages or other types of electronic documents. Any number of user computers may be supported.
  • the computing environment described according to this embodiment preferably includes at least one network.
  • the network can be any type of network familiar to those skilled in the art that can support data communications using any of a variety of commercially-available protocols, including without limitation SIP, TCP/IP, SNA, IPX, AppleTalk, and the like.
  • the network maybe a local area network ("LAN”), such as an Ethernet network, a Token-Ring network and/or the like; a wide-area network; a virtual network, including without limitation a virtual private network ("VPN"); the Internet; an intranet; an extranet; a public switched telephone network (“PSTN”); an infra-red network; a wireless network (e.g., a network operating under any of the IEEE 802.11 suite of protocols, the BluetoothTM protocol known in the art, and/or any other wireless protocol); and/or any combination of these and/or other networks.
  • LAN local area network
  • VPN virtual private network
  • PSTN public switched telephone network
  • wireless network e.g., a network operating under any of the IEEE 802.11 suite of protocols, the BluetoothTM protocol known in the art, and/or any other wireless protocol
  • the system in varying embodiments may also include one or more server computers.
  • One server may be a web server, which may be used to process requests for web pages or other electronic documents from user computers.
  • the web server can be running an operating system including any of those discussed above, as well as any commercially-available server operating systems.
  • the web server can also run a variety of server applications, including SIP servers, HTTP servers, FTP servers, CGI servers, database servers, Java servers, and the like. In some instances, the web server may publish operations available operations as one or more web services.
  • the computing environment may also include one or more file and or/application servers, which can, in addition to an operating system, include one or more applications accessible by a client running on one or more of the user computers.
  • the server(s) may be one or more general purpose computers capable of executing programs or scripts in response to the user computers.
  • the server may execute one or more web applications.
  • the web application may be implemented as one or more scripts or programs written in any programming language, such as JavaTM, C, C#TM, or C++, and/or any scripting language, such as Perl, Python, or TCL, as well as combinations of any programming/scripting languages.
  • the application server(s) may also include database servers, including without limitation those commercially available from Oracle, Microsoft, SybaseTM, IBMTM and the like, which can process requests from database clients running on a user computer.
  • the web pages or equivalent graphical displays created by the application server may be forwarded to a user computer or user mobile device via a web server.
  • the web server may be able to receive web page requests, web services invocations, and/or input data from a user computer and can forward the web page requests and/or input data to the web application server.
  • the server may function as a file server.
  • the computing environment may also include a database.
  • the database may reside in a variety of locations.
  • database may reside on a storage medium local to (and/or resident in) one or more of the computers. Alternatively, it may be remote from any or all of the computers, and in communication (e.g., via the network) with one or more of these.
  • the database may reside in a storage-area network ("SAN") familiar to those skilled in the art.
  • SAN storage-area network
  • any necessary files for performing the functions attributed to the computers may be stored locally on the respective computer and/or remotely, as appropriate.
  • the database may be a relational database, which is adapted to store, update, and retrieve data in response to SQL- formatted commands.
  • the computer system may also comprise software elements, including but not limited to application code, within a working memory, including an operating system and/or other code. It should be appreciated that alternate embodiments of a computer system may have numerous variations from that described above. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Further, connection to other computing devices such as network input/output devices may be employed.
  • the server may include one or more components that may represent separate computer systems or electrical components or may software executed on a computer system. These components include a load balancer, one or more web servers, a database server, and/or a database.
  • the load balancer is operable to receive a communication from the mobile device and can determine to which web server to send the communication.
  • the load balancer can manage, based on the usage metrics of the web servers, which web server will receive incoming communications.
  • the load balancer may not receive further communications.
  • the load balancer may be able to redistribute load amongst the web servers if one or more web servers become overloaded.
  • one or more web servers are operable to provide web services to the user devices.
  • the web server receives data or requests for data and communicates with the database server to store or retrieve the data.
  • the web server functions as the intermediary to put the data in the database into a usable form for the user devices.
  • a database server is any hardware and/or software operable to communicate with the database and to manage the data within the database.
  • Database servers for example, SQL server, are well known in the art.
  • the database can be any storage mechanism, whether hardware and/or software, for storing and retrieving data.
  • machine-executable instructions may be stored on one or more machine-readable mediums, such as CD-ROMs or other type of optical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, flash memory, or other types of machine-readable mediums suitable for storing electronic instructions.
  • machine-readable mediums such as CD-ROMs or other type of optical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, flash memory, or other types of machine-readable mediums suitable for storing electronic instructions.
  • the methods may be performed by a combination of hardware and software.
  • embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof.
  • the program code or code segments to perform the necessary tasks may be stored in a machine-readable medium such as storage medium.
  • a processor(s) may perform the necessary tasks.
  • a code segment may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements.
  • a code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • General Physics & Mathematics (AREA)
  • Operations Research (AREA)
  • Tourism & Hospitality (AREA)
  • Quality & Reliability (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne des systèmes et des procédés de demande, de suivi et de rapport de modifications apportées à un enregistrement. Dans un mode de réalisation, l'enregistrement est associé à un système de gestion des relations avec la clientèle, CRM. Selon divers modes de réalisation, le système et le procédé peuvent être mis en œuvre grâce à l'utilisation d'un ou plusieurs modules et peuvent permettre d'entreprendre une action parmi plusieurs actions possibles par rapport à un enregistrement.
PCT/US2018/052056 2017-09-20 2018-09-20 Systèmes et procédés de demande, de suivi et de rapport de modifications apportées à un enregistrement WO2019060618A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201762560915P 2017-09-20 2017-09-20
US62/560,915 2017-09-20
US15/826,026 2017-11-29
US15/826,026 US11182549B2 (en) 2017-03-06 2017-11-29 Systems and methods for modifying and reconciling negotiated documents

Publications (1)

Publication Number Publication Date
WO2019060618A1 true WO2019060618A1 (fr) 2019-03-28

Family

ID=65810560

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/052056 WO2019060618A1 (fr) 2017-09-20 2018-09-20 Systèmes et procédés de demande, de suivi et de rapport de modifications apportées à un enregistrement

Country Status (1)

Country Link
WO (1) WO2019060618A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070239514A1 (en) * 2003-12-09 2007-10-11 Lissy Gregory P Lead management in multi-tiered sales organizations
US20090182824A1 (en) * 2008-01-16 2009-07-16 Thomas R Haynes System and method for follow-on message processing
US20140350966A1 (en) * 2013-05-24 2014-11-27 Boston Scientific Neuromodulation Corporation Systems and methods for managing medical services

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070239514A1 (en) * 2003-12-09 2007-10-11 Lissy Gregory P Lead management in multi-tiered sales organizations
US20090182824A1 (en) * 2008-01-16 2009-07-16 Thomas R Haynes System and method for follow-on message processing
US20140350966A1 (en) * 2013-05-24 2014-11-27 Boston Scientific Neuromodulation Corporation Systems and methods for managing medical services

Similar Documents

Publication Publication Date Title
US11003654B2 (en) Systems and methods for requesting, tracking and reporting modifications to a record
US11593400B1 (en) Automatic triage model execution in machine data driven monitoring automation apparatus
JP5885859B2 (ja) 構成可能なワークフロー機能の提供
US10963293B2 (en) Interactions with contextual and task-based computing environments
US11209962B2 (en) System, method, and apparatus for providing insights, and taking actions thereon, for contextually relevant user-specific content integrated with a third-party Personal Information Management (PIM) application within a cloud based computing environment
US9317390B2 (en) Collecting, aggregating, and presenting activity data
US20140278663A1 (en) Electronic discovery systems and workflow management method
US20130346329A1 (en) System and methods for social data sharing capabilities for enterprise information systems
US8660881B2 (en) Mechanism for facilitating dynamic visual workflow and task generation in an on-demand services environment
US9245256B2 (en) Assigning and managing reviews of a computing file
CN105740368A (zh) 一种生成报表的方法及装置
US10768794B2 (en) Truncated synchronization of data object instances
US20210182754A1 (en) Minimizing unmet demands due to short supply
US20200081727A1 (en) A method and a system for hosting multiple multi-tenant applications
WO2019060618A1 (fr) Systèmes et procédés de demande, de suivi et de rapport de modifications apportées à un enregistrement
US11636431B2 (en) Systems and methods for dynamic assignment, monitoring and management of discrete tasks
WO2023231716A1 (fr) Procédés et appareil de traitement de données, dispositif électronique et support d'enregistrement
US9537922B2 (en) Partitioning digital media for consumption
US9087127B1 (en) Method for providing an integrated video module
WO2021028891A1 (fr) Système de collecte de données interactif évolutif
US10810640B1 (en) Automated time tracking of events in a calendar and use of the same to generate invoices
US20180268374A1 (en) Electronic change planning manager
US20150006329A1 (en) Distributed erp
US20240220237A1 (en) Smart grouping of code packages
US20220237550A1 (en) Enterprise legal platform backed by custom tables integrated into a data lake

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18859625

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 03.08.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18859625

Country of ref document: EP

Kind code of ref document: A1