- Down equipment list now attempts to pull a secondary address if the primary isn’t available.
- Customer Status Lists now link both the customer name as well as ID to the customer account.
- Excluded services no longer generate with the rest in the 477 report.
- The account subclass report now properly classifies payments or tax credits.
- Removed default date in the account subclass report.
- Fixed a case in which deleted services would not be included in the account subclass report.
- Sets host application limit to match user limit. This helps with missing application history on the user.
- Added host exclusion list to Saisei. This allows you to define a list of IP addresses that you are manually managing within the STM itself.
- Added the ability to prevent Powercode from writing MikroTik firewall rules. This allows you to write your own firewall rules using the Powercode generated address lists.
- Generates PCQs for slowed plans if applicable.
- Added the ability to require Date of Birth in the Add Customer Wizard.
- Customer alerts no longer become deactivated when they are edited.
- Customer alerts now show which tags they have associated with them.
- Customer alerts now update upon customer edit.
- Allow Auto/Manual now properly restricts or allows customers from switching payment type in the Customer Portal.
- Resolved a problem with the duplicate serial check that was checking deleted equipment and triggering a false-positive.
- Resolved an issue that would not link a ticket email to the appropriate customer.
- Escalating a call log to a ticket is now only available if you have ticketing enabled.
Powercode System Updates
- Changed how we load available patches to avoid loading incompatible patches.
- We now strip non numeric characters from phone numbers before sending them to BOSS to avoid odd behavior.
- Fixed a validation issue that would result in multiple accounts being created accidentally.
- When managing service areas, we were being too strict on validation which resulted in some states not being able to be created if they were new to your system.
- We now add the entire parent/child tree into Saisei so long as only a single parent exists for a device.
- Fixed a case where slow plans were not being applied properly.
- When creating a service related event, we now show you the ‘ISP Description’ field as well so you know which service you are selecting if you have multiple that share the same main name.
- Improvements to configuration wizard – added the setting of Ubuntu and STM passwords to the default accounts for increased security.
- Password security improvements: config wizard forces CLI/GUI/Rest and shell passwords to be changed, to something not readily guessable.
- Fix problems with changing system name, which could lead to the system becoming inconsistent.
- Support history collection and analysis for all users, up to 20,000.
- Improve built-in packet capture facility.
- Fix some problems with traffic accounting in complex configurations, which could lead to traffic being counted twice and to limits being applied incorrectly.
- Allow 32 bit Autonomous System numbers, previously the STM only handled 16 bit values
- Correct the flow counts associated with policy entries
- P2P applications were being incorrectly identified and placed in other application groups, this has been corrected.
- FTP transfers were being incorrectly identified, the initial handshake was correct however the data transfer phase was not, this has now been corrected
- Heavy traffic loads together with heavy REST usage triggered system reloads, this is now fixed
- The behavior for packet forwarding when using a LAG interface has been changed, originally packets were “rebumped” and could perhaps be sent out on an interface not associated with the BITW port pair that the inbound packet was accepted on. The behavior is now changed to always send packets on the egress interface linked directly to the ingress interface.
- Correct an error when creating user specific applications. The REST documentation allows a user to create a wildcarded application to capture all applicaations containing the wild carded string, perhaps there are several entries in the application tables containing the string “dstv.com”, the user merely needs to create a new application with the server string dstv.com to capture all such entries. This was not working correctly and has been corrected.
- Due to a cabling error where Internal and External cables were swapped a crash was observed which was discovered to be associated with the system running out of Egress Flow Class table entries, the software was found not to return an error state and hence caused a crash. The error return has now been corrected.
- Poor REST API performance has been observed at an installation and found to be associated with an excessive number of internal hosts being created, partially due to inbuilt processing
Powercode will be closing early on Friday, March 30, 2018 to host a company event for the afternoon. We will close at 12PM (Noon) CST for the day. If you have a business impacting outage, please call in and proceed to engage our on-call services. Please leave a detailed message and we’ll get back to you as soon as possible.
Most IPPAY/Powercode Customers Are Not Affected By This.
We were made aware of some changes required by IPPAY related to the SEC code sent during transactions involving bank accounts. We have received the requirements from IPPAY and understand some Powercode users will have received a similar message as well. Powercode is currently on working on providing the tools necessary to correctly code bank accounts and their transactions. This will be released in an update currently scheduled for November 22, 2017. Please keep an eye on this website after that release for full information related to the SEC code and what you should do to mitigate any discrepancies.
We apologize for any confusion and are working with IPPAY to adhere to these new requirements as soon as possible.
As of 17.10.19, Powercode’s backups integration for Dropbox has been updated and may require you to authorize your account again for your backups to Dropbox to continue functioning. Below is a quick guide focusing on how to reauthorize your Dropbox account for Powercode to push the backup files to. If you are not using Dropbox, you can ignore this post.
On a side note, we will be providing Amazon S3 as a backup destination option within the next couple weeks.
- Navigate to Config->Backup Settings
- Set Enable Backups to “Enabled”
- Set your backup schedule
- Set Remote Backups to “Enabled”
- Set Backup Method to “Dropbox”
- Click “Get Authorization Code”
You will now be routed to Dropbox’s site where you will generate an authorization code.
Allow Powercode Remote Backups Access
You need to give Powercode permission to save backups to your Dropbox account.
- Log in to your account (or create a new account) if required
- Grant Powercode access to save backups to your account by clicking “Allow”
- Copy the authorization code that Dropbox generates
Now that you have an authorization code you can continue with the process in Powercode.
Complete Backup Settings
Enter the remaining information to complete the backup settings.
- In Powercode paste the authorization code into the appropriate field
- Enter a directory path of your choice where the backups will be saved
- Save settings
Powercode is now configured to save backups to your Dropbox account.
Bing maps is having a confirmed outage for some users starting around 11AM CST. Powercode uses Bing Maps as a provider for map related functionality. Your software will be affected until Bing Maps is restored. We are monitoring the outage and will update here.
Update: As of 12:08PM CST, it looks like most Powercode users that were having an issue have seen a resolution.
Track Your Truck, a third party that Powercode has integrated with for certain features, suffered an outage today. Whether your company has enabled the Track Your Truck feature or not, your Powercode instance will be quite sluggish.
We have been told by Track Your Truck that they have switched to backup servers, but DNS propagation will take some time.
If you are having issues in the meantime, please call Powercode support and we will add a dummy DNS entry on your server to resolve the current issue.
On a slightly related note, we have fixed a bug in which if you aren’t using Track Your Truck, your server stops relying on Track Your Truck. This change would limit Track Your Truck issues to only those using Track Your Truck in the future.
We’ve opened a new Powercode Slack community to connect with each other, have some fun, and foster the type of feedback our team needs to continue making Powercode great. So if you are interested in joining us, send an email to email@example.com asking for an invite. Once you join, you’ll be connected to a few members of the Powercode staff as well as other Powercode users.
Again, shoot an email to Sajan (firstname.lastname@example.org) for an invite.