JS7 JobScheduler

Space shortcuts

Page tree

Versions Compared

Old Version 2

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version 3

changes.mady.by.user Gitesh Patidar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

User 1 (Proposer) prompts User 2 (Approver) to confirm an operation. 

  • The prompting can be performed within the JOC Cockpit.

  • Failover and switchover of the JOC Cockpit have to be supported.

  • The prompts are persisted, and a list of open prompts should be available on the JOC Cockpit, allowing users to cancel and confirm prompts.

  •  A specific role is required to confirm or cancel a prompt.


When User 2 (Approver) is not connected to the JOC Cockpit at the moment

  • If User 1 prompts to confirm an operation and User 2 is not connected to the JOC Cockpit at the moment, User 2 should be able to confirm or cancel the operation from an application on their smartphone.

  • The confirmation process needs to be handled by an external app, allowing User 2 to approve the operation without connecting to the JOC Cockpit directly.

  • For example -

    • JOC Cockpit could generate a challenge code whenever a confirmation is needed for an operation.

    • JOC Cockpit sends this challenge (via an outgoing connection) to an external component that is hosted on a secure server with internet access.

    • The external server, integrated with a third-party authorization app (ex-Google Authenticator), passes the challenge to Approver's smartphone.

    • The Approver receives the challenge on their smartphone and uses the app to generate the related response code. They then verbally communicate this response code back to User 1.

    • User 1 enters the response code into the JOC Cockpit to confirm the operation.

    • If the Approver wants to cancel the operation request the application can have a cancel button or an option to generate a cancellation response code

Prompt Notification System

When User 1 prompts User 2 to confirm an operation, User 2 should receive a notification on JOC Cockpit and via email (only high-priority operations) and if User 2 confirms or cancels a prompt, User 1 should receive a notification in JOC Cockpit and via email, so that they can immediately be informed about the status of the operation and act accordingly. 

  • Notifications should include details of the prompt and the response (confirmed/canceled).

  • Users can customize notification preferences. In case User 2 is not available, User 3 should receive a notification on JOC Cockpit and via email.

Fallback User Notification

When User 2 is unavailable, User 3 should be notified to take over confirmation to ensure that the confirmation process is not interrupted. 

  • The list of accounts for fallback to confirm an operation has to be predefined.

  • JOC Cockpit should automatically check the availability of User 2. If unavailable, User 3 is notified and prompted to confirm.

Pending prompts summary - 

  • Along with the real-time notification of high-priority prompts,  approvers could receive a summary of pending prompts at predefined intervals (hourly or daily basis) to manage pending prompts more efficiently.

Multiple operation conformation - 

  • The approver should be able to confirm or cancel multiple operation prompts in a single action to handle

Audit Log Entries for Operations

  • The audit log should contain all operations and confirmations so that users can identify any discrepancies. The audit log should record all operations, confirmations, and cancellations. The log includes user IDs of both User 1 and User 2, and operation details.

Table of Contents