Pinned
Template
coreFORCE Feature Request Template
Feature Request Template: This template provides a clear structure for suggesting new features. It includes sections for describing the problem, proposing a solution, explaining user impact, and defining success criteria. This format ensures all key details are captured, making it easier to evaluate and prioritize feature requests. How to Use: When posting a feature request on the forum, copy and paste the template into your post. Fill out each section to explain what you’re requesting, why it’s needed, and how it will benefit users. Providing mockups or examples from similar systems can further strengthen your proposal. Feature Request Title: A concise, descriptive title of the feature being requested. Summary: A brief overview of the feature and what it aims to achieve. Problem Statement: Describe the problem or pain point that this feature is intended to solve. Be specific about the challenges faced without this feature. Proposed Solution: Detail the proposed feature and how it would function. Include high-level details on how it could be implemented or integrated. User Impact: Explain how this feature would benefit users. Include examples of who would use it and how it would improve their experience. Additional Notes: Include any related references, links to mockups, similar features in other systems, or technical constraints.
Josh Okey About 1 year ago
💡 coreFORCE Feature Requests
Pinned
Template
coreFORCE Feature Request Template
Feature Request Template: This template provides a clear structure for suggesting new features. It includes sections for describing the problem, proposing a solution, explaining user impact, and defining success criteria. This format ensures all key details are captured, making it easier to evaluate and prioritize feature requests. How to Use: When posting a feature request on the forum, copy and paste the template into your post. Fill out each section to explain what you’re requesting, why it’s needed, and how it will benefit users. Providing mockups or examples from similar systems can further strengthen your proposal. Feature Request Title: A concise, descriptive title of the feature being requested. Summary: A brief overview of the feature and what it aims to achieve. Problem Statement: Describe the problem or pain point that this feature is intended to solve. Be specific about the challenges faced without this feature. Proposed Solution: Detail the proposed feature and how it would function. Include high-level details on how it could be implemented or integrated. User Impact: Explain how this feature would benefit users. Include examples of who would use it and how it would improve their experience. Additional Notes: Include any related references, links to mockups, similar features in other systems, or technical constraints.
Josh Okey About 1 year ago
💡 coreFORCE Feature Requests
Pinned
Template
coreSTORE Feature Request Template
Feature Request Template: This template provides a clear structure for suggesting new features. It includes sections for describing the problem, proposing a solution, explaining user impact, and defining success criteria. This format ensures all key details are captured, making it easier to evaluate and prioritize feature requests. How to Use: When posting a feature request on the forum, copy and paste the template into your post. Fill out each section to explain what you’re requesting, why it’s needed, and how it will benefit users. Providing mockups or examples from similar systems can further strengthen your proposal. Feature Request Title: A concise, descriptive title of the feature being requested. Summary: A brief overview of the feature and what it aims to achieve. Problem Statement: Describe the problem or pain point that this feature is intended to solve. Be specific about the challenges faced without this feature. Proposed Solution: Detail the proposed feature and how it would function. Include high-level details on how it could be implemented or integrated. User Impact: Explain how this feature would benefit users. Include examples of who would use it and how it would improve their experience. Additional Notes: Include any related references, links to mockups, similar features in other systems, or technical constraints.
Josh Okey About 1 year ago
💡 coreSTORE Feature Requests
Pinned
Template
coreSTORE Feature Request Template
Feature Request Template: This template provides a clear structure for suggesting new features. It includes sections for describing the problem, proposing a solution, explaining user impact, and defining success criteria. This format ensures all key details are captured, making it easier to evaluate and prioritize feature requests. How to Use: When posting a feature request on the forum, copy and paste the template into your post. Fill out each section to explain what you’re requesting, why it’s needed, and how it will benefit users. Providing mockups or examples from similar systems can further strengthen your proposal. Feature Request Title: A concise, descriptive title of the feature being requested. Summary: A brief overview of the feature and what it aims to achieve. Problem Statement: Describe the problem or pain point that this feature is intended to solve. Be specific about the challenges faced without this feature. Proposed Solution: Detail the proposed feature and how it would function. Include high-level details on how it could be implemented or integrated. User Impact: Explain how this feature would benefit users. Include examples of who would use it and how it would improve their experience. Additional Notes: Include any related references, links to mockups, similar features in other systems, or technical constraints.
Josh Okey About 1 year ago
💡 coreSTORE Feature Requests
Pinned
Template
coreFORCE Bug Report Template
Bug Report Template Bug Report Template: This template is designed to help users report issues clearly and effectively. It breaks down the key components of a bug report into structured sections: expected behavior, actual behavior, steps to reproduce, and additional notes. By following this format, users ensure their reports are easy to understand and actionable for the development team. How to Use: When posting a bug on the forum, copy and paste the template into your post, fill in each section with as much detail as possible, and provide screenshots or additional context if necessary. This helps the team replicate the issue and address it quickly. Bug Report Title: A concise title summarizing the issue. Expected: Describe the expected behavior or functionality. Actual: Describe the actual behavior or the observed problem. Steps to Reproduce: Step 1: What to do first. Step 2: What to do next. Step 3: What happens after? Notes: Add any additional observations, context, or comments to emphasize the impact of the issue.
Josh Okey About 1 year ago
🐛 coreFORCE Bugs
Pinned
Template
coreFORCE Bug Report Template
Bug Report Template Bug Report Template: This template is designed to help users report issues clearly and effectively. It breaks down the key components of a bug report into structured sections: expected behavior, actual behavior, steps to reproduce, and additional notes. By following this format, users ensure their reports are easy to understand and actionable for the development team. How to Use: When posting a bug on the forum, copy and paste the template into your post, fill in each section with as much detail as possible, and provide screenshots or additional context if necessary. This helps the team replicate the issue and address it quickly. Bug Report Title: A concise title summarizing the issue. Expected: Describe the expected behavior or functionality. Actual: Describe the actual behavior or the observed problem. Steps to Reproduce: Step 1: What to do first. Step 2: What to do next. Step 3: What happens after? Notes: Add any additional observations, context, or comments to emphasize the impact of the issue.
Josh Okey About 1 year ago
🐛 coreFORCE Bugs
Pinned
Template
coreSTORE Bug Report Template
Bug Report Template: This template is designed to help users report issues clearly and effectively. It breaks down the key components of a bug report into structured sections: expected behavior, actual behavior, steps to reproduce, and additional notes. By following this format, users ensure their reports are easy to understand and actionable for the development team. How to Use: When posting a bug on the forum, copy and paste the template into your post, fill in each section with as much detail as possible, and provide screenshots or additional context if necessary. This helps the team replicate the issue and address it quickly. Bug Report Title: A concise title summarizing the issue. Expected: Describe the expected behavior or functionality. Actual: Describe the actual behavior or the observed problem. Steps to Reproduce: Step 1: What to do first. Step 2: What to do next. Step 3: What happens after? Notes: Add any additional observations, context, or comments to emphasize the impact of the issue.
Josh Okey About 1 year ago
🐛 coreSTORE Bugs
Pinned
Template
coreSTORE Bug Report Template
Bug Report Template: This template is designed to help users report issues clearly and effectively. It breaks down the key components of a bug report into structured sections: expected behavior, actual behavior, steps to reproduce, and additional notes. By following this format, users ensure their reports are easy to understand and actionable for the development team. How to Use: When posting a bug on the forum, copy and paste the template into your post, fill in each section with as much detail as possible, and provide screenshots or additional context if necessary. This helps the team replicate the issue and address it quickly. Bug Report Title: A concise title summarizing the issue. Expected: Describe the expected behavior or functionality. Actual: Describe the actual behavior or the observed problem. Steps to Reproduce: Step 1: What to do first. Step 2: What to do next. Step 3: What happens after? Notes: Add any additional observations, context, or comments to emphasize the impact of the issue.
Josh Okey About 1 year ago
🐛 coreSTORE Bugs
In Progress
Error when trying to merge customers with the same DL number in CoreSTORE
When client tries to merge their customers they get a white screen and and error of "Column 'person_id' in order clause is ambiguous" in the error log.
Torilyn Jade 2 days ago
🐛 coreSTORE Bugs
In Progress
Error when trying to merge customers with the same DL number in CoreSTORE
When client tries to merge their customers they get a white screen and and error of "Column 'person_id' in order clause is ambiguous" in the error log.
Torilyn Jade 2 days ago
🐛 coreSTORE Bugs
In Progress
"Error in Console log" When trying to upload an image to the FFL maintenance ( FFL PDF)
When uploading an FFL image into the FFL maintenance section of CF we get "Error in Console Log"
Torilyn Jade 3 days ago
🐛 coreFORCE Bugs
In Progress
"Error in Console log" When trying to upload an image to the FFL maintenance ( FFL PDF)
When uploading an FFL image into the FFL maintenance section of CF we get "Error in Console Log"
Torilyn Jade 3 days ago
🐛 coreFORCE Bugs
FFL LICENSE COPY IS NOT SAVING
when the file is uploaded, and save is clicked it says record sucessfully updated, but it's not saving the file.
Kierstenn Dionisio 3 days ago
🐛 coreFORCE Bugs
FFL LICENSE COPY IS NOT SAVING
when the file is uploaded, and save is clicked it says record sucessfully updated, but it's not saving the file.
Kierstenn Dionisio 3 days ago
🐛 coreFORCE Bugs
In Progress
Fragment not working for MAP on product
Client would like to set up a fragment TEXT_BANNER_FOR_MAP_PRODUCTS, for every MAP policy except for: "ignore" and "see price in cart". We have added to code into the java script of the product detail page but it is still not showing on products
Torilyn Jade 4 days ago
🐛 coreFORCE Bugs
In Progress
Fragment not working for MAP on product
Client would like to set up a fragment TEXT_BANNER_FOR_MAP_PRODUCTS, for every MAP policy except for: "ignore" and "see price in cart". We have added to code into the java script of the product detail page but it is still not showing on products
Torilyn Jade 4 days ago
🐛 coreFORCE Bugs
In Progress
Base cost not updating on product
Base cost is not updating from distributor feeds. Cost is updating on Inventory tab, but is not being updated in Base Cost field on the Pricing tab.
Keli Cropley 6 days ago
🐛 coreFORCE Bugs
In Progress
Base cost not updating on product
Base cost is not updating from distributor feeds. Cost is updating on Inventory tab, but is not being updated in Base Cost field on the Pricing tab.
Keli Cropley 6 days ago
🐛 coreFORCE Bugs
"Download Receipt" Failing
Client noticed that the "Download Receipt" option seems to be failing. "Failed to Generate PDF" error received when attempting to download the receipt. This was replicated by support on the client's site but we have not been able to replicate in any test environment so far.
Keli Cropley 7 days ago
🐛 coreFORCE Bugs
"Download Receipt" Failing
Client noticed that the "Download Receipt" option seems to be failing. "Failed to Generate PDF" error received when attempting to download the receipt. This was replicated by support on the client's site but we have not been able to replicate in any test environment so far.
Keli Cropley 7 days ago
🐛 coreFORCE Bugs
In Progress
Product images do NOT Display in the new search pop out
The product has an image in the back end of CF, on the product detail page and in the catalog but the image does not show in the new search pop out window Example UPC: 082442981840
Torilyn Jade 7 days ago
🐛 coreFORCE Bugs
In Progress
Product images do NOT Display in the new search pop out
The product has an image in the back end of CF, on the product detail page and in the catalog but the image does not show in the new search pop out window Example UPC: 082442981840
Torilyn Jade 7 days ago
🐛 coreFORCE Bugs
In Progress
Variations showing behind the price in search pop up
Variation items are showing the dropdown for the variation behind the price in the search pop up Class example - 266488643. Membership example -89955836
Torilyn Jade 8 days ago
🐛 coreFORCE Bugs
In Progress
Variations showing behind the price in search pop up
Variation items are showing the dropdown for the variation behind the price in the search pop up Class example - 266488643. Membership example -89955836
Torilyn Jade 8 days ago
🐛 coreFORCE Bugs
In Progress
Firearm Transfers for Private Parties aren't populating Middle Name in the Acquisition.
Seller's middle name does not get entered into acquisition record for any private party firearms transfers processed on the Firearm Transfer Dashboard
Keli Cropley 10 days ago
🐛 coreSTORE Bugs
In Progress
Firearm Transfers for Private Parties aren't populating Middle Name in the Acquisition.
Seller's middle name does not get entered into acquisition record for any private party firearms transfers processed on the Firearm Transfer Dashboard
Keli Cropley 10 days ago
🐛 coreSTORE Bugs
In Progress
Continuation : Google Analytics code not working for View_Item
Google Analytics code was working and the client has noticed that since the new check out, the analytic code is no longer tracking: View_item
Torilyn Jade 10 days ago
🐛 coreFORCE Bugs
In Progress
Continuation : Google Analytics code not working for View_Item
Google Analytics code was working and the client has noticed that since the new check out, the analytic code is no longer tracking: View_item
Torilyn Jade 10 days ago
🐛 coreFORCE Bugs
In Progress
Commissions are not calculating correctly.
The Commission Default Rate is set to 1% But sales in the Commission Detailed Report are not showing the correct calculation for this 1% of the selling price.
Torilyn Jade 10 days ago
🐛 coreSTORE Bugs
In Progress
Commissions are not calculating correctly.
The Commission Default Rate is set to 1% But sales in the Commission Detailed Report are not showing the correct calculation for this 1% of the selling price.
Torilyn Jade 10 days ago
🐛 coreSTORE Bugs
In Progress
Waiver isn't transferring to coreSTORE properly
Client has a customer who has a wavier form in CoreFORCE on his Contact that shows correctly in CoreFORCE but when it transmits to CoreSTORE it is showing as a FFL PDF and not the form he filled out on CoreFORCE
Torilyn Jade 10 days ago
🐛 coreFORCE Bugs
In Progress
Waiver isn't transferring to coreSTORE properly
Client has a customer who has a wavier form in CoreFORCE on his Contact that shows correctly in CoreFORCE but when it transmits to CoreSTORE it is showing as a FFL PDF and not the form he filled out on CoreFORCE
Torilyn Jade 10 days ago
🐛 coreFORCE Bugs
In Progress
Quoted Item Not Displayed in Cart After Clicking Quote Email Link
Despite being logged in, when the customer clicks the quote email link, the cart appears empty.
Mark Kalalo 13 days ago
🐛 coreFORCE Bugs
In Progress
Quoted Item Not Displayed in Cart After Clicking Quote Email Link
Despite being logged in, when the customer clicks the quote email link, the cart appears empty.
Mark Kalalo 13 days ago
🐛 coreFORCE Bugs
In Progress
NoFraud isn't receiving AVS codes
When No fraud is attempting to help with a charge back they determined they didn't receive any AVS information from us for a specific order 149336
Torilyn Jade 14 days ago
🐛 coreFORCE Bugs
In Progress
NoFraud isn't receiving AVS codes
When No fraud is attempting to help with a charge back they determined they didn't receive any AVS information from us for a specific order 149336
Torilyn Jade 14 days ago
🐛 coreFORCE Bugs
Add a permission to restrict changing the sales person
When the setting to change the sales person during the sale is enabled we need a permission to not allow certain employees to change the sales person.
Zachary Meyers 15 days ago
💡 coreSTORE Feature Requests
Add a permission to restrict changing the sales person
When the setting to change the sales person during the sale is enabled we need a permission to not allow certain employees to change the sales person.
Zachary Meyers 15 days ago
💡 coreSTORE Feature Requests
Tier Types setting based off Subscritptions with coreCLEAR
When selling memberships using coreCLEAR & coreSTORE it should allow us to automatically set a customer tier type based off of the subscription sold.
Zachary Meyers 15 days ago
💡 coreSTORE Feature Requests
Tier Types setting based off Subscritptions with coreCLEAR
When selling memberships using coreCLEAR & coreSTORE it should allow us to automatically set a customer tier type based off of the subscription sold.
Zachary Meyers 15 days ago
💡 coreSTORE Feature Requests
In Progress
Debit card issues on account payments
Debit is not working when trying to make a payment on an already existing layaway made on CF
Torilyn Jade 16 days ago
🐛 coreFORCE Bugs
In Progress
Debit card issues on account payments
Debit is not working when trying to make a payment on an already existing layaway made on CF
Torilyn Jade 16 days ago
🐛 coreFORCE Bugs
In Progress
Credit Card Fee's don't get applied if Credit Card is set as default Payment Type
Having a "default payment method" set in coreSTORE company>settings>payment types to "Credit Card" and having credit card fees under company>location>taxes and fees, does not seem to be applying credit card fees.
Tyler Early 16 days ago
🐛 coreSTORE Bugs
In Progress
Credit Card Fee's don't get applied if Credit Card is set as default Payment Type
Having a "default payment method" set in coreSTORE company>settings>payment types to "Credit Card" and having credit card fees under company>location>taxes and fees, does not seem to be applying credit card fees.
Tyler Early 16 days ago
🐛 coreSTORE Bugs
In Progress
coreSTORE: Buyers Assistant Filters not functioning properly.
In coreSTORE, if you go to Purchasing > Buyers Assistant > For the "Select criteria for analysis:" filter, select the "Items that have sold in past week" option > Click "Review" > It doesn't show nearly as much as what was actually sold on the Detailed Sales Report.
Keli Cropley 18 days ago
🐛 coreSTORE Bugs
In Progress
coreSTORE: Buyers Assistant Filters not functioning properly.
In coreSTORE, if you go to Purchasing > Buyers Assistant > For the "Select criteria for analysis:" filter, select the "Items that have sold in past week" option > Click "Review" > It doesn't show nearly as much as what was actually sold on the Detailed Sales Report.
Keli Cropley 18 days ago
🐛 coreSTORE Bugs