Best practices in Liquid Implementing debug data in
Best practices in Liquid Implementing debug data in a “Liquid template” Ruben Moerman, 14/05/2019
Debugging is the process of finding and resolving defects or problems within “liquid code”. © 2019 Deloitte Private | Accountancy & Advisory. Best practices in Liquid 2
Implementing debug data in a “Liquid template” Sample reconcilliation Show debug information based on • Signed on user in Silverfin • Depending on a flag in liquid code © 2019 Deloitte Private | Accountancy & Advisory. Best practices in Liquid 3
Implementing debug data in a “Liquid template” Debug data prompted depending on your selection Formula data reveals how it’s calculated © 2019 Deloitte Private | Accountancy & Advisory. Adjustments and how they relate to each other Best practices in Liquid 4
Implementing debug data in a “Liquid template” Sample reconcilliation © 2019 Deloitte Private | Accountancy & Advisory. Best practices in Liquid 5
Implementing debug data in a “Liquid template” How? Current user check versus power users configured V Same applies for flag to set manually V Don’t forget to hide it during export V Adding extra information towards user V © 2019 Deloitte Private | Accountancy & Advisory. Best practices in Liquid 6
Implementing debug data in a “Liquid template” Outcome of the code snippet Non-power user (Sylvie) Power user (Ruben) © 2019 Deloitte Private | Accountancy & Advisory. Best practices in Liquid 7
Implementing debug data in a “Liquid template” When? Complexity is involved It’s likely you need it For a liquid template with straight forward functionality. There might be no intrest for implementing it. The future belongs to people who prepare for it today. © 2019 Deloitte Private | Accountancy & Advisory. If you have to debug an issue, it might be a trigger telling you to leave the debug data in with a smart system. Best practices in Liquid 8
Implementing debug data in a “Liquid template” Why? Efficiency in analysis Write code once Transparency Reduce the time needed to get a proper analyses of an issue. Leave your code snippet from development phase in the code, in a display friendly way. Make the template self explaining in the mechanics behind the scene. Clarify an outcome on the screen as a result of a formula in no-time. Avoiding you need to write the code over and over again each time you need to investigate the template. © 2019 Deloitte Private | Accountancy & Advisory. Best practices in Liquid 9
Implementing debug data in a “Liquid template” Thank you for attending this session Ruben Moerman Senior. net developer Deloitte Accountancy rumoerman@deloitte. com + 32 11 89 39 25 © 2019 Deloitte Private | Accountancy & Advisory. Best practices in Liquid 10
The content and the layout of this presentation are the exclusive property of Deloitte Accountancy* (hereafter “Deloitte”) and/or its employees, and are protected by copyright and other relevant intellectual property right laws and conventions. Absolutely no reproduction in any form or via any medium is allowed without Deloitte’s express permission. This presentation was drawn up in general terms and therefore cannot be depended on for specific situations. Although Deloitte verifies the reliability of the information given, such information is general and Deloitte may under no circumstances be held liable for possible errors that might occur as a result of the use or the interpretation of this information without the assistance of Deloitte. The information that is contained in this presentation is based on the law, regulations, case-law, specific cases, rulings and other sources that exist at the time of the presentation. Consequently, subsequent changes in or to the foregoing (about which Deloitte bears no responsibility to inform the reader/user) can invalidate the information contained in the presentation. Application of the principles contained in the presentation will depend on the specific applicable circumstances, and we advise you to request professional advice before taking or refraining from any action on the basis of the content of this presentation. Deloitte would be happy to assist the reader/user by advising him on how to apply these principles in specific situations. Deloitte accepts no duty of due care or liability for any loss caused to a person who takes or refrains from any action as a result of any information contained in this presentation. About Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited (“DTTL”), its global network of member firms, and their related entities. DTTL (also referred to as “Deloitte Global”) and each of its member firms are legally separate and independent entities. DTTL does not provide services to clients. Please see www. deloitte. com/about to learn more. Deloitte Private is the brand under which firms in the Deloitte network provide services to privately owned entities and high-net-worth individuals. Deloitte is a leading global provider of audit and assurance, consulting, financial advisory, risk advisory, tax and related services. Our network of member firms in more than 150 countries and territories serves four out of five Fortune Global 500® companies. Learn how Deloitte’s approximately 286, 000 people make an impact that matters at www. deloitte. com. © 2019. For information, contact Deloitte Private | Accountancy & Advisory.
- Slides: 11