Forum Replies Created
-
# 11 months agoin reply to: Translation of Screen properties# 1 year ago::
Hi Kahn,
here it is:
try {
var resultConnector = Simplifier.Connector.DataLoad.saveT002FromSAP({
CustID: input.CustID,
SystemID: input.SystemID,
params: dataset
});
Simplifier.Log.debug(“resultConnector”, resultConnector);
insertedID = resultConnector.generatedID;} catch (e) {
//error is catched but ‘e’ is <undefined>
Simplifier.Log.debug(“error in connector call”, e);
message_text = e.message;
message_name = e.name;
}The result of the connector:
{
“message”: “Duplicate entry ‘1-3-D’ for key ‘PRIMARY'”,
“success”: false
}Best regards
Klaus
in reply to: try-catch doesn’t work with connector callin reply to: How to call an email template in generic matter# 1 year agoin reply to: How to call an email template in generic matter# 1 year ago::Hi Jennifer,
yes I know.
No header property of any widget is flagged as translatable. That means I have to flag all myself.
If I do that: could you please confirm that this won’t be overwritten with a version update of Simplifier?
Why aren’t those properties like ‘header’ are translatable flagged supplied by Simplifier?
Best regards
Klaus
in reply to: Translation header property of Generic_Tile# 1 year agoin reply to: Translation header property of Generic_Tile# 1 year ago# 1 year ago::Hi Ksenia,
you can do that mapping directly in process designer when calling your connector “CWTool->getLand” assuming that your output parameter in the getLand call of your connector has a variable of type json object (structure) or a simple string type.
If you have an input field on your screen I assume that you’re expecting not several values (no array) as output from your connector.
If not use a table instead of the input field. Then you can map the array of the connector result to the items (e.g. columnlistItems) of the table.
Best regards
Klaus
in reply to: Output for SQL connector call# 1 year agoin reply to: Feature Ideas# 1 year ago::Hi Mathieu,
several months ago when this topic was created I managed it without a dynamic sql but now I have chance to do it without one.
I don’r really understand what you’re thinking of when you say “if you want to create a complete dynamic select you can fill the request parameter with a business object and create the select there”.
I can’t imagine how to execute a complete sql statement imported as string or to take a dynamic sql where-clause as string and execute it.
Could you provide me an example, please?
Best regards
Klaus
in reply to: sql connector: dynamic table and column# 1 year ago::Hi Christian,
I suppose I know the registration of the plugin.
JSON config file inside the docker container registrates the plugin at 127.0.0.1:8085. Correct?
Unfortunately this does not work. See the dump.
events.js:292
throw er; // Unhandled ‘error’ event
^Error: connect ECONNREFUSED 127.0.0.1:8085
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16)
Emitted ‘error’ event on ClientRequest instance at:
at Socket.socketErrorListener (_http_client.js:426:9)
at Socket.emit (events.js:315:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
errno: ‘ECONNREFUSED’,
code: ‘ECONNREFUSED’,
syscall: ‘connect’,
address: ‘127.0.0.1’,
port: 8085
}Best regards
Klaus
in reply to: ldap connector# 1 year agoin reply to: ldap connector# 1 year agoin reply to: sql statements in sql connectors# 1 year ago::Hello Christian,
yeah, that’s true but I do not mean that.
I’ve about 15 sql connectors and maybe more than 100 connector calls.
I need an overview which attributes are used in a result or in where-clause in which connector call in which connector because unfortunately I’ve to split connectors for secure reasons (e.g. for attribute encryption).
Therefore I’ve to analyze all connector calls…
Best regards
Klaus
in reply to: sql statements in sql connectors# 1 year ago::Hi Christian,
ok. Thanks for the information.
I’ve found only that doku for your plugin development:
https://community.simplifier.io/doc/current-release/plugins/plugin-development/
But that does not really to get the big picture how accessing a plugin, which interfaces it has to be implemented, etc.
Is there an other source for developing a plugin (for a developer) and not only on a high level?
Best regards
Klaus
in reply to: ldap connector