Quantcast
Channel: VMware Communities : Discussion List - vRealize Orchestrator
Viewing all articles
Browse latest Browse all 6251

Loading a module as a locked attribute good or bad?

$
0
0

After going through the coding guide I realize I have a ton to clean up in my workflows and actions.  One thing that I know I am doing way too much of is System.getModule() calls.  I am wondering if it is considered good practice to do something like setting an attribute to a module that gets used often throughout the workflow and passing that attribute into scriptable tasks or if it is better to set a variable each time within the scripted task?  I know there is some serialization and parsing that occurs between objects in a workflow so I want to make sure setting that attribute to a module doesn't actually end up causing me grief.

 

A good example of a module that gets extremely heavy use is our ServiceNow module.  So what I am hoping I can do is in the workflow set attribute snModule = our service now module.  Then pass it into a scriptable task.  Then simply call snModule.closeTask(); or whatever action I am taking with ServiceNow.  In a large workflow I might have 4 or 5 snippets where I want to call actions in this module.


Viewing all articles
Browse latest Browse all 6251

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>