For those who are following ComfortClient developments, I have now started work on the next version; this will be known as version 4.
One of the key features will be an extensible \"Connector\" model. Connectors will be \"typed\" i.e.; Email, Database, Application, SMS etc. Each of these types is a dedicated Connector DLL. So over time more can be added (in the same way as Plugins) to extend functionality.
Connectors will be setup centrally via a new \"Connection Manager\" (See taster screenshot) application by adding one or more connection entries to each type node. You will also where appropriate be able to test the connector (ie for an email connector send a test message).
Once setup these connectors can be used on floorplan objects and trigger via conditions. So for example if a value of a counter goes beyond a certain threshold (defined by condition)you could send an email and also log to a database table purely by adding both connectors and setting their \"payload\" content in Object Properties. The \"payload\" will hopefully also support object placeholders too so for say a SQL connection the payload could be something like (you obviously are SQL experts hey if you want to use SQL!):
\"...
insert into CC_log_table (cc_date, cc_id, cc_value) values (getdate(), {ObjectID:Value}, KitchenDoor:Value})
...\"
Or for emails and SMS you can use in the body of the message. The \"payloads\" attributes for the email connector would include email title, body text, priority, to, CC etc.
You hopefully get the idea. The intention is to connect events with external applications and pass the necessary data over.
enough of that thought for now...
Also in v4 I intend to add license keys and there will be online/offline activation. All that will be needed to request as many licence keys as you want will be a user/registrant name and email address. So integrators can request keys for their customers centrally too or the customers can request for them etc. A key will be locked to a machine.
Regards
Julian
One of the key features will be an extensible \"Connector\" model. Connectors will be \"typed\" i.e.; Email, Database, Application, SMS etc. Each of these types is a dedicated Connector DLL. So over time more can be added (in the same way as Plugins) to extend functionality.
Connectors will be setup centrally via a new \"Connection Manager\" (See taster screenshot) application by adding one or more connection entries to each type node. You will also where appropriate be able to test the connector (ie for an email connector send a test message).
Once setup these connectors can be used on floorplan objects and trigger via conditions. So for example if a value of a counter goes beyond a certain threshold (defined by condition)you could send an email and also log to a database table purely by adding both connectors and setting their \"payload\" content in Object Properties. The \"payload\" will hopefully also support object placeholders too so for say a SQL connection the payload could be something like (you obviously are SQL experts hey if you want to use SQL!):
\"...
insert into CC_log_table (cc_date, cc_id, cc_value) values (getdate(), {ObjectID:Value}, KitchenDoor:Value})
...\"
Or for emails and SMS you can use in the body of the message. The \"payloads\" attributes for the email connector would include email title, body text, priority, to, CC etc.
You hopefully get the idea. The intention is to connect events with external applications and pass the necessary data over.
enough of that thought for now...

Also in v4 I intend to add license keys and there will be online/offline activation. All that will be needed to request as many licence keys as you want will be a user/registrant name and email address. So integrators can request keys for their customers centrally too or the customers can request for them etc. A key will be locked to a machine.
Regards
Julian


