Hi All,

I understand that invokeAction operation is to support any custom or proprietary function/action to be supported Haystack server.

Queries:

1. If the application does not need any custom operation support, then invokeAction operation need not be supported. An error can be returned saying "not supported". Is this understanding correct ?
2. Are there any examples of user-defined operations which can be used by Haystack client and should be defined by Haystack server ?

Thanks.

If you don't have any actions, then I would suggest just not support that operation.

Typical actions are things related to commanding points such as a manual setpoint or manual auto. But really they could be anything a user might want to do.

Thanks Brian.

I didn't understand following part of your comment:

---

things related to commanding points such as a manual setpoint or manual auto

---

Can you please elaborate? Thank you

things related to commanding points such as a manual setpoint or manual auto

For example in Niagara, there are typically a set of "actions" available when you right click an object in its context menu:

• Manually Set a writable object
• Manual Auto a writable object
• Clear a history object
• Reset a totalizer object
• etc

In SkySpark we allow you to perform point writes that way such as "turn this on for 1hr"

Thanks Brian !