Transaction Series: 3 Authoring Tips From an Old Pro

By Jennifer Hwang on Nov 4, 2015

Having worked at Winshuttle for nearly 7 years, I’ve written my fair share of Transaction scripts. I’m probably one of the few people in the world who can honestly say they’ve written thousands of them! And in that time, I’ve honed best practices, learned a few tips and tricks, and overall know-how. In this short blog series, I will share some of my transaction “commandments” with you! transaction screen shot small

Search for help

Whenever you want to author a new script, especially if it’s a new t-code you’ve never tried or it requires looping or condition statements, do a quick search for any help that might already exist.  Whether you’re searching the Winshuttle Support site, the Documentation library, YouTube, or trusty Google, you may find helpful articles, how-to videos, or sample scripts and templates to help you get started.  Any guidance is helpful, and you may very well find samples that work on your system!

Keep it simple

Are you recording a t-code that is long, complex and requires extensive logic? Have you spent days or weeks trying to get it to work?  If at all possible, keep it simple!  If the use case allows it, consider creating 2 or 3 smaller scripts and linking them together instead of having one big complex script.  If loops are not absolutely required, then don’t loop them!  This might not be possible for creation scenarios, but if you’re updating multiple line items, update them separately, and avoid looping to simplify the process.

Keep it clean

A Winshuttle script is going to do exactly what you tell it to do.  If your script includes moving to screens where no changes are being made, and buttons are clicked that don’t need to be, all these extra actions are going to run each time.  Each extra step will increase the run time, albeit a very short amount of time; however when you’re updating hundreds or thousands of records, those milliseconds add up. Keep your recordings clean by cleanly recording them or cleaning them up afterwards by removing all unnecessary steps.

Stay tuned for Part 2 coming soon! If you have any questions about transaction scripts, feel free to reach out and I’m happy to continue the discussion.

About the author

Jennifer Hwang

Jennifer Hwang is a software consultant and business process analyst with 20+ years of experience implementing and optimizing various technical solutions. As a Solutions Engineer for Winshuttle, with 12+ years of Winshuttle consulting expertise, she ensures customer success by being their trusted technical advisor.

Questions or comments about this article?

Tweet @Winshuttle to continue the conversation!