WHMS validations: where can I put my code

 


Ever come across a situation where you needed to induce validations, in Warehouse Management mobile apps, before letting the user finally submit data? 
For example: you need to check if the supplied value for the target license plate, while shipping a transfer order, must be exactly 12 characters long. Or the supplied date of a warehouse Load must be more than or equal to 5 days from today. Or imagine there is a flag in your warehouse, called Stopped for all transactions and while doing GRN from your mobile app, you need to see if it's a stopped warehouse.
For all such situations, there is a trusted class (dedicated exclusively for WHMS) called: WhsControl and you need to wisely put your code there.
Essentially WhsControl is a class that has all the variables stacked up in it: the associated WMSLocationId, InventLocationId or ItemId or even the calling menu item. You can simply do a CoC on "processControlUsingDisplay" method, so as to perform these validations and return true or false accordingly.
The below example shows how to check if your license plate is 12 characters long:
#WHSRF
#WHSWorkExecuteControlElements
#WHSWorkExecuteDisplayCases

#define.callingMenuTransferOrder("ShipTransferOrder")
protected boolean processControlUsingDisplay(str _value)
{
    boolean ret = next processControlUsingDisplay(_value);
    if (this.parmName() == #TargetLicensePlateId && 
         _value &&
        this.parmMenuItemName() == #callingMenuTransferOrder)
    {
        if (!this.validateCharacterCount(_value))
        {
            this.fail(/*Label file for invalid character count*/);
        }
    }
    return ret;
}

The method validateCharacterCount checks the logic for the 12-character long code of the target license plate.
Here the referred macros: WHSRF contains the definitions for TargetLicensePlate, MenuItems, etc. and you can ask the code only to be triggered when called from ShipTransferOrder menu.
(I mentioned, wisely, in my above statement ☝☝☝ : for example, the above code only checks if this is called from TransferOrder shipment -- certainly this should not get called from everywhere).
Lastly see the method: this.fail(): this method carries the result of the validation and is equivalent of 'Ret = checkFailed()' [in fact its sets ret = checkFailed, internally].

Comments

Post a Comment

Popular posts from this blog

X++ : mistakes which developers commit the most

Image
   The most important thing is to remember where and when to write the code. a. Developers have an inherent habit of writing erratic select statements: select * from custTable where custTable.AccountNum == <SomeValue> Where in essence we need to make use of optimized choice of fields in the select statement. b. Making use of 'continue' keywords: While select custTrans where <someConditions> { if (cusTTrans.CustGroup != mappingTable.CustGroup) { continue; } } 'Continue' statements are precisely a very unhygienic way of designing your code. The above statement could have been easily ornamented by using exists/not exists joins. Using Continue statements would eventually result in a high performance impact. Also select statements should be made punctuated with a 'firstonly' clause -- just not from best practise standpoint, but also from performance considerations. c. Writing nested loops: This is a common mistake that perha
Read more

Make your menu items visible on main menu, conditionally,, using this cool feature of D365FO

Image
  Wassup guys? I am sure you must have encountered this situation where you needed to display your menuItems, on main menu, based on some condition, haven't you? This was only possible by using config keys and flights. Things get a bit tricky,  when suppose you have a requirement like this: you need to make it dynamic, by introducing a toggle switch on a field on a paremeter form.  Suppose on Accounts Receivables Parameters >> You have a field called ' Show US customer '. You have a requirement that says when you turn on this toggle, then only the menuItem ' Input SSN details ', under AR module. This is now highly acheivable by leveraging subscription to 'SysMenuNavigationObjectFactory' class, simply by saying a. Create a new class USMenuItemsVisibilityManager b. Copy the following method, with proper documentation (don't change signature/anything else) [SubscribesTo(classstr(SysMenuNavigationObjectFactory), staticdelegatestr(SysMenuNavigationObjec
Read more

Speed up your execution performance by using SysGlobalCaches

Image
  Ever come across a situation where you needed to  a. Using a multi-threaded batch to import a journal header and lines, from a staging table. The table already contains the Journal Ids which you need to assign to the header and allocate the lines under that header. b. You need to continuously check after each line being imported, if the journal with the Id has been created. If not, it will create the header and create the lines under it;  If yes, it will directly create the lines for the header (Find or create). c. As you could rightly guess, this architecture has an inherent sluggishness associated with it -- each time you keep on checking if the header has been created or not, it does mean a lot of performance effects, as a consequence. Also as you can understand it's a multithreaded code, which means each thread has no direct relation with the other -- which does mean there is no way I can talk between the threads/pass on any information. SysGlobalCaches to the rescue: I perso
Read more