> For the complete documentation index, see [llms.txt](https://docs.airapi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airapi.io/release-notes/v1.7.1.md). # v1.7.1 Creation Date: 28.09.2021 ### [Go – Live Request Management](https://docs.apigo.com/en/latest/Documents_Relase_Notes/v1.7.1.html#go-live-request-management) **47427 – Development of the GoLive-Penetration test response upload form** The product management requests that a screen be prepared so that the Action Required - Penetration test request from the institution’s web service cannot be answered. The answer produced in this form is sent to the institution’s web service as a reply. Thus, the communication between the developer and the institution is provided through the product. **47428 – Development of the GoLive-Answer answer upload form** The product management requests that a screen be prepared to respond to the Action Required - Message request coming from the corporate web service and that the response generated in this form is sent to the corporate web service as a response. Thus, the communication between the developer and the institution is provided through the product. **47556 – GoLive-Integration Go Live management for non-EndPoint configurations** For customers whose integration Workflow endPoint is not defined in the Go-Live Request configuration, the product management requests the necessary improvements to be made to manage the Go-Live request on ApiGO. Thus, Go-Live can be run in the product without service integration. **42392 – Making the necessary development for adding the GoLive Request management card to the developer portal** Product management requests the creation of a GoLive management card in the Developer portal. Thus, developers can switch to the screen to start a go-live request or see their started processes. **42537 – GoLive Request Policy development** Product management requests GoLive request policy development to be used on the EndPoint definition screen. Thus, Banks will be able to define which endPoint can be Go-live control. For this Policy to be shown in the definition Policy list, the following rule applies; * There are two types of Go-Live Request Workflows on AIRAPI. Client-Only and With EndPoint * This Policy will not be shown in environments where Go-Live Request is not defined. * Client-Only Not displayed in Selected Environments. * Shown in Environments with EndPoints. **41910 – Necessary work for the development of the Go Live Request Management page** The product management requests that the developer can list their go-live requests and initiate a New Request should be developed in the developer portal. Thus, developers have a page where they can follow up on Go Live-Request. **42394 – Developing the required page to start the new Go Live request** The product management requests the development of the necessary page to initiate Go-Live requests from the sub-environment. Thus, the developer will be able to create a new GoLive request. **42395 – Development of GoLive Request List detail page** Necessary work is done to display the list details on the product management, GoLive request page. ### UX Studies **45738 – Preparation of UX design of agreement pages** The product management requests the UX design of the Agreement page to be prepared. Thus, a missing item in the product UX transformation is closed. ### Payment Order Transactions **47075 – Payment Order - TCM Standards main heading and subheadings under ApiGo Internal Function policy** The product management requests that the TCM Standards main title and accordingly the following Sub-titles be defined to the Airapi Internal Function policy to be used in TCM standards, and the relevant code blogs must be set as catchable on the gateway. Thus, the necessary software infrastructure is provided for the development of these functions. * Create Payment Consent * Get Payment Consent * Create transaction token **48872 – Carrying out the necessary work to open the environment in TCM standard on the product** Product management requests that a new environment type named TCM standard be created when creating a new environment. Thus, necessary developments for TCM standards will be able to start from this point. **48865 – Necessary work to develop the service that satisfies the Payment Order Start Request** The product management requests that the service that will meet the payment order initiation requests in TCM standards be prepared at the Gateway layer on the product. Thus, the development gains the ability to initiate a payment order in TCM standards. **48865 – UX design for Payment Consent Order Display and confirmation screen** Product management requests UX design for Payment Consent Order Display and approval screen in TCM standards. ### List Pages UX Transformation **47679 – Necessary work to adapt the Developer List screen to the new UX design** The product management requests that the developer list in the Management portal be renewed according to the new UX design. Thus, progress is achieved in the product UX transformation. **47680 – Making the necessary work to make the developer list detail suitable for the new UX design** The product management requests that the necessary work be done to adapt the Developer list detail to the new UX design to make progress in the product UX transformation. ### Changing Menu & Profile Section **47330 – Carrying out the necessary work for the notification list to be displayed in the upper left menu** Product management wants Notification impressions to be developed based on the top left menu. Thus, product UX integrity is ensured. **39749 – Refreshing the Messages Detail page according to the new UX design** Product management requests the Notification Detail page to be refreshed by the new UX design. Thus, product UX integrity is ensured. **39745 – Refreshing the Messages List according to the new UX design** The product management requests that the Notification Listing screen be renewed according to the new UX design, thus ensuring product UX integrity. ### FIXED ISSUES | PORTAL | TASK | ISSUE | ACTION | STATUS | | ----------------- | ----- | ---------------------------------------------------------------------------- | ------------- | ------ | | Management Portal | 48352 | The solution to null errors when navigating to various pages in Dev Portal | Backend fixed | Done | | Management Portal | 48512 | Adding rel=noopener to manapi verify mails | Backend fixed | Done | | Management Portal | 48728 | Validation error when entering a complex password on Password update screen | Backend fixed | Done | | Management Portal | 48275 | import export page does not export Scope Claim Settings and Global Variables | Backend fixed | Done | | Management Portal | 49851 | Spot color in Notifications | UI fixed | Done | | Management Portal | 49855 | Font color in Language | UI fixed | Done | | Management Portal | 49867 | Color of buttons on the Environments screen | UI fixed | Done | | Management Portal | 49894 | Developer Portal Settings/Delete button color | UI fixed | Done | | Management Portal | 49901 | Consent Management - Delete icon color | UI fixed | Done | | Management Portal | 50040 | Comment Management - Editing | UI fixed | Done | | Management Portal | 50044 | Notification Preferences - Switch behavior | UI fixed | Done | | Management Portal | 49895 | Developer Portal Settings/Add Menu Item button | UI fixed | Done | [Next ](https://docs.apigo.com/en/latest/Documents_Relase_Notes/v1.7.0.html)[ Previous](https://docs.apigo.com/en/latest/Documents_Relase_Notes/v1.7.2.html)