AgilePoint Documentation
Send an email to iamsupport@boston.gov to request a TEST and/or Dev Access Boston account
Note: HCM only periodically refreshes their non-Prod environments. If an employee is new they may not be there and will need a random user account. Sponsored accounts are not replicated down into lower environments but accounts can be created for them.
Users need to log in to Test Access Boston here https://access-test.boston.gov/
or
Users need to log in to Dev Access Boston here https://access-boston-dev.digital-staging.boston.gov/
Select "Ping Federate" to login in & authenticate
Click on AgilePoint icon
When users have logged into the Test AgilePoint environment they can be added to a Group.
Note: These steps are the same in Dev, Test & Prod
In AgilePoint: Log into the test environment & click on "Manage" at the top
Click on the lock (1) and select Group
Search for or scroll to the name of the group and click the arrow (2)
Click the edit / pencil icon (3)
Click on Members (4)
Click the + sign (5)
Enter in employee ID or part of name (6) Note: Employee ID is preferred method
Click the search icon (7)
Select user & click OK
If more people to add click the + again and add the next. When all are listed on the page below ensure all new users have a tick next to them & then click Update (9).
There are 3 AgilePoint environments. DEVELOPMENT (https://boston-d-app01.nxone.com) - Used for creating applications TEST (https://boston-s-app.nxone.com) - Used for end-user testing PRODUCTION (https://boston.nxone.com) - Used for “live” applications
Applications are created in the DEV environment and then moved to the TEST environment for end-user testing. If changes are required then the app should be updated in DEV and then when ready for additional testing migrated again to TEST.
There should not be any creation or updating of apps in TEST or PRODUCTION environments.
When updating or making changes to an existing application, this should be done in DEV, and then moved to TEST as well as PROD. Even if no end user testing for the change/update is required. E.g. If you are only making cosmetic changes to wording etc the updated app should be moved into TEST as well.
NOTE: If there are one or more Data Entities involved with an application, and there usually is, these need to be migrated to the TEST & PRODUCTION environments first before migrating the application. You can only migrate a Data Entity once. If you need to add additional fields to the data entity after it has been migrated, then you will need to add the field manually in each environment. So - before migrating, try & make sure the Data Entity is final or as near final as can be as adding fields manually in the additional two environments can be time consuming.
Migrating an app to another environment requires several steps
DEV Environment
Publish the application. Highlight the app you want to migrate
(1) Click Publish
(2)