// Rules for generating connections.json files for Logic Apps Standard. Covers serviceProviderConnections format, mandatory reference lookup, FileSystem mountPath rule, and connector parameter constraints.
Rules for analysing a single TIBCO flow group's architecture. Covers source file reading depth, Mermaid diagram rules, flow/sub-process rendering, processor mapping priority ladder, and the required multi-step store tool sequence.
Rules for optional cloud deployment and testing of Logic Apps Standard projects. Covers ARM/Bicep generation, deployment method, app settings management, cloud test execution, and reporting.
Rules for generating ordered conversion task plans. Covers mandatory task ordering, required task types, descriptive task ID rules, optional vs non-optional tasks, output path conventions, and what each task must contain.
Rules for discovering, analysing, and classifying missing dependencies during TIBCO flow analysis. Covers JAR/Java decompilation, Maven dependency analysis, custom module classification, and what blocks migration.
Rules for detecting and grouping TIBCO integration artifacts into logical flow groups using a process-call chain strategy. Covers process-call chain rules, fallback grouping when no sources exist, and required output fields.
Creates .NET local functions (custom code) for Azure Logic Apps Standard. Covers exact NuGet packages, namespaces, csproj, MSBuild targets, VS Code config, function.json, and workflow InvokeFunction patterns for both .NET 8 and .NET Framework 4.7.2.
| name | connections-json-generation-rules |
| description | Rules for generating connections.json files for Logic Apps Standard. Covers serviceProviderConnections format, mandatory reference lookup, FileSystem mountPath rule, and connector parameter constraints. |
Purpose: Authoritative rules for generating
connections.jsonfiles. Follow exactly.
BEFORE writing ANY connections.json:
migration_searchReferenceWorkflows with category="connection" to find the exact connections.json format for each connector.migration_readReferenceWorkflow to read the full JSON.All connections use the serviceProviderConnections format:
{
"serviceProviderConnections": {
"<connectionName>": {
"parameterValues": {
"<param1>": "<value1>",
...
},
"serviceProvider": {
"id": "/serviceProviders/<providerId>"
},
"displayName": "<Display Name>"
}
}
}
If the flow uses File System connector:
connections.json MUST include mountPath in parameterValues (the ONLY required parameter for runtime).connectionString or rootFolder to the FileSystem connection — they are NOT valid parameters.@appsetting("FileSystem_mountPath") for the value.FileSystem_mountPath to local.settings.json.FileSystem_mountPath must NOT be /home, /home/site, or /home/site/wwwroot; use a dedicated non-overlapping path.For EVERY connector used by the flow:
mountPathUseDevelopmentStorage=true)After provisioning cloud resources, retrieve the connection string and UPDATE local.settings.json with the real value.
If ANY workflow uses X12/EDIFACT/AS2 encode/decode actions:
local.settings.json:
WORKFLOWS_SUBSCRIPTION_IDWORKFLOWS_TENANT_IDWORKFLOWS_RESOURCE_GROUP_NAMEWORKFLOWS_LOCATION_NAMEWORKFLOWS_MANAGEMENT_BASE_URIWORKFLOWS_INTEGRATION_ACCOUNT_ID with that value.WORKFLOW_INTEGRATION_ACCOUNT_CALLBACK_URL with that value.local.settings.json with those real deployed values.schemaReferences array in BOTH receiveAgreement.protocolSettings and sendAgreement.protocolSettings MUST be populated with references to the uploaded message schemas. An agreement with empty schemaReferences: [] will cause EdifactDecode/X12Decode actions to fail at runtime with "UnexpectedSegment" errors. For each message type the flow processes, add an entry like {"messageId": "<messageType>", "schemaVersion": "<version>", "schemaName": "<schemaNameInIA>"}. Use a PATCH or re-PUT of the agreement after schema upload to add these references.Artifacts/Schemas/ / Artifacts/Maps/ folders.Artifacts/Schemas/ and Artifacts/Maps/ folders only when the flow does NOT choose the Integration Account model.