Hedera Send Transaction Tool

Introduction

The Hedera Send Transaction Tool is a process tool plugin that allows you to transfer HBAR and tokens from one account to another on the Hedera Distributed Ledger Technology (DLT). This plugin also provides an option to schedule transactions, such as those involving multi-signature accounts or transactions that require receiver signatures.

Get started

Prerequisites

• You have access to the Hedera DLT network.
• The sender and receiver accounts are correctly set up with adequate permissions.

Where to get the plugin

Download the Hedera Send Transaction Tool from the JogetOSS GitHub repository.

How to install

1. Click Download on this plugin screen (It will be a .jar file).
2. Go to your Joget localhost or server. In the Joget Console, go to Admin Bar > Systems Settings > Manage Plugins and click the Upload Plugins button.
3. Under Upload Plugin, select the plugin .jar file you downloaded and click Upload.
4. Depending on the plugin type, you can now view your new plugin in your form, List, or UI Builder.
5. Remember to uninstall the old plugin before uploading a new version.
6. The Joget Knowledge Base has more information on managing and developing plugins.

Configure hedera send transaction tool properties

• Operator ID: This corresponds to your Hedera Operator ID. For further details, see the Hedera Default Backend Configuration.
• Operator Key: Enter your Hedera Operator Key to create an account.
• Network Type: Choose Previewnet, Testnet, or Mainnet based on your environment.

Transaction details

• Form: Select a form from which to retrieve transaction data.

  All fields from the selected form will be available for field mapping in the below sections.

Token configuration

• Payment Type: Select the token type to transfer:
  • HBAR
  • Fungible Token
  • Non-fungible Token
• Token ID: This property will only appear when Payment Type is Fungible Token or Non-fungible Token.

  The ID of an existing token on the Hedera DLT that the sender account possesses. You can use a Hash Variable or hardcoded.

• NFT Serial Number: This property will only appear when the Payment Type is Non-fungible Token.

  The serial number of the NFT that belongs to the Token ID set above is what the sender account possesses.
  Typically, a Hash Variable is used here.

Payment configuration

• Sender Account ID: Account to send funds from.
• Sender Account Mnemonic Phrase: The sender account's secret key is required to perform actions with the sender's account. Only accepts Hash Variable that points to the sender's encrypted stored mnemonic phrase.
  
  Caution: Ensure that the Account Mnemonic Phrase is always kept secure. Anyone with access to this phrase has complete control over the account and can cause irreparable damage.
• Receiver Account ID: The account to which funds are sent.
• Auto-associate Token with Receiver: This property will only appear when the Payment Type is Fungible Token or Non-fungible Token. It caters to use cases where receiver accounts are within the Joget platform's control.
• Receiver Account Mnemonic Phrase: This property will only appear when the Payment Type is Fungible Token or Non-fungible Token. Mnemonic phrase of the receiver account.
  Only accepts Hash Variable that points to the receiver's encrypted stored mnemonic phrase.
  This is used only to associate tokens for the receiver before the token transfers automatically.
• Amount to Send: This property will only appear when the Payment Type is HBAR or Fungible Token.
  Amount of tokens to send. For HBAR, amount can only contain a maximum of 8 decimal places.
  For Fungible Token, decimal places depend on the token's decimal value previously set by the token minter.
• Insert Files SHA256 Checksum in Memo: 
  Check this option to insert the SHA256 checksum(s) of the uploaded file(s) in the transaction memo.
  If multiple files are present, they will be sorted by file name in ascending order, and the final checksum value will be the hash of all file checksums concatenated. 
  This is typically used when working with files uploaded in a form record, and you wish to record the integrity of such file(s) on the Hedera ledger.
• File(s) to Hash: This property will only appear when Insert Files SHA256 Checksum in Memo is checked.
  Select a File Upload field within your selected form.
• Transaction Memo: Insert your custom note for transfer transactions. It also accepts Hash Variable.
• Set as Scheduled Transaction: Check this option to schedule this transaction, such as performing transactions with multi-sig accounts, receiver signature required, etc.

Store response to workflow variable

• Schedule ID: Only available if Set as Scheduled Transaction property is checked.
  To store the schedule ID of this scheduled transaction for logging purposes or for Joget apps to refer to this value later to further act on this scheduled transaction.
• Is Transaction Validated: Indicates whether the transaction was successfully validated.
• Consensus Timestamp: To store the timestamp of when the majority of the network members received the transaction. At this point, the transaction becomes final and verifiable.
• Transaction ID: To store the transaction ID of the transaction performed.
• Transaction Explorer URL: This function generates a URL to track a transaction on a public ledger explorer (the default is Hashscan).

Download plugin

• Hedera Ledger Pack