Skip to Content

Summary-

How to debug NAKISA from Front-end and know Data information flow .

Purpose-

This will help to identify NAKISA roles, R/3 Roles, User population details and other useful details as well.


Preparation-

Log in into Portal for NAKISA iview or go to Nakisa user link.


Debugging Steps-

Go to portal and click on Nakisa i-view link first or go to NAKISA user link.  Then type below link into next tab of internet explorer.

Convert http://###########/OrgChart/default.jsp TO http://###########/OrgChart/nak-debug.jsp

Go to link mentioned above after org chart user NAK-DEBUG.JSP to go to debug page of Nakisa. This will help you to identify NAKISA roles, R3 Roles, User population details and other useful details as well.

/wp-content/uploads/2014/06/debug_486682.jpg

Hope it helps.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Stephen Millard

    Ishaan.

    I’m guessing you missed that this had already been documented in the VSN space wiki:

    The VSN Wiki is definitely worth a read through!

    Also just a few things to note that might clarify things a little further for people looking to use this debug VSN feature:

    • It is applicable to all VSN modules – not just OrgChart.
    • VSN modules are not always deployed to a Portal solution and this debugging page will work regardless of whether it is or not.
    • It will also work in any supported (see Nakisa compatibility matrix document for details) non-IE supported browsers.  This coulld include Firefox and Chrome depending upon your application version.
    • It is the browser session resources that need to be shared for the debug page to be able to display the correct data – i.e. you can actually have it open in any tab (not just the next tab) in the same browser window or even in a separate window of the same browser application (if the session resources are shared – i.e. not incognito mode or equivalent, not a forced new session (Microsoft Internet Explorer), etc.)

    Regards,

    Stephen.

    (0) 

Leave a Reply