Troubleshooting (Organization)

troubleshooting in {{jigxmanagement}} helps identify problems when an app crashes, or when issues and errors occur while using and running solutions on the {{jigxapp}} think of this as runtime troubleshooting performed by support or your organization's administrator versus design time debugging which is available in the {{jigxbuilder}} for creators who are building solutions permissions required solution owner or organization owner troubleshooting {{jigxmanagement}} troubleshooting levels there are three levels of troubleshooting in {{jigxmanagement}} troubleshooting (organization) docid\ pqc4nyhx 9ttloydm4mvu provides troubleshooting context for all users and solutions in that organization the exact correlation id is required to start troubleshooting users docid\ hy9sngxqzprabe51imv7q provides troubleshooting context only for that specific user, and spans across all solutions assigned to that user troubleshooting (solution) docid\ tzqjid9go54bvhzap88co provides troubleshooting context only for that specific solution, and spans across users using that solution when clicking on the correlation id the next level of detail shows who the user was at the top right of the screen configure logging on the {{jigxapp}} to configure logging on the mobile device perform the following steps open the {{jigxapp}} on your mobile device click on your profile icon in the top right hand corner of the app tap troubleshooting the following settings are configurable error and crash logging enabled by default logs any errors displayed while using the app and logs when the app crashes basic logging logs basic flow when using the solutions in the app detailed logging logs errors, app crashes, and flow of the app, and exposes some data tap on the field to see the available categories enable the categories you require, use the selected tab to see what is enabled debug categories select from the listed categories trace categories select from the listed categories use troubleshooting information troubleshooting allows you to drill down into the detail logged for each correlation id click on the correlation id to drill down to see the log information the following levels are logged depending on the troubleshooting settings enabled on the mobile device \ warning \ error \ debug \ info category shows the area where the issue occurred such as rest provider, action sync entities, or jig default message provides exact details of the issue such as execute failed, or failed to sync entity 'user profile/get user ' click on a specific level entry in the list to drill down into the log detail the side pane opens displaying the solution id, correlation id, device id, app id, message, and additional parameters use the copy to clipboard icon to use the values elsewhere