This is based on a partner question related to the openAI Extension.

Based on my testings a few things should be changed:

1. the default value for prompt should be {{input.text}} , the current value is wrong and utterly confusing, the model already has the information
2. based on the openAI documentation and my testing the following default settings should be changed to the following values:

• temperature: 1
• max_tokens: 100
• top_p: 0.1

In terms of postprocessing the following code provides good results in extracting the first proper paragraph:
input.openai.match(/\w.*[!"#$%&'()*+,\-.\/:;<=>?@[\]^_{|}~]/m)`
this should probably be part of the readme

Describe the bug
Google maps extension is not working on webchat (Show google map)

We should include our new Extension features such as Tokens, Localization, etc. in our examples

Hello,

I been working on a solution to be able to add a Note to any salesforce entity. I built the code to add the new node. It has worked perfectly. Can you please add this feature to the SalesForce-crm Extension.

The new Node is "Add Note" makes it easier for users to just add a note to salesforce without having to build the JSON structure. The node has all the fields required to add a note to any entity.

Please email me and I can send over the files.

Johnny Balji
Senior Sales Engineer- North America

Mobile: 201-403-3004
Email: [email protected]
Cognigy Inc.

Currently the following issues exist:

• Create Entity and update entitiy Nodes only support very few types, we need to make this universal
• The Query Nodes need to be checked that you can enter dynamic input

The Append Values node is calling update instead of append.

While we have our auto translation feature, some use cases would require to translate text that is not directly related to the Flow output, but for API requests to third party systems.
Our current status of the Azure Extension does not include a Translation API Node, even though we support the API through our Auto Translation feature.

Please add a "Translate" Node to the Extension

Add the old Get Releases Node:
https://github.com/Cognigy/Extensions/blob/aeea73ded56884b803c05b61e11015d78d1d5feb/extensions/uipath/src/nodes/getReleases.ts

Related extension module

elastic-search

Short description:

Present one result item with additional details

Configuration options:

• List of attributes to present
• (?) List design (layout: how to arrange the selected item attributes based on defined "list" design)

Support for nested list elements required.

Flow dependencies:

1. Requires Elastic-Search Node
2. Probably, requires Result List Node

Additional context:

Reason for expected dependency to Result List Node is, that I expect we have to present a list first before we can select a single item.
Exception might be that we present only one certain item (e. g. the number one hit)

Is your feature request related to a problem? Please describe.

There is no authentication function provided at the moment.

Related extension module

elastic-search

Short description:

Present one result item in gallery view - means (at least) take a certain gallery layout and show the DocIcon

Flow dependencies:

1. Requires Elastic-Search Node
2. Probably, requires Result List

Support for nested list elements required.

Additional context

Related to available node types:
Similar to Say Node Output Type Gallery (?)

Reason for expected dependency to Result List Node is, that I expect we have to present a list first before we can select a single item.
Exception might be that we present only one certain item (e. g. the number one hit)

I'm trying to use the Google Sheets extension and running into some issues and questions.

• The connection field looks like it has to be in quotes, otherwise the log shows an error
• There doesn't appear to be an error reporting on invalid API key or invalid spreadsheet ID. I suspect this could be why it's not working for me.
• What's the format of the values field? Example?

Describe the bug

If I create a Jira ticket via HTTP request form cognigy with this payload:

{
    "fields": {
       "project":
       {
          "id": "10016"
       },
       "summary": "{{ context.issue_tittle }}",
       "description": "{{ context.issue_description }}",
       "issuetype": {
          "id": "10015"
       }
   }
}

works fine, however if i do via the congigy extension i get this error:

  "jira": {
    "post": "{\"statusCode\":400,\"body\":{\"errorMessages\":[],\"errors\":{\"project\":\"Specify a valid project ID or key\"}} {... omited ...}
 }

To Reproduce

Create a ticket from Jira extension in cognigy.

Expected behavior

Ticket should be created.

Is your feature request related to a problem? Please describe.
Our current documentation of the Zendesk Extension is lacking where to get the necessary input values from Zendesk, especially the client ID and secret.

Describe the solution you'd like
Extend the documentation to include the necessary steps, either here in Github or as an article in our helpcenter, which would be linked from the Extension readme.

The jsforce npm packge the old Custom Module was using is not working as expected in this Extension.

It always returnes this error:

{
  "salesforce": {
    "entity": "\n\n\n\n\n\n<html>\n<head>\n<meta http-equiv=\"Content-Type\" content=\"text/html;charset=utf-8\"/>\n<title>Error 405 Only POST allowed</title>\n</head>\n<body><h2>HTTP ERROR 405</h2>\n<p>Problem accessing /services/Soap/u/42.0. Reason:\n<pre>    Only POST allowed</pre></p><hr /><br/>\n\n\n\n\n<!-- Body events -->\n<script type=\"text/javascript\">function bodyOnLoad(){if(window.PreferenceBits){window.PreferenceBits.prototype.csrfToken=\"null\";};}function bodyOnBeforeUnload(){}function bodyOnFocus(){}function bodyOnUnload(){}</script>\n\t\t\t\n</body>\n</html>\n\n\n<!--\n...................................................................................................\n...................................................................................................\n...................................................................................................\n...................................................................................................\n-->"
  }
}

It says that the POST request is not allowed.

https://github.com/microsoftgraph/msgraph-sdk-javascript/blob/HEAD/docs/QueryParameters.md

When using the MS Power Automate extension I experienced some issues:

1. I can only use JSON as body. It's also a valid use case to just send text (e.g. like in the HTTP node).
2. When using JSON, I couldn't figure out how to use dynamic data (e.g. {{context.myStoredValue}}. I can add it like usual, but it is not going to be processed and replaced with the actual data.

Greetz,

Sascha

FYI: @alexteusz

Related extension module

elastic-search

Short description:

Present X result items from the result list

Configuration options:

• Number of items do display
• Item attribute to use for item presentation (configuration mandatory)
• Item attribute to use to set item link (configuration optional)

Support for nested list elements required,

Flow dependencies:

1. Requires Elastic-Search Node
2. Can be used as subsequent component to Transform Result List Items - But can also use the raw result list

Additional context

Related to available node types:
Similar to Say Node but

• can display a list of items
• can set links to source item

Additional Usage criteria:
From my point of view: title and link attributes has to be filled. For link attribute it's true if an link source attribute was configured.
Items that don't come with these two attributes should be skipped
Means:

• that the next list item has to be selected
• the result list has to provide elements 1 to X+n (n number of skipped items)

Related extension module

elastic-search

Short description:

Transform items coming from the original result/hit list into standardized result format

Expected Configuration options

Set of essentially required item attributes

• Title attribute
• Summary attribute
• Modified Date attribute
• Link attribute
• DocIcon attribute
  Plus option to define additional attribute mappings

The result list format can be (a bit) complex - means required input attributes can be integrated as nested elements.
So, it's required to select nested elements from the result list.

Flow dependencies:

1. Requires Elastic-Search Node in a previous step to trigger the search request