A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.225

1. For Backinzo Premium Users, Bankex will also be the part of “DTE W.r.t Monthly Expiry Only for BNF, FIN and MID” for the Monthly Expiry Tick Box under Backtest settings window.

2. RiskOn / Risk Off wasn't working properly for the Premium / Greek Based legs, this is fixed now.

3. We were getting requirements from the users to monitor for the Premiums of CE and PE legs and when the difference between both of them increased by some percentage, then take the action.

To achieve this, we have added “Premium Comparison Monitoring” under the “Other Settings” Tab.

Premium Comparison Monitoring

If Enabled, It will compare the Premium of first active CE and PE legs as per the settings. If more than one CE / PE legs, then it will compare the premiums of first active PE vs CE leg. it will compare a lower premium with a higher premium. For example: if the CE is 50 and PE is 60. it's 20% higher than the lower strike.

Difference Percentage:
Here you have to enter the value in percentage which will be checked between the active CE / PE premiums. If the premiums between the Active CE / PE legs become more than the mentioned percentage, then selected action will be taken by the app.

Suppose CE was 100 and PE was 120, in this case percentage will be calculated w.r.t lower values with the difference which will come to 20%.

If you have specified the Min Hold for Seconds, then Before taking any action, the app will take action if the difference stays for more than mentioned time.


Min Points:
In some cases of lower premium, difference percentage may become a negligible value. In that case this field can be useful.

If this is mentioned, then the App will consider the higher value between ‘Difference Percentage’ and ‘Min Points’.

Suppose Lower premium was 5 and difference percentage was mentioned as 10% which will come to 0.5. Now suppose Min Point was mentioned as 2 then the app will consider 2 as a difference.


Min Hold for Seconds:
If you want to wait for sometime to avoid any sharp movements, you can specify the wait time in seconds here.

App will take the action only if the mentioned difference is sustained for more than the specified seconds.


Which Leg to SqOff:
Here you can set which leg you wanted to SqOff if the different conditions met.


Which Action to take on SqOff:
If you have specified any On SL / On Target action for the leg, then from here you can specify which action you wanted to take for that leg.

This will treat SqOff of the leg as per the action selected. Suppose you want to take OnSL action in case of SqOff due to Premium Difference, then the App will treat that leg was SqOff as OnSL and its action will be taken accordingly.

In Simple words, it will specify that the leg will be SqOff as OnSL or OnTarget.

IT IS IMPORTANT TO NOTE THAT IF THE ACTION HAS REECEUTION (OF ANY TYPE) OF THE LEG, THEN BEFORE TAKING ANY ACTION APP WILL FIRST CHECK THE CONDITION AND DETERMINE IF THE NEW LEG WILL HAVE DIFFERENT STRIKE OR NOT.

IF THE NEW LEG IS ALSO GOING TO HAVE THE SAME STRIKE, THEN IT WILL NOT TAKE ANY ACTION TOWARDS PREMIUM DIFFERENCE AND IT WILL DELAYED THE CONDITION CHECKING OF PREMIUM DIFFERENCE.

NEW LEG WILL ONLY EXECUTE WHEN IT DIFFERS FROM THE PREVIOUS STRIKE

Please let us know on DM If you have any observations / suggestions regarding these newly launched features.

Update version you can see at the left bottom of Login Screen.

A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.227

1. There are some changes specific to some certain rare cases.

Update version you can see at the left bottom of Login Screen.

A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.228

1. Please use the Cache Manager after the Update.

Update version you can see at the left bottom of Login Screen.

A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.229

1. In some cases, the DTE selection on the Backtest screen (where you enter the name for backtest) wasn’t working as expected, this is fixed now.

Update version you can see at the left bottom of Login Screen.

A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.240

1. Reliance Strike Step was coming as 80 which has to be 10, this is fixed now.

Update version you can see at the left bottom of Login Screen.

Dear Users,

Some users are facing an error while saving / testing the BNF Portfolio

Those users can click Options Trading > Refresh Masters > then Click YES

When masters loaded successfully then remember to restart the Backinzo.


Thanks

A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.241

1. Now you can take Backup of all the profiles in a single click from the settings. Similarly you can restore all the profiles in a single click too.

If you have taken backup of all the profiles and wanted to restore only for one selected profile, then just login backinzo into that profile, Goto settings > click restore and select the backup file and keep the tick box 'Backup / Restore All Profiles' unticked. In this way backinzo will restore backup only for the logged-in profile.

2. Reliance Strike Step was coming as 80 which has to be 10, this is fixed now.

3. In a few cases of Positional Portfolio, Portfolio Re-Execution Delay was not working as expected, it's fixed now.

Update version you can see at the left bottom of Login Screen.

A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.242

1. If Move SL to Cost was performed for any leg and when its Moved SL gets hit, It was treated as OnSL, now it will be treated as OnTrailSL.

This may have an impact for the purpose of ‘On SL Action On’ Settings under ‘Other Settings’ Tab.


Update version you can see at the left bottom of Login Screen.

Dear Users,

Users are reaching us with different queries regarding changes in the lot size. Backinzo always uses the actual lot size as applicable to that particular expiry.

However in many cases users wanted to use the same lot size throughout the backtest period, for this user can enable the Settings > Settings and Plugins Installation > Enable Keep Same lot Size for All Expiries > Save Settings > Restart Backinzo.

If this is enabled, then Backinzo will use the latest lot size throughout the backtest period.

Any changes in the lot size will be automatically taken care of as per changes in the exchange masters.


Thanks

Dear Users,

Some users are facing an error while saving / testing the BNF / SENSEX Portfolio(s)

Those users can click Options Trading > Refresh Masters > then Click YES

When masters loaded successfully then restart the backinzo.


Thanks

Dear Users,

If anyone is unable to open the HTML report in the browser due to the large size of the report, then export and share that html report on DM @backinzosup

Thanks

A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.245

1. In case of Positional Backtesting, If you were testing the different exchanges in a same backtest, then it was giving the result from the latest date only. For Eg. If you are testing positional portfolios of NIFTY and SENSEX in the same batch, then results are coming from 2023 only.

This is because SENSEX options started from 2023 only. This is fixed now. Now you can test multiple different exchanges / symbols in the same backtest.

2. Users were asking to enter the Lot Size as per their requirements. For this purpose we have provided 3 types of Lot Settings.

I. LatestLotSize
Backinzo will use the same (latest) lot size from the masters for all the expiries.

II. ActualLotSize
Backinzo will use the actual lot size as applicable to the concerned expiry.

II. ManualLotSize
Backinzo will use the Lot Size and Freeze Qty as set by the user in the Grid.

From this update, By Default backinzo will now use the latest lot size only. However, Now you can change the lot size as per your requirements.


3. In rare cases, after compilation of any Backtest, when users try to create / modify the portfolio then they get an error “Error Occurred while selecting legs” or “Unable to get the LTP” etc.

It is important to note that if these errors are coming only after the performing and Backtest / Simulation then it is possible that previous BT / Simulation moved the clock till 15:30 and there is no data after that.

This update should fix this, however even after this update, if any user is getting an error after completion of the test. Then just select the previous date and select for simulation > start simulation > when test starts then Stop simulation.


Update version you can see at the left bottom of Login Screen.

Dear Users,

Backinzo doesn't support backtesting of data of abnormal days / times like Saturday / Sunday and Mahurat Tradings.

The Purpose of the backtesting is to estimate the performance of any strategy in a regular time which can be deployed in the live, depending upon its performance. The special session like budget cannot be certain and can vary greatly due to many factors.

Including the abnormal days / time will just slow down the overall performance greatly and that too without getting much. It can generate ambiguities in the results.

This was decided in earlier days using a poll among all the users at that time.

Thanks for your understanding.

A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.249

There are some major changes with respect to the Dynamic hedges. If you are using Dynamic Hedge functionality, then due care is required.

1. Now in case of the ReEntry / Execute / Pyramiding etc, If Dynamic hedge was ticked for the original leg, then Backinzo will try to add the more hedge quantity if there is a shortfall.

2. Functionality will behave differently in case of Hedge Leg Sqoff on PortfolioSqoff or with the leg itself.

3. In case of V1 portfolios, Backinzo supports at max 8 legs, however in a rare case, due to the requirement of dynamic hedge, there now can be 9 legs.

For any suggestions or issue reporting for this functionality, you may DM @backinzosup.


Update version you can see at the left bottom of Login Screen.

A new update of Backinzo was rolled out. When you restart the Backinzo, there will be an update version 1.0.2.254

1. Sometimes users were getting an error 'Error occurred while selecting legs' when they try to modify a portfolio after performing a backtest, it's fixed now.

2. In some cases, dynamic hedges were not getting bought for the Idle legs; it's fixed now.

3. We were requested to buy dynamic hedges based on a fixed distance from the related sold leg to maintain Var & margin requirements.

It's implemented now. Users can now choose two types of dynamic hedges, based on fixed distance or Premium based hedge selection which is an existing feature.

4. Security Implementation

Many users are continuously demanding extra security for the MultiLeg Portfolios. Here in this update we are implementing the multi layer security for the MultiLeg module and Portfolio(s).

It is important to understand that all the data of application / portfolio(s) are residing in your PC only. We do not have any kind of access so keep note of your passwords as we won’t be of any help in case you forget them.

Data Locking
Your data resides in your local PC only, however any Backinzo ID can login to the backinzo and is able to access that data. Now your data will be still in your PC but it will be locked to the Backinzo ID and it cannot be accessed from any other Backinzo ID.


Roles
Now you can define the Roles under the Settings > Settings and Plugins Installation > Multi-Leg Security. If the Roles are defined, then the user has to choose the role after login into the system.

There are 3 different roles that can be defined.

1. User: User can only Manage the MultiLeg Grid, it can not Edit, Delete, Create or Export any Portfolio.

2. Editor: Editor can Create, Edit, Delete and Manage the portfolios, however he cannot Export the Portfolios.

3. Admin: Admin has no limitations subject to the security of any individual Portfolio.

After the First Implementation, Only Admin roles will be allowed to change these settings. Changes in These settings will be applied after the Restart of Application.

If you’re required to login the role in the running application, then you can use Options Trading > Change Logged-In Role


Security Tab in Portfolio
Now there is an additional Tab ‘Security’ while creating the portfolio. Here you can set the password for the Edit and Export actions. This can be used to secure a particular portfolio. Editor and Admin roles can set / change these passwords.

If passwords are set, then the application will ask you the required password before taking the Edit / Export action on that particular portfolio.


Export of Portfolio(s)
Now you can secure the Export of the Portfolio(s) with more security settings. For this you need to tick the option ‘Secure Export’ while exporting the Portfolio. This will show you another window where you can set below described securities.

1. Platforms: Which platforms are allowed to import these exported ports.

2. User Ids: Comma Separated List of User IDs of the Platforms for which you are allowing these portfolios to be imported. If left blank, then any user can import these portfolio(s).

If specified, then these ports can only be imported in the mentioned user ids only.

3. Edit Password: If specified, then the importer needs this password before editing the portfolio. Once set, the importer cannot change these passwords even if he gets the edit access.

4. Export Password: If specified, then the importer needs this password before further exporting of the portfolio. Once set, the importer cannot change these passwords even if he gets the edit access.


Update version you can see at the left bottom of Login Screen.