*** FEATURE UPDATE ***

LIMIT / SL-LIMIT ENTRY ORDERS

Positions can now be entered with Limit and/or SL-Limit orders
This option can be selected from under Advanced Settings on the algo configuration page under ‘Entry order type’.

RELEASE NOTES:

Settings:
1. Trigger & Limit price buffer in: Configure the buffer price between Limit price and Trigger price in points or percentage
2. Trigger & Limit price buffer value:
- Set buffer value between trigger price and limit price.
- In the case of normal entry orders without Wait & Trade, and in the case of Wait & Trade with Immediate settings, the buffer value is added or subtracted to or from the LTP to define the limit price for entry. In the case of a Buy entry order, buffer value is added to LTP and Limit order is placed (LTP + buffer value = limit price). In case of a Sell entry order, buffer value is subtracted from the LTP and limit order is placed (LTP - buffer value = limit price)
3. Entry with Market order if order Open for (N) secs: If the limit order doesn’t get executed within N seconds of being placed, a Market order is shot to execute the entry orders


In what case will Limit orders be placed, and in what case SL-Limit orders be placed for entries?

- Buy entry order with ⬆️ W&T settings, SL-Limit order will be placed
- Buy entry order with ⬇️ W&T settings, Limit order will be placed
- Sell entry order with ⬆️ W&T settings, Limit order will be placed
- Sell entry order with ⬇️ W&T settings, SL-Limit order will be placed


In what cases is the buffer value used?
1. In the case of normal entry orders without Wait & Trade
2. In the case of W&T entries with ‘Immediate’ settings
3. For SL-Limit entries


Points to remember:
1. Make sure to use ‘Square off and terminate algo’ button if you choose to deactivate the algo where the positions have not entered already. If you use the ‘Terminate algo’ option, the entry orders placed in Limit or SL-Limit will not get cancelled, and will stay open.

2. For Wait & Trade Limit orders, buffer will not be used. The limit price will be entry price calculated from the reference price itself.

3. Once the algo goes into ‘Trade Active’ status, the entry order type settings ie. buffer value in, buffer value and ’N’ seconds setting cannot be modified.

4. In the case where the calculated entry price from the reference prices gives a negative value, an order will not be placed. Any previous pending Limit/Sl-Limit order will stay as it is. In such a case, the status of the order will show Pending in red color on the algo dashboard (refer to the sample screenshot shared in the mailer emailed to you). Incase you get this error, you should change to W&T settings where the limit price can be a positive number.

5. If you modify the W&T settings from a value to Immediate, the entry order will get modified from Limit/SL-Limit order to a Limit order where the limit price would be LTP+/- buffer value (as explained above).

6. It is not advisable to keep W&T settings with small values like 0, 1, 2 etc. If the LTP goes below or above the trigger price in the case of Sell and Buy respectively, then the order will get rejected, because in the case of Sell SL Limit order the trigger price has to be lower than LTP and in the case of Buy SL Limit order the trigger price has to be higher than the LTP (refer to the sample screenshot shared in the mailer emailed to you).

7. If 'Trade only first entry' is selected, and in the case where the price has moved too fast, it is possible that more than 1 leg gets executed because of very quick price movement before the 2nd leg order can get cancelled. If the order gets executed, then it will have to be squared off manually. Such a scenario can occur when CE has ⬆️ W&T setting and PE has ⬇️ W&T setting and the market has moved up very quickly, and vice versa

*ANNOUCEMENT*

All ZERODHA users need to enable TOTP to be able to broker login tomorrow.

There is no change with how the API works or Quantiply works with regards to TOTP. Only difference is that you will be using a TOTP instead of the 6 digit PIN that you normally use during the login process on Zerodha

*** UPDATE ***

Modify subscription plan (ie. add or subtract algos to the daily algo limit) without Subscription date getting revised

When you 'Edit' subscription plan to add or subtract algos to the daily algo limit, the subscription date will not change. This means that the additional credits will not be charged as subscription start date doesn't get revised to the day the plan was modified. The subscription period will stay the same, and credits will get debited if algo limit increased, and credits will get deposited back if algo limit is reduced.

Note: There is no major change in Subscriptions and the way it works, this update just simplifies credit calculation while adding or subtracting additional algos to the currently subscribed plan

** ANNOUCEMENT **

All ZERODHA users who had trades rejected today inspite of setting up TOTP, need to make sure you are logged out from the Zerodha terminal or any other Zerodha universe platform from all browsers and devices, tonight, without fail.

If you fail to logout, then today's session will still be active tomorrow morning when you attempt to broker login. This old session is the session which was logged in using the PIN and not the TOTP, hence it will give order rejections.

So just log out, don't stay logged in, so broker login can be done correctly tomorrow morning, and a new session can be started and a fresh token can be generated for tomorrow. This is just a one time thing for today

** ANNOUCEMENT **

New plans launched

1. SEMI PRO - 3 algos/day @ 1250 credits/month

2. DISCOUNTED PRO* - 12 algos/day @ 1600 credits/month

*Discounted Pro plans are available only for trading accounts opened using our account opening links. All existing Discounted Pro subscriptions will run as it is and does not require any switch in plan

*** FEATURE UPDATE ***

MTM / COMBINED PREMIUM EXITS in MULTIPLE LEGS with LIMIT ORDERS

Now exits can happen with Limit orders in multiple legs, instead of just Market orders for the following 3 cases:
1. When combined premium (MTM) Target or Stoploss is hit
2. For exits when 'Square off all positions & Terminate algo' button is used to exit all open positions
3. When algo squares off open positions at the end time

This update will not require any settings to be changed from your side. It will use the LTP +/- buffer value to determine a limit price, the same way it does for L/SL-L entry orders

Announcement for IIFL users

All those using the XTS Blaze mobile app, please uninstall the previous app and install the new updated app

Android App
https://drive.google.com/file/d/1iJ-gDwPFvF5rld1VedpXFJ5Tkpfs9Gmp/view?usp=sharing

iOS App
https://testflight.apple.com/join/VOssI4bd

*** FEATURE UPDATE ***

PREMIUM BASED ENTRIES

You can now enter positions in strikes with premiums close to a specified premium value. This feature scans the entire Option Chain to select an appropriate strikes as per the specified premium value

RELEASE NOTES:

Settings:

I. Specify premium value:
1. Premium close to: A strike with premium closest to the specified value will be selected. The premium selected can be more or less than the specified value but will be the closest to the specified value

2. Premium higher than: A strike with premium higher than but closest to the specified value will be selected

3. Premium lower than: A strike with premium lower than but closest to the specified value will be selected

II. Specify strike selection:
1. None (default setting): With this option there is no restriction in terms of which strike is selected in the option chain, the algo will scan the premiums of all available strikes and select the strike as per the premium value specified

2. 500/100 multiple strikes: The specified premium will be checked only for the strikes that occur in the multiples of 500 for Banknifty (eg. 39000, 39500 and so on), & 100 for Nifty (eg. 13000, 13100 and so on). The 500 multiple strikes for Banknifty and 100 multiple strikes for Nifty hold good OI and are more liquid compared to other nearby strikes, hence, are a better option when taking positions in far OTM or ITM strikes.


Important points & recommendations:

1. When buying or selling far away OTM or ITM strikes, use the option to select strikes which occur in multiples of 500 (in Banknifty) and 100 (in Nifty) as some far away strikes may have 0 or very less Open Interest or no price at all.

2. VERY IMPORTANT: When trading far away OTM strikes, with Entry order type SL Limit selected, it is best to keep a buffer value in percentage rather than points, so as to avoid placing stoploss limit orders with limit prices that cross the circuit price for that symbol. For example: for a strike being entered where the premium is 5 and the SL Limit buffer value is 5 points, there are high chances that the order gets rejected as the limit price of 10 may be outside the circuit limit for a strike that has a premium of 5
feature-premium-based-entry-screenshot-2

3. Wait & Trade with premium based entries: The strike will get selected as per the specified premium value and the current price as reference price, and the trade will get executed as per wait & trade settings.

4. For deep OTM and ITM strikes, price updates can be slow sometimes, in such a case, the algo will take positions only when the latest tick arrives after the start time, this can take an additional few seconds. Only once all legs have a price update will the algo shoot the order in all legs together. The algo will not take positions in a few legs partially, it will wait for all strikes to have a price update after the start time.

5. For very low deep OTM premium values, make sure to use premium higher than or premium close to settings, and NOT premium lower than. There can be strikes which may not have the premium that you may have specified with the setting premium lower than, and the algo won’t be able to take positions if it can’t find the premium that you have specified. Keeping the settings premium higher than or premium close to will allow the algo to take positions in the deepest OTM or ITM strike closest to the specified premium value.

ANNOUNCEMENT:
1. An edge case has been addressed for algos running premium lower than setting for deep OTMs. If you are using such a setting, disable and re-enable the algo
1. Points 4 & 5 added under Important points & recommendations in the Premium based entries release notes.

Thank you all for voting for the next feature. Work on the Positional feature has begun.

Upon scoping and planning the implementation of the Positional feature, we’re seeing that it requires multiple fundamental changes to the current system and additional supporting modules, hence, has a slightly longer timeline. So for this reason we’ve decided to implement the algo wise MTM and square off & terminate buttons in parallel while the work on the Positional feature continues. The algo wise mtm and buttons on the homepage will be released sometime after the Diwali break

Wishing the entire Quantiply family
🪔 🪔 🪔
𝗛𝗔𝗣𝗣𝗬 𝗗𝗜𝗪𝗔𝗟𝗜
&
𝗛𝗔𝗣𝗣𝗬 𝗡𝗘𝗪 𝗬𝗘𝗔𝗥
🪔 🪔 🪔

FEATURE ANNOUCEMENT

Live MTM data & other functionality on the main page (Phase 1 features)

Release notes:

(As pointed out in the attached screenshot):
1. Live MTM data: View live MTM data for each individual algo, under the MTM column

2. Error alert: Warning icons under the Alerts column will indicate any error or rejections that may have occurred in an individual algo

3. Square off+Terminate algo and Terminate algo buttons added under the Actions column for quick exits or termination of the algo from the main page itself

4. Search bar: You can now filter or search algos by algo name, client id, broker name or algo status

5. Re-size column width: Increase or decrease the column width size to optimise your data visibility

6. Change column order: Drag and drop the column to change the order of the columns. For example, place the MTM column right in front of the table, followed by the Name column if you are using Quantiply on mobile

**ANNOUCEMENT**

ALGO RESET

Monday onwards, if an algo goes into an error state due to an order rejection or API errors, then get in touch with @abhishah33 to reset your algo so it can be re-used

**** UPDATE ****

Trailing Stoploss logic update

Quantiply will now consider the high and low made by the traded symbol within the trailing frequency interval time frame, instead of checking if the trailing stoploss condition is fulfilled at the closing price or end of the trailing frequency interval time frame.

For example:
If suppose the settings for the Trailing frequency interval is set to 30 seconds, then the algo will now consider the high price and low price made my the symbol/traded instrument instead of directly checking if the trailing condition is being fulfilled at the end of the 30 seconds, with the closing price.

This update will enable faster and more precise trailing of the stoploss.
This change in logic has been published and will be effective immediately

**ANNOUCEMENT FOR IIFL USERS**

IIFL users can now directly credit (pay in) or debit (pay out) funds from TTBLAZE WEB & MOBILE APP (XTS API system) from the Backoffice tab. No need to transfer funds to IIFL's in house TTWEB terminal

***UPDATE***

Entry & Exit time

You will now be able to see an entry and exit time under the average entry and exit price respectively

NOTE: This timing is the timestamp when the order update with average entry price and exit price is received from the broker. It's not the same as the exact execution time. Both timings are the same 99% of the times. This time will be changed to execution time in one of the future updates

When a broker's API is down, and new orders are not getting executed..

- Previously placed SL Limit or Limit orders, will get executed normally, as these orders are already in the exchange's system. But since the API is down, your Quantiply dashboard will not be able to show order updates ie. average exit price & time of the executed order, at that time

- Trailing of SLs will not work, SL limit/limit orders will not get modified with the new SL, once the API is back online, the already placed SL orders will get trailed to the latest SL directly.

- Individual leg target and MTM based SL or Target orders which the algo fires at the time, will throw errors and have to be monitored and managed manually from the broker's terminal. Once the API is back online, the algo will immediately fire orders if the trade has crossed the MTM Target or MTM Stoploss.

- If the trade has been managed manually or exited completely while the API was down, then you need to Terminate the algo as well. This is because when the API is back online, and any Target or SL conditions get fulfilled, the algo will try to exit orders. To avoid any unwanted orders being fired the algo should be Terminated if all the positions have been exited earlier

⚠️ IIFL USERS can update to the latest mobile app versions:

iOS: https://testflight.apple.com/join/VOssI4bd

Android: download attached .apk file