Action Library
Action libraries are reusable transaction flows to create complex transactions that invoke several services, therefore speeding up the transactions building process. They can be used in as many transactions as necessary.
For example, you can have a transaction that validates an OTP, validates user and password, verifies products and asks for a balance detail. Each operation can be turned into an action library that can be invoked every time you need it in a different transaction.
Within the Action Library tab (Global Logic > Action Libraries ) you see a list of all the action libraries created within the Studio environment. To find an action library, use the search bar and search by name or description.
From this page, you can create an action library, which redirects you to the transactions editor, and edit existing action libraries.
Caution
Editing or deleting an action library that is in use might affect the transaction that is invoking it.
You can choose additional actions from the three-dot icon next to an action library:
You can delete an action library that is not being used; that is, it does not have any dependencies that may affect the transaction's functionality.
You can verify an action library's dependencies. By doing this, you can verify if that action library is being used in one or more transactions in the environment. A modal shows the code, name and product of the transactions where the action library is being used.
You can duplicate the action library.
Read Create an Action Library to learn more about this process, or Action Libraries in the Transactions section to learn how to use your action libraries within a transaction.