This week I want to talk about how we can use iLogic to enforce Company Standards. Today’s scenario comes from a customer that wants to be able to push data from their inventor properties to an ERP system, but there is a character limit when importing to ERP. This is a great use of iLogic in your template file.
iLogic is great for “If this happens, do this” scenarios. So, in the above problem, we’re really thinking: If my Description field is more than 25 characters, then I need to know about it and adjust it.
The iLogic code for this would read:
This rule is saying, If the Length of the Description is greater than 25, it will throw a message box letting us know. If it is less than 25, it will do nothing.
iLogic Rule: Highlighting Message Box components
We will also want to make sure we set the Event Trigger to happen before save, so it checks this rule each time you save. Once that is set, we can save this as our template and when we start a new file, it will be checking our Description length to make sure it will go in to our ERP system without issue.
Event Trigger
This is just a simple rule that informs us of the issue and doesn’t even begin to scratch the surface of what is possible via iLogic. For example, you could have the code perform some calculations and let you know how many characters you need to remove, or you could also have it open a form that allows you to correct the iProperties immediately. However, creating simple rules is a great way to get started with iLogic and I encourage you to try adding iLogic to your files to help enforce some standards or just save time. - Dan Hunsucker
Do you use any of these tips and tricks in your daily workflow? Feel free to brag about your success in the comments!
Like what you’ve read? Subscribe to our blog!
Feel free to share on Twitter or Facebook!
