Prosecution Insights
Last updated: November 12, 2026
Application No. 19/044,966

SYSTEM AND METHOD FOR ENFORCING BROWSER-BASED APPLICATION WORKFLOW COMPLIANCE

Final Rejection §103§112
Filed
Feb 04, 2025
Priority
Nov 04, 2022 — provisional 63/422,906 +2 more
Examiner
KIM, TAE K
Art Unit
2496
Tech Center
2400 — Computer Networks
Assignee
Openmethods
OA Round
2 (Final)
75%
Grant Probability
Favorable
3-4
OA Rounds
80%
With Interview

Examiner Intelligence

Grants 75% — above average
75%
Career Allowance Rate
502 granted / 673 resolved
+16.6% vs TC avg
Moderate +5% lift
Without
With
+5.3%
Interview Lift
resolved cases with interview
Typical timeline
Avg Prosecution
25 currently pending
Career history
707
Total Applications
across all art units

Office Action

§103 §112
DETAILED ACTION This Action is in consideration of the Applicant’s response on August 19, 2026. Claims 1, 7, 10, 11, 15, 16, and 20 are amended by the Applicant. Claims 1 – 4, 7 – 13, 15 – 18, and 20, where Claims 1, 10, and 15 are in independent form, are presented for examination. Notice of Pre-AIA or AIA Status The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA . Response to Arguments Applicant's arguments filed August 19, 2026 have been fully considered but they are moot based on the new grounds of rejection necessitated by amendment. Claim Rejections - 35 USC § 112 The following is a quotation of 35 U.S.C. 112(b): (b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention. The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph: The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention. Claims 1 – 4, 7 – 13, 15 – 18, and 20 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention. 1. A broad range or limitation together with a narrow range or limitation that falls within the broad range or limitation (in the same claim) may be considered indefinite if the resulting claim does not clearly set forth the metes and bounds of the patent protection desired. See MPEP § 2173.05(c). In the present instance, Claims 1, 10, and 15 recite the broad recitation “a workflow-compliant action,” and the claim also recites “the workflow-compliant action satisfying the workflow sequence requirements” which is the narrower statement of the range/limitation. The claim(s) are considered indefinite because there is a question or doubt as to whether the feature introduced by such narrower language is (a) merely exemplary of the remainder of the claim, and therefore not required, or (b) a required feature of the claims. In other words, the claimed workflow-complaint action that is received to further enable interaction with the browser-based application does not specify any type of requirement, whereas later in the claims the same workflow-compliant action is supposed to satisfy the workflow sequence requirements of the predefined workflow sequence. The bounds of this specific limitation are unclear. The dependent claims are rejected based on their dependency on Claims 1, 10, and 15 and under the same rationale. Claim Rejections - 35 USC § 103 The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. Claim(s) 1 – 4, 7 – 13, 15 – 18, and 20 are rejected under 35 U.S.C. 103 as being unpatentable over PGPub. 2021/067608 (hereinafter “Fleck”), in view of PGPub. 2017/0242567 (hereinafter “Lefor”). 2. Regarding Claims 1, 10, and 15, Fleck discloses a system for enforcing workflow compliance [Figs. 2 and 7], comprising: a computing device comprising at least one processor, wherein a plurality of programming instructions, when operating on the at least one processor [Fig. 2; Para. 0031-38], causes the computing device to: receive application data from a browser-based application [Figs. 8-10; Para. 0077-81; user input in a CRM application session within a web browser]; analyze the application data to detect workflow events, wherein the workflow events correspond to deviations from a predefined workflow sequence [Figs. 8-10; Para. 0077-81; identify if there is a problem with user input into a CRM app form being submitted; certain fields must be filled to continue registering new customer (predetermined workflow sequence)]; select notification content based on the detected workflow events, wherein the notification content provides guidance for proceeding in accordance with the predefined workflow sequence [Figs. 8-10; Para. 0077-81; pop-up window provides a solution to the user]; cause display of the notification content in connection with the browser-based application [Figs. 8-10; Para. 0077-81; pop-up window provides a solution to the user], wherein the notification content comprises a modal dialog that disables interactions with the browser-based application until a workflow-complaint action is received [Figs. 8-10; Para. 0077-81; pop-up window provides a solution to the user that resolves the detected error to continue the form submission]; and validate subsequent user actions against workflow sequence requirements of the predefined workflow sequence until the workflow-compliant action is received [Figs. 8-10; Para. 0077-81; determine if user action results in successful outcome for the CRM app form]. Fleck, however, does not specifically disclose that the workflow-complaint action satisfies the workflow sequence requirements of the predefined workflow sequence. Lefor discloses a system and method for generating a pop-up or modal dialog box when there is an unexpected or failed action [Figs. 1A, 1B, 2; Para. 0020]. Lefor further discloses that the user cannot proceed to interact with the main application until the user supplies the required information (the workflow-complaint action satisfies the workflow sequence requirements of the predefined workflow sequence) [Para. 0021]. It would have been obvious to one skilled in the art before the effective filing date of the current invention to incorporate the teachings of Lefor with Fleck since both systems detect missing information within an application and trigger an alert to the user based on this detection. The combination would enable Fleck to provide clear notifications to the user of what is missing and required within the application prior to continuing with entering additional data within the application. The motivation to do so is to focus the user’s attention to the specific issues discovered for faster problem resolution (obvious to one skilled in the art). 3. Regarding Claims 2, 11, and 16, Fleck, in view of Lefor, discloses the limitations of Claims 1, 10, and 15. Fleck further discloses that the browser-based application is a customer relationship application [Figs. 8-10; Para. 0077-81; user input in a CRM application session within a web browser]. 4. Regarding Claims 3, 12, and 17, Fleck, in view of Lefor, discloses the limitations of Claims 1, 10, and 15. Fleck further discloses that the workflow events comprise skipped or dismissed workflow steps [Figs. 8-10; Para. 0077-81; detect missing data in mandatory form fields for CRM app form]. 5. Regarding Claims 4, 13, and 18, Fleck, in view of Lefor, discloses the limitations of Claims 1, 10, and 15. Fleck further discloses of: retrieve enterprise-specific formatting rules from a database [Figs. 8-10; Para. 0080-81; solutions can be presented to the user via pop-ups, arrows, watermarks, and other indicators based on the problem]; and format the notification content based on the enterprise-specific formatting rules [Figs. 8-10; Para. 0080-81; solutions can be presented to the user via pop-ups, arrows, watermarks, and other indicators based on the problem]. 6. Regarding Claims 7 and 20, Fleck, in view of Lefor, discloses the limitations of Claims 1 and 13. Fleck further discloses that validating subsequent user actions comprises: monitoring user actions responsive to the displayed notification content [Figs. 8-10; Para. 0077-81]; determining whether each monitored user action satisfies workflow requirements [Figs. 8-10; Para. 0077-81; determine if user action results in successful outcome for the CRM app form]; and repeatedly displaying the notification content until the workflow-compliant action is detected [Para. 0077-81]. 7. Regarding Claim 8, Fleck, in view of Lefor, discloses the limitations of Claim 1. Fleck further discloses that the workflow sequence requirements define mandatory steps that must be completed in a prescribed order [Para. 0077-81; CRM required fields must be completed prior to submitting the charm]. 8. Regarding Claim 9, Fleck, in view of Lefor, discloses the limitations of Claim 1. Fleck further discloses that the system is further configured to store workflow events and associated user actions in a database for analysis of workflow compliance patterns [Para. 0075, 0079]. Conclusion Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a). A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action. Contacts Any inquiry concerning this communication or earlier communications from the examiner should be directed to TAE K KIM whose telephone number is (571)270-1979. The examiner can normally be reached M-F 9:30-5:30. Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Jorge Ortiz-Criado can be reached at 5712727642. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /TAE K KIM/Primary Examiner, Art Unit 2496
Read full office action

Prosecution Timeline

Feb 04, 2025
Application Filed
May 19, 2026
Non-Final Rejection mailed — §103, §112
Aug 19, 2026
Response Filed
Oct 29, 2026
Final Rejection mailed — §103, §112 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12783667
METHODS AND SYSTEMS FOR PROTECTING SHADOW COPIES
3y 7m to grant Granted Nov 03, 2026
Patent 12776917
CRYPTOGRAPHIC PROOF OF IDENTITY WITH INDEPENDENT VERIFICATION AND PROVABLE RECOVERY
4y 2m to grant Granted Oct 27, 2026
Patent 12776920
CROSS-CERTIFICATION METHOD AND DEVICE FOR CHARGING ELECTRIC VEHICLE
2y 10m to grant Granted Oct 27, 2026
Patent 12775731
PROVENANCE DATA INTEGRITY PROTECTION
2y 1m to grant Granted Oct 27, 2026
Patent 12755023
Non-Intrusive Method of Detecting Security Flaws of a Computer Program
2y 1m to grant Granted Oct 06, 2026
Study what changed to get past this examiner. Based on 5 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

3-4
Expected OA Rounds
75%
Grant Probability
80%
With Interview (+5.3%)
Moderate
PTA Risk
Based on 673 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month