• State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 96 subscribers
  • Views 4931 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Is it possible to debug by attaching to process?

dan
over 7 years ago

Using v7.1.1. Is it possible to run a debugging session in visual studio and attach to a One Identity process and break into some scripts that I'm running through Process Orchestration? The reason I want this is that I'm passing in PWO objects and there's no way to enter an IEntity into the System Debugger screen where you can run scripts. This would make my life much easier. I've looked at entity patches and using them is a possible workaround (overload my functio, taking an entity patch as input and test with that) but I can't see where to get an entity patch for any PWO. Thanks for any help.

Parents
  • 0 over 7 years ago

    First of all, every script that is executed during the process generation is not running on the job service but one the client/web portal/appserver that is generating the process.

    But this gives you the opportunity to make use of the base (or Entity) object in the System Debugger.

    The System Debugger allows you to define the base data as described here https://support.oneidentity.com/technical-documents/identity-manager/8.0/configuration-guide/90#TOPIC-862642.

    This allows you to have either a more flexible _Debug function that does nothing besides calling your original script using the Entity as a parameter. The Entity itself, that will be used in your debug run, can be configured in the System Debugger as shown in the screenshots.

    Or, you refactor your script to use the (base) Entity directly without having to use a parameter of type iEntity. Please be aware that this would mean that the script can only be executed, where the base object is available (for example it is unavailable in a script executed by the script component).

    Just for completeness my simple script CCC_UseBase.

    Public Function CCC_UseBase() As String

    Return Entity.Display

End Function

Reply
  • 0 over 7 years ago

    First of all, every script that is executed during the process generation is not running on the job service but one the client/web portal/appserver that is generating the process.

    But this gives you the opportunity to make use of the base (or Entity) object in the System Debugger.

    The System Debugger allows you to define the base data as described here https://support.oneidentity.com/technical-documents/identity-manager/8.0/configuration-guide/90#TOPIC-862642.

    This allows you to have either a more flexible _Debug function that does nothing besides calling your original script using the Entity as a parameter. The Entity itself, that will be used in your debug run, can be configured in the System Debugger as shown in the screenshots.

    Or, you refactor your script to use the (base) Entity directly without having to use a parameter of type iEntity. Please be aware that this would mean that the script can only be executed, where the base object is available (for example it is unavailable in a script executed by the script component).

    Just for completeness my simple script CCC_UseBase.

    Public Function CCC_UseBase() As String

    Return Entity.Display

End Function

Children
No Data