Programmatic OCA orders
Author: Musashi1970
Creation Date: 12/18/2014 12:57 AM
profile picture

Musashi1970

#1
Hi

Is it possible to attach a OCA order group no. to an order in WealthScript ?

Thx
profile picture

Eugene

#2
Hi Patrick,

It's not possible because OCA Groups exist only in the WealthSignals Publisher. (No connection to WealthScript). However, let me research into your idea and get back to you.
profile picture

Eugene

#3
Off the top of my head, it might look like this:

1. Introduce a new preference in WSP Setup dialog:

[v] Create OCA pairs automatically
OCA signal name: [____________]

2. If it's enabled and the signal name is not empty, the WSP will automatically mark new Alerts that contain (or are equal, I haven't decided) OCA signal name as OCA orders.

Looks reasonable? Let me know if it does and I'll add it to our product backlog. Your ideas are welcome.
profile picture

Musashi1970

#4
Hello Eugene

As always thx for the quick response.

Your idea sounds very promising. So I could easily implement an OCA in WS by naming the Signal according to the parameter in the WSP preference dialog.
Just to make sure. I use a combination strategy. and each of these individual strategies could produce OCA oders. So I have OCA:1 orders, OCA:2 and so on.
Would your method be able to differentiate between the orders belonging to different strategies and therefore generate different OCA signals (the OCA group name could be e.g. the strategy name)... Then I am not sure if you have restrictions regarding the length of an OCA group name...

profile picture

Eugene

#5
Glad you asked. Sorry to disappoint you but proposed method won't be able to differentiate between the orders coming from different strategies. Adding such feature presumes that it's simple, universal, intuitive and does not rely on guesswork. Handling delimiters and numbers would be an impossible single-user solution.

On a related note, since the OCA preference could not be made strategy specific (to avoid complicating things) it would have to be a global preference. This means that any and all your WS strategies would have to follow the same naming convention i.e. signal name equal (not "contains", "is like" etc) to the specified string for the feature to work.

If you're still interested, I'll enter it in our backlog for a future review.
profile picture

LenMoz

#6
QUOTE:
but proposed method won't be able to differentiate between the orders coming from different strategies.

Why not make this...
OCA signal name: [____________]
rather...
OCA signal prefix: [____________]

The author could specify the prefix. The prefix signals that a signal is part of OCA series, and each underlying strategy provides its unique suffix. The characters after the prefix would be used to group the orders by (sub-)strategy.
profile picture

Eugene

#7
Sounds good. Thanks LenMoz.
profile picture

Musashi1970

#8
Same here.

Sounds very good. Thanks for the suggestion (LenMonz) and consideration and possible implementation (Eugene).
profile picture

Eugene

#9
Feature request has been entered in our product backlog. I plan to implement it (among other potential enhancements) next year.
profile picture

Eugene

#10
Turning down this feature request due to no user interest and (most importantly) potential conflict with the new additions to the WSP such as "Flatten Alerts".