Recently, we received a follow-up question to the September 2021 Trail Mix: We often experience users anxious to get back into the system after month-end processing. Although the Period End flag has been cleared allowing this to occur technically, we still wish to prevent users from performing maintenance until the accounting/finance has given the “all clear.” How do you recommend we prevent users from accessing the system during these periods?

Read More

 

For many Lessors with teams operating across multiple time zones, it is critical to maximize system availability. This requires a holistic study of all aspects of system operations, but we have found the daily and monthly execution of batch processing like Nightly Job Stream (NJS) to be “low hanging fruit” to monitor and improve performance.

Read More

 

We’ve shared the tips and tricks that we find helpful, but now we want to hear from you. Do you have any problems that you just can’t seem to find the solution to or processes that you find cumbersome? Any tips you’ve found useful that you think could benefit others? Submit your problems, ideas, or tips to trailmix@tamaracknow.com. If we use your idea, we’ll send you a Tamarack Yeti-brand tumbler and some edible trail mix to go with it.

Read More

 

Contracts can be added to the WK.INVOICE file using the following methods: 1) Invoice Processing via the NJS, 2) Manual Invoicing, or 3) Invoice Utility. Note: the N.CODE.USERID field clarifies how contracts were added to the work file.

Read More

 

The Nightly Job-Stream (NJS) allows you to combine both system updates and reporting functions into a single process that can be pre-scheduled to run daily, monthly or yearly. One of the features of NJS processing is the ability to further customize the process by imbedding your own processes to automatically run within the NJS. Custom processes can be incorporated into one of seven “User Exit” points that occur at specific times during the NJS process.

Read More