Non-Profit Financial Management 1.0.2: Automated Release from Use Restriction Transactions

Non-Profit Financial Management SuiteApp version 1.0.2 introduces an Auto Release from Restriction script that programmatically creates Release from Restriction transactions for eligible use-restricted revenue. Previously this was a fully manual process; the new script can be run on demand or scheduled.

What changed

• New script deployment: An "Auto Release from Restriction" script is bundled with the SuiteApp. It reads results from a saved search and creates one Release from Restriction transaction per eligible result.
• Saved search configuration: A new General Preferences field lets an administrator select which saved search drives the automation. On install or upgrade the SuiteApp sets a locked default saved search. You can swap it for a custom search provided it uses compatible criteria and supported grouping fields (exact field list is not documented — see note below).
• Scope limited to use restrictions only. Revenue that is funding-restricted for future use is excluded from the releasable amount. Automatically created transaction lines will not include a Time Restriction value. Time-restricted revenue must still be released manually via the Release from Time Restriction report.

What is unclear

• Oracle does not specify the script type (likely Scheduled or Map/Reduce) or its script ID. Inspect the SuiteApp bundle post-install under Customization > Scripting > Scripts and filter by bundle to identify the deployment.
• The "supported grouping fields" for a compatible custom saved search are not enumerated. Start from the locked default search, duplicate it, and inspect its criteria and result columns before customizing.
• No governance or volume limits are mentioned. If your dataset is large, monitor the script's governance consumption in the Script Execution Log after the first run.

What to do

1. Install or upgrade Non-Profit Financial Management to version 1.0.2 via SuiteBundler or SuiteApp Marketplace.
2. Verify account setup: Confirm that at least one active Income or Other Income account has its Applies To field set to Release from Restriction. Without this the script will have no valid target account.
3. Review the default saved search: Navigate to the General Preferences setting added by the SuiteApp. Open the locked default saved search to understand its criteria and grouping. If it meets your needs, leave it in place.
4. Optionally create a custom search: Duplicate the default search, adjust criteria or grouping fields, and select it in General Preferences. Ensure the custom search uses the same result columns and grouping structure as the default.
5. Choose an execution mode: Run the Auto Release from Restriction script on demand for initial testing, then schedule it (e.g., monthly after period close) once validated.
6. Monitor first execution: Check the Script Execution Log and review the generated Release from Restriction transactions for correctness. Validate amounts against the Release from Time Restriction report to confirm time-restricted revenue was properly excluded.
7. Continue manual process for time restrictions: This automation does not cover time-restricted revenue. Keep using the Release from Time Restriction report and manual transaction creation for those cases.