Used In
Used In is a feature within App Flow that allows you to search if a screen, process, transaction, token or array is being used within your branch's screens and processes. This helps determine the impact any updates can have on your app. For example, you can verify how many processes are consuming an specific transaction before making updates that can have a large impact on the app. You can also verify if certain token is being used within screens or processes in your branch.
Important
Used In searches for elements within screens and processes only.
With Used In, you can also download a list of tokens and arrays that are in use within your environment, so that it is easier to track which ones are unavailable or taken.
Additionally, after your search, you can select to diagram the element in App Flow to visualize how it is being used, and its previous and following steps within the app's flow.
Search for an Element
In Used In, you can search for different elements and track if they are in use within screens or processes in your branch. First, click one of the choice chips to select the type of element you want to find. These elements are:
Screens. Search screens by name or long syntax.
Legacy and 
lambda processes. Search processes by name.Transactions. Search native and configurable transactions by name and transaction code. Predictive search is not enabled for this element.
Tokens. Search tokens by number, alias, or with the #S expression (#S10). Note that, when searching by expression, Used In will only search for the value (in this case, the value is 10). Predictive search is not enabled for this element.
Arrays. Search arrays by number, alias, or with the #A expression (#A{10:30:2}). Note that, when searching by expression, Used In will only search for the value (in this case, the value is 10). Predictive search is not enabled for this element.
When looking for screens and processes, the predictive search will throw coincidences or suggestions for you to select from. Select the screen or process from the coincidences listed, and Used In will search if it is being used within the screens and processes on your app.
 |
Since Used In only detects elements in use within screens and processes in your branch, the results will be divided into two tabs: Screens and Processes, and the number of entities that are using the corresponding element between brackets.
See below for an example where a user needs to analyze which processes are consuming transaction number 1058. They select the Transaction choice chip and type the 1058 ID, then Used In throws three results: two lambda processes and one legacy process.
On the results panel, you can click the App Flow icon next to each screen or process that is using the element you searched for in Used In. This way, you can draw the flow for the selected screen or process and visualize how the app is built. You can also click edit to open the corresponding screen or process.
Read below to learn about the information Used In provides depending on the elements you are searching for.
When searching if a screen or process is used within your branch, Used In displays the following:
In the Screens tab, you see the screens that are using the selected screen or process with the name and their syntax. If a screen is referencing itself, the same screen also appears as a result.
In the Process tab, you see the processes (legacy or lambda) that are using the selected screen or process and their description. If a process is referencing itself , the same process also appears as a result.
Important
Note that, in legacy processes, if there is an entity invoked with another token different than 801, which is the process' next step, that entity will not throw any results in Used In. For example, if I state on step 10 in a legacy process that the token 780 has the screen payment_screen01 as value, when I search for the screen in Used In, the feature will not throw any results as the screen is not being used on the next (801) token.
When searching if a transaction is used within your branch in legacy or lambda processes, Used In displays the name of the processes (legacy or lambda) that are using the transaction, their description and, for legacy processes, the steps that are invoking the transaction. In lambda processes, you see the name of the blocks that are invoking the transaction.
When searching if a token or array is used within your branch, Used In displays the following:
In the Screens tab, you see the screens that are using the token or array with their name, syntax, and the component that is using it, with its name and ID.
In the Process tab, you see the processes (legacy or lambda) that are using the token or array, their description and, for legacy processes, the steps that are using the token. In lambda processes, you see the name of the blocks that are using the token.
Unavailable Tokens and Arrays
With Used In, you can see and download a list of tokens and arrays in use, so that it is easier to detect which tokens and arrays are unavailable. Every token or array that is not on the list, should be free to be used.
Important
Using tokens or arrays that are already in use may result in the replacement of valuable data.
To see tokens or arrays in use in your environment, click the Tokens or Arrays tab, and then See all used.
You will see a list of all the tokens or arrays in use. Click Download results to download a copy of the list in .csv format.