[go: up one dir, main page]

WO2018011653A1 - Système et procédé pour échanger des informations sur un système de discussion par l'intermédiaire de formulaires structurés - Google Patents

Système et procédé pour échanger des informations sur un système de discussion par l'intermédiaire de formulaires structurés Download PDF

Info

Publication number
WO2018011653A1
WO2018011653A1 PCT/IB2017/053794 IB2017053794W WO2018011653A1 WO 2018011653 A1 WO2018011653 A1 WO 2018011653A1 IB 2017053794 W IB2017053794 W IB 2017053794W WO 2018011653 A1 WO2018011653 A1 WO 2018011653A1
Authority
WO
WIPO (PCT)
Prior art keywords
chat
sender
information
approvers
chat room
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/IB2017/053794
Other languages
English (en)
Inventor
Venkateshappa Janardana HOSUR
Karthik HOSUR
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
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
Application filed by Individual filed Critical Individual
Publication of WO2018011653A1 publication Critical patent/WO2018011653A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/101—Collaborative creation, e.g. joint development of products or services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H04L12/1822—Conducting the conference, e.g. admission, detection, selection or grouping of participants, correlating users to one or more conference sessions, prioritising transmission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]

Definitions

  • the embodiments herein generally relate to information exchange between users through structured forms over chat system. More specifically, the invention provides a system and a method for exchanging information over chat system through structured forms in addition to generic methods of sharing information. Particularly, the system and method helps the users of the computer system to submit structured forms of data to reach recipients directly or after intermediate approval.
  • chat systems are generally used for both personal and business purpose that serves as a close to real-time but a disconnected method of exchanging information between sender and receiver.
  • the chat systems are not like online software that will have a continuous connection between user interface (form) and the underlying back end software.
  • chat system supporting unstructured or chunks of information sharing between users.
  • the chat system also functions as an asynchronous and near-real time transmission of information from sender to receiver(s). Further, the chat system can function as a medium to exchange structured data using pre-defined forms that minimizes dependency on online software applications and minimize security risks due to the online/(always connected) nature of software applications.
  • a main object of the present invention is to provide a system and method for exchanging the information in structured form through a chat system to reach recipients directly or after intermediate approval.
  • Another object of the present invention is to provide a system and method for enabling the administrator(s) of the created chat room(s) to design and publish reusable structured form templates.
  • Still another object of the present invention is to involve multiple approvers in each form so that the form with information is delivered to recipient(s) only after approval from all attached approvers of that form according to the requirement.
  • Yet another object of the present invention is to provide a system and method for performing an automated task as defined in the form template after reception of the information at the recipient end where the recipient may be user(s) or smart device(s) of any kind and send back the response to the sender and/or approvers as required.
  • Another object of the present invention is to provide a system and method for allowing the users to view the information submitted by multiple senders in a structured report format, extract or retrieve the information using software tools or allow third party software tools to either send or extract the information using APIs (Application Programming Interfaces).
  • Another object of the present invention is to provide a system and method for allowing the users to export the information into another software using chat system export tools or third party software tools send/retried messages (forms) using APIs (Application Programming Interfaces) provided by the chat system and based on the type of data access permission given to those users by the administrators of each group.
  • Another object of the present invention is to provide a system and method for allowing the user to reuse the form templates.
  • Another object of the present invention is to provide a system and a method for allowing the sender to do transaction in the chat system by means of a payment gateway control.
  • an embodiment herein provides a system and method for providing a chat system that can send structured forms with data to reach recipients directly or after intermediate approval by one or more users of the system in additions to other standard methods of data transfer used in a typical chat system.
  • the chat system comprises a sender user interface, a chat engine, an approver chat user interface, and a recipient chat user interface (this may be the sender user interface or specifically designed user interface).
  • the chat engine can allow a chat room administrator(s) to design and publish reusable structured form templates having information section, optional approving user(s) definition section and recipient(s) definition section. Further, the chat engine can provide certain functionality for the chat room administrators to design reusable form templates using chat system internal form design tools. Based on the template layout, a chat system interpreter in the chat engine can build a form with programming script dynamically so that the sender can populate data into the form for submission and also pre-defined programming script based automation can be executed in approval process and at recipient process.
  • the chat system can be utilized by a sender to send information through structured forms.
  • the chat system can enable the sender to find a chat room based on name, purpose, any other chat room description or publisher name. Further, the chat system can allow the sender to select required chat room, view the listed form templates available in that chat room, select one of the listed form template, fill the information and submit the same to one or more approvers and to one or more recipients after approval.
  • the system may perform automation tasks as defined in the form template using programming script support by the chat system interpreter that can be an Alarm, post TODO List to the recipient, order form that recipient has to deliver, meeting task that has to be posted onto recipient's planner, store the data into a specified store point, activate a connected device and so on and script that can send required information back to sender or approvers or recipients itself.
  • programming script support by the chat system interpreter that can be an Alarm, post TODO List to the recipient, order form that recipient has to deliver, meeting task that has to be posted onto recipient's planner, store the data into a specified store point, activate a connected device and so on and script that can send required information back to sender or approvers or recipients itself.
  • the chat system can help the users (senders, approvers or recipients) to view the information in a structured format, extract or retrieve the information using connecting tools (application programming interfaces or APIs) or export the information into another software using APIs based on the permission given to those users by the administrators of each group.
  • connecting tools application programming interfaces or APIs
  • the method for providing a chat system to exchange information in using structured form templates includes a functions performed by the chat room administrator while creating the chat room and a process involved in the chat system after creation of the chat room.
  • the functions performed by the chat room administrator comprising the steps of, creating a form template using data elements, defining approvers, defining data elements that have to be updated by the approvers, defining data elements that can be viewed by the sender and /or recipients, defining receipts and data elements that have to be updated by the receivers after receiving the form, defining data elements that can be viewed by the sender and /or approvers, scripting to either validate the data elements of the form, incorporating automation tasks to be performed by the form, defining access criteria or filters so that only those recipients with matching filters can only view the information that supports sending of information to multiple users but only select users should be able view the received information form and publishing the form onto one or more created chat room(s) along user types (public or private) who can access
  • the process involved in the chat system comprising the steps of, allowing the sender to locate chat room based on the information or publisher name, allowing the sender to select the chat room to send message using form, allowing the sender to select relevant form from the list of published forms, allowing the sender to fill the information in the selected form, allowing the sender to submit the filled form, submitting the same form to the approvers based on the form template definition, in case approvers are defined in the form, allowing the approvers to reject or approve the form submitted by the sender, in case approvers are defined in the form, allowing the system to send the approved form to the receiver(s), in case approvers are defined in the form, sending the form to the recipient directly, in case approvers are not defined in the form, allowing the recipient to update the form status, and allowing the sender to view the information as a report and downloading the form to external software, according to the access rights of the sender or received by a system
  • Fig.1 illustrates the general architecture of the chat system, according to an embodiment herein;
  • FIG. 2 illustrates the schematic of chat engine, according to an embodiment herein;
  • FIG. 3 illustrates the process of chat room administrator, according to an embodiment herein.
  • Fig. 4 illustrates the process of the chat system, according to an embodiment herein.
  • FIGS. 1 through 4 where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.
  • a system and method for providing a chat system that can send structured forms with data to reach recipients directly or after intermediate approval by one or more users of the system in additions to other standard methods of data transfer used in a typical chat system.
  • the chat system comprises a sender user interface, a chat engine, an approver chat user interface, and a recipient chat user interface (this may be the sender user interface or specifically designed user interface).
  • the chat engine can allow a chat room administrator(s) to design and publish reusable structured form templates having information section, optional approving user(s) definition section and recipient(s) definition section. Further, the chat engine can provide certain functionality for the chat room administrators to design reusable form templates using chat system internal form design tools.
  • a chat system interpreter in the chat engine can build a form with programming script dynamically so that the sender can populate data into the form for submission and also pre-defined programming script based automation can be executed in approval process and at recipient process.
  • the chat system can be utilized by a sender to send information through structured forms.
  • the chat system can enable the sender to find a chat room based on name, purpose, any other chat room description or publisher name. Further, the chat system can allow the sender to select required chat room, view the listed form templates available in that chat room, select one of the listed form template, fill the information and submit the same to one or more approvers and to one or more recipients after approval.
  • the system may perform automation tasks as defined in the form template using programming script support by chat system interpreter that can be an Alarm, post TODO List to the recipient, order form that recipient has to deliver, meeting task that has to be posted onto recipient's planner, store the data into a specified store point, activate a connected device and so on and script that can send required information back to sender or approvers or recipients itself.
  • chat system interpreter can be an Alarm, post TODO List to the recipient, order form that recipient has to deliver, meeting task that has to be posted onto recipient's planner, store the data into a specified store point, activate a connected device and so on and script that can send required information back to sender or approvers or recipients itself.
  • the chat system can help the users (senders, approvers or recipients) to view the information in a structured format, extract or retrieve the information using connecting tools (application programming interfaces or APIs) or export the information into another software using APIs based on the permission given to those users by the administrators of each group.
  • connecting tools application programming interfaces or APIs
  • Fig. 1 illustrates the general architecture of the chat system, according to an embodiment.
  • the general architecture of the chat system comprises a sender 101, a user interface 102, a chat engine 103, an approver chat user interface 104, a recipient chat user interface 105 and a payment processing system (smart device) 106.
  • the chat system can enable the sender 101 to find a chat room based on name, purpose, and any other chat room description or publisher name using the user interface 102.
  • the user interface 102 can allow the sender 101 to navigate the respective chat room, view the listed form templates available in that chat room, select one of the listed form templates, fill the information and submit the same to one or more approvers and to one or more recipients after approval.
  • the chat engine 103 can receive and store the forms submitted by the sender 101.
  • the chat engine 103 may verify the received forms for approver definition.
  • the received form contains any approver definition then the same form may send to the approver for approval.
  • the chat system can allow the approver to verify the forms using the approver chat user interface 104. After obtaining approval from the approver, the approved form may send to a recipient.
  • the chat system can allow the recipient to view the information in a structured format, extract or retrieve the information using connecting tools (application programming interfaces or APIs) using recipient chat user interface 105 or export the information into another software using APIs based on the permission given to those recipients by the chat room administrators of each group. The recipient can update the form status.
  • the chat engine 103 may send a feedback to the sender 101. Further, the chat system may allow the sender 101 to view the information as a report and downloading the form to external software, according to the access rights of the sender 101.
  • the payment processing system may include but not limited to a back end server, an interface to smart device, external systems and so on.
  • the payment processing system 106 utilized for transmitting sender requirement by collection credit card, debit card, bank account or wallet information and submits the same to payment gateway to process the payment at the back end server and upon success or failure of the process, communicate the same to the sender. Further, the payment processing system 106 is provided to send back any intermittent requests from server to the user interface using messaging or a direct API call to ask user for additional information like OTP (One time password) to proceed for payment after first level(one or more levels of process) like authorization, verification and so on.
  • OTP One time password
  • the sender can be allowed to send back the OTP from the approver to the payment gateway back for final payment process or a transaction ID and allowing a merchant bank module to return status in case direct submission of OTP to payment gateway is not permitted.
  • the API of the payment processing system 106 is allowed to call payment gateway for payment exchange. This can be done either from application user interface side or from the server side of the application system or through mediating software connecting to messaging/chat server. Similar to any chat system, software user interface or application user interface for sender, approver and receiver actions can be a single software page interface unless there is a need to make a separate interface or an application for any of the user(s).
  • Fig. 2 illustrates the schematic of chat engine, according to an embodiment.
  • the chat engine includes modules but is not limited to a chat room admin module 201, approver module 202, sender/ user module 203, recipient module 204, form filling 205, form submission module 206, update module 207, publishing module 208, feedback module 209 and other modules 210.
  • the chat room admin module 201 can be configured for creating a form template using data elements, defining approvers and the data elements that have to be updated by the approvers and defining data elements that can be viewed by the sender and /or recipients. Further, the chat room admin module 201 can be configured for defining receipts and data elements that have to be updated by the receivers after receiving the form and defining data elements that can be viewed by the sender and /or approvers.
  • the data element that includes but is not limited to a text box, a numeric input, a drop down combo box, a radio button, a table view, a list view, a grid view, a tree view, a checkbox, a date control, a location and address control, a digital signature control, a payment gateway control, an attachment control to attach a document or capture an image from camera and the like elements that aid in building a computer user interface form.
  • the chat room admin module 201 can be further configured for providing payment gateway control for transmitting sender requirement by collection credit card, debit card, bank account or a wallet information and submit the same to payment gateway to process the payment at the back end server and upon success or failure of the process, communicate the same to the sender.
  • the approver module 202 can be configured for rejecting or approving the form submitted by the sender, in case approvers are defined in the form. Further, the approver module 202 can be further configured for sending the approved form to the receiver, in case approvers are defined in the form. The approver module 202 can be further configured for sending back any intermittent requests from server to the user interface using messaging or a direct API call to ask user for additional information like OTP (One time password) to proceed for payment after first level(one or more levels of process) like Authorization, verification and so on.
  • OTP One time password
  • the sender/ user module 203 can be configured for locating the chat room based on the information or publisher name and selecting the chat room to send message using form.
  • the sender/ user module 203 can be further configured for selecting relevant form from the list of published forms.
  • the recipient module 204 can be configured for updating the form status and sending the status of the form back to the sender through chat engine.
  • the form filling module 205 can be configured for allowing the sender user interface to auto-fill the information in a selected form using the information stored in user profile.
  • the form submission module 206 can be configured for sending the form to the recipient directly, in case approvers are not defined in the form.
  • the update module 207 can be configured for updating the status of the form submitted by the sender.
  • the publishing module 208 can be configured for updating the data elements of the form in the chat engine.
  • the feedback module 209 can be configured for providing feedback to the sender after receiving feedback from the approver and recipient.
  • the feedback module 209 can be further configured for allowing the sender to send back the OTP from the approver to the payment gateway back for final payment process or a transaction ID and allowing a merchant bank module to return status in case direct submission of OTP to payment gateway is not permitted.
  • the feedback module 209 can be further configured for allowing API to call payment gateway for payment exchange. This can be done either from Application User Interface side or from the server side of the application system or through mediating software connecting to messaging/chat server.
  • Exemplary methods for providing a chat system to exchange information in structured form are described with reference to Fig 3 & 4. These exemplary methods can be described in the general context of computer executable instructions.
  • computer executable instructions can include routines, programs, objects, components, encrypted or open data structures, procedures, modules, functions, and the like that perform particular functions or implement particular abstract data types.
  • the methods can also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communication network.
  • computer executable instructions may be located both in local and remote computer storage media, including memory storage devices.
  • the exemplary methods are illustrated as a collection of operations in a logical flow graph representing a sequence of operations that can be implemented in hardware, software, firmware, or a combination thereof.
  • the order in which the methods are described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the methods, or alternate methods. Additionally, individual operations may be deleted from the methods without departing from the spirit and scope of the subject matter described herein.
  • the operations represent computer instructions that, when executed by one or more processors, perform the recited operations.
  • the method for providing a chat system to exchange information in using structured form templates includes a functions performed by the chat room administrator while creating the chat room and a process involved in the chat system after creation of the chat room.
  • the functions performed by the chat room administrator comprising the steps of, creating a form template using data elements, defining approvers, defining data elements that have to be updated by the approvers, defining data elements that can be viewed by the sender and /or recipients, defining receipts and data elements that have to be updated by the receivers after receiving the form, defining data elements that can be viewed by the sender and /or approvers, scripting to either validate the data elements of the form, incorporating automation tasks to be performed by the form, defining access criteria or filters so that only those recipients with matching filters can only view the information that supports sending of information to multiple users but only select users should be able view the received information form and publishing the form onto one or more created chat room(s) along with user types (public or private) who can
  • the process involved in the chat system comprising the steps of, allowing the sender to locate chat room based on the information or publisher name, allowing the sender to select the chat room to send message using form, allowing the sender to select relevant form from the list of published forms, allowing the sender to fill the information in the selected form, allowing the sender to submit the filled form, submitting the same form to the approvers based on the form template definition, in case approvers are defined in the form, allowing the approvers to reject or approve the form submitted by the sender, in case approvers are defined in the form, allowing the system to send the approved form to the receiver(s), in case approvers are defined in the form, sending the form to the recipient directly, in case approvers are not defined in the form, allowing the recipient to update the form status, and allowing the sender to view the information as a report and downloading the form to external software, according to the access rights of the sender or received by a system
  • the data element that includes but is not limited to a text box, a numeric input, a drop down combo box, a radio button, a table view, a list view, a grid view, a tree view, a checkbox, a date control, a location and address control, a digital signature control, a payment gateway control, an attachment control to attach a document or capture an image from camera and the like elements that aid in building a computer user interface form.
  • the Location and Address control can be linked to Maps by map technology providers like Google, Apple, Bing Maps or a similar service provider to read the address of selected map location or current map location.
  • the Payment gateway control can provide the payment functionality over chat/messaging channel or by calling payment gateway directly from the user interface.
  • Fig. 3 illustrates the process of chat room administrator, according to an embodiment. While creating the chat room, the functions performed by the chat room administrator comprising the steps of, creating a form template using data elements 301, defining approvers 302, defining data elements that have to be updated by the approvers 303, defining data elements that can be viewed by the sender and /or recipients 304, defining receipts and data elements that have to be updated by the receivers after receiving the form 305, defining data elements that can be viewed by the sender and /or approvers 306, scripting to either validate the data elements of the form 307, incorporating automation tasks to be performed by the form 308, defining access criteria or filters 309 so that only those recipients with matching filters can only view the information that supports sending of information to multiple users but only select users should be able view the received information form and publishing the form onto one or more created chat room(s) 310 along with user types (
  • the method allows the chat room administrator to create the form templates to design and publish reusable structured form templates having information section, optional approving user(s) definition section and recipient(s) definition section. Further, method provides certain functionality for the chat room administrators to design reusable form templates using its own internal layout. Based on the template layout, a chat system interpreter in the chat engine can build a form dynamically so that the sender can populate data into the form for submission.
  • Fig. 4 illustrates the process of the chat system, according to an embodiment.
  • the process involved in the chat system comprising the steps of: allowing the sender to locate chat room based on the information or publisher name 401, allowing the sender to select the chat room to send message using form 402, allowing the sender to select relevant form from the list of published forms 403, allowing the sender to fill the information in the selected form 404, allowing the sender to submit the filled form 405, submitting the same form to the approvers, based on the form template definition, in case approvers are defined in the form 406, allowing the approvers to reject or approve the form submitted by the sender, in case approvers are defined in the form 407, allowing the approvers to send the approved form to the receiver, in case approvers are defined in the form 408, sending the form to the recipient directly, in case approvers are not defined in the form 409, allowing the recipient to update the form status 410, and allowing the sender to view
  • the chat system can allow the chat room admin to create form templates. But there is possibility to change the chat system for the user (sender / recipient / approver) to create forms according to their preference and to create multiple group administrators.
  • the method for information exchange using chat system can eliminate the need for a safer and real-time connecting network and also eliminates the need for a real-time online application forms to enable users submit information.
  • This disconnected, asynchronous method of data interchanges is a safer and a reliable method of information sharing that required minimum infrastructure compared to typical software systems and online user interface.
  • the chat system can either minimize or eliminate the purpose of building online forms for receiving structure information from users. Further, the chat system can enable individuals and organizations to define their own chat rooms, publish required number of form for internal users (employee/consultant use) or for external users. Typical forms that be designed by organization are like Leave Request, Travel Request, Time sheet submission, Stationary request and the like internal forms for employees or external forms like Resume submission form that will be routed to Recruitment Team, Customer Service Request routed to customer support team, Contact Us form routed to general company administrator, Sales Enquiry form routed to sales team and so on. [00060] According to an embodiment, the chat system can be used in payment gateway control.
  • the payment can be initiated at the user interface through a simple chat like message and that can be understood by the Artificial Intelligent system based on natural language like input or using a predefine template/Form (static or dynamically configured template) through mobile app, web portal software interface or a desktop based user interface client form.
  • a simple chat like message and that can be understood by the Artificial Intelligent system based on natural language like input or using a predefine template/Form (static or dynamically configured template) through mobile app, web portal software interface or a desktop based user interface client form.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Data Mining & Analysis (AREA)
  • Multimedia (AREA)
  • General Engineering & Computer Science (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention concerne un système et un procédé pour partager des informations par un expéditeur à un ou plusieurs destinataires à l'aide de modèles de formulaires prédéfinis sur un système de discussion. Ce système de conversation aide les utilisateurs à économiser du temps, de la complexité et de l'authentification/du processus de signalisation à chaque fois que l'utilisateur souhaite soumettre une quelconque information sous la forme d'une page web ou de données non structurées envoyées sous la forme d'un message qui ne peut pas être utilisé en tant qu'information formelle. En outre, le système peut fournir un moyen pour permettre à de multiples approbateurs de réaliser des transactions à l'aide de ce système de messagerie et les informations reçues par l'intermédiaire de ce système peuvent être extraites sous une forme de rapport standard ou par une application logicielle d'ordinateur externe utilisant des API. Ce système peut permettre à des individus et à des organisations de définir leurs propres salles de conversation, de publier un nombre requis de formulaires pour des utilisateurs internes (utilisation d'employés/consultant) ou pour des utilisateurs externes.
PCT/IB2017/053794 2016-07-11 2017-06-26 Système et procédé pour échanger des informations sur un système de discussion par l'intermédiaire de formulaires structurés Ceased WO2018011653A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN201641023631 2016-07-11
IN201641023631 2016-07-11

Publications (1)

Publication Number Publication Date
WO2018011653A1 true WO2018011653A1 (fr) 2018-01-18

Family

ID=60952851

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2017/053794 Ceased WO2018011653A1 (fr) 2016-07-11 2017-06-26 Système et procédé pour échanger des informations sur un système de discussion par l'intermédiaire de formulaires structurés

Country Status (1)

Country Link
WO (1) WO2018011653A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107644317A (zh) * 2017-09-21 2018-01-30 成都信息工程大学 一种基于多层次双向流转控制的业务引擎

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020174050A1 (en) * 2000-12-27 2002-11-21 James Eynard Business capacity transaction management system
US6769012B1 (en) * 2000-07-24 2004-07-27 Song Liu Method and system for managing message transactions between a sender and recipient within a virtual mailbox

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6769012B1 (en) * 2000-07-24 2004-07-27 Song Liu Method and system for managing message transactions between a sender and recipient within a virtual mailbox
US20020174050A1 (en) * 2000-12-27 2002-11-21 James Eynard Business capacity transaction management system

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107644317A (zh) * 2017-09-21 2018-01-30 成都信息工程大学 一种基于多层次双向流转控制的业务引擎

Similar Documents

Publication Publication Date Title
JP6349328B2 (ja) アクセスの管理されたインタラクションのシステムおよび方法
US8566414B2 (en) Systems and methods for subscription management in a multi-channel context aware communication environment
US8788819B2 (en) System and method for a cloud-based electronic communication vault
US20130217365A1 (en) Automatic profile update in a mobile device with transactional and social intelligence capabilities
US10348843B2 (en) Must-reply mobile questionnaire system and method
US12361433B2 (en) Compliance document creation, modification, and provisioning
EP3613188B1 (fr) Inscription par identifiant personnel pour des utilisateurs organisationnels
US11146649B2 (en) Computer-implemented method and computer system for distributing push notifications
CN111585868B (zh) 一种信息处理方法、装置、计算机设备以及可读存储介质
AU2016200982B2 (en) Communication system and method
US20150052047A1 (en) Methods and systems for facilitating document banking
WO2019130809A1 (fr) Système de gestion de transaction, dispositif de gestion de transaction, procédé de gestion de transaction et programme de gestion de transaction
US20250238762A1 (en) Communication exchanges and methods of use thereof
US20150039986A1 (en) Collaboration system and method
WO2018011653A1 (fr) Système et procédé pour échanger des informations sur un système de discussion par l'intermédiaire de formulaires structurés
US20110247082A1 (en) Integration of Different Mobile Device Types with a Business Infrastructure
US20150213405A1 (en) Methods and systems for facilitating document transactions
Fritsch Identification collapse-contingency in Identity Management
Umuhoza Ritha et al. Mobile Based Application for E-services and E-payments: A Study case of Habari Node Public Limited Company in Arusha, Tanzania.

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: 17827075

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17827075

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17827075

Country of ref document: EP

Kind code of ref document: A1