The first day I started to learn about Remedy’s development I noticed the lack of a very important type of field, the boolean field. As any Remedy developer knows, there is no boolean field on Remedy. So we must use other types of field to emulate the boolean functionality.
In this post I will cover the boolean field concept and provide some best practices over ARS. … Read the complete post
Sometimes you need to create a request, and retrieve its ID to continue the processing. On those situations, the $LASTID$ keyword is your best ally. But, it can became your worst enemy when after a minimum change, everything hangs and your code starts malfunctioning.
In this post I will cover the risk of using the $LASTID$ keyword on your developments. … Read the complete post
Latest moves from BMC about training certifications and Action Request Systems show every sign of moving his highly customisable product to a highly configurable. In this new paradigm, the Remedy Developer is useless, or at least it seems that bad times are coming.
Dale Hurt, at his blog “ITSM Tools Review“, has published a very intersenting article about this topic. … Read the complete post
The service action was introduced with ARS version 7.1. It allows the creation of sets of code to be processed at the served that can be called from anywhere, proving input and output parameters. This new action opened a new developing paradigm where the creation of shared libraries of code where allowed.
In this post I provide a little tutorial about the service action, giving some hints and providing some best practices.
… Read the complete post
The PUSH action is one of the cornerstones of Remedy’s development. It allows to create or modify requests of other forms when executing workflow. The basis of this action are well described at official manuals. But, do you know how to take the most profit of it?
In this post I will review some aspects I consider that are not well developed on BMC docs about the PUSH action. … Read the complete post