- Creation
-
-
- Menu Item
Visual developmentBuild powerful business apps for automation, decision-making, and customer service using an intuitive, visual drag-and-drop interface.
Data modelDevelop data models that support data types of any complexity and structure them in arrays, maps, or other custom data markups.
IntegrationsIntegrate ProcessMIX apps with any database or REST/SOAP web services using the embedded connector builder.
Decision TablesCreate complex business logic and handle a large number of rules simultaneously in tabular format.
ScorecardsCalculate final scores based on the input parameters of certain characteristics to improve your decision-making.
PMMLExecute existing models based on Predictive Model Markup Language (PMML) to define statistical and data mining models.
Version controlFacilitate app development with ProcessMIX version control for code change monitoring, history, reversion, and dev team collaboration.
Debug and testTest and debug your app’s flows and check their performance on each execution breakpoint.
Deploy and useDeploy apps in a click in the cloud and use them instantly. ProcessMIX supports Docker packaging, Kubernetes service, and AWS cloud.
- Menu Item
-
-
- Solutions
Assignment of risk level and customer category within KYC processes at customer onboarding
Cross-Sell Offer Calculation for the 12M Client BaseDebug
Debug is used to test the execution of the current flow, view the received values stored in the nodes, examine the flow’s execution path, and troubleshoot problems in the flow’s implementation.
How to work with Debug?
To start working with the Debug, you need to check errors in the project through the error panel. If there are no errors, click on the deploy project button. After the project has been successfully deployed and the deploy button has turned green, the debug button is available. It is located to the right of the project deploy button.
To check the received values in a certain place in the flow, the user needs to select the required node, select the context menu, and select the “Add breakpoint”. The number of breakpoints in a flow is unlimited.
To start debugging, click on the Debug button located to the right of the project deployment button. The Test Helper opens. Here you need to select the necessary flow and enter the required values as request parameters and click on the Run button to start the process.
The debugging process started and stopped at the first breakpoint, if there is one. You can see the current value of all variables during the execution of the flow in the section “Flows in the debug state.” All values can be edited, while debugging that adds flexibility to the process. On the left part of the “Flows in the debug state” section displays the node where the debug process is stopped. If the user has not added a single Breakpoint, the result of the entire flow is available to him.
You can add additional breakpoints to the flow during the debug process.
Click the run button on the bottom bar to run part of the flow up to the breakpoint and view the execution result. Also, by pressing this button, the user can execute from the current node to the next breakpoint. If the user is in the last node of the flow, then clicks the run button, the debug ends.
Also, to complete the debugging, the user can click on the stop button.
If the user has a subflow node in the flow, the user can switch to the internal flow by clicking on the step into the button.
There are two ways to remove a breakpoint for a user.
The first way. In the ADE section, select the required endpoint, right-click to go to the context menu, then select Remove breakpoint.
The second way. The bottom panel contains the Breakpoints section. To do this, to delete a breakpoint, the user needs to select a specific breakpoint, then click on the delete icon.
