Sajan Parikh

Home/Sajan Parikh

About Sajan Parikh

This author has not yet filled in any details.
So far Sajan Parikh has created 20 blog entries.

Release 19.02.12 [Beta]

This is the first set of release notes for Powercode v19 which runs on CentOS 7.  These release notes do not represent all of the changes between v18 and v19.  These release notes are for changes from v19.01.09 through v19.02.12.  We are going to start publishing release notes for each version of v19 as we start putting v19 into more and more people’s hands.  If you are currently on v18, many of the bug fixes in v19 releases are backported and you should continue to review the release notes for v18 releases of Powercode.  Publishing release notes regularly is another step in us making v19 available to everyone, we thank you for your patience.

These release notes are for the benefit of those helping us beta test v19.  v19 is still in beta and as such there are a higher volume of bug fixes.  Many items you read about in a v19 release are exclusively affecting v19.

System Changes

  • Re-establishes connection after each successful backup to the remote backup server, as previously we were failing to properly backup multiple files.
  • Displays an error message as a reason when a patch fails to apply.
  • Resolved issues with Powercode process identification files so they now have the appropriate permissions.
  • Resolved some issues that were causing some system crashes due to infinite worker spawning.
  • Fixed icon alignment for the account profile picture in the navigation bar.


  • Fixed Bank Account returns so they log the appropriate response reason for why they failed.
  • Updated how we verify transactions so it checks the gateway properly before running.
  • Resolved issues for processing payments for Charge Cards on Bill Due Day.
  • Charge Cards on Bill Due Day now labels Bank Account payments properly.
  • Resolved an issue in which Accounts > Enter Payment was not functioning as expected.
  • Customers can no longer delete a Bank Account that has a payment in the PaymentQueue.
  • IPPay verification now returns the transaction result to verify as expected.
  • Fixed one-time scheduled event charges from adding taxes as debits.
  • Resolved issues with the Expired Credit Card script to properly validate / send emails when they do expire.
  • Creating ACH Batches now properly pulls account number to deposit the batch into.
  • Permissions are now properly checked when generating a manual invoice.
  • Resolved issues with ProPay not checking the correct transaction when verifying them.
  • Verifying transactions no longer loads transactions from all time, and instead
    only loads transactions from the past month.
  • Logs the correct response from Authorize to fix errors with determining what happened.
  • Fixed Late Fee Days after Due to display the saved value properly.


  • Added PC_Speedtest application to Saisei to handle how Saisei 7.3 detects speed tests.
  • We now generate PCQ slow plans for Saisei if applicable.
  • Removes applications from policies that have groups in Saisei (was causing issues).
  • Saisei mirrors are no longer required to be Saisei BMUs.
  • Ookla will now identify as speedtest.
  • Optimized how we load equipment relationship data to greatly increase sync data speeds, especially on large network customers.
  • Added ‘don’t care’ option to Saisei internal ranges.
  • Added host exclusion list to Saisei.
  • Sets host application limit to match user limit.
  • Added checks to ensure default Upload/Download values are pushed if they don’t exist.
  • “Other” Saisei policies can now be edited.
  • The queries to fetch infrastructure equipment and their parents have been update to accurately retrieve all applicable equipment with accurate upstream values.
  • Updated the way we display the Saisei version string on the BMU Overview page.


  • Added the ability to enable or disable firewall rules for MikroTik.


  • Added optimizations to how we handle Preseem data to increase performance.

Powercode BMU

  • Fixed issues with customer update events that were causing the Slave BMU to kick into an out of sync status.


  • Fixed a problem with the Debits / Credits report from trying to select a non-existent data field.
  • Removed Failed Tokenization report.
  • New Financial Dashboard (v2).
  • The entire customer status report can now be exported, as opposed to just the active page, and it now functions properly.
  • Fixes missing tablesorter from the individual site overview logs.
  • Fixed a bug that was excluding duplicate-customer-name entries from the Address Range report.
  • Fixed missing pager and exporter in the Accounts With Balances Due report.
  • Customer status reports now link the Customer Name as well as the ID to the customer account.
  • Equipment by Status now tries for a second address if the first is non-existent.
  • SubAccountClass report now properly classifies taxes and credits.
  • SubAccountClass fixes for issues with loading service information for deleted services.
  • Removed default date from the SubAccountClass report.
  • Form 477 report will no longer generate for excluded services.


  • Resolved an error that was checking for equipment name even if we failed to load it.
  • Removed requirement to have a piece of equipment before adding a Remote Subnet.
  • Auto Parent Child now delete jobs after 2 failures, it will get kicked back in and tried during the next cycle anyway.
  • Auto Parent Child now properly determines which BMU to send to, reroutes if there is a Bad BMU in the pipe.
  • Auto Parent Child will now only re-queue equipment if prior equipment has finished processing.
  • Auto Parent Child will no longer die unexpectedly.
  • Re-added missing quick item assign functionality to Powercode.
  • Fixed IP queries that were loading IPs in range from being so slow.
  • Added permission for choosing not to link matching mac to inventory.
  • Added serial field to equipment form inventory search.
  • Added a permission to allow editing a equipment’s device type and category after its added.
  • Fixed issues in which the Network Site list would not fully populate.
  • Fixed an issue that was setting slowAfterTriggered to an incorrect value.


  • You can now remove a Network Site contact.


  • Custom Customer Alerts for a customer account now update on save, and remain active.
  • Customer alert groups no longer trigger updates twice unnecessarily.
  • Forces verification to ensure our security questions are valid.
  • Resolves an error with trying to increment a bad pass if the WebUser doesn’t exist.
  • No longer show the SMS button on the customer overview if the system isn’t set up for it.
  • Fixed a bug that was preventing contact’s usernames from being updated.
  • Removed readonly attribute from contact username input field.
  • Changes made to ExternalAccountID are now logged.
  • ExternalAccountID now loads as expected when editing a Customer account.
  • Manual status changes for accounts no longer logs as “due to payment”.
  • All country edits / updates are now uniformly saved to proper ISO code.
  • Fixed a bug that was saving address states / countries as numeric values.
  • Added option to require date of birth when creating a new customer.
  • Contact default language preference now defaults to the system default rather than none.
  • Call logs should now sort by their entered time as expected, instead of last updated.
  • Resolved issues with customer address states not saving properly.
  • Added back Saisei graphs to the Customer Overview.

Custom Info Templates

  • Resolved an issue that was preventing you from adding newly-created custom info templates to accounts.
  • We no longer show the disconnect_text report link if that custom template doesn’t exist.

Customer Portal

  • Permissions for setting a payment account to manual or automatic in the Customer Portal is now properly accounted for.
  • Customer Portal users from different countries can now properly select their state or province.
  • Removed permission checks for payment accounts so that existing customer accounts could be used to make payments through the portal.
  • Added ability to change / update username from the Customer Portal.
  • Added default settings to prevent robots from crawling the Customer Portal.


  • Fixed a bug that was preventing all taxes from being removed from a service.
  • Fixed a bug that was causing cancel to submit a one-time credit.
  • One-Time services that are added to accounts before activation will no longer round incorrectly.
  • Fixed rate multiplier text option to display the correct value.


  • Fixed a bug that was causing Powercode-generated emails to be blank.
  • Resolved issues that would result in associated customer email from being blank.

Schedule Live View

  • Resolved issues with schedule live view trying to reference legacy files.
  • Fixed job notes template pager from not displaying.


  • Resolved a problem adding Bank Accounts through the API that was incorrectly validating for a Credit Card.
  • Updates for readCustomer have been made to include current amount due and past due balance.
  • Fixed a bug that was allowing for multiple payments accounts to be primary.
  • We now properly handle JSON new line characters.
  • Added the ability to update equipment addresses.
  • Added getContactByEmail endpoint.
  • Returns error now on failed API payments.
  • Added new endpoint to get a transaction list.
  • Added name and type to listCustomerInvoices.
  • Updated changePortalPassword endpoint to accept email or username in addition to the contact.
  • Fixed a bug preventing you from updating user’s passwords through the API.
  • Resolved an issue with loadByUsername in which multiple accounts were returned.

Mobile View

  • Deletion of equipment now allows for you to return it to stock on mobile.
  • Fixed issues preventing adding equipment back to inventory from equipment on mobile.


  • Added missing Webhooks to Mobile View.
  • Added ‘Serial’ field to equipment webhooks.
  • Equipment add/edit webhook now identifies which specific action it was triggered by.
  • Remove Subnet webhooks will now actually return data.
  • Added a webhook for removing customer services.
  • Added webhook for editing a customer account.
  • Fixed missing trigger for add service webhook during customer creation.
  • Added webhook on delete equipment.
  • Added the ServiceID to equipment and remote subnet webhooks.
  • Fixed a bug that was causing customers with no service from sending out webhooks.
  • Added imsi to equipment webhooks.
  • Added webhooks for remote subnet CRUD methods.
  • Resolved an issue in which Customer Tags wouldn’t associate properly to account update webhooks.

Mass Notification

  • Fixed proper SMS and Email portions showing when they shouldn’t have been.
  • Fixed an issue with getting customer information for a SMS specific customer.
By |2019-08-29T10:58:13-05:002019 February 13th|Changelog|0 Comments

Release 18.12.23 [Stable]


  • 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.

Customer Portal

  • 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.
By |2019-02-12T15:11:03-06:002018 December 23rd|Changelog|0 Comments

Release 18.10.16 [Beta]

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.

Scheduled Events

  • 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.
By |2018-10-16T14:03:37-05:002018 October 16th|Changelog|0 Comments

Saisei STM Update 7.2 9617

  • 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 “”, the user merely needs to create a new application with the server string 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
By |2018-06-20T20:25:22-05:002018 June 15th|Changelog|0 Comments

Easter Friday Phone Support

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.

By |2018-03-30T11:37:28-05:002018 March 30th|News|0 Comments

Important IPPAY Changes With Powercode

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.

By |2017-11-13T17:55:03-06:002017 November 13th|News|0 Comments

Dropbox Backup Updates

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.

Enable Backups

  • 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.

By |2017-11-02T10:32:13-05:002017 November 2nd|News|0 Comments

Bing Maps Disruption August 15, 2017

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.

By |2017-08-15T12:09:13-05:002017 August 15th|News|0 Comments

Track Your Truck Outage July 19, 2017

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.

By |2017-07-19T16:30:49-05:002017 July 19th|News|0 Comments

Join Powercode On Slack!

Powercide & Slack

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 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 ( for an invite.

By |2017-07-17T11:14:10-05:002017 July 17th|News|0 Comments
Go to Top