Deployment Steps - 2025_MAY_01

Deployment

Potential Issues

1. If the deployment admin does not have access to Storage Accounts, the Storage Account deployment part will fail. There are no changes to the storage accounts in this release, so this can be ignored
2. The Custom Functions Function App (npobp_common) tends to have trouble with deployment and may need to be manually deployed
3. The Seed Data step may not work if APIM is secured within a vnet. In that instance, the #Manual Steps below will allow the same changes to be added manually

Prerequisites

We will follow the deployment instructions from: Hosted Model Deployment Guide Please read and understand the additional prerequisites below before continuing:

1. Ensure the logged in user has access to the following storage accounts. If the storage account is part of a VNet, the user's IP address needs to be explicitly added:
   1. Data Store - Master (npobp_mast)
   2. Data Store - Reporting (npobp_custrep)
   3. Data Store - Execution (npobp_custexec)
   4. Data Store - Configuration (npobp_custconfig)
2. Do the same for the following, for both the Main site and Advanced Tools site:
   1. NPO Portal (npobp_portal)
   2. Portal Backend (npobp_portalbackend)
3. In your existing customerconfig.json file, ensure the following settings are correct:
   1. prerequisutes.validateEnabled
   2. otherSettings.downloadAdditionalScripts
   3. otherSettings.downloadArtifacts
4. The Custom Functions Function App (npobp_common) function app tends to fail when run manually through the script, so it may need to be manually redeployed

   $resourceGroupName = 'NAME_OF_YOUR_RESOURCE_GROUP'  
   $functionAppName = 'NAME_OF_YOUR_COMMON_FUCNTION_APP'  
   $deployZipPath = 'PATH_TO_THE_ARTIFACTS_ZIP_FILE_IN_ARTIFACT_FOLDER_34'
   
   az account set --subscription ""
   
   az functionapp deployment source config-zip `  
                   --resource-group $resourceGroupName `  
                   --name $functionAppName `  
                   --src $deployZipPath
   

Manual Steps:

Manually deploy the npocommon function app:

$resourceGroupName = 'YOUR_RESOURCE_GROUP'
$functionAppName = 'NAME_OF_YOUR_NPOCOMMON_FUNCTION_APP'
$deployZipPath = 'PATH_TO_ \34\EXTRACTED\DROP\XXXX.ZIP'

az account set --subscription "YOUR_SUBSCRIPTION_GUID"

az functionapp deployment source config-zip `
                --resource-group $resourceGroupName `
                --name $functionAppName `
                --src $deployZipPath

TechStack

1. Confirm property:
   1. Name: BaseUrlNPOFunctions
   2. Value: Ends with the root path in APIM, no trailing slash (e.g. URL/api or URL/npocommonfunctions)

Smoke Tests

1. From the MASTER storage account, open the TechStack table and confirm new property "TableConditionPath" has value "/system/tablecondition"
2. Confirm execution of a Flow unit test that uses custom functions
   1. Multi Decision Branch
   2. Concat