Contents x
    Use the App to Update Flow Metadata
    • 06 Jun 2024
    • 3 Minutes to read
    • Contributors
    • Print
    • Dark
      Light
    Contents

    Use the App to Update Flow Metadata

    • Updated on 06 Jun 2024
    • 3 Minutes to read
    • Contributors
    • Print
    • Dark
      Light
    Article summary

    Removing Unused Variables from Flows

    1. Access the Analyzer Run record that relates to the flows you are interested in modifying by either clicking the link in the email you received or finding it in the Analyzer Run tab in the Flow Analyzer app.
    2. In the actions bar, click the Flow Mechanic button
      image.png
    3. Click the Remove Unused Variables option
      image.png
    4. Select one or multiple variables to remove and click the Add to Request button
      image.png
    5. If you do not wish to add additional jobs to the request, click the Run Mechanic button
      image.png
    6. Once the job is completed, you will land on a page with details on the flows. If the job was successful for a flow, you can click on the link to open the flow builder to the new flow version with the variables removed. Otherwise, you will see some error details on why the job was unsuccessful.
      image.png

    Updating API Versions in Flows

    1. Access the Analyzer Run record that relates to the flows you are interested in modifying by either clicking the link in the email you received or finding it in the Analyzer Run tab in the Flow Analyzer app.
    2. In the actions bar, click the Flow Mechanic button
      image.png
    3. Click the Update API Versions option
      image.png
    4. Select one or many flows and an API version to which they should be updated. Click Add to Request.
      image.png
    5. If you do not wish to add additional jobs to the request, click the Run Mechanic button
      image.png
    6. Once the job is completed, you will land on a page with details on the flows. If the job was successful for a flow, you can click on the link to open the flow builder to the new flow version with the variables removed. Otherwise, you will see some error details on why the job was unsuccessful.
      image.png

    Replacing Hard-Coded IDs

    How do we replace hard-coded IDs?

    The Flow Analyzer uses a tried and true algorithm for replacement of hard-coded IDs. The Flow Analyzer follows the below steps to replace a hard-coded ID:

    1. Create a variable to store the record ID.
    2. Place a Get Records element at the beginning of the flow to retrieve the record details using other, unique sets of fields. The get records element stores the record ID in the variable created above.
    3. Replace all references to the hard-coded ID with references to the variable in which the ID was stored in step 2.
    What limitations exist with the way the Flow Analyzer replaces hard-coded IDs?

    The algorithm described above has one serious limitation in it's current implementation. If there are more than one ID of a certain object (i.e. there are two record type IDs being replaced in the same flow), the app will currently create a separate get records element for EACH of the record type IDs.

    There are plans to enhance this feature to condense those get records element into one in the version 1.7 release.

    1. Access the Analyzer Run record that relates to the flows you are interested in modifying by either clicking the link in the email you received or finding it in the Analyzer Run tab in the Flow Analyzer app.
    2. In the actions bar, click the Flow Mechanic button
      image.png
    3. Click the Replace Hard-Coded IDs option
      image.png
    4. Select one or many hard-coded IDs to replace and click the Add to Request button
      image.png
    5. If you do not wish to add additional jobs to the request, click the Run Mechanic button
      image.png
    6. Once the job is completed, you will land on a page with details on the flows. If the job was successful for a flow, you can click on the link to open the flow builder to the new flow version with the variables removed. Otherwise, you will see some error details on why the job was unsuccessful.
      image.png
    Was this article helpful?
    What's Next