Describe your idea. The more information you provide, the clearer picture of your idea we will have. |
Every calculated or read only locked field allows the option of overriding it to enter your own value |
How will this idea help you and potentially others? Understanding how things are done today, where the pain is, and how the idea is beneficial puts us in your shoes. |
While the calculated fields in CTRAC tax forms are very helpful, it can be difficult accounting for every possible tax situation. While implementing custom logic for every tax situation would be ideal, allowing an override would give a workaround so the form can still be filed before the custom logic has been implemented. Less last-minute tax filing emergencies |
Who will benefit from this idea? Whether it's specific roles of users, users of a specific product, or certain departments/markets, this helps us know who to talk to when we need more information. |
Organizations whose unique tax situation as not been accounted for in the application logic yet. |
How do you envision this idea being implemented at K1x? You're the expert and understanding how you see this working helps kickstart the idea. |
Similar to existing overridable field implementations. Turn calculated fields into input boxes and indicate with styling whether the value is calculated or user entered (state forms module implementation) OR Integrate a small checkbox/button onto the read-only fields. Clicking turns into an input box with custom value. |