NetAsset - Automate Jobs

Overview

NetAsset supports automation of key asset lifecycle processes through pre-configured script deployments. This functionality is designed to reduce manual intervention by enabling background scripts to run on a scheduled basis, such as daily or weekly. Automating these steps helps streamline asset management for clients generating high volumes of assets, improving efficiency and reducing human error.


Prerequisites

  • Users must have access to Customization > Scripting > Script Deployments.

Step-by-Step Process

  1. Navigate to Script Deployments

    • Go to Customization > Scripting > Script Deployments.

  2. Filter for NetAsset - Automate Jobs MR

    • Expand the filters and set the Script filter to NetAsset - Automate Jobs MR 

    • Five script deployments should appear for the following jobs:

      • Journals

      • Disposals

      • Schedules

      • Queue for Capitalization

      • Revaluation Proposals

  3. Open the Script for the desired job you want to automate

    • Click the relevant deployment

    • Click Edit on the deployment record.

  4. Schedule the Script

    • Change the Status to Scheduled.

    • Under the Schedule section:

      • Choose frequency: Daily, Weekly, or Monthly (based on needs).

      • Set the Start Date (e.g., tomorrow’s date).

      • Set the Time for script execution (e.g., 2:00 AM).

      • Leave End Date blank if the script should run indefinitely.

  5. Define Parameters

    • Edit the saved search that determines which assets are included in the job for any specific needs

  6. Save

    • Click Save to activate the scheduled script.

  7. Repeat for Other Processes (Optional)

    • If automating additional tasks like capitalization, journal creation, or disposals, repeat the same steps for each script deployment.

Limitations/Things to Be Aware Of

  • The saved search used in the parameters defines which assets are affected. If this search is too broad or too narrow, it may include or omit unintended records.

  • Only one deployment is needed if schedule generation and queuing for capitalization should occur in sequence—this can be configured via the checkbox in parameters.

  • Scripts will not run unless explicitly scheduled; default deployments are inactive until configured.

Troubleshooting

  • If a script does not run as expected:

    • Confirm that it is set to Scheduled and not Not Scheduled.

    • Check the saved search to ensure it includes valid assets.

    • Verify that the script has not failed due to a permission or data issue.

  • For recurring execution issues, review logs under Customization > Scripting > Script Execution Logs.

Was this article helpful?