The generic transactor

Last updated on
15 April 2018

Included in the module, it is a very basic transactor. It really does nothing on execution, except changing its execution status. It has two main usages:

  • to create transactional flows that only hold information, such as tracking or logging systems

  • to be used as a base for more complex transactors

Meta-fields

This transactor has the following meta-fields in the transaction entity:

  • log_message
    (optional) a text field with details about the transaction

And in the target entity:

  • last_transaction
    (optional) an entity reference field to be updated with a reference to the last executed transaction

Configuration options

None.

Execution validation

There are no particular conditions to satisfy prior the execution of transactions with this transactor.

Execution result codes and messages

On successful execution

  • RESULT_OK (1)
    “The transaction was executed successfully.”

On failed execution

  • RESULT_ERROR (-1)
    Soft error: “There was a recoverable error in the transaction execution.”
    Hard error: “There was a fatal error in the transaction execution.”

Message compositions

Transaction description

  • For executed transactions: “Transaction #N”

  • For pending transactions: “Transaction #N (pending)”

  • For new transactions (not saved): “Unsaved transaction”

Transaction details

A single line with the contents of the log message field if it is present and not empty.

Execution indications

A simple note telling the user that the target entity might be updated as a result of the transaction execution.

Help improve this page

Page status: No known problems

You can: