CN116011955A - Robot flow automation demand realization method, device, equipment and storage medium - Google Patents
Robot flow automation demand realization method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN116011955A CN116011955A CN202211651354.3A CN202211651354A CN116011955A CN 116011955 A CN116011955 A CN 116011955A CN 202211651354 A CN202211651354 A CN 202211651354A CN 116011955 A CN116011955 A CN 116011955A
- Authority
- CN
- China
- Prior art keywords
- pra
- requirement
- flow
- user
- demand
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 107
- 238000012550 audit Methods 0.000 claims abstract description 23
- 238000004801 process automation Methods 0.000 claims abstract description 12
- 230000008569 process Effects 0.000 claims description 54
- 238000013461 design Methods 0.000 claims description 31
- 238000012360 testing method Methods 0.000 claims description 31
- 238000004590 computer program Methods 0.000 claims description 16
- 238000012827 research and development Methods 0.000 claims description 4
- 238000007726 management method Methods 0.000 abstract description 26
- 238000012545 processing Methods 0.000 description 14
- 238000010586 diagram Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 8
- 238000011161 development Methods 0.000 description 5
- 230000009471 action Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012552 review Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a method, a device, equipment and a storage medium for realizing automatic requirements of a robot flow. The method comprises the following steps: acquiring a robot process automation PRA requirement of a first user so as to enable a second user to audit the robot process automation requirement; when the PRA requirement approval is confirmed to pass, automatically generating a PRA flow file according to the PRA requirement; and uploading the PRA flow file to be used for downloading the PRA flow file by the first user. According to the embodiment, the PRA requirement of the first user is sent to the second user for auditing, and when the PRA requirement passes, the PRA flow file is automatically generated according to the PRA requirement and is used online, so that automatic requirement management of the robot flow is realized, and the problem of low flow synchronization efficiency is solved.
Description
Technical Field
The present invention relates to the field of robot process automation, and in particular, to a method, an apparatus, a device, and a storage medium for realizing robot process automation requirements.
Background
The robotic process automation (Robot i c Process Automat i on, RPA) may be software running on a personal computer or server, and the primary function may be for simulating the human handling of various system software and automatically executing business processes, which may be suitable for large-scale and highly repetitive business scenarios.
The current RPA process requirements suggest, process and go online mainly depend on offline flows, and lack special and effective management tools. This approach requires manual maintenance of the information and status of the demand on-line, making real-time synchronization difficult. And the management process lacks unified standard, and sometimes the problem of nonstandard demand processing process and the like occurs. The RPA flow changes due to the service changes, and the offline management mode is inconvenient to maintain multiple versions. After the RPA flow is online, the online achievements are inconvenient to share with other people, and version update information of the flow is inconvenient to synchronize during version update.
Therefore, how to solve the problems of the inefficiency of the automation requirement management and the process synchronization of the robot becomes a urgent need.
Disclosure of Invention
The invention provides a method, a device, equipment and a storage medium for realizing automatic demand of a robot flow, so as to realize automatic demand management of the robot flow and solve the problem of low flow synchronization efficiency.
According to a first aspect of the present invention, there is provided a method for realizing automation requirements of a robot flow, including:
acquiring a robot process automation PRA requirement of a first user for a second user to audit the robot process automation requirement;
when the PRA requirement approval is determined to pass, automatically generating a PRA flow file according to the PRA requirement;
and uploading the PRA flow file to be downloaded and used by the first user.
According to another aspect of the present invention, there is provided a robot flow automation demand implementation apparatus, including:
the PRA demand acquisition module is used for acquiring the robot flow automatic PRA demand of the first user so as to enable the second user to audit the robot flow automatic demand;
the PRA process file generation module is used for automatically generating a PRA process file according to the PRA requirement when the PRA requirement approval is confirmed to pass;
and the PRA process file online module is used for online the PRA process file so as to be downloaded and used by the first user.
According to another aspect of the present invention, there is provided an electronic apparatus including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the method of any one of the embodiments of the present invention.
According to another aspect of the invention, there is provided a computer readable storage medium storing computer instructions for causing a processor to perform the method according to any of the embodiments of the invention.
According to the technical scheme, the PRA requirement of the first user is sent to the second user for verification, the PRA flow file is automatically generated according to the PRA requirement when the PRA requirement passes, and the PRA flow file is used online, so that automatic requirement management of the robot flow is realized, and the problem of low flow synchronization efficiency is solved.
It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the invention or to delineate the scope of the invention. Other features of the present invention will become apparent from the description that follows.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1a is a flow chart of a method for implementing the automation requirement of a robot flow according to a first embodiment of the present invention;
fig. 1b is a schematic view of an application scenario of a requirement list according to a first embodiment of the present invention;
fig. 1c is a schematic view of an application scenario of a requirement audit list according to a first embodiment of the present invention;
fig. 1d is a schematic view of an application scenario of a demand pool list according to a first embodiment of the present invention;
fig. 1e is a schematic view of an application scenario of a process market according to a first embodiment of the present invention;
fig. 1f is a schematic diagram of an application scenario of online of a flow file according to a first embodiment of the present invention;
FIG. 2a is a flowchart of yet another method for implementing the automated requirements of a robot flow according to a second embodiment of the present invention;
fig. 2b is a schematic diagram of an application scenario of a requirement list binding according to a second embodiment of the present invention;
fig. 2c is a schematic diagram of an application scenario corresponding to a requirement and a process version according to a second embodiment of the present invention;
fig. 3 is a flowchart of another method for realizing the automation requirement of the robot process according to the third embodiment of the invention
Fig. 4 is a schematic structural diagram of a robot flow automation requirement implementation device according to a fourth embodiment of the present invention;
fig. 5 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list or list of elements is not necessarily limited to those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
Example 1
Fig. 1a is a flowchart of a method for implementing a robot flow automation requirement according to an embodiment of the present invention, where the method may be implemented by a robot flow automation requirement implementing device, and the device may be implemented in hardware and/or software, and the robot flow automation requirement implementing device may be integrally configured in an electronic device. As shown in fig. 1a, the method comprises:
s110, acquiring the robot flow automation PRA requirement of the first user so as to enable the second user to audit the robot flow automation requirement.
The first user can serve as a requirement initiator to propose corresponding robot flow automation PRA requirements; corresponding robot flow automation software can be automatically generated based on the robot flow automation PRA requirements and used for users to use, download and the like.
The second user may act as an auditor to audit the robotic process automation PRA requirements.
It should be noted that, the first user may issue one or more automatic PRA requirements for the robot flow, which is not limited in this embodiment, and the second user may be a plurality of auditors with auditing rights.
In this embodiment, the user may log in to the RPA demand management platform using an account number to register the automation business process demand.
Specifically, if the business department user a finds that a certain business can be automated through the RPA robot during work, the user a can use its account number to create a robot flow automation PRA requirement on the RPA requirement management platform and submit the requirement to the second user for auditing.
Illustratively, acquiring the robotic flow automation PRA requirement of the first user may include: when the login request of the first user is confirmed to be received, the demand template is called, and the demand template is displayed for the first user to fill in; receiving demand content sent by a first user based on a demand template, and generating a demand draft according to the demand content, wherein the demand content comprises a demand name, a demand background, a target use department, a manual operation step description of a business process, and a related software and hardware system or a related picture video file; and displaying the requirement drafts in a requirement list, and adding an initial version number to the requirement drafts and generating PRA requirements when determining that a submitting and auditing instruction of a user to the requirement drafts is received.
The requirement template can contain elements such as a style and page layout of a file for completing filling in the requirement content.
In this embodiment, after the requirement content is filled in according to the requirement template, the user may display the requirement draft in the requirement list, or submit an audit command to send the requirement draft to the second user for audit. The requirements draft submitting the audit may automatically flag the initial version number, which may optionally be presented in the form of a positive integer.
In this embodiment, since each of the automated PRA requirements of the robotic process requires the second user to perform the audit, each of the PRA requirements has a corresponding audit state, which may include a pending submitted state, a pending audit state, an agreed state, a rejected state, and a terminated state.
The to-be-submitted state can be understood as the PRA requirement newly issued by the user and is not submitted to the second user for verification; the state to be checked can be understood as that the user sends the PRA requirement to the second user, and waits for the second user to check; the agreed state may be understood as the second user agreeing to generate the PRA requirement to the robotic process automation software; the rejected state may be understood as the second user rejecting the PRA requirement of the first user, which has the opportunity to modify the PRA requirement and then continue to generate a new PRA; the terminated state may be understood as the second user rejecting the PRA requirement of the first user and the first user having no opportunity to modify the PRA requirement.
It should be noted that, for the terminated state, if the first user considers that the automatic PRA requirement of a certain robot process has no development prospect, the first user may also select the terminated state.
In this embodiment, the newly generated PRA requirements may appear in the requirement list for display, and specifically, as shown in an application scenario of a requirement list in fig. 1b, each requirement may carry a corresponding serial number, and each requirement has a corresponding auditing state.
Illustratively, after acquiring the robotic flow automated PRA requirement of the first user, further comprising: the PRA requirement in the state to be checked is displayed in a checking list for a second user to check; when the approval passing instruction of the second user on the PRA requirement is determined to be received, updating the state of the PRA requirement into an approved state in an auditing list; and displaying the PRA requirements in the agreed state in the requirement pool list, and updating the state of the PRA requirements in the requirement pool list to be the requirement design state.
In this embodiment, the PRA requirement in the to-be-checked state is sent to the second user for checking, and the PRA requirement in the to-be-checked state may be transferred to the checking list of the second user.
The second user can be an administrator with PRA requirement auditing authority; the PRA requirement status in the second user's audit list may include a pending status, an approved status, and a rejected status.
In this embodiment, if the second user sends the PRA requirement to the second user, the state of the PRA requirement is updated in the audit list to be the state to be audited; and if the second user refuses the approval passing request of the PRA requirement, updating the state of the PRA requirement into the refused state in the auditing list.
Specifically, an application scenario of the requirement audit list may be as shown in fig. 1 c.
In this embodiment, if the second user passes the PRA requirement, the PRA requirement in the agreed state is displayed in the requirement pool list, and specifically, an application scenario of the requirement pool list may be shown in fig. 1 d.
The demand processing state of the demand pool list may include the following state nodes: a demand design state, a demand development state, a demand test state, a demand online state, an online state, and a terminated state.
In this embodiment, when the status of a PRA requirement is a requirement design status in the requirement pool list, the PRA requirement may be pushed to a requirement audit list of a specified second user, and the second user may perform a processing action on the requirement, where the processing action may include comment, care-of, return, and the like, and this embodiment is not limited specifically.
And S120, when the PRA requirement approval is determined to pass, automatically generating a PRA flow file according to the PRA requirement.
The PRA flow file may be used for downloading and use, among other things.
For example, automatically generating the PRA flow file according to the PRA requirements may include: automatically generating a flow design document according to semantic recognition of PRA requirements, and updating the PRA requirements in a requirement pool list to be in a requirement research and development state, wherein the flow design document comprises design flow content and test flow content; analyzing design flow content in the flow design document to automatically generate a PRA flow file, and updating PRA requirements in a requirement pool list to be in a requirement test state.
In this embodiment, when a PRA requirement is updated in the requirement pool list to be in a requirement development state, the PRA requirement can automatically identify the semantics of the information and materials contained in the PRA requirement by the management platform, and automatically generate a flow design document, where the flow design document includes design flow content and test flow content, and at this time, the PRA requirement is updated in the requirement pool list to be in a requirement development state. And then automatically generating a PRA flow file by analyzing the design flow content, and updating the PRA requirement into a requirement test state in a requirement pool list.
Illustratively, after automatically generating the PRA flow file according to the PRA requirement, the method may further include: analyzing the test flow content in the flow design document to automatically generate PRA flow test cases, and updating PRA requirements in a requirement pool list to be in a requirement online state; and testing the PRA flow file through the PRA flow test case, and determining that the PRA flow file meets the online requirement when the PRA flow file passes the test.
In this embodiment, when a PRA requirement is updated in the requirement pool list to be in a requirement test state, the management platform may automatically analyze the test flow content and generate an RPA flow test case, and update the PRA requirement in the requirement pool list to be in a requirement online state. However, at this time, the online permission interface of the second user to the PRA process file is not yet opened, specifically, the required online state can be marked with gray color, at this time, the PRA process file needs to be tested by adopting the PRA process test case, when the test is determined to pass, the PRA process file is determined to meet the online requirement, at this time, the online permission interface of the second user to the PRA process file is opened, and the required online state is marked with green color.
S130, the PRA process file is online so as to be downloaded and used by the first user.
If the PRA flow file is online, a second user indicating a required processing state checks links required by each state.
Illustratively, the uploading the PRA flow file may include: receiving an online instruction of a PRA requirement in a requirement online state of a second user, and containing attribute information aiming at a PRA flow file in the online instruction, wherein the attribute information comprises a flow name, a flow icon, a flow label, flow introduction text, introduction pictures and introduction videos; and after the PRA flow file and the attribute information are combined, publishing the PRA flow file on the flow market so as to put the PRA flow file on line.
In this embodiment, the attribute information may include, but is not limited to, a flow name, a flow icon, a flow label, a flow introduction text, an introduction picture, an introduction video, and the like, which is not particularly limited in this embodiment.
In this embodiment, if the PRA flow file is online, the PRA requirement is updated to the online status in the requirement pool list. It should be noted that, in each stage before the online, that is, the requirement design state, the requirement development state, the requirement test state, and the requirement online state, the first user or the second user may set the state as the terminated state according to the actual situation.
Furthermore, the online PRA process file can be displayed in the process market, and the user can search through the process name and the introduction text keyword and screen the required PRA process file through the tag. The PRA flow file of interest may be downloaded locally or into the flow file and the system may automatically record the number of downloads. Users who download the PRA process files can also comment on the PRA process files to propose respective suggestions or comments.
Specifically, the online PRA process files are shown in the process market as an application scenario of one of the process markets of fig. 1e, where each PRA process file has a corresponding version number.
In this embodiment, the user may import the PRA flow file downloaded locally to the flow designer to continue editing, or the user may use the PRA flow file downloaded to the flow list to issue a robot task, etc.
In this embodiment, as shown in an application scenario of online PRA process files in fig. 1f, the whole process from audit to audit passing of the requirement list, to release of online PRA process files to the process market, and to download to the process list is shown.
According to the embodiment of the invention, the PRA requirement of the first user is sent to the second user for auditing, the PRA flow file is automatically generated according to the PRA requirement when the PRA requirement passes, and the PRA flow file is used online, so that automatic requirement management of a robot flow is realized, the problem of low efficiency of flow synchronization is solved, and the on-line management flow and version management of the requirement are realized by constructing a method and platform for unified management of the requirement and the flow, so that standard and efficient flow requirement processing and achievement synchronization are realized.
Example two
Fig. 2 is a flowchart of a method for realizing automation requirements of a robot flow according to a second embodiment of the present invention, where after a PRA flow file is online, the method further includes: receiving a demand update instruction of a first user for PRA demand; and generating a PRA updating flow file according to the demand updating instruction, and binding the PRA updating flow file with the PRA flow file. The same terms as those of the above embodiments are not repeated herein. As shown in fig. 2, the method includes:
s210, acquiring the robot flow automation PRA requirement of the first user so as to enable the second user to audit the robot flow automation requirement.
And S220, when the PRA requirement approval is determined to pass, automatically generating a PRA flow file according to the PRA requirement.
S230, the PRA flow file is online.
S240, receiving a demand update instruction of the first user for the PRA demand, wherein the update instruction comprises an initial version number and demand update content.
In this embodiment, when the first user wants to update the PRA requirement or change the requirement of the service department, a requirement update instruction may be issued, and because the update instruction includes the initial version number and the requirement update content, the PRA flow file that needs to be updated may be obtained based on the update instruction.
S250, generating a PRA update flow file according to the demand update instruction, and binding the PRA update flow file with the PRA flow file.
In this embodiment, after the update instruction is submitted, the PRA update flow file may automatically append a new version, and automatically bind the requirements of the new version and the old version together.
Specifically, as shown in an application scenario of binding a requirement list in fig. 2b, the requirements of the new version and the old version can be bound.
In this embodiment, if a user submits multiple version requirements for a service, the PRA flow file versions corresponding to the online requirements may also be automatically bound, as shown in an application scenario diagram corresponding to one of the requirements and the flow version in fig. 2 c.
And S260, the first user downloads and uses the PRA flow file.
In this embodiment, when a new version of the first user downloading process is online, the first user may select the most recent version of the PRA process file for downloading and use, or may fall back to a certain history version. All versions of PRA flow files may be found and used in the flow market.
According to the embodiment of the invention, the PRA requirement of the first user is sent to the second user for auditing, the PRA flow file is automatically generated according to the PRA requirement when the PRA requirement passes, and the PRA flow file is used online, so that automatic requirement management of a robot flow is realized, the problem of low efficiency of flow synchronization is solved, and the on-line management flow and version management of the requirement are realized by constructing a method and platform for unified management of the requirement and the flow, so that standard and efficient flow requirement processing and achievement synchronization are realized.
Example III
Fig. 3 is a flowchart of a method for realizing the automation requirement of the robot flow according to the third embodiment of the present invention. The same terms as those of the above embodiments are not repeated herein. As shown in fig. 3, the method includes:
s310, registering a robot flow automation PRA requirement of a first user.
In this embodiment, when the service department user a finds that a certain service can be automatically implemented through the RPA robot during work, a robot flow automatic PRA requirement is created on the requirement management platform and submitted for auditing, and the requirement management platform registers the robot flow automatic PRA requirement of the first user.
S320, the second user checks the automatic PRA requirement of the robot flow.
In this embodiment, the process design department director B may review the PRA requirement, and if it is determined that the PRA requirement has an implementation prospect, the PRA requirement review is passed and sent to the second user corresponding to the requirement design state, the requirement research and development state and the requirement test state.
S330, the second user processes the robot flow automation PRA demand state.
And S340, if the verification of the PRA requirement of the robot process automation is passed, uploading the PRA process file corresponding to the PRA requirement of the robot process automation to a process market.
In this embodiment, if the robotic flow automation PRA requirement audit passes, the second user uploads the PRA flow file corresponding to the robotic flow automation PRA requirement to the flow market, and reminds the first user to download and use in the flow market.
S350, the first user downloads and uses the PRA flow file.
In this embodiment, if the first user a uses the PRA flow file, an update requirement may be set for the PRA flow file to update the PRA flow file.
According to the embodiment of the invention, the PRA requirement of the first user is sent to the second user for auditing, the PRA flow file is automatically generated according to the PRA requirement when the PRA requirement passes, and the PRA flow file is used online, so that automatic requirement management of the robot flow is realized, and the on-line management flow and version management of the requirement are realized by constructing a method and a platform for unified management of the requirement and the flow, so that standard and efficient flow requirement processing and achievement synchronization are realized.
Example IV
Fig. 4 is a schematic structural diagram of a robot flow automation requirement implementation device according to a fourth embodiment of the present invention. As shown in fig. 4, the apparatus includes: a PRA requirement acquisition module 401, a PRA flow file generation module 402, and a PRA flow file online module 403.
The PRA requirement acquisition module 401 is configured to acquire a robot flow automation PRA requirement of a first user, so that a second user can audit the robot flow automation requirement;
a PRA procedure file generating module 402, configured to automatically generate a PRA procedure file according to the PRA requirement when it is determined that the PRA requirement is approved;
and a PRA procedure file online module 403, configured to online the PRA procedure file, so that the first user downloads the PRA procedure file for use.
Optionally, the PRA requirement acquisition module 401 is specifically configured to:
when the login request of the first user is determined to be received, a demand template is called, and the demand template is displayed so that the first user fills in the demand template;
receiving demand content sent by the first user based on the demand template, and generating a demand draft according to the demand content, wherein the demand content comprises a demand name, a demand background, a target use department, a manual operation description of a business process, and a related software and hardware system or a related picture video file;
and displaying the required draft in a required list, and adding an initial version number to the required draft and generating the PRA requirement when determining that a submitting and auditing instruction of a user to the required draft is received.
Optionally, the PRA requirement acquisition module 401 is specifically configured to:
displaying the PRA requirement in the to-be-checked state in a checking list for the second user to check;
when the approval passing instruction of the second user on the PRA requirement is determined to be received, updating the state of the PRA requirement into an approved state in the auditing list;
and displaying the PRA requirements in the agreed state in a requirement pool list, and updating the state of the PRA requirements in the requirement pool list into a requirement design state.
Optionally, the PRA flow file generation module 402 is specifically configured to:
automatically generating a flow design document by semantic recognition according to the PRA demand, and updating the PRA demand into a demand research and development state in the demand pool list, wherein the flow design document comprises design flow content and test flow content;
analyzing the design flow content in the flow design document to automatically generate the PRA flow file, and updating the PRA requirement in the requirement pool list to be in a requirement test state.
Optionally, the PRA flow file generation module 402 is specifically configured to:
analyzing the test flow content in the flow design document to automatically generate a PRA flow test case, and updating the PRA requirement in the requirement pool list to be in a requirement online state;
and testing the PRA flow file through the PRA flow test case, and determining that the PRA flow file meets the online requirement when the PRA flow file passes the test.
Optionally, the PRA flow file generation module 402 is specifically configured to:
receiving an online instruction of the PRA requirement in a requirement online state of the second user, and containing attribute information aiming at the PRA flow file in the online instruction, wherein the attribute information comprises a flow name, a flow icon, a flow label, a flow introduction text, an introduction picture and an introduction video;
and after the PRA flow file and the attribute information are combined, publishing the PRA flow file on a flow market so as to put the PRA flow file on line.
Optionally, the PRA flow file online module 403 is specifically configured to:
receiving a demand update instruction of the first user for the PRA demand, wherein the update instruction comprises the initial version number and demand update content;
and generating a PRA update flow file according to the demand update instruction, and binding the PRA update flow file with the PRA flow file.
The robot flow automatic demand realizing device provided by the embodiment of the invention can execute the robot flow automatic demand realizing method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the executing method.
Example five
Fig. 5 shows a schematic diagram of the structure of an electronic device 10 that may be used to implement an embodiment of the invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic equipment may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.
As shown in fig. 5, the electronic device 10 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may perform various appropriate actions and processes according to the computer program stored in the Read Only Memory (ROM) 12 or the computer program loaded from the storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.
Various components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, etc.; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.
The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the various methods and processes described above, such as the robotic flow automation demand implementation method.
In some embodiments, the robotic flow automation requirement implementation method may be implemented as a computer program tangibly embodied on a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM12 and/or the communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more of the above-described robot flow automation requirements implementing methods may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the robotic flow automation requirement implementation method in any other suitable manner (e.g., by means of firmware).
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuit systems, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems On Chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for carrying out methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.
It should be appreciated that the various forms of flow shown above may be used, reordered, added or deleted. For example, the respective embodiments described in the present invention may be executed in parallel, sequentially or in a different order, so long as the desired results of the embodiments of the present invention can be achieved, and are not limited herein.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
Claims (10)
1. The method for realizing the automatic requirement of the robot flow is characterized by comprising the following steps:
acquiring a robot process automation PRA requirement of a first user for a second user to audit the robot process automation requirement;
when the PRA requirement approval is determined to pass, automatically generating a PRA flow file according to the PRA requirement;
and uploading the PRA flow file to be downloaded and used by the first user.
2. The method of claim 1, wherein the acquiring the robotic flow automation PRA requirement of the first user comprises:
when the login request of the first user is determined to be received, a demand template is called, and the demand template is displayed so that the first user fills in the demand template;
receiving demand content sent by the first user based on the demand template, and generating a demand draft according to the demand content, wherein the demand content comprises a demand name, a demand background, a target use department, a manual operation description of a business process, and a related software and hardware system or a related picture video file;
and displaying the required draft in a required list, and adding an initial version number to the required draft and generating the PRA requirement when determining that a submitting and auditing instruction of a user to the required draft is received.
3. The method of claim 2, wherein after the obtaining the first user's robotic flow automation PRA requirement, further comprising:
displaying the PRA requirement in the to-be-checked state in a checking list for the second user to check;
when the approval passing instruction of the second user on the PRA requirement is determined to be received, updating the state of the PRA requirement into an approved state in the auditing list;
and displaying the PRA requirements in the agreed state in a requirement pool list, and updating the state of the PRA requirements in the requirement pool list into a requirement design state.
4. The method of claim 1, wherein the automatically generating the PRA flow file according to the PRA requirement comprises:
automatically generating a flow design document by semantic recognition according to the PRA demand, and updating the PRA demand into a demand research and development state in the demand pool list, wherein the flow design document comprises design flow content and test flow content;
analyzing the design flow content in the flow design document to automatically generate the PRA flow file, and updating the PRA requirement in the requirement pool list to be in a requirement test state.
5. The method of claim 4, wherein after automatically generating a PRA flow file according to the PRA requirement, further comprising:
analyzing the test flow content in the flow design document to automatically generate a PRA flow test case, and updating the PRA requirement in the requirement pool list to be in a requirement online state;
and testing the PRA flow file through the PRA flow test case, and determining that the PRA flow file meets the online requirement when the PRA flow file passes the test.
6. The method of claim 5, wherein the uploading the PRA flow file comprises:
receiving an online instruction of the PRA requirement in a requirement online state of the second user, and containing attribute information aiming at the PRA flow file in the online instruction, wherein the attribute information comprises a flow name, a flow icon, a flow label, a flow introduction text, an introduction picture and an introduction video;
and after the PRA flow file and the attribute information are combined, publishing the PRA flow file on a flow market so as to put the PRA flow file on line.
7. The method of claim 2, wherein after the PRA procedure file is online, further comprising:
receiving a demand update instruction of the first user for the PRA demand, wherein the update instruction comprises the initial version number and demand update content;
and generating a PRA update flow file according to the demand update instruction, and binding the PRA update flow file with the PRA flow file.
8. A robot flow automation demand realization device, comprising:
the PRA demand acquisition module is used for acquiring the robot flow automatic PRA demand of the first user so as to enable the second user to audit the robot flow automatic demand;
the PRA process file generation module is used for automatically generating a PRA process file according to the PRA requirement when the PRA requirement approval is confirmed to pass;
and the PRA process file online module is used for online the PRA process file so as to be downloaded and used by the first user.
9. An electronic device, the electronic device comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,,
the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.
10. A computer readable storage medium storing computer instructions for causing a processor to perform the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211651354.3A CN116011955A (en) | 2022-12-21 | 2022-12-21 | Robot flow automation demand realization method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211651354.3A CN116011955A (en) | 2022-12-21 | 2022-12-21 | Robot flow automation demand realization method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116011955A true CN116011955A (en) | 2023-04-25 |
Family
ID=86034970
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211651354.3A Pending CN116011955A (en) | 2022-12-21 | 2022-12-21 | Robot flow automation demand realization method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116011955A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116432169A (en) * | 2023-06-13 | 2023-07-14 | 达而观信息科技（上海）有限公司 | Automatic task permission control method, system and equipment based on sharing strategy |
-
2022
- 2022-12-21 CN CN202211651354.3A patent/CN116011955A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116432169A (en) * | 2023-06-13 | 2023-07-14 | 达而观信息科技（上海）有限公司 | Automatic task permission control method, system and equipment based on sharing strategy |
| CN116432169B (en) * | 2023-06-13 | 2023-09-26 | 达而观信息科技（上海）有限公司 | Automatic task permission control method, system and equipment based on sharing strategy |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9824403B2 (en) | Measuring problems from social media discussions | |
| CN111435367A (en) | Knowledge graph construction method, system, equipment and storage medium | |
| CN116011955A (en) | Robot flow automation demand realization method, device, equipment and storage medium | |
| US9530112B2 (en) | Common conditions for past projects as evidence for success causes | |
| CN116483707A (en) | Test method, test device, test apparatus, test program, and test program | |
| CN116185389A (en) | Code generation method and device, electronic equipment and medium | |
| CN116009847A (en) | Code generation method, device, electronic equipment and storage medium | |
| CN116089739A (en) | Message pushing method, device, electronic equipment and storage medium | |
| CN115860877A (en) | Product marketing method, device, equipment and medium | |
| CN115016321A (en) | Hardware-in-loop automatic testing method, device and system | |
| CN114443493A (en) | Test case generation method and device, electronic equipment and storage medium | |
| CN116629810B (en) | Operation recommendation method, device, equipment and medium based on building office system | |
| CN113438428B (en) | Method, apparatus, device and computer-readable storage medium for automated video generation | |
| CN115859926B (en) | Electronic form data relationship processing method and device, electronic equipment and medium | |
| CN114219453A (en) | Task processing method and device, electronic equipment and storage medium | |
| CN117311675B (en) | Service configuration method and device related to distributed system and electronic equipment | |
| CN112560462B (en) | Event extraction service generation method, device, server and medium | |
| CN113239296B (en) | Method, device, equipment and medium for displaying small program | |
| CN117632874A (en) | Automatic drawing storage method, device, equipment and medium for CAD software | |
| CN117931176A (en) | Business application generation method, device, platform and medium | |
| CN118210408A (en) | Information display method and device, electronic equipment and storage medium | |
| CN117251196A (en) | Data maintenance method, device, equipment and storage medium | |
| CN116578372A (en) | Editing method, device, equipment and storage medium for large data screen | |
| CN118193389A (en) | Test case generation method, device, equipment, storage medium and product | |
| CN115983222A (en) | EasyExcel-based file data reading method, device, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |