FAQ1. How do you decide what goes into Nav-to-Net?
For the most part, features that are added to Nav-to-Net are influenced by feedback from partners and customers. DVP balances several considerations to decide on new or evolving features.
Some of these consideration include; feature dominance, feature usefulness, feature practicality, likelihood of ROI, and "coolness" of new feature.
FAQ 2. What limits your ability to create new features?
Besides the financial commitment involved in creating new features, the #1 limitation for building new features in Nav-to-Net stems from our commitment to tight integration with NAV. Nav-to-Net generally will not present a business process or capability to a customer unless the exact same functionality already exists or can exist in NAV. Also, Often the NAV approach to handling certain requirements does not map well to an internet users experience.
FAQ 3. What are some of the key considerations that go into your functional design?
In addition to requiring compelling functionality on NAV, some key considerations include:
i) Performance of the code
ii Amount of data involved
iii) Possible load on the backend system
iv) Scalability of the design