When importing components from Git, the Commit information is stored in ISPW and is displayed in the Assignment and Release Views in Topaz.Ī new webhook now alerts you when something is waiting for approval so that you can use the Approval API to approve and continue.īased on user feedback, the Containers View is now sorted in descending order when you click a column header.īased on feedback from users to improve usability, the Outline View in the editor is now the default view in the ISPW perspective.
#Proc engine error topaz clarity code
Local copybooks are always found if the project is included in the Copybook Concatenation list within the project in which the source code is located. While most copybooks can be found within the current project, applications frequently use common copybooks across multiple applications. Topaz Git projects configured for ISPW can now automatically look up copybooks that are referenced by the source code being edited within other ISPW projects.You can import your code from Git into ISPW directly to a Sandbox Assignment. For example, a generate action references only copybooks from your sandbox or above the Test level of the life cycle leg where the assignment for the sandbox is located.Īs a developer using Git, you can now use the sandbox to build and test the changes. Sandboxes are stand-alone environments that are independent from other changes at the same level. We are introducing Sandbox Assignments in ISPW, which are isolated areas for developers on which to perform their generate, build, and test actions at the Test level. Use the generate, build, deploy, and sync actions.
When ready for mainframe compile and testing, you can invoke the actions via a Push request to load the components to ISPW on the mainframe, and then compile (generate or build) to enable your testing.
0 kommentar(er)
