Page Comparison

Click Solutions → APSD → ... → Switch to classic

1. Clone the APSD-PAPS repository to your local computer.

2. On the left hand menu, navigate to Data → Custom Connectors.

3. Click on + New custom connector → Import an OpenAPI file.

4. In the Connector name field, type “NAPA-SNAPA”.

5. Click Import and go to \repos\APSD-PAPS\Custom Connectors\JSON and select the NAPA-SNAPA.json file.

6. Click Continue.

7. Verify that the Host and Base URL point to the correct location for the environment you are in (refer to chart below).

8. For NAPA API only: Set up OAuth security

9. Click Create connector.

10. Click on the Test tab, then + New connection.

11. Enter the API Key (RDIMS 17999814) and click Create connection.

12. Repeat steps 3-10 to create the rest of the connectors using their json files (SIAPI, SPAPI, MTAPI & TMAPI). *Note: SIAPI doesn’t require an API Key.

13. On the left hand menu, navigate to Data → Connections.

14. For each connection, share them with the organization.

    • Click ... → Share → + Add everyone in my org → Save.

    • This must be done so that any changes to the API Key get shared to all users. The update should be instant, if users are not receiving the updated key, they will need to clear their browser’s cache.

    • Give edit access to TC-CivAv Azure group.

      

1. Go to the desired environment.

2. Once the Env Variables solution has been imported

   • Edit the variables to ensure they have the correct values for the environment

3. Once the Custom Connectors solution has been imported

   • Clone the APSD-PAPS repository to your local computer.

   • Go into the APSD-PAPS Custom Connector solution. **Must be done from within the solution to ensure that the same name is generated (ap_5Fnapa-2Dsnapa).**

   • Click on + New > Automation > Custom connector

     

   • Enter in the info as follows:

     • Connector Name: NAPA-SNAPA

     • Host: www

   • Click Create connector.

   • Return to the APSD-PAPS Custom Connector solution and verify the name of the connector is ap_5Fnapa-2Dsnapa.

   • On the left-hand menu, click on Data/Dataverse > Custom connectors.

   • Beside the NAPA-SNAPA connector, click ... > Update from OpenAPI file.

     

   • Click Import and go to \repos\APSD-PAPS\Custom Connectors\JSON and select the NAPA-SNAPA.json file.

     • Use the NAPA-SNAPA [PROD].json for Production environment

   • Click Continue.

   • Toggle the Swagger Editor ON > OFF.

   • Go to the Security tab and enter in the information as per RDIMS 17999814.

   • Click Update connector.

   • Click on the Test tab, then + New connection.

   • Click X Close.

   • For the rest of the connectors, edit them and go to the Test tab, then click + New connection (API key are in RDIMS 17999814).

   • On the left-hand menu, click on Data/Dataverse > Connections.

   • For the MTAPI, SPAPI & TMAPI connections, share them with the organization.

     • Click ... → Share → + Add everyone in my org → Save.

       • This must be done so that any changes to the API Key get shared to all users. The update should be instant, if users are not receiving the updated key, they will need to clear their browser’s cache.

     • Give edit access to TC-CivAv Azure group.

       

4. Import the APSD solution

5. When importing the Flows solution

   • Click Next twice then select the CivAv APSD Service Principal connection for Dataverse and the shared connections for the APIs.

   • For the Office 365 and Excel Online connections, select the Do Not Reply APSD / Ne Pas Répondre PAPS connection created earlier.

     

6. Click Import and wait for the process to finish.

7. Click on Publish all customizations.

8. Verify that all the required flows are turned on. If any are off, follow the steps at the end of this section.

9. Share the APSD-PAPS Canvas App with Everyone in TC. Uncheck the box at the bottom “Send an email invitation to new users”.

   

10. Share the Canvas apps with the other developers individually, checking off the co-owner box.

11. PROD ONLY: Edit the APSD-PAPS Canvas App. Go into the App.OnStart() and edit the MTOA JWT token to the Production one.

12. Assign a security role to yourself in order to test the application.

    • Can be done through Advanced Settings or the Admin center (see Granting security roles to users section).

      

If ‘Modify Users’ flow is off, turn on ‘Remove User’ and ‘Update User’ flows first (if not already on).

1. Select the flow and click Turn on.

2. If there is an error, select the flow and click Edit.

3. If you are brough to a screen asking to confirm the flow connections, ensure all are using the connection references inside the solution then click Continue.

   

4. Once you are brought to the flow screen, click Save.

5. Steps 6 - 9 are only for certain flows (e.g. those with a manual trigger).

6. Go back to the solution and click on the flow name to view its details.

7. Click on Edit in the Run only users section.

   

8. Ensure that all the connections are using the generic account connections and NOT “Provided by run only user”.

   

9. Click Save.

10. Click Turn on.

11. Repeat steps 1-10 for any other flows that are not on.

1. Open the Power Apps Studio and select the ap-dev-tcd365 environment.

2. Select the solution you need to migrate.

3. Click Export → Publish → Next.

4. Increase the version number as needed (revision # is automatically increased).

5. Select corresponding export as type, then click on Export.

   • Managed: APSD, APSD-PAPS Admin, DataVerse-Security Role

   • Unmanaged: APSD-PAPS Flows, APSD-PAPS Custom Connectors, APSD-PAPS Env Variables

6. Download the exported file.

7. Repeat steps 2-6 for any other solutions required.

1. Go to the desired environment.

2. Click on Solutions on the left-hand menu and then Import in the top menu bar.

3. Select Browse and point to the zip file, e.g. APSD_PAPS_EnvVariables_1_0_0_X.zip, created in the export solution steps.

4. Click Import and wait for the process to finish.

5. Import the rest of the solutions as needed.

6. Click on Publish all customizations.

7. Verify that all the required flows are turned on (flows are inside Flows and Admin solutions).

If any of the flows are off:

1. Select the flow and click Turn on.

2. If there is an error, select the flow and click Edit.

3. If you are brough to a screen asking to confirm the flow connections, ensure all are using the connection references inside the solution then click Continue.

   

4. Once you are brought to the flow screen, click Save.

5. Steps 6 - 9 are only for certain flows (e.g. those with a manual trigger).

6. Go back to the solution and click on the flow name to view its details.

7. Click on Edit in the Run only users section.

   

8. Ensure that all the connections are using the generic account connections and NOT “Provided by run only user”.

   

9. Click Save.

10. Click Turn on.

11. Repeat steps 1-10 for any other flows that are not on.

1. Go to the environment that has the master set of data for the SCRAM tasks. Currently, this is QA.

2. On the left menu, go to Data → Tables, then open the Scram Tasks table.

3. On the top menu, click on Data → Export data. Once the export has been successfully completed, click on Download exported data.

4. Unzip the csv file.

5. Switch to the environment you are deploying to.

6. On the left menu, go to Data → Tables, then open the Scram Tasks table.

7. On the top menu, click on Data → > beside Get data → Get data from Excel.

   

8. Upload the csv file from step 4. If there are any mapping issues, fix them.

   

9. Click Import. Wait for the process to complete, then verify that the data was imported.

Follow the same steps using the AP Task table instead.

1. Edit the APSD-PAPS Canvas app.

2. When prompted, select Don't Allow.

3. 

   Remove all connections that are showing as not connected - 5 connections (APSR, MTAPI, SIAPI, SPAPI, TMAPI), Office365Users and APSD_Translations.

   

4. Add all of them back.

   

5. SharePoint data connector: for APSD_Translation file. In the box enter the following URL: https://034gc.sharepoint.com/sites/DSD-CivilAviation/Lists/APSD_Translations/AllItems.aspx

   

6. Check off the APSD_Translations list & click Connect.

   

7. Run the App Checker and ensure no errors are reported.

   

8. Turn on “Allow searching” in the properties for the following elements:

   • New Service Request Step One Screen - cboNapaProject element

     

   • New Service Request Step Three Contact Info Screen - cboFindOrganizationAlt element

     

   • Service Request Review Screen - ddSRRChangeReAssignment element

     

   • New Invoice Step One Screen - cboInvoiceCustomer and cboCustomerAddress elements

     

   • Weekly Time Entry Normalized Screen - cmbProject

     

9. Save and Publish the app.