Transaction Overview

Organizational Collaboration

Efficient collaboration between two or more organization is essential for a transaction to be executed in a timely manner. Block Aero's transaction feature allow an organization to design it's transaction workflow template and choose other network organizations to participate and accomplish a cooperative task. All documents, data, reviews, approvals, signature is stored in the blockchain for transparency, auditing and trust.

In this documentation, you will learn about the general components within a transaction to better prepare for the workflow between two organization.

Transaction Participants

Each of transaction has two types of participants

  • Initiator is an organization/individual who initiates a transaction and invite other network organization into the transaction workflow.
  • Participant is an organization/individual who has been invited from the initiator to participate in the transaction workflow
3360

πŸ“˜

Transaction Initiator is always Italicized

In most cases, initiator of a transaction will be the organization that moves a stage forward by approving a stage completion.

Transaction Status

3362
Transaction StatusDescription
PendingThe initial status after completing a transaction creation. This transaction is awaiting for all participating organization to approve.
ActiveAn ongoing transaction that all participants are working on.

Status transition from

"Pending" to "Active"
CompleteA complete transaction

Status transition from

"Active" to "Complete"
Pending TerminationWhen one of participant has request a transaction to be terminated.

Status transition from

"Pending" to "Pending Termination"
"Active" to "Pending Termination"
TerminatedWhen all participant organization has approved a termination request.

Status transition from

"Pending Termination" to "Terminated"
RejectedA pending transaction that was rejected from an organization

Status transition from

"Pending" to "Rejected"

General Transaction Layout

Transaction are divided into 4 main compartments:

  • Transaction Summary - contains primary assets of the transaction, participating organizations, transaction status, current stage within the transaction workflow, transaction due date, transaction creation date and transaction ID
  • Audit Log - contains a log of all the events, actions and remarks that has occurred within this transaction.
  • Navigation Panel - contains information about the transaction's workflow in stages and requirement. The user can navigate the workflow panel by using this navigation panel.
  • Workflow Panel - contains stage requirements and tasks that the participants need to accomplish. It is where majority for the work is going to be done.
3360

General Transaction Layout

Stage and Transaction Requirements

Every transaction has different stages and requirements that is predefined in the workflow that was selected in the "Create a Transaction" process.

It is imperative to understand the concept of stages and requirements in every transaction.

3366

Stage and Transaction Requirement Level

Stage Level

Each stage contain multitude of requirements for participants to work on. All requirements within a stage must be completed and approved before moving onto the next stage of the transaction workflow.

3360

A completed stage awaiting for the transaction initiator's approval

Transaction Requirement Level

Each Transaction Requirement Level, may have the different requirement names, instructions, and methods to complete. All requirement's structure are predefined in the transaction workflow template.

Transaction requirements lives in 3 main buckets: Submit Data, Review and Approve Data, and Completed Requirement.

  • Submit Data: contains requirement that needs to be filled with proper data and documents by an organization's data entry participant.
  • Review and Approve Data: contains requirement that needs to be reviewed and approved by organization participants who is responsible to review and approve data.
  • Completed Requirement: contains requirement that was review and approved by organization participants who is responsible to review and approve data.

Every transaction requirement has instructions for participants to follow.

2090

Submit Data, Review and Approve Data, Completed Requirements

3198

Submit Data - Expanded Requirement, Requirement was resubmitted by a reviewer due to faulty data and documents.

πŸ“˜

Previewing Stages and Requirements

Organization participants of a transaction can preview stages and requirements during "Pending Transaction" and while working on an "Active Transaction".

3360

Preview mode in a "Pending Transaction"